• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Porting an FSUIPC program to SimConnect

Messages
516
Hi,
I've written a program using FSUIPC that uses offsets 310A to disable joystick inputs to the sim, reads actual input axis positions with 3328, etc. and then writes them back into 0BB2, etc.

Is this sort of behaviour possible with SimConnect? I've got no experience with it, and I'd like to establish that what I want to do is possible before I start porting my program.

Thanks,

Si
 
I've written a program using FSUIPC that uses offsets 310A to disable joystick inputs to the sim, reads actual input axis positions with 3328, etc. and then writes them back into 0BB2, etc.

Is this sort of behaviour possible with SimConnect?
Yes of course. FSUIPC4 itself uses SimConnect to do it!

Regards

Pete
 
Ok, thanks. I wasn't sure since the Offsets Status pdf in your SDK lists 310A as internal to FSUIPC, so I was concerned that perhaps you were intercepting the Windows joystick driver and allowing modification of the values before the joystick data gets to FSX.

Si
 
Ok, thanks. I wasn't sure since the Offsets Status pdf in your SDK lists 310A as internal to FSUIPC

Yes, of course, it is. SimConnect doesn't offer a bit-mapped "disconnect this axis" facility which I simply map to 310A. The 310A facility is purely an FSUIPC mechanism for use by FSUIPC clients.

Just as all the other complicated shenanigans FSUIPC has to get up to to maintain the illusion shown in documents like the Offsets Status, you have to intercept, block, change and re-transmit events as you wish to accomplish your task.

Nothing in FSUIPC's documents is as simple internally as it is made to look, you know! ;-)

Regards

Pete
 
Back
Top