Achilles Philippopoulos

Sorry typo mistake. I use the latest 3.918. I do not know how I wrote 3.817. Anyway. After checking, no offset refresh. So, the only way is to wait fs to refresh them? In FSX with 4.525 seems to work fine. I can confirm that offset 30C0, 3BFC, 2EF8 are refreshing immediatelly. I do not know about 30C8 because I do not use it. Not supported, for a long time. Please always update to a supported version (3.90 or later) before posting. Yes, I know, and it is documented that way as no one ever found a way to propagate the change through the system. You didn't read this in the offsets documentation? Pete

Hi Pete, FSUIPC version : 3.817 Using from offsets 1400 to 1F40 (payload values) to write values to FS it is OK. The new values can be seen at the payload page from inside FS, but does not refresh the 30C0. If you change the values from inside FS then the offsets 30C0 works fine. 1.) Try to emply all of your payload. 2.) Check 30c0 offsets value 3.) Write to offset 1400 a value. Result: 30C0 value is the same 1.) Try to emply all of your payload. 2.) Check 30c0 offsets value 3.) Change first payload from inside FS Result: 30C0 value has changed

thanks forthe explanation. maybe I am not very close to get the marker signal. I'll explain both words: "Activated" means that the Marker radio signal is being received and the sound (if enabled) is heard and the O M or I light is lit or flashing. If you are not receiving a marker signal then the Marker receiver is currently inactive, i.e. "not activated" by a signal. Okay? Note that you have to be pretty much overhead a marker to receive it and so activate the receiver into providing the sound and flashing light. "True" is a BOOLEAN expression, the opposite of which is FALSE. In FS (and most programming) terms, TRUE is represented by a non-zero value, and FALSE by a zero value. Ok? Regards Pete

Hi, I am trying to figure out what you mean by (activated when true) 0BAC 2 Inner Marker: activated when TRUE 0BAE 2 Middle Marker: activated when TRUE 0BB0 2 Outer Marker: activated when TRUE Never find out a way to recieve a true flag from those offsets. What I do wrong?

Hi Pete, I am trying to find the new weather offsets but it is imposible. I looked everyware. Can you help me please? Thanks in advance

Hi, Ivao uses dx9 aircraft models. So it is not compatible with dx10. That is causing your problems

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

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

Hi Pete, Sorry for offset 0225. It is offset 0255. Typo mistake. This offset reads always 0. 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. 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? How? There are facilities in SimConnect to create and control cameras, but no provision at all for reading about them. Regards Pete

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

Hi Pete, Thank very much. Achilles Wonder of wonders, my FS2004 PC booted up okay today! I've checked 2EF8 and, whilst I do not know enough to tell whether the figures are correct, the value given most certainly varies as one would expect when changing the payloads. Why do you think it isn't working? (I am using FSUIPC 3.911, in case there's a difference). Comparing the sorts of values I'm getting there with those in FSX I can see what your problem might be -- it's a bug in the FSX version. I am presenting it as a percentage whereas it should be a fraction -- i.e. not 16.2345 but 0.162345 -- in FS2004 and before it was always the fractional value, you multiply by 100 for a percentage. I'll fix FSUIPC4 -- look out for Version 4.517 soon! Regards Pete

Hi pete, The offset 2EF8 gives a reasonable value for fsx like 25 to 27 that is correct accoring to my calculations, but fs9 returns a value of 0,15 to 0,20. This is not correct. I use 3.90 for fs9. Positions 3,4,5 yes Positions 1,2 I do not know but it exists inside aircraft.cfg Maybe you can provide the Full pathname of the current cfg file like the air file of offset 3C00? Then I can read position 1 and 2 from the text file.

Hi Pete, I would like to calculate the CG% of the aircraft. In case of FSX I read the 2EF8 offset but in case of FS9 it does not work. So, the only way to calculate the CG% at FS9 is to read 1.) empty_weight_CG_position 2.) empty_weight_pitch_MOI 3.) Aircraft empty weight 4.) Aircraft total weight 5.) reference_datum_position of payload stations and fuel tanks. I can read throu fsuipc the positions 3,4,5 but not the positions 1,2 Can you find a solution of reading those positions throu offsets? Achilles

