Ailerons, elevator, rudder etc. input not working.

[Robson]

Hi all,

I develop software for my homecockpit based on FSUIPC. Currently I transfer input from joystick via my app and FSUIPC offset to FS. It works like a charm in FS9 but I'm unable to set these values in FSX.

I can read every value and write some of them so this is not a connection problem. Also my app is working fine cause even FS-Interrogate cannot set for example aileron value.

I tried various things like reinstalling FSUIPC (of course clean install performed) and many others but I still have no idea whats wrong...

Maybe someone encountered similar problem?

Regards,

Robert.

[Pete Dowson]

Currently I transfer input from joystick via my app and FSUIPC offset to FS. It works like a charm in FS9 but I'm unable to set these values in FSX.

I can read every value and write some of them so this is not a connection problem. Also my app is working fine cause even FS-Interrogate cannot set for example aileron value.

Sorry, i need to know more to be able to help you. What offsets are you using? What version of FSUIPC?

I tried various things like reinstalling FSUIPC (of course clean install performed) and many others but I still have no idea whats wrong...

"Reinstalling" FSUIPC only replaces FSUIPC4.DLL with FSUIPC4.DLL, which cannot change anything unless you are also changing versions. If the DLL was itself corrupted then it wouldn't run -- you'd get an error message in the Log as its signature check would fail.

More likely that you have some SimConnect problem. but without information I cannot really advise further. Please check the FSUIPC log -- in fact, use logging. that's what it is for, to help you diagnose problems and obtain information.

Regards

Pete

[Robson]

I use 0BB2, 0BB6 and 0BBA offsets, and according to FSUIPC log values are written (no error) and then read back to app but returned value differs from send one.

FSUIPC 4.60a.

That's part of log:

255468 WRITE0 0BB2, 2 bytes: 88 13 ..

255967 READ0 0BB2, 2048 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 04 ..............6.

255967 36 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6...............

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

255967 00 00 00 00 00 00 FF 3F 00 00 FF 3F 00 00 FF 3F .......?...?...?

255967 00 00 FF 3F 00 00 5B 84 01 00 00 00 00 00 00 00 ...?..[.........

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

255967 00 00 00 00 00 00 00 00 00 01 00 00 00 00 31 31 ..............11

255967 3A 30 31 3A 35 33 00 30 30 2E 30 00 30 30 30 00 :01:53.00.0.000.

255967 00 30 30 2E 30 00 30 30 30 00 00 00 00 00 72 FC .00.0.000.....r.

255967 00 00 01 00 00 00 00 00 00 00 00 29 54 01 00 00 ...........)T...

255967 00 00 00 00 5A 00 00 00 00 00 5A 00 3B 01 00 00 ....Z.....Z.;...

255967 00 00 00 00 00 00 00 00 00 40 00 00 00 00 28 00 .........@....(.

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Unfortunately I understand nothing from this beside that it writes it and reads somewhere.

[Pete Dowson]

I use 0BB2, 0BB6 and 0BBA offsets, and according to FSUIPC log values are written (no error) and then read back to app but returned value differs from send one.

0BB2, 0BB6 and 0BBA are working fine here. They are used by my own controls.

FSUIPC 4.60a.

I really cannot support such an old version. The current version is 4.745 (with an update to 4.746 in the Download Links subforum), and the earliest version which is supported is 4.70.

That's part of log:

A rather uninformative part too. Look nearer the beginning. Are there any problems with SimConnect logged?

255967 READ0 0BB2, 2048 bytes:

Why on Earth are you reading 2048 bytes?

First, update your FSUIPC installation. You can get the 4.745 installer here, in the Download Links subforum, or you can go to the Schiratti site.

Second, if there is still a problem, show me the Install log and the FSUIPC log -- but not with all IPC Reads and Writes logged., please. That will cloud the issue too much. Better to use the Monitor facilities on the right-hand side of the Logging tab. Put 0BB2 and 0BB4 there, both as S16 type. I've just done that and written first 5000 (your hex 1388) and then -5000 to 0BB2, via FSInterrogate. I can see the effect on the elevator, and the results are confirmed, in the Log, by the SimConnect readouts logged. See here:

   642156 Monitor IPC:0BB2 (S16) = 5000
   642172 SimRead: 0BB2="ELEVATOR POSITION"
        	FLT64: 0.30517583956
   642172 Monitor IPC:0BB4 (S16) = 2726
   642172 SimRead: 0BB4="ELEVATOR DEFLECTION PCT"
        	FLT64: 16.638187499

   671375 Monitor IPC:0BB2 (S16) = -5000
   671375 SimRead: 0BB2="ELEVATOR POSITION"
        	FLT64: -0.305236993926
   671375 Monitor IPC:0BB4 (S16) = -2726
   671375 SimRead: 0BB4="ELEVATOR DEFLECTION PCT"
        	FLT64: -16.6427727652

Regards

Pete

[Robson]

Ok, it works now ;]

Thank you very much. For information update to 4.745 helped ;]

Regards,

Robert.

[Pete Dowson]

Ok, it works now ;]

Thank you very much. For information update to 4.745 helped ;]

Versions 4.70 and later connect to Simconnect in a different way, avoiding many of the problems folks get with the Windows Side-by-side library system (WinSxS). It sounds like you have some sort of such problem with your FSX installation -- something which happens very easily if you ever try to uninstall and reinstall FSX (the uninstaller makes a hash of it).

Regards

Pete