not 99%, a good percentage of simmers are using latest hardware the tech market offers, and more than that, MS Flight Simulator is one of the reasons why ppl should upgrade to the latest hardware available. and even more, some few only purchase new setups just to try the sim, & iam one of them, because its a game changer in the software industry.
seems there are also reports for âtodayâ in âmemory could not readâ topic⊠may be it really relates together, and that may also another âproâ for âpossible connection/server issuesâ.
I am repeatedly suffering by this issue on Windows 10. It is after the latest update of MSFS.
Same for me. It must be serverrelated. Today I get it all the time.
This Thursday (or if it was Wednesday) it ran just fine.
Hope this is due to bug-testing frĂ„n MS//Asobo that they are trying to get this message to appearâŠ
I never got the error popup and also not the memory could not read error. But today I got my first connection lost message. It reconnected directly without issues, but just wanted to mentioned it because there is one theory here, that the servers are possible involved and seemingly some new reports in both topics.
I only get the message about error en ountered. Get no out of memory-message. This Thursday I got the connection lost message two times, but my flights was not disrupted.
I have experienced the graphics device error on several sceneries mostly the new KLAX when I approach near Gate 55 but now its spreading to other sceneries and now in flight had it 5 times today. I think Asobo need to find this bug and fix it as the sim seems unplayable for a great many of us.
i purchased the sim before almost 3 weeks, and didnât have the chance to try it in an appropriate way yet! as SU10 was only days after the purchase, LOL.
It sure isâŠI am thinking it must be serverrelated. Could be a certain cluster within their servers that hosts specific accounts or somethingâŠ
Iâve been saying for some time that peaks in the incidence of the CTDs do appear to coincide with peaks in server demands, downloading new updates for example.
However, if these issues are server-related, the client code should still be able to cope and should not CTD as a result. In other words, fixing the server issues might reduce the incidence of these CTD, maybe to close to zero, but until the errant client code is also fixed, there will always be a chance of a recurrence.
After weeks of having having the crash issue I followed the guide and the game isnt crashing on the start menu and I was finally able to complete a flight. Thank you for posting the guide. I recommend everyone with issues still to give it a shot. I didnt think it was going to work but it did.
So⊠whereâs this bug in the latest development update? Slide 3 claims the highest-voted bug in the last three months regards the haze layer and has only 77 votes. Meanwhile, this thread with 216 votes doesnât even appear at all, yet total nothingburgers like âthe moon isnât always the right way upâ get listed with as little as 20-25 votes.
Can someone please explain why weâre not even acknowledged in the dev update published just three days ago, when this thread now has close to a thousand posts in the last month?
Gotcha, thanks for the confirmation. Might I gently suggest if a bug has to exist for more than three months to be mentioned in that list, perhaps the name of that snapshot could be changed (or a footnote added) to reflect that, as itâs very non-obvious? Clearly, not by yourself, Iâm not suggesting you have access, just that the feedback could be passed along.
Can help the gpu & the system perform better by optimizing performance, but this wont be considered a long-term solution due to the instability that the sim currently has.
& i dont see a point of uninstalling nvidia experience, since you can control what settings it changes.
Itâs interesting that you say that. I wasnât flying near KLAX, but I had just reinstalled the default scenery for it. I had previously uninstalled it so it wouldnât interfere with a 3rd party one, but I no longer use 3rd party sceneries. I had forgotten it was disabled until this weekend, and I hadnât had any CTD until this weekend.
My crash didnât happen until an hour into my flight, so Iâm not motivated to experiment with it.
More than three months with this bug?!? That is a NO GO item!
if the error is fixed in 3months Asobo but been fast.
The error memory could not be read has not been repaired for 7 months
My issue is even stranger, until recently all fine but now I get the Graphics Device error as soon as I move my mouse. The game loads fine into the main menu, as soon as I move my mouse, bangâŠpopup error. Tried in Safe Mode and exactly the same issue.
Why not? Who am I to doubt the recommendations of a real pilot?
I am glad that you tried it and that it worked!
Donât know if this is of any help put parts of my experiences are:
-I have never flown a plane sice I bought the Sim in eary september
-I get the âgraphics device has encounteredâŠâ in loadup screen before main menu always
-I did a lot what was mentioned: reinstalling the game, moving it to SSD, reinstaled and/or switched to studio driver and back to game ready driver, force started it trough steam in DX11 and DX12, Toggeled Windows Performance settings, Changed Nvidia Control Settings, reset graphic cards firmware, renewed the thermal paste and combinations of the mentioned above and more
-then i figured to instead of using my ânewâ (but preowned) GTX1070 founders revert my sytem back to my old GTX970 and I coudnât belive my eyes but the Sim was running for the first time. I was able to play the tutorials but on a custom flight it wold always crash but without no warning prompt.
But since Iâm also rocking a new msi WQHD 1440p 165hz Monitor I ofcourse went back to the GTX1070 for all the other games and demand that the Studio fixes the problem which shouldnt be my system as from what I read here.
Today i ran afterburner and right before the prompt pops up my GPU spikes to 100% in loading screen. Why is the game doing that to the gtx1070 but not the gtx 970. Doesnât make sense.
UNPLAYABLE ALWAYS UNFORTUNATELEY
UPDATE: It fully runs now without any issues after I upgraded to a RTX3070. Something about my i7 6700k + my gtx 1070 founders turned the game off.