I know that the 'FSX is lousy at handling timezones' topic has kinda been done to death, but this is an oddity I'm hoping someone might be able to shed some light on.I hadn't really paid much attention to what FSX was doing with time over the last few weeks since we in the UK switched from BST back to GMT for the winter, but yesterday I noticed while Installing and trying to get MyTrafficX running, that my FSX is still setting UK time to be UTC+1., although pressing reset sets the UTC time to UTC-1 and thus the 'Local Time' is 'correct'.None of the normal tricks worked (deleting/recreating default flights, installing FS RealTime demo (already had it installed), or installing Mr Thompson's TZ30 scenery). But it's become a little bit of a white whale for me now.Now, getting to the weird part... In my experiments to find out why the UTC Bias value is wrong, I tried turning off and on various pieces of add-on scenery that I have installed, to no avail, but while doing this, I tried from a variety of UK airports, and found something REALLY bizarre.Even with all of my non-standard scenery disabled, EGSS (Stansted) has the correct UTC bias, as does EGUL (Lakenheath AB), EGSC (Cambridge), and I suspect others in a narrow strip down the center of the UK, but none of the others I frequently fly in/out of have the correct bias, they're all still UTC+1 (EGNM, EGLL, EGHI, EGKK).Does anyone have any insights on why this group of airports seems to have a different UTC bias to the rest of the UK, and even better if anyone can tell me how to get my FSX to use the time properly (not that I expect there is any way :(

Don't know but bglcomp in the sdk allows you to set the timezone and DST so I guess you could experiment and see.scott s..

Dunno what caused it, but restoring the original ...Scenery folder from my backup fixed it all up, all UK airports working at GMT/UTC now. I can go back to being 100% focused on my hatred for API.dll crashes...