December 9, 20214 yr Didn't really know what to call the topic. Recently I have been reading in this forum about people who fly long flights having issues after some amount of time where the sim is not responding properly anymore. I myself don't yet fly any long flights as I am still learning how to fly in general. However, last night I opened the sim and pulled up one of the included training sessions. The sim was just idling as I had not yet clicked "Fly". Then I got called to dinner and then I eventually got tired and fell asleep without going back to the sim. So the sim just sat there all night waiting for me to return and click the Fly button. Well, when I tried to starting using the sim again in the morning, it was a mess; the image was stuttering all over the place and things I clicked did not respond or responded very slowly. When I shut down and rebooted the sim again, everything was fine. I am only putting this out there in case knowing that issues arise over time, even if you're not flying, might help you folks to determine what's going on with the sim. Case: (Lian Li PC-011 Dynamic XL), PSU: (MEG Ai300p pcie 5 & ATX 3.0), Motherboard: (ASUS TUF Gaming x670E-PLUS WIFI 6E), CPU: (AMD Ryzen 7 7800-X3D) Memory: (G.Skill Trident Z5 NEO RGB Series 64GB DDR5 6000), GPU: (Zotac Gaming GeForce RTX 4090 AMP Extreme Airo). CPU Cooler: (ASUS ROG Strix LC RGB 360) Fans: (7 Corsair LL Series 120mm RGB)
December 10, 20214 yr I think I have had this sort of issue with every sim I have ever used. Putting on pause and leaving coming back hours later and my CPU or RAM memory has been sapped. Bryan Wallis aka "fltsimguy" Maple Bay, British Columbia Near CAM3
December 11, 20214 yr Any number of things could have happened -- computer went into power save/sleep, screensaver kicked on, etc. I have to say I've been impressed by MSFS ability to hit "Esc" and sit there for a few hours and be ok, although I have never left it on overnight. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
December 11, 20214 yr Commercial Member These issues are usually caused by "memory leaks". Which is a slightly misleading term for a situation where programmers request memory from Windows to use for whatever purpose they, then forget to release it or release it incorrectly. If this goes on long enough they'll end up requesting all your memory. Memory leaks can be hard to find, and can be small or large. A slight leak in MSFS that would take overnight to eventually grab everything wouldn't surprise me. If so, they'll find it and remove it - eventually. These bugs are often introduced as a result of fixing code, when the person fixing it doesn't fully understand what's going on and inserts logic that skips around a necessary memory de-allocation. There've been TONS of fixes to MSFS. Edited December 11, 20214 yr by Dutch727 Clarity Charles "Dutch" Owen - Developer at Military Visualizations - currently working on the C310R and SR-71A project for MSFS.
Archived
This topic is now archived and is closed to further replies.