MobiFlight Community Support

yes please

captainmcduff2@aol.com

Hi

Just a question cause there are still requests for this files.....

If Pete Dowson include that elements in FSUIPC ( Pretty sure he did if you need a list with that data now) then he normaly also include that stuff in his help-files.

I can not install FSUIPC 5.xx cause i not own P3D a.t.m.
Can somebody confirm that newest Update of FSUIPC for P3D include in "/documents" subfolder the needed PDF file already ?

Hi,

I do not scan the forum every day so a late input from my side but I can confirm that in the latest version of FSUIPC (5.153) the help files are updated too. The pdf file with the offsets of the PMDG 737 is extended with a (small) table with the new or changed offsets for the NGXu version (compared to the NGX version). I hope this is what you are looking for.

Succes,
Hans K

I hope this is what you are looking for.

Thank you !

Hi Rigdeandgable,

I have all my Inputs for B737NGXu working except for ENG and APU GENERATOR sws, they switch OFF ok but when I select
ON , the sws moves to on but GEN power does not come on. If I select sws with mouse it works ok.
I have tried a Mouse Macro and it moves sws , but still does not bring GEN power on.
Does your GEN sws work ok and what event ID are you using.

Regards lud733

Hi,

Yesterday I installed my NGXu and start testing my Mobiflight driven overhead panel.
Indeed nearly all switches and indicators did work as with the NGX but… for some functions the switch was moving but the function itself didn’t work. However, when I used the cursor in the 3D cockpit it worked OK.
For most functions in the NGX you can use as parameter 0,1 enz. However, in the NGXu for some functions the switch moves but the function itself is not activated. Solution: use the value for left or right mouse button as parameter (and use the same event as in the NGX)

At least in my cockpit it seems that nearly all functions are working now. The only problem I still have is the adjustment of the flight altitude and the landing altitude. The value in the display on my overhead is in line with the 3D cockpit so that is OK. Decreasing the value by turning the rotary left is functioning well: the value in the display decreases. When I turn the rotary to increase the value nothing happens. I use the same events as for the NGX because I learned from the SDK documentation the event values for this these functions are not changed. For the NGX I used as parameter the value for the left and right mouse button (which worked well in the NGX). Whatever parameter in the NGXu I tried, up to now no result.
Perhaps somebody has the solution for this problem.

Regards,
Hans

Hi Hans,

did you try the mouse-wheel-function. Parameter is 8192 for decrease and 16384 for increase.

Hi Stephan,

I tried every parameter for the mouse (I thought ) but your suggestion was the right one (again)!
Vielen Dank für deine schnelle Reaktion!

Grüße,
Hans

Hi, Hans,

I did tried the Macro Mouse function onthe the GEN sws but used the NGXU event id and didnt work, so I will try NGX
event and see what happens.

Ludwig

Hi Ludwig,

I will give you the values I used.
All generator switches (Gen1, Gen2 and 2x APU) have three positions: one centre, one temporarily on and one temporarily off. So in Mobiflight I used two lines to control these switches.

Gen 1 On: Event: 69659. Parameter on press: 536870912
Gen 1 Off: Event: 69659. Parameter on press: 0
APU Gen 1 ON: Event 69660. Parameter on press: 536870912
APU Gen 1 Off: Event 69660. Parameter on press: 0
APU Gen 2 ON: Event 69661. Parameter on press: 536870912
APU Gen 2 Off: Event 69661. Parameter on press: 0
Gen 2 ON: Event 69662. Parameter on press: 536870912
Gen 2 Off: Event 69662. Parameter on press: 0

Succes,
Hans

@ Hans

That sounds strange..... I trust in you that it work but its not logical....

You use a "click" Parameter for ON but use a "set" Value parameter "0" to bring it in Off position.
This is not logical and a mixing of that sytems make no real sense....
For me it looks like only one system is correct BUT it also work with your "wrong" entry.

A ) If its a Set Event.
In that case On Position would also work same way if you use "1" or maby "2" (If this is realy a 3 Position witch) instead of 536870912
( Make sense that all above 2 is handle like 2)

If its a Click Event
Then for Off Position the "0" will do the same as Righclick.... by Parameter -2147483648
(Also make sense cause a negative Value is the lowest.... Technical all below 8192 (Wheel down) every value "can" be a rightclick . )


Maby check this out.

Hi Pizman,

You are completely right but that is because for the NGX nearly all switches worked perfect with the parameters 0, 1 and 2. I used that configuration as a base when I moved to the NGXu. Nearly all switches in the NGXu works in the same way as for the NGX except for a few one. For these the switches moved but they did not really switch the circuit. I tested and only for the switches that did not realy switch the circuit I changed the parameter. That were only a few ones (I think 6). That is the reason for the mix-up. But I will test if your suggestion is correct (I believe it is) and report back.

Hans

"Maby" you already give me the awnser....

Are you sure this switches have three positions in the NGX-u ???

I just check my Offsetlist for the "old" NGX Version..... The List show the GEN Switches as "Boolean" .... Means it have only 1/0
This would be the awnser.... If you use the "old" System with ON=1 and OFF=0 this will no longer work.... Cause ON is now "2" intead of "1".

But... No Matter aslong your system work fine.... This is just cause i´m always interested how a thing is working finaly.

Hi again,

As always on this forum: interesting discussion….Some answers:
The rightclick mouse parameter (-2147483648) does work. So I changed in my configuration the “0”’s in this value because it is more consequent.
The switches for the APU and generators in the NGXu overhead are (physically) 3 position switches: the normal position is in the centre, then there is a momentary up but also a momentary down position (Both up and down are springloaded). But of course: only two positions (momentary up and momentary down) are generating an action.

Regards,
Hans

Hi Hans,

Thanks for the values you use, I agree with Pizman thats it is strange it works that way, but if it works
that is good. On the Forum as you said we are learning what makes things work, so I will
try your values, and tell you if I have success.
I have tried the new NGXu mouse click values in the new SDK but did not work.

Ludwig