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

FSX SP2 and Scasm - Desaster

K

KlausKlausen

Messages
15
Country
germany
Dear Fellowsimmers,

so far I have used extensive scasm-compiled scenery with FS-X and SP1 installed - it went flawlessly, everything was fine. Having installed SP2, however, it seems pure horror - whenever I load my scasm scenery, FS-X crashes to desktop. When loading a flight in slew mode, it still works, however, as soon as I move in slew mode and a few scasm objects come in sight, FS-X crashes and says APPCRASH in module ntdll.dll. However, it seems I can fly in all the default sceneries without a crash.

So I stongly suppose SP2 has ruined the scasm backward compatibility of FS-X. The question is, is there only a certain command in the scasm language or is this compiler no longer usable? The testbgl-routine of scasm shows no errors with my *.scm code.

Any help would be appreciated.

Klaus
 
Hi Klaus,

The answer is quite simple, SCASM can not make scenery that is compliant to the FSX SDK. So you are strongly advised to move to the techniques of the SDK.

Due to the backwards compatibility most objects should still work though, although some exotic tricks might no longer work. I never experienced such structured crashes as you mention. But also for performance it is a lot better to move to the new techniques.
 
Hi Arno,
Yes, of course it is best to completeley change to bglc sdk language, however, my scasm scenery is quite extensive and contains some tricky programming, since I would like to keep as much as possible form it (though your genius modelconverterx does a GREAT job, congratulations).

I just want to find out whether scasm code does not at all work with FSX SP2 (since everything was completely fine with FSx ans SP1), or whether there is just one instruction which is no longer compatible.

If others haven't experienced complete crashes, that would mean that there still is a compatibility and one could change things step by step instead of completely reprogramming everything.
Klaus
 
Hi Klaus,

Agreed, I think it should still be possible to get it working. Maybe you could test by removing some objects to see which one causes the crash?
 
Hi Arno,

I did so, reducing the source code to 3 buildings to start with. It was ok at first, but the textures are distorted, and finally, FS-X crashed with another kind of exception error. It seems FS-X did not retain the compatibility with SP2, only with SP1. I think it is best to abandon Scasm completely by now, but fortunately, there is your ModelConverterX.

Greetings,
Klaus
 
You must log in or register to reply here.
Back
Top