Jump to content
The simFlight Network Forums

Issue with PMDG 737 NGXU MCP changing values issue


Recommended Posts

Hi,

I have a strange issue managing the MCP values (CRS,Heading, Speed, Altitude, VS) in the PMDG 737 NGXU with FSUIPC 6.0.11 and VRInsight MCP.

Using the SDK controls to set the values, instead to have an increment/decrease of 1 digit I get an increment/decrease of 5 (e.g if I want to set the heading from 101 to 102 I get instead 106 and with a second input 111 and so on).

The strange thing is that this happens only using with FSUIPC the control (from PMDG SDK) and the correspondent value for mouse right or left clicking , if  I click on the rotary of the MCP panel  with the mouse the increment/decrease of values is correct (e.g 101 102 103 and so on)

Any idea of the possible reason for that and a possible solution?

Thanks and KR

Joe

Link to post
Share on other sites
19 hours ago, cellular55 said:

Using the SDK controls to set the values, instead to have an increment/decrease of 1 digit I get an increment/decrease of 5 (e.g if I want to set the heading from 101 to 102 I get instead 106 and with a second input 111 and so on).

The strange thing is that this happens only using with FSUIPC the control (from PMDG SDK) and the correspondent value for mouse right or left clicking , if  I click on the rotary of the MCP panel  with the mouse the increment/decrease of values is correct (e.g 101 102 103 and so on)

Any idea of the possible reason for that and a possible solution?

