I cannot stand anymore depth sorting specialy after this:
... A #%!& depth sorting bug appear from nowhere!!!!!
selden wrote:Most of the problems I've been seeing happen at close distances. If the viewpoint is further away, things are rendered properly. Your problems may be different, though.
p.s. and don't forget that translucent surfaces are known to still have problems. I just go ahead and do the model as it "should" be and don't worry about them. They'll be fixed. Eventually.
)
chris wrote:It should be possible to make this work with the existing code. When two objects overlap, Celestia will draw the opaque one first followed by the translucent one. I think that the problem here is that Celestia has a hard time telling if an object is translucent if it has to look at the texture to do so, i.e. the opacity of the material is 1.0, but the texture has transparent parts. If you give me a link to an ASCII cmod for the fire, I might be able to tweak the material definition for you so that Celestia knows that it's translucent. Or, you may be able to do something in your modeler by assigning the reentry fire an opacity of 0.99 or something.
--Chris
