Yetty

Everyone great news, this was fixed in v1.0.1 I am at Ho Chi Minh City at 8x speed. Thanks @richboy2307 I cannot believe you guys managed to fix this in less than a day!!

Hey, Its one of the SIM VARS, I got its name wrong, its called SIM_RATE_INCR and it increases the sim rate, then SIM_RATE_DECR does the opposite. There is keybinds for both of these in the keybind settings under INCREASE SIM RATE and DECREASE SIM RATE I think the default keybinding is ALT + R and then the Plus and Minus symbols.

If you need me to gather any further information I can, I can easily replicate this issue everytime, its really weird I agree!

Incase this is needed too: Route OFP (Attach PDF)VVTSWSSS_PDF_1740669904.pdf Sim Used (FS 20 or 24) Both OIS Navdata Setting (SIM DEFAULT or NAVIGRAPH) Navigraph Latest Variant (A350-900 or 1000) 1000 and 900 System Specs (CPU, GPU, RAM) Ryzen 9800x3D, RTX 5080 Sim Rate used (2x, 4x): 4x Any other 3rd Party utilities running with sim (FSRealistic/FSUIPC etc.): None All assistance is off. Live weather was off and flight model is Modern. Turbulence is Low setting to any other mode makes no difference

Hello Rich, Please see my thread here where I have done some really easy to replicate steps for this issue: The bug only occurs in the eastern hemisphere of the globe.

Please also see the relevant Discord Threads where users are reporting similar issues: https://discord.com/channels/535246634448191499/1344658554262523926 https://discord.com/channels/535246634448191499/1344624075061858314

Summary In the Inibuilds A350 on Microsoft Flight Simulator 2020 and 2024 if you attempt to fly in the Eastern Hemisphere of the globe the time compression will only go to 2x and not 4x this is regardless of framerate. I believe from my understanding there is some code in place to check if you are at the poles and if so it reduces the auto time compression, but I presume there is a bug in this code which is making the entire eastern hemisphere unable to move up to 4x time compression. An example below I am at Ho Chi Minh City in Vietnam which is rather central in Asia, I have set the auto time compression to 4x and switched on auto time compression, you can see its stuck at 2x This occurs despite a very respectable framerate of 255 FPS. This is easily able to be replicated anywhere in the Eastern Hemisphere of the globe a few places I have tested: East India Japan China Singapore Vietnam Australia Area of the map where simulation rate wont go above 2x If I go to London, Heathrow in the Western Hemisphere which is rather heavy on framerate and performance the sim has no issues with keeping it at 4x time compression. In-fact I can actually force it to 8x time compression with the SIMULATION_RATE_UP sim var Here we can see at London Heathrow the Simulation Rate is at 8x despite us having 107.5 FPS almost half. This concludes to me that performance is not the reason the Simulation Rate is being decreased by is something to do with the longitude calculations. For testing purposes I took the airplane to the northern pole to see if the simulation rate would be reduced to 2x as mentioned during the developer livestream, but even right at the highest point nearest the pole the simulation rate stays at 8x This gives me a very strong suspicion that the maths maybe incorrectly using the Latitude instead of Longitude to limit time compression? Steps to Reproduce Load up the A350 in any Eastern Hemisphere Airport (Singapore, Vietnam, Australia, Japan, China, Eastern India) Go to Options -> Simulation -> Max Compression -> Up to 4X Select Time Compression -> Auto Expected Behavior I expect the time compression to go up to 4x in the Eastern Hemisphere when FPS performance is good. Actual Behavior The simulation rate will not go above 2x anywhere in the Eastern Hemisphere. Environment A350 Version: 1.0.0 Operating System: Windows 11 Flight Sim Version: 2024 1.3.22.0 (Occurs in MSFS 2020 too) CPU: Ryzen 9800x3D GPU: RTX 5080 RAM: 64GB DDR5-6000