• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Project editor locking up

B

Brian Franklin

Messages
59
Country
unitedkingdom
Hi guys, has anyone else experienced the FS project editor locking up after opening a project. Doesn't matter what project or the sim location. I've tried reinstalling the SDK but that was no different. Even fails when opening projects that have succeeded before.

Any ideas gratefully received.

Brian
 
The SDK just has documentation, samples and tools. The actual compiler is within the sim, so it appears your sim may be corrupted (or perhaps you have some hardware failure).

You can reinstall the sim without re-installing all the Official folder. Just rename the Official folder temporarily, uninstall the sim, rename any C:\Users\yourname\AppData\Roaming\Microsoft Flight Simulator folder temporarily, rename the Official folder back, re-install the sim (making sure the install looks in the right place for the Official). After testing to see if it works, you can then rename your C:\Users\yourname\AppData\Roaming\Microsoft Flight Simulator folder back.

If that isn't the problem, then you may have a hardware failure... memory failure or lack of memory most likely or perhaps an overclocking problem.
 
rhumbaflappy said:
The SDK just has documentation, samples and tools. The actual compiler is within the sim, so it appears your sim may be corrupted (or perhaps you have some hardware failure).

You can reinstall the sim without re-installing all the Official folder. Just rename the Official folder temporarily, uninstall the sim, rename any C:\Users\yourname\AppData\Roaming\Microsoft Flight Simulator folder temporarily, rename the Official folder back, re-install the sim (making sure the install looks in the right place for the Official). After testing to see if it works, you can then rename your C:\Users\yourname\AppData\Roaming\Microsoft Flight Simulator folder back.

If that isn't the problem, then you may have a hardware failure... memory failure or lack of memory most likely or perhaps an overclocking problem.
Click to expand...
Thanks Dick, I'll give that a go
 
I've been struggling with a similar problem recently too, it's not so much the Project Editor locking up, because it loads my project in fine, but when I move around to go and start placing object down, the sim just completely freezes, nothing is clickable and I have to exit out via task manager. At first I thought it was maybe something to do with my GPU overclock but after reverting to default speed I'm still encountering the same issue. Hoping that the SDK update that'll come with world update 3 fixes this issue.
 
I have 32 BG of memory in my computer. I have read of developers having problems with 16 GB Ram, and I have an 8 GB graphics card. Perhaps 6 GB is not enough. Expensive to fix if that is the problem.
 
Ironically since I posted my reply earlier, I fixed my issue by rolling back my Nvidia driver to 460.89, now my issue is gone! Very strange. I have 32GB RAM and an RTX 3080 for reference.
 
You must log in or register to reply here.
Back
Top