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

SCASM code list

Messages
6
Country
ca-quebec
Hello to you all!

I'm a CFS1 a/c designer who is currently "learning the ropes" with Alain Breton on how to tweak MDL code with MDLDisAs, a GUI to decompile-recompile using SCASM.

Alain told me, for example, that 0x004 varptr was pointing to global (earth) coordinates while 0x028 varptr was pointing to a/c coordinates.

My question is: Is there a list of those variables and constants codes somewhere that I could d/l? I think that the reason why is obvious. :o

Being a regular at SOH's CFS1 forum, I do feel at home here.

Thanks in advance!

Hubbabubba
 
Hi,

I am not really sure what you mean with varptrs? Are you refering to the opcode commands used or are you talking about address of variables?

In both cases I think the SDK documentation from MS would be your best source of information.
 
Hi arno!

varptr (presumably "variable pointer") is hex code for indirect coordinates like the following lines:

:L001352
Call( :L0013A0 )
RefPoint( nsi :L001372 0x028 v1= 0 v2= 11 )
SetScaleX( :L001372 0 0 7 )
PBHCall( :MAINVC 0x01C )

But I would also be interested in var hex codes like those found in commands such as IfVarAnd.

I will look again in the SDK but I found nothing the first time. Those hex codes must be somewhere as I can't imagine people "guessing from the top of their heads" those codes.

Thanks anyway arno!

Hubbabubba :)
 
Hi,

That is interesting, I haven't seen it being used like that. For scenery you would have the position (lat/lon) at that location in the RefPoint command. I guess this is a special notation for aircraft, as they have no static position of course :).

The SDKs I refered to are mainly for scenery, but maybe you can find some interesting stuff in them:

Fs2000 SDKs: http://www.microsoft.com/GAMES/flightsimulator/fs2000_devdesk_sdk.asp

Fs98 SDKs: http://www.microsoft.com/GAMES/flightsimulator/fs98_downloads_sdk.asp
 
Yeah arno!

AF99 (and FSDS I've heard) is using SCASM code the same way scenery does.
Its only that their objects are flying!

I have re-read FS98SDK and found nothing. Will try FS2K.

Thanks!

Hubbabubba:wave:
 
Yes, the code is generated with the same commands (MakeMDL for GMax can also create both scenery and aircraft). But there are some differences in how the commands are used. And as most people here are scenery designers, we might not know all the details on the aircraft.

I had a look in some GMax output and there they are refering to a certain struct, so I guess that is the same as your pointer. I could not yet found to which address that struct should be pointing, but I guess it would be the same are the pointer you posted.
 
`Just so you know arno.

Before making aircraft for CFS1 I was making sceneries - mainly military airport of the era - and API macros for those sceneries using EOD. Unfortunately, EOD was "to advanced" to compile CFS1 objects and I had to fiddle with their SCASM code so that they would show properly.

One thing leading to another, I came to do more than corrections. Here's a small sample of my work:


This represent a three (or four) stories watch tower of Fleet Air Arm Service as they were built throughout England during WWII. Returning to SCASM for designing aircraft is,in a sense, a way to return to origins.

So long!

Hubbabubba
 
Back
Top