Not without further information. Could you activate event logging and produce a log file showing your problem (complete please - don't start a new log file!). Also increase or decrease using the mouse afterwards, to see hat that logs. Attach that log file, together with your .ini file and I'll take a look.

John

Link to post
Share on other sites

As you are using Files for profiles, can you also attach your ini file for your B738U profile please.

Your log shows that you are using the ROTOR_BRAKE control with various parameters. Are these valid for the PMDG aircraft? I thought PMDG used lvars together with its own FSUIPC offset area, not rotor brake codes which are used by FSLabs and others.

Also, which logging entries (if any) show the correct increments when using the mouse? 

John

Edited by John Dowson
Further info added
Link to post
Share on other sites

Hi John,

the control is 70022.

About the ROTOR BRAKE I have seen that and it's really strange because, as you can also see in the INI file, I do not use at all that control: I use only controls that are listed in the PMDG 737NGXU SDK document and the FSUIPC offsets. So I do not understand why that's is happenning.

Attached the file related the NGXU profile

KR

Joe

B738U.ini

Link to post
Share on other sites
32 minutes ago, cellular55 said:

the control is 70022.

Are the parameters you are using for those controls correct? Can you check that (and let me know what header file you are using, as I asked, so I can see if I have a copy somewhere....): I guess these are the controls that are giving the problem: 

Quote

   336281 *** EVENT: Cntrl= 70022 (0x00011186), Param= -2147483648 (0x80000000)  <70022>
   336422 *** EVENT: Cntrl= 70022 (0x00011186), Param= -2147483648 (0x80000000)  <70022>
   337344 *** EVENT: Cntrl= 70022 (0x00011186), Param= -2147483648 (0x80000000)  <70022>
   337547 *** EVENT: Cntrl= 70022 (0x00011186), Param= -2147483648 (0x80000000)  <70022>
   338531 *** EVENT: Cntrl= 70022 (0x00011186), Param= -2147483648 (0x80000000)  <70022>

32 minutes ago, cellular55 said:

About the ROTOR BRAKE I have seen that and it's really strange because, as you can also see in the INI file, I do not use at all that control: I use only controls that are listed in the PMDG 737NGXU SDK document and the FSUIPC offsets. So I do not understand why that's is happenning.

No, me neither - I can't see any assignments to that control in either your general assignments or the profile assignments for that aircraft. Maybe these are events that the PMDG aircraft use internally and can be ignored - if thats the case, you could use the DontLogThese ini parameter to ignore these (also available for Profiles).

Could you active logging for Buttins & Keys, and produce another log file please, so I can see what buttons you are pressing to send the controls.
Also, let me know which are the log entries produced when you use the mouse/UI to change the values.

Also, you have controllers active in P3D:
     1906 Controllers are set to ON, using RawInput within P3D

Can you either disable controllers in P3D, or check that you don't have any assignments there.

John
 

Link to post
Share on other sites

Hi,

attached a new log file and the file related the PMDG SDK (I think that is the header file you mention).

I do not understand which can be the  log entries when I use the mouse.

About controllers the assignment are empty.

Could you please address about how to sue the DontLLogThese entriy in the ini file and in which section that should be placed?

Another point: effectively using a default aircraft tghe ROTOR BRAKE entries are not in the log

Thanks and KR

Joe

FSUIPC6.log PMDG_NG3_SDK.h

Link to post
Share on other sites
16 hours ago, cellular55 said:

I do not understand which can be the  log entries when I use the mouse.

If you keep the console open, you will see the entries logged (or not!) when you use the mouse. Doo you see anything doing this?

16 hours ago, cellular55 said:

About controllers the assignment are empty.

Ok, but why not just disable controllers in P3D then? This will prevent them from being automatically re-assigned by P3D, which can happen.

16 hours ago, cellular55 said:

Could you please address about how to sue the DontLLogThese entriy in the ini file and in which section that should be placed?

It can go in the [General] section or in a a [Profile.xxxx] section. You want it in the latter, i.e. add this to your [Profile.B738U] section (and maybe your other PMDG profile sections): 
     DontLogThese=66587 

16 hours ago, cellular55 said:

Another point: effectively using a default aircraft tghe ROTOR BRAKE entries are not in the log

Yes, as this is used internally by your PMDG aircraft.

Also, please don't start a new log file - I need to see the complete log file.

You have also assigned to send the control on both press and release:
     242=P257,17,C70022,-2147483648     -{Custom control: <70022>}-
     243=U257,17,C70022,-2147483648     -{Custom control: <70022>}-
So this will send to controls (one on press, one on release), so maybe remove one of those - this will half the change rate.

Your last log is also quite strange, as it shows several button presses per second:

Quote

  1257078 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
  1257203 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 242=P257,17,C70022,-2147483648
  1257516 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
  1257750 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 242=P257,17,C70022,-2147483648
  1257953 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
  1258125 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 242=P257,17,C70022,-2147483648
  1258297 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
  1258422 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 242=P257,17,C70022,-2147483648
  1258594 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
  1258797 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 242=P257,17,C70022,-2147483648
  1259125 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 240=P257,19,C70022,536870912
  1259203 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 243=U257,17,C70022,-2147483648
 

If you press this button once, do you see multiple press entries in your log? What is your 257 device (some type of VRI device?)?
Is that sending repeated button press/releases when 'on'?

John

P.S. Please keep your console open when testing, so you can see what is logged on each individual button press/release.
Other than that, your assignments look fine according to the header file.

Edited by John Dowson
pasted ini entries corrected
Link to post
Share on other sites

Hi John,

thanks for the support and suggestions.

Attached the file containing the console entries when clicking the mouse, and another log.

I send to controls 2 times (one on press, one on release) because is the only way to have the value set when acting on the rotary: if I send to contol only 1 time (e.g. for press), I have to act on the rotary two times to have the value on the MCP changing and by the way the incerment is anyway 5 digits.

Yes... the device is the VRInsight MCP Combo

Clicking only once I have in the log these rows added:

1412125 Button changed: bRef=0, Joy=257, Btn=19, Pressed
  1412125 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 240=P257,19,C70022,536870912
  1412125 *** EVENT: Cntrl= 70022 (0x00011186), Param= 536870912 (0x20000000)  <70022>
  1412125 FS Control Sent: Ctrl=70022, Param=536870912  <70022>

Thanks again and KR

Joe

FSUIPC6.log console.txt

Link to post
Share on other sites
1 hour ago, cellular55 said:

I send to controls 2 times (one on press, one on release) because is the only way to have the value set when acting on the rotary:

Sounds strange. Did you try sending the control on the release only?

1 hour ago, cellular55 said:

Clicking only once I have in the log these rows added:

1412125 Button changed: bRef=0, Joy=257, Btn=19, Pressed
  1412125 [Buttons.PMDG 737-800NGXu SSW LUFTHANSA] 240=P257,19,C70022,536870912
  1412125 *** EVENT: Cntrl= 70022 (0x00011186), Param= 536870912 (0x20000000)  <70022>
  1412125 FS Control Sent: Ctrl=70022, Param=536870912  <70022>

Then this seems correct - only one control being sent. If that is incrementing by 5 rather than 1, I think you need to ask PMDG why...

What is logged when you increment by 1 with the mouse?

Have you trued using a mouse macro for this instead?

And lookin art the PMDG website, someone also posted the issue there: https://forum.pmdg.com/forum/main-forum/pmdg-737-ngxu-for-prepar3d-v4/57103-mcp-heading-selector-event-evt_mcp_heading_selector-event-70022-jumping-in-steps-of-value-of-5

The proposed solution is to assign keys for this in the PMDG setup, and then assign to those keys in FSUIPC. Maybe try that?

John

Link to post
Share on other sites

Hi,

yes.. I have tried also sending the control only on release.

No change with the mouse macro end no change assigning keys.

I have found only a way to have that: just after to have loaded the plane if I click in the panel on the rotaries with the mouse, after the commands issued trough the device increment of 1 digit

Crazy!

KR

Joe

Link to post
Share on other sites
2 hours ago, cellular55 said:

No change with the mouse macro end no change assigning keys.

The mouse macro should emulate the mouse click, so it is very strange that they give different results. And also weird that assigning to keys doesn't work, as that was reported as a possible solution in that thread on the PMDG forums.

Sorry, but I'm out of ideas on this one. Maybe try posting on the PMDG forums to see if any one else has had this issue and has found a workaround.

John

Link to post
Share on other sites

Hi John,

an update on the point. 

I noticed that I did not have installed the last update of PMDG, after the installation of the last version of the plane things seem to be fine now.

Thanks again for your support 

KR

Joe

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.