• 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.

MSFS20 Sim freezes after building a package

Misho

Misho

Messages
1,042
Country
ca-ontario
Hi everyone,

As of yesterday, I am getting inexplicable sim freezes AFTER building scenery packages (ModelLib, Scenery, SimObjects and MaterialLib). I also have a WASM module package but that doesn't cause the freeze upon build.

The SDK apparently builds the libs, and then even shows the console logs (no errors) but then it simply locks up, not even CTD - I have to use TaskManager to end it.

I have tried to repair the Sim (didn't needed it), then I went and initiated the SDK repair through in-sim installer path (went through it although I am not sure if anything needed repair).

Does anyone have any idea on how to fix this?
 
Misho said:
Hi everyone,

As of yesterday, I am getting inexplicable sim freezes AFTER building scenery packages (ModelLib, Scenery, SimObjects and MaterialLib). I also have a WASM module package but that doesn't cause the freeze upon build.

The SDK apparently builds the libs, and then even shows the console logs (no errors) but then it simply locks up, not even CTD - I have to use TaskManager to end it.

I have tried to repair the Sim (didn't needed it), then I went and initiated the SDK repair through in-sim installer path (went through it although I am not sure if anything needed repair).

Does anyone have any idea on how to fix this?
Click to expand...
Ok - I got into a bit of investigating, and the problem is with my WASM code :D (which is infinitely better news than some obscure problem with SDK and my project files). I have a setup that cleanly loads/positions and unloads any number of SimObjects. Then, I started loading(spawning)/removing default Asobo 747... and there I get random lockups.

I am using SimConnect_AICreateSimulatedObject function which is perfectly fine to use for this. Perhaps I should move this question to WASM/SimConnect forum.

​

 
Misho said:
I have a setup that cleanly loads/positions and unloads any number of SimObjects. Then, I started loading(spawning)/removing default Asobo 747... and there I get random lockups.
Click to expand...
The term "cleanly" sounds a bit relative. Wouldn't mind having a look under the hood of your system, nonetheless.
 
=rk= said:
The term "cleanly" sounds a bit relative. Wouldn't mind having a look under the hood of your system, nonetheless.
Click to expand...

Hey Rick, thanks for chiming in!

I have a framework which loads any number of SimObjects into my own array of SimObject classes, from where I can access them all by ObjectID issued by server (sim) and manipulate them in any way I need to (even if they are multiples of the same SimObject). I then have a SimObject class container manager that (among other things) deletes and respawns them as needed, and these operations are "clean", leaving no SimObject duplicates or orphans - that's what I meant.

I have since (kind of) fixed up the problem - which manifests only when I try to load this Asobo 747 along with all the other SimObjects in the loading cue. I think it is something to do with a delay of loading such a large SimObject, so I developed a way of loading it as a one-off, which works without any problems. I'll investigate the actual cause when I get a bit more free time, but for now this works.
 
You must log in or register to reply here.
Back
Top