Offsets Report

[Achilles Philippopoulos]

Hi Pete,

FSUIPC 3.911

Offset 0225

Offset 0256

Offset 0C44

Are they exist is fs9? They are not included at the documentation but included at FSInterrogate2std.

Anyway, if they exist they do not work

FSUIPC 4.500

Offset 0C92 - Shows value 4 (At document the range is 0-3) Maybe up to 4?

Offset 832C - Any chance to be fixed?

Thanks in advance

[Pete Dowson]

Offset 0225

Offset 0256

Offset 0C44

Are they exist is fs9? They are not included at the documentation but included at FSInterrogate2std.

Er, 0225 is within the 256 bytes assigned for the current flight plan in FSUIPC4. Before FSX it was never assigned for anything.

0256 is clearly denoted in the FSUIPC4 offsets as new for FSX, and is also checked against FSX only in the FSInterrogate data. Evidently you aren't looking that far? Did anything before FSX have thermal visualisation?

0C44 is documented in both FSUIPC3 and FSUIPC4 documents. And it is clearly marked in the FSUIPC3 programming documentation as not working in either FS2002 or FS2004. You need to go back to FS2000 to get that. However, it does work in FSX. It is clearly marked in the FSInterrogate data (the checkmarks for different FS versions) as being for FS98, FS2000 and FS98.

Please do check the documentation AND the FSInterrogate data a little more thoroughly before such reports.

FSUIPC 4.500

Offset 0C92 - Shows value 4 (At document the range is 0-3) Maybe up to 4?

ErI have it down as not working at all in FSUIPC4. I've checked the code, and there is nothing populating that offset, so whether it says 4 or 64 is irrelevant. It doesn't work. I'm surprised it isn't zero -- some other application must be writing there?

Offset 832C - Any chance to be fixed?

How? There are facilities in SimConnect to create and control cameras, but no provision at all for reading about them.

Regards

Pete

[Achilles Philippopoulos]

Hi Pete,

Sorry for offset 0225. It is offset 0255. Typo mistake. This offset reads always 0.

Offset 0225

Offset 0256

Offset 0C44

Are they exist is fs9? They are not included at the documentation but included at FSInterrogate2std.

Er, 0225 is within the 256 bytes assigned for the current flight plan in FSUIPC4. Before FSX it was never assigned for anything.

0256 is clearly denoted in the FSUIPC4 offsets as new for FSX, and is also checked against FSX only in the FSInterrogate data. Evidently you aren't looking that far? Did anything before FSX have thermal visualisation?

0C44 is documented in both FSUIPC3 and FSUIPC4 documents. And it is clearly marked in the FSUIPC3 programming documentation as not working in either FS2002 or FS2004. You need to go back to FS2000 to get that. However, it does work in FSX. It is clearly marked in the FSInterrogate data (the checkmarks for different FS versions) as being for FS98, FS2000 and FS98.

Please do check the documentation AND the FSInterrogate data a little more thoroughly before such reports.

FSUIPC 4.500

Offset 0C92 - Shows value 4 (At document the range is 0-3) Maybe up to 4?

ErI have it down as not working at all in FSUIPC4. I've checked the code, and there is nothing populating that offset, so whether it says 4 or 64 is irrelevant. It doesn't work. I'm surprised it isn't zero -- some other application must be writing there?

Offset 832C - Any chance to be fixed?

How? There are facilities in SimConnect to create and control cameras, but no provision at all for reading about them.

Regards

Pete

[Pete Dowson]

Sorry for offset 0225. It is offset 0255. Typo mistake. This offset reads always 0.

Offset 255 is undefined in FSUIPC3, it is clearly documented as new in FSUIPC4 -- all the entries in BLUE are new. Please do refer to the documentation!

If your only guide is FSInterrogate data, which is a data file put together by many folks over the years, you should be more cautious. However, in this case it explicitly only checks FSX in the list of applicable FS versions for that offset!!

:-(

Pete

[Achilles Philippopoulos]

Hi Pete,

FSUIPC 4.500

Offsets

0910

09A8

0A40

0AD8

Conversion type? It is mentioned only as hours at the documentation but I get a value of 22 which is not true.

With best regards,

Achilles

[Pete Dowson]

Conversion type? It is mentioned only as hours at the documentation but I get a value of 22 which is not true.

22 for a 32-bit float? No factional parts?

It is read direct from SimConnect, with "hours" stipulated as the units. So, SimConnect says it is hours, and it appears correct in my experience. Why do you think otherwise? What values are you expecting? There's absolutely no manipulation of this value in FSUIPC.

Regards

Pete

[Achilles Philippopoulos]

Hi Pete,

There are also factional parts but the value number seems to be wrong. For a boeing 737-700, 22 hours and something for remaining engine fuel (each engine) does not seems correct. Also there is no change at the value when fuel flow changes. It should be I think.

Conversion type? It is mentioned only as hours at the documentation but I get a value of 22 which is not true.

22 for a 32-bit float? No factional parts?

It is read direct from SimConnect, with "hours" stipulated as the units. So, SimConnect says it is hours, and it appears correct in my experience. Why do you think otherwise? What values are you expecting? There's absolutely no manipulation of this value in FSUIPC.

Regards

Pete

[Pete Dowson]

There are also factional parts but the value number seems to be wrong. For a boeing 737-700, 22 hours and something for remaining engine fuel (each engine) does not seems correct.

Sorry, but that makes no sense. The fuel quantity can be changed -- it refreshes each time you load a flight, for instance. Fuel quantity and engine running time have no defined relationship, therefore -- the engine running time is cumulative from when you installed FSX unless you remove the files containing the data.

Also there is no change at the value when fuel flow changes. It should be I think.

Sorry, I've no idea when the value updates. Check the STATE.CFG file for the aircraft in the SimObjects subfolder in the same place as your FSX.CFG file. I think that's where the values are kept.

Regards

Pete