I've received two bugreports in the forum for which I would like to ask some advice here:
1) The ultra terrain shader makes runway designation signs go away: http://www.flightgear.org/forums/viewtopic.php?f=47&t=18999 It would appear that all the sign boards in airports are driven to grey when the highest level terrain shading is used. I have now identified the reason, which is that these signs are actually handled by the terrain shader. The terrain shader subsequently detects a vertical surface and concludes correctly that terrain with such a steep surface can't be anything but rock, so they the signs get the rock texture overlay. Now, one fix of the problem would be to declare the rock overlay texture void for all of the signs, so they would never get an overlay, but I feel that the root cause of the problem is that sign boards should not be handled by the terrain shader in the first place, they should go to a model shader instead, in which the whole problem would not arise in the first place because it wouldn't try to run all the terrain heuristics. Is there any compelling reason these signs are handled by terrain shaders? Would it be a problem using model-default.eff for the signs rather than terrain-default.eff? 2) Flickering in water http://www.flightgear.org/forums/viewtopic.php?f=68&t=18924&start=15#p176001 With the sun in the back, under some conditions a strange flickering in the water can be observed. Dialling down the amount of direct light, I could verify that these are light reflections, they go away when no direct light is available, although they appear unnaturally large and blocky. What bothers me is: * I have never before observed this flickering, I did hundreds of test flights under all possible conditions, I've looked at water from altitude ranges of zero to suborbital, I have logged several hours of flights over open water since I last changed the shader. Under Windows I have a 1 1/2 months old binary in which I am 99% sure the problem does not occur there, although it occurs on recent GIT. * I have not changed the shader code or effect code for more than 3 months So this would indicate that the problem was caused by some other developement and slipped in. Does anyone have an idea as to what this could have been? Were there any changes to the water shader files / normal maps/ textures in the default rendering scheme (the Atmospheric Light Scattering version uses the same files)? Or to the effect files? Could the ATI hack have done something weird? Any ideas welcome, I have no good plan of attack for this yet. Thanks, * Thorsten ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
