This are the (new) Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.

At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

IRS Button assignme…
 
Notifications
Clear all

IRS Button assignment for PMDG

Posts: 19
Registered
Topic starter
(@skythelimit)
Joined: 3 weeks ago

Hi John, I’m trying to assign IRS buttons to go to PMDG events in the usual way discussed here, specifically the SYS Display selector and the Display Selectors shown in the image below: https://fsuipc.com/community/fsuipc-faq-buttons/how-to-program-joystick-buttons-and-keys-to-control-pmdg-aircraft-using-custom-controls/#post-472

The link above states that you have 2 options for the Parameters, either Mouse Click Codes (which I have used until now) or Direct Values as follows:

I believe I need to be able to use Direct Values for the IRS, because these are knobs.  The Direct Values seems to be as follows from the sdk:-

So in my sioc script I am doing the usual and writing to those 2 offsets as follows, this is an example for the DISP SEL “TEST” position on the knob:

Var 0760, name TESTCtrl, Link FSUIPC_OUT, Offset $3110, Length 4 

Var 0761, name TESTParam, Link FSUIPC_OUT, Offset $3114, Length 4 

So the above parameter for TEST is 0 and the Control Event is 69632 + 229 = 69861

So in my SIOC script I have the following, placing the Parameter before the Control, as I understand is the recommended way:

Var 0730, name IRS_TEST, static, Link IOCARD_SW, Device 7, Input 48     // IRS TEST ROTARY SWITCH
{
  IF &IRS_TEST = 1
  {
     &TESTParam = 0  
     &TESTCtrl = 69861
  }
}

But this does not work, I can see in sioc the button press is producing the values above, but they don’t seem to be doing anyhting in pmdg.  The SIOC script works fine for mouse clicks but not these Direct Values


13 Replies
Posts: 19
Registered
Topic starter
(@skythelimit)
Joined: 3 weeks ago

John, one other question, to be able to read PMDG 737-800 (MSFS 2024) offsets, we should place the following in the [GENERAL] section of the fsuipc.ini, correct?  (I already have the PMDG Broadcasting set up)

PMDG737offsets = Auto

Reply
Posts: 113
Admin
(@fsuipc)
Joined: 6 months ago

Posted by: @skythelimit

to be able to read PMDG 737-800 (MSFS 2024) offsets, we should place the following in the [GENERAL] section of the fsuipc.ini, correct?

Yes, but it should be there by default. 

Posted by: @skythelimit

But this does not work, I can see in sioc the button press is producing the values above, but they don’t seem to be doing anyhting in pmdg.  The SIOC script works fine for mouse clicks but not these Direct Values

Not sure why its not working for you. I have checked here with the PMDG 737-700 in MSFS2020, and using custom control 69861 with parameters 0 – 4 moves the IRS Display selector knob to the correct position, depending on the parameter.
Not sure what to advise – maybe try a direct assignment in FSUIPC (e.g. a key assignment) to this first to check if it is working correctly in the 373-800 in MSFS2024.


Reply
Posts: 19
Registered
Topic starter
(@skythelimit)
Joined: 3 weeks ago

maybe try a direct assignment in FSUIPC (e.g. a key assignment) to this first to check if it is working correctly in the 373-800 in MSFS2024

Thx John, I’ll try that and check my fsuipc.ini.  I’ll also try reversing the lines in the sioc script, I had understood best practice was to put the parameter line 1st then the control, I’ll try the other way around

 


Reply
Posts: 113
Admin
(@fsuipc)
Joined: 6 months ago

Posted by: @skythelimit

I’ll also try reversing the lines in the sioc script, I had understood best practice was to put the parameter line 1st then the control, I’ll try the other way around

No point trying that really. You always write the parameter first, as the control is sent when it is written to 0x3110. If you write the parameter afterwards, the control will be sent with whatever is held in 0x3114 when you write to 0x3110.


Reply
Page 1 / 3