Ok. I found the fcuipc offset list for fs9. Thanks 2AE0 type mistake. I use 2EA0 (Trim value) What do you do wrong? How about not using the supplied reference lists of offsets for FS2004 and before, and not even noticing that some of the offsets you are using are NEW to FSX, as clearly noted by the BLUE colour in the document? Of those you list above, 1330, 126C are not supported in FS9 or before, and 1334 was only added in version 3.80 of FSUIPC. Offset 2AE0 is unknown to me in any case. What do you think is there? Please PLEASE use the reference lists I provide!! Pete

Hi Pete, Recently I builded a small tool for payload. However, it works fine at FSX (4.50) but not at FS9 (3.90) I attach a photo of fs9 and a photo of fsx. With the same offsets I get different results. FS9 FSX The offsets I use for reading from FSX are the bellow: 1330 3BFC 126C 30C0 1334 2EF8 2F00 2F08 0BC2 2AE0 However, some of those offsets are working ok to FS9 but not all of them. What I do wrong? Thanks in advance Achilles

If you wish, but I am changing FSUIPC4 to do this in any case. Later ... Pete There was no result. The same bad situation.

Hi Pete, The value is 4800 to 5620 from arming. I will try to set the OBCC offset from pmsystems when OBD0 is between 4800 and 5620 and I will inform you about the result. Achilles

Hi Pete, I will try then with a microswitch to set the 4800 value at the offset. But I am afraid in this case, that if I arm at the air (set 4800 value at the offset) and for some reason I want to extend to 50%, then when i move the lever back to arm position the value 4800 is not accepted from the offset and so I can not arm. It goes from value 5621 (1% of spoilers) directly to 0 value. Maybe I must set the microswitch to use the 0BCC offset? With best regards, Achilles

Hi Pete, I still can not figure out who to arm my spoilers at fsx. I use fsuipc 4.40. I build a throttle unin with phidgets and fs2phidgets. I use a potensiometer for the spoilers. I set up the spoiler with the OBD0 offset. Spoilers control, 0 off, 4800 arm, then 5620 (7%) to 16383 (100% fully deployed). The 4800 value is set by arming. Values from 0 to somewhere close to, but below, 4800 do nothing. The percentage extension is the proportion of the distance in the range 4800 to 16383, even though values 4800 to 5619 cannot be used—7% seems to be the minimum. I configured the offset to work from 0...16383 and when I move the spoiler to arm position I get the 4800 value but actually the offset 0BCC 4 stays at 0 meaning that spoilers are not armed. I have a logic that when spoilers are armed and when Aircraft on ground flag then the logic to be true but never comes true because of the spoilers never armed. Just for your information, with the same setup, everythink is working apsolutelly fine at fs9 with fsuipc 3.85. Any tip that you can provide? Thanks in advance Achilles

Hello, I need help with the mcpex1 of cpflight. I want to add the ground proximity callouts. I added the switches and according to mcp_conf are working fine. But at the drop down menu there are no gwrs callouts. So according to pmsounds the values are 5562, 0 bit for terr inhibit, bit 1 for gear inhibit and bit 2 for flaps inhibit. I added the lines to the digital.txt file to have them at the drop down menu but I am not able to program the values right. "Flaps Inhibit","&H5562",2,0,2,0 or 2,0,1,0 "Gear Inhibit","&H5562",2,0,1,0 or 1,0,1,0 "Terr Inhibit","&H5562",2,0,0,0 or 0,0,1,0 Can anyone help? Best regards, Achilles

What do you want to DO to offset 564D? What you appear to have told it to do is set the BYTE (8 bits) at offset 564D to zero (00). If that is what you want to do, you've done it already! ;-) If you wanted to set it to some other value, you need to enter that value as the PARAMETER in the options dialogue. Pete I am trying to send an wheel well fault to see if my hardware is working (fire panel from cockpitsonic). I do it in the right way?

Hello, I am trying to send 564D offset configuring from joustick button. I can not understand how to do that. I have read many times all the manuals. Any help? I get the value 1=P0,9,Cx0100564D,x00 What i do wrong? Achilles