My map displays only in yellow tones (menus look fine) on my Surface Pro 3 with Release 120.0.1 running Windows 8.1. I tried using both versions of the Windows executable with the same result. I have attached a small screen capture. Any ideas on how to fix?
Strange. I can't think of anything that should affect the map and the GUI differently that is also OS/machine dependent, but doesn't care about SDL versus GDI.
This started also with the previous stable version in December. Maybe Microsoft did something with Windows update?
I'm using Windows 8.1 and it's working nicely.
Delete the "settings.xml" and defualt.sve files in your own documentas/simutrans folder. THis should reset the broken brightness definition of your game.
It would be nice to head if it worked or not.
If so, there is the question how brightness became broken.
QuoteIf so, there is the question how brightness became broken.
Maybe an old version was run at some stage? Or a Nightly with an error that was fixed?
Perhaps some form of validation would be better in this case. If brightness is out of range (or at least not reasonable) it should assume some default value.
Quote from: DrSuperGood on February 04, 2015, 01:01:21 AM
Maybe an old version was run at some stage? Or a Nightly with an error that was fixed?
Running older versions tend to reset all settings to default. mleeoh seems to have been using stable versions when the problem occured.
QuoteRunning older versions tend to reset all settings to default. mleeoh seems to have been using stable versions when the problem occured.
I thought settings were only reset if an old version tried to load more recent settings? Nothing should stop a recent version from loading old settings.
No, but nobody else has problems reported problems loading old settings.
Sorry for the late reply: Deleting the settings.xml and default.sve files solved the problem. Many thanks for the fix.
Just a thought. Would a system crash or a simutrans crash cause a bad brightness setting to get stuck? One of those events may have happened when this started to occur.
Quote from: mleeoh on February 05, 2015, 09:44:54 AM
Just a thought. Would a system crash or a simutrans crash cause a bad brightness setting to get stuck? One of those events may have happened when this started to occur.
Possibly. Or that what crashed the system is what corrupted the brightness, maybe even at different times. That would indicate something hardware related, like bad RAM, or even just a stray interstellar subatomic particle hitting your computer at just the right/wrong place.
It could have been also hitting the + or - key on a old installation of pak128 too many times. The setting is then saved upon exit.
How old is old? That's very possible. My Pak128 is from March 2014.