Starting automatic scenery download/synchronization. Using built-in SVN support. Directory: '/Users/student/Library/Application Support/FlightGear/TerraSync'.
Warning Electronic System ... ok
loading scenario 'nimitz_demo'
Electrical System ... ok
AFDS System ... check
Brake System... OK
Warning: detected OpenGL error 'invalid operation' at after RenderBin::draw(..)
Warning: detected OpenGL error 'invalid operation' at after RenderBin::draw(..)
fmg wrote in Tue Feb 12, 2013 12:39 am:
2.6 DDS textures don't work on my mac. That is not so important, since you don't have to use them. Worse thing about it is, that allot of effects or shaders rely only on dds textures. I converted all I could find of them into .png. Some of them now seemed to work, but I never managed to see waves on the water.
IMHO it would be better to use files that work on all platforms for such stuff.
In general I got the impression, that tile get loaded quite late. If you fly at about 15000 ft altitude you can always see the border and for the real horizon 2-3 rows of tiles seemed to be missing (that was so in b375 before also).
2.5 Landmass Shader produces artefacts in it's strongest position.
Worse thing about it is, that allot of effects or shaders rely only on dds textures
2.7 Reducing or increasing haze with the z and Z key is no longer working (manual input choosen).
2.8 Couldn't type in the METAR field in the weather dialog. If you change wind in the Basic Troposphere Weather dialog the old METAR string remains. I would be good to have the basic values of the actual weather displayed some where.
2.9 With skydome scattering on and weather conditions with low visibility (e.g. CAT I) the red light pos_lamp_red_light_2st becomes quit invisible. That ins't so without skydome scattering.
Frame rate stays low: with skydome scattering 16/17 and 19/20 without. In FG 2.6-r319 it is 29/30fps.
i4dnf wrote in Tue Feb 12, 2013 1:11 am:
There should be no effect relying on .dds textures (unless, of course, you select the .dds materials scheme).
If you found such effects please list them here so we can fix them. (again, only if such effects appear when you select the regional/default materials scheme)
Z/z doesn't work with advanced weather on (aka. "Model overall weather conditions based on METAR" ) by design.
Thorsten wrote in Tue Feb 12, 2013 8:18 am:That's probably the LOD bare setting - which you can set to a higher value in the menu. The default value is fairly low.
Thorsten wrote in Tue Feb 12, 2013 8:18 am:We don't have a METAR string assembler - you get the base METAR string, if you don't like that you can specify override options, but once the override options are specified they don't go back and change the string (the idea being that if you set the wind to 20 kt by hand, you're likely to remember that the wind is now 20 kt).
Thorsten wrote in Tue Feb 12, 2013 8:18 am:I don't think lights get any special grace - if the visibility is 300 m, objects are gone in 300 m distance. Maybe lights get special treatment in the default scheme.
Thorsten wrote in Tue Feb 12, 2013 8:18 am:Try with comparable graphical goodies and comparable weather conditions - there are no changes between 2.6 and 2.8 which could account for that, but the default standard has gone up, so you can't compare default against default.
So the haze is more realistic with the default rendering scheme. But the red shine of the lamp is much lower though the visibility seems to be much better with atmospheric light scattering.
Thorsten wrote in Wed Feb 13, 2013 7:55 am:The evidence from the screenshots would suggest that there's a problem with the skydome shader on your machine.
So - do you get any errors related to the skydome shader?
Fair Weather after open the weather dialog and leavy it with OK without changing anything
Marginal VFR. This seemed way to bad to me. Visibilty should be much better then below according to the METAR string.
Here a example with live weather on. As you can see, sometimes the color off the sky is changing. So if there might be an error it seems that it's not always there or isn't always in the same manner.
Thorsten wrote in Thu Feb 14, 2013 2:19 pm:*g* You may have left the METAR string as is, but you switched the weather engine from Basic to Advanced Weather (you probably have 'Model overall conditions based on METAR checked...). Since Advanced Weather delivers a full set of control parameters to the shader rather than defaults, it also works a bit better for Light Scattering.
Thorsten wrote in Thu Feb 14, 2013 2:19 pm:You probably ended up inside the rain region. The particular tile sets up various rain systems in the tile, you get the nominal visibility as reported if you're outside but a reduced if you happen to be in rain. I believe that would happen under rain patches in reality as well - you could have a decent VFR flight around them, but not through them.
Thorsten wrote in Thu Feb 14, 2013 2:19 pm:These shots look all more or less plausible to me. So what was the problem before???
Now I know there is none.Thorsten wrote in Wed Feb 13, 2013 7:55 am:The evidence from the screenshots would suggest that there's a problem with the skydome shader on your machine
Hmm - made a short flight (ca. 4-7 nm). But didn't got much better. Found it rather dark for noon. Must be a huge rain region.
Now I know there is none.
Users browsing this forum: No registered users and 1 guest