> > I have no idea too. It looks like an uninitialized value that get > > one when we click on the slider. Do you reproduce the problem I see ? > > For some (yet to be determined) reason the shader settings are not > archived on Flightgear exit in my local devel branch since my > next-to-last update three weeks ago. That could explain why I never > really saw the problem, because I start with landmass slider > initialized to 3 and always shift it to 4 by hand - so I always > touched it in my tests before the shader came on. I'll try later > today to set the shader quality via commandline and see what happens > then (I'm at the wrong computer to try at the moment...)
Maybe you already know that, but closing the window using the windows manager close decoration bypass setting saving here. The default value in preferences.xml is 1, so if you start at 3, either you changes preferences.xml locally, or you have your private settings loaded. Maybe they are now read-only. Regards, -Fred ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
