Entering Offset 0x9400

[masterk]

Hi,

i have a question. I must enter for the iflytofsuipc tool the offset 0x9400 to the FSUIPC. I used Offset dword set. But when i entered that the value changes to x0000. Is that normal? The only way i can enter x9400 but then the iflytofsuipc tool doesn´t work.

Here is a print from the logfile

LogOptions=00000001

902341 System time = 11/01/2012 17:05:01, FS2004 time = 16:57:47 (15:57Z)

921451 Button changed: bRef=0, Joy=1, Btn=12, Pressed

921451 [buttons.iFly 737-800 Air Berlin (Normal screen)] 68=P1,12,Cx03009400,x00000430

921451 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x430

922309 Button changed: bRef=0, Joy=1, Btn=12, Released

922309 [buttons.iFly 737-800 Air Berlin (Normal screen)] 69=U1,12,Cx03009400,x00000429

922309 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x429

923182 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4

923182 .. Key not programmed -- passed on to FS

923260 KEYUP: VK=18, Waiting=0

5787777 Button changed: bRef=0, Joy=1, Btn=12, Pressed

5787777 [buttons.iFly 737-800 Air Berlin (Normal screen)] 70=P1,12,Cx03009400,x000001AE

5787777 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x1AE

5789197 Button changed: bRef=0, Joy=1, Btn=12, Released

5789197 [buttons.iFly 737-800 Air Berlin (Normal screen)] 71=U1,12,Cx03009400,x000001AD

5789197 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x1AD

5790507 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4

5790507 .. Key not programmed -- passed on to FS

5790632 KEYUP: VK=18, Waiting=0

I have tested 2 ways. First only enterd x430 and the second only 430 and ich changed to x1AE.

Br

Christian

[Pete Dowson]

i have a question. I must enter for the iflytofsuipc tool the offset 0x9400 to the FSUIPC. I used Offset dword set. But when i entered that the value changes to x0000. Is that normal? The only way i can enter x9400 but then the iflytofsuipc tool doesn´t work.

If you are talking about assignment to an offset control in FSUIPC, then the correct format ix x9400. The "C" format 0x9400 will resut in x0000 being used, as you found, because of the leading 0. FSUIPC needs to first see the 'x' to know it is hexadecimal, not decimal.

Here is a print from the logfile

...

921451 Button changed: bRef=0, Joy=1, Btn=12, Pressed

921451 [buttons.iFly 737-800 Air Berlin (Normal screen)] 68=P1,12,Cx03009400,x00000430

921451 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x430

922309 Button changed: bRef=0, Joy=1, Btn=12, Released

922309 [buttons.iFly 737-800 Air Berlin (Normal screen)] 69=U1,12,Cx03009400,x00000429

922309 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x429

Okay. That shows that pressing button 12 on joystick 1 causes the 32-bit (4-byte or DWORD) offset x9400 to be set to the value x430, but then, on release, to the value x429.

I don't know why you are doing this, but if that's what you intended. what is the problem?

Presumably you then changed it:

5787777 Button changed: bRef=0, Joy=1, Btn=12, Pressed

5787777 [buttons.iFly 737-800 Air Berlin (Normal screen)] 70=P1,12,Cx03009400,x000001AE

5787777 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x1AE

5789197 Button changed: bRef=0, Joy=1, Btn=12, Released

5789197 [buttons.iFly 737-800 Air Berlin (Normal screen)] 71=U1,12,Cx03009400,x000001AD

5789197 IPC Offsets Control: Ctrl=x0300, Length=4, Offset=9400, Param=x1AD

because now the same button sets x1AE when pressed and x1AD when released.

I have tested 2 ways. First only enterd x430 and the second only 430 and ich changed to x1AE.

If you put decimal 430 it will be identical to hexadecimal x1AE. They are identical values, no different at all. Likewise 429 = x1AD.

The picture you added shows exactly what is actually occurring.

I'm afraid I don't find any actual question to answer in your posting. Did you have one?

Pete