Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
There's not much to do:Code: [Select]yourObject.setBillboarding(Object3D.BILLBOARDING_ENABLED);
Based on that, it would have the same number of polys as it usually would.How do you figure? Just because you rotate a 2-poly Object3D so it always faces the camera, it still only has 2 polys. Use the appropriate texture, and Voila - you have your simulated volume.
I thought the whole point (the only point) of billboards was to improve rendering speed by displaying a static bitmap image of the object beyond a defined distance? Otherwise, what's the point?The point of billboards is to simulate a volume of some kind with only two polygons, vs the multiple polygons that would be required to do the same without billboarding. Billboards are useful for all sorts of things, including plants and trees, spheres, smoke, explosions, glowing effects, etc. I use them all the time myself.
A billboard IS an Object3D. It's just rotated in a way that it always faces towards the camera. So in your scenario, i don't think that this will do any good unless i got you wrong somehow.
If varying the colors is the only issue, just create a texture containing all 256 levels from black to white as small 2x2 quad and assign them to your polygons using a second texture layer with color modulation and u/v coordinates located in the middle of each 2x2 quad. That should allow you to use different shades per quad while still using one texture. I think it will still look tiled though
With quad, you mean a real quad consisting of two polygons? If yes, then this will be the absolute killer for performance...don't do this. Try to create chunks of geometry as large as possible to try to minimize state changes, i.e. use one set of textures on as many polygons as possible. If you want to use different colored textures for each quad for whatever reason, merge them into one larger texture instead.
As i've already said above, you can try to increase the near clipping plane, albeit this might not help much in the distance. And ensure that you are really getting a 24bit zbuffer at least...this should be visible in the log at initialization stage.
Apart from that, i don't see many options left. If the accuracy isn't high enough, it's simply not high enough. There's no magic switch to increase it.
Which graphics hardware are you using and how is your water plane build? Is it one large quad or more tessellated? If it's one large quad, i may help to tessellate it some more.
If you look at my terrain demo, you'll notice slight z-fighting too if you move further away. I've just adjusted the far clipping plane and the fog in a way, it's not that noticeable.
From what i'm seeing of your screen shots. It looks like the ground plane is near the same height as your water. Increase the elevation of the vertex points so the terrain is more terrain'y with hills, mounds and lake/river drops. Then see if there is the same graphical problems. As it is, it just looks like the ground is too close to the water which is causing the graphical problems.
No, setSortOffset() doesn't have an effect. Why isn't increasing the distance between ground and water surface an option?
The screen shots show z-fighting, i.e. the zbuffers accuracy isn't high enough to separate the ground and the water, because they are too close together. The reason why this increaes when moving the camera further away is, that on most hardware actually not z will be stored but a/z (with a being some scalar). That's pretty accurate close by but the inaccuracies increase if z increases, i.e. accuracy isn't linear in camera/clipping space.
You may try different things: a) Move the water away from the ground. b) Decrease the far clipping plane. c) set Config.glIgnoreNearPlane to false (the docs of this switch are reversed, i'll correct this) and increase the near clipping plane (this will move the scene close too the camera...so don't increase it too much, or you'll end up with a very distorted scene).
