Looking for offsets

[High-Octane]

Hi Pete

I was hoping there are offset that can get aircraft doors such as enterance/exit. cargo or perhaps engine doors. There are some type of addon aircraft that include it, and it can be found under FS2002 or higher command control "select exit" or wing fold/unfold.

Let me know

[Pete Dowson]

I was hoping there are offset that can get aircraft doors such as enterance/exit. cargo or perhaps engine doors. There are some type of addon aircraft that include it, and it can be found under FS2002 or higher command control "select exit" or wing fold/unfold.

I only know of the single aircraft door state listed at offset 3367, and that's for FS2004 only. I'm not doing any more hacking into FS2002 or earlier I'm afraid. Life is too short! :wink:

I have no idea how the other doors are implemented. If some clever aircraft designer can work out where in FS these things are handled I could maybe have a look, but there doesn't appear to be anything useful about them in any of the Microsoft documents.

I'm very reluctant to start hacking deep through a load of the DLL code when I don't even know how to recognise what I'm looking for, and I've been resisting doing any more hacking because it's late now in FS2004's life and I'd only have to start again with the next version, whenever.

Sorry!

Regards,

Pete

[High-Octane]

Yeah Pete, Sometime I wish there is easy way for you to hack some variables in FS, so that way everyone can entitle to use so many varible that FS uses for their 3rd party or written program. Perhaps next version could be better for you :wink:

I have recongise some of variable listed in FS interrogation has already declared offset but FSUIPC does not support it. I was curious to know why?

[Pete Dowson]

I have recongise some of variable listed in FS interrogation has already declared offset but FSUIPC does not support it. I was curious to know why?

No idea. Do you have examples?

Pete

[Pete Dowson]

At the very right side there are some comments on usage and some of them labeld "NOT FSUIPC SUPPORTED" .

OOPS! I did it again -- sorry. I edited your message instead of posting my reply. that's twice recently, after never before for two years! Senility is setting in rapidly! Ugh.

Anyway, you know what you said, so:

This means that they are unverified, and possibly won't be maintained in future FS versions. In general these are items that are currently in the second table in the SDK's "Programmer's Guide" documentation. That second table lists things "discovered by accident", as it describes there.

There used to be many many more in this category. Gradually the values they contain have been analysed and understood and used. As a result of this they've been gradually moved from the second table to the first, along with explanations, and thus have become "supported".

Entries which are "supported" are those which I will give priority to finding in each successive version of FS. Those which are "not supported" may or may not be found, and take a lower priority in any case.

That is what that means. Okay?

Possibly, eventually, someone will investigate those values more thoroughly, offer explanations, and actually use them for something significant. If they want them in future FS releases they would then need to give me all that information with their request for ongoing support so I can re-categorise them.

This process has been ongoing now for four years or more. You will notice credits listed to many folks who have contributed in this way -- browse through the Programmer's Guide document some time, you'll see what I mean.

Regards,

Pete

[High-Octane]

Okay :) Will keep on reading, reading and reading. Will try to play around and anaylize and find some crucial information on offsets. Thanks