Jump to content
The simFlight Network Forums
Sign in to follow this  
ontheair

PMDG 737 NGX and FSUIPC

Recommended Posts

From the PMDG 737 NGX intro manual :

"During testing we have found that in extremely rare

circumstances, users with FSUIPC installed would need to delete

their FSUIPC.CFG file after installing the PMDG 737NGX in order

to get everything playing well together. We recommend that you

try this if it seems the NGX is not behaving normally after

installation"

I must admit I had to re-install and re-register FSUIPC just after installing the PMDG 737 NGX : once it was installed I discovered the FSX Add-ons menu was empty !!

What is this FSUIPC.cfg file they are talking about ? I cannot find it on my PC. Would it not rather be the FSUIPC4.ini file ?

I'd like to understand

Merci

Edited by ontheair

Share this post


Link to post
Share on other sites

From the PMDG 737 NGX intro manual :

"During testing we have found that in extremely rare

circumstances, users with FSUIPC installed would need to delete

their FSUIPC.CFG file after installing the PMDG 737NGX in order

to get everything playing well together. We recommend that you

try this if it seems the NGX is not behaving normally after

installation"

All that's talking about deleting your settings and re-doing assignments and calibrations to suit the NGX, because it just might be that your own axis calibrations and assignments may not suit the way the NGX is set up. All you really need to do is create a new Profile or Aircraft-specific set.

I must admit I had to re-install and re-register FSUIPC just after installing the PMDG 737 NGX : once it was installed I discovered the FSX Add-ons menu was empty !!

It sounds like their installer destroyed or corrupted the DLL.XML file, which loads both their DLLs and the FSUIPC4.DLL. However, it certainly didn't happen here when I installed the NGX. And in any case you certainly would not have needed to re-register unless you deleted the KEY file in the FSX Modules folder.

What is this FSUIPC.cfg file they are talking about ? I cannot find it on my PC. Would it not rather be the FSUIPC4.ini file ?

Yes, the INI file. INI files are configuration files loaded during program initialisation. The terms INI and CFG are interchangeable, but INI was set as a precedent by Microsoft for the standard Private Profile system, which both FS and FSUIPC have used for many years. These days Microsoft prefer that everyone put everything in the Registry, but I think that's horrible and FSX certainly never went that way either.

But you've no need to do anything unless you encounter some problem you cannot deal with by just reassigning or recalibrating controls. Deleting all of your existing settings seems rather over-drastic unless you are really stuck. I think the PMDG folks just don't want the bother of trying to explain the differences for the NGX in these matters.

Pete

Share this post


Link to post
Share on other sites

Thanks Pete. Sounds much clear now.

"you certainly would not have needed to re-register unless you deleted the KEY file in the FSX Modules folder"

This key file was not deleted and I was not asked to re-register, but at the end of the FSUIPC4 re-install process the registration window pops up prompting me to do so. I might have skipped/ignored it.

" ...... you cannot deal with by just reassigning or recalibrating controls. Deleting all of your existing settings seems rather over-drastic unless you are really stuck..."

As I'm using the Thrusmater HOTAS Cougar I don't feel concerned about reasignement or calibration controls.

Jean-Louis

Share this post


Link to post
Share on other sites

Is there a way (an easy way?) to take the Lua file for the NGX from LINDA and make it in to a MCRO file for FSUIPC?

I like LINDA quite a bit, but it doesn't work with my Saitek panels. I have the SPAD drivers, so FSUIPC will see it as a joystick, but LINDA will not, and I'd really like to get that working in the 737.

Share this post


Link to post
Share on other sites

Is there a way (an easy way?) to take the Lua file for the NGX from LINDA and make it in to a MCRO file for FSUIPC?

I like LINDA quite a bit, but it doesn't work with my Saitek panels. I have the SPAD drivers, so FSUIPC will see it as a joystick, but LINDA will not, and I'd really like to get that working in the 737.

It might be a good idea to post this question to the Linda folks, or at least put it into the pinned LINDA thread near the top of the Forum.

Generally Lua plug-ins are not the same as Macros files, though each can use the other, so some solutions will be a combination.

Now I've fixed a newly-reported bug in FSUIPC's mouse macro creation facilities, it seems it is quite easy to make them for the PMDG 737NGX. You'll need to download FSUIPC 4.721 or later, though. See the Download Links subforum.

Regards

Pete

Share this post


Link to post
Share on other sites

I can do that.

Either way, I'd rather have some kind of MCRO file as opposed to using mouse stuff, but I guess it could work.

Share this post


Link to post
Share on other sites

Either way, I'd rather have some kind of MCRO file as opposed to using mouse stuff, but I guess it could work.

Most folks' MCRO files for PMDG aircraft are full of such "mouse stuff". With those aircraft there aren't so many alternatives because they don't respond to normal FS controls.

And mouse macros are generally easier to work out and program than L:Var settings, which tend to need a lot more investigation and experimentation.

Until the PMDG NGX SDK is available I don't think there'll be many alternatives to those two methods. There are only so many keypress combinations, and I'm sure not all of the NGX buttons and so on are susceptible to those in any case.

Regards

Pete

Share this post


Link to post
Share on other sites

I just posted a MCP macro on Pete's support site. I'll be doing others tomorrow. I flight tested this and it worked fine with my homebuilt MCP.

Ed F.

[Macros]
Module="PMDG_737NGX.DLL"
1=MCP_N1=RX48bd0*X8bcc
2=MCP_IAS=RX43480*Xe8cc
3=MCP_LVL CHG=RX48c90*X8bcc
4=MCP_HDG=RX43740*X8bcc
5=MCP_APPR=RX48cd0*X8bcc
6=MCP_ALTHLD=RX48d10*X8bcc
7=MCP_VS=RX48d30*X8bcc
8=MCP_IAS_DN=RX48c50*X8bcc
9=MCP_IAS_UP=RX48c50*X8bcc,31
10=MCP_CRSA_DN=RX48b90*X8bcc
11=MCP_CRSA_UP=RX48b90*X8bcc,31
12=MCP_HD_DN=RX437c0*X8bcc
13=MCP_HD_UP=RX437c0*X8bcc,31
14=MCP_ALT_UP=RX48cf0*X8bcc,31
15=MCP_ALT_DN=RX48cf0*X8bcc
16=MCP_VS_UP=RX43a70*Xe8cc
17=MCP_VS_DN=RX43a70*Xe8cc,31
18=MCP_BANK_INC=RX43860*Xe8cc,31
19=MCP_VORLOC=RX43970*X8bcc
20=MCP_LNAV=RX48cb0*X8bcc
21=MCP_VNAV=RX43660*X8bcc
22=MCP_AT=RX43300*Xe8cc
23=MCP_FDA=RX43360*Xe8cc
24=MCP_CO=RX434e0*Xe8cc
25=MCP_SPDINTV=RX435a0*Xe8cc
26=MCP_ALTINTV=RX43a50*X8bcc
27=MCP_CMDA=RX43ad0*Xe8cc
28=MCP_CMDB=RX43b30*Xe8cc
29=MCP_APDISCON=RX43c80*X8bcc
30=MCP_CWSA=RX43b90*Xe8cc
31=MCP_CWSB=RX43bf0*Xe8cc
32=MCP_FDB=RX433c0*Xe8cc
33=MCP_BANK_DEC=RX43860*Xe8cc
34=MCP_TOGA=RX43ca0*X8bcc
35=MCP_HDG_UP=RX43790*Xe8cc,31
36=MCP_HDG_DN=RX43790*Xe8cc
37=MCP_CRSB_UP=RX432b0*X8bcc,31
38=MCP_CRSB_DN=RX432b0*X8bcc

Share this post


Link to post
Share on other sites

I just posted a MCP macro on Pete's support site. I'll be doing others tomorrow. I flight tested this and it worked fine with my homebuilt MCP.

Quick work! Excellent -- thanks Ed!

Pete

Share this post


Link to post
Share on other sites

Wow, thanks, that's exactly what I needed to get the panels to work through SPAD.

Unfortuantely, it seems like the F/D and CMD A and CMD B aren't working properly, but maybe that'll just take some tweaking?

EDIT: Figured it out.

These work fine with the Honeywell MCP, but not the Collins MCP.

Edited by xAlpha

Share this post


Link to post
Share on other sites

Sorry for my question, but i can't understand what i should to do.

I have registered FSUIPC, i have PMDG NGX and i have SAITEK MULTI PANEL.

And in 737 NGX only CRS switch is working, but when i turn it in HDG or ALT - it's doesn't responding.

I have try to create macro file, put it near fsuipc.dll, then i have create profile for NGX, but nothing changes.

May be i doing something wrong?

Share this post


Link to post
Share on other sites

I have try to create macro file, put it near fsuipc.dll, then i have create profile for NGX, but nothing changes.

Did you test the Macro and see it work, as documented (i.e. use the TAB key)?

Did you actually assign any buttons or switches to the macros? you don't say what your "profile" includes.

I'm afraid I cannot support Saitek devices, so I can't advise specifically on them. Just on the assignment of buttons seen in FSUIPC.

Regards

Pete

Share this post


Link to post
Share on other sites

Sorry for my question, but i can't understand what i should to do.

I have registered FSUIPC, i have PMDG NGX and i have SAITEK MULTI PANEL.

And in 737 NGX only CRS switch is working, but when i turn it in HDG or ALT - it's doesn't responding.

I have try to create macro file, put it near fsuipc.dll, then i have create profile for NGX, but nothing changes.

May be i doing something wrong?

Are you using the SPAD drivers?

Saitek's panels are not "joysticks" or even input devices of any sort, at least not with Saitek's drivers, so FSUIPC can't see the panels at all.

If you download these instead: http://fstools.weebly.com/

You'll find it works just great.

Share this post


Link to post
Share on other sites

Are you using the SPAD drivers?

Saitek's panels are not "joysticks" or even input devices of any sort, at least not with Saitek's drivers, so FSUIPC can't see the panels at all.

If you download these instead: http://fstools.weebly.com/

You'll find it works just great.

Yes, i'm using SPAD instead of original drivers. But it's not working correctly.

When i turn wheel - nothings changes (digits on panel display are changing, but in FS - not), but if i turning wheel in FS (for example - HDG) - digits changes in FS and on panel display.

Unfortunately i should wait for some updates from pmdg or saitek...

Share this post


Link to post
Share on other sites

Yes, i'm using SPAD instead of original drivers. But it's not working correctly.

When i turn wheel - nothings changes (digits on panel display are changing, but in FS - not), but if i turning wheel in FS (for example - HDG) - digits changes in FS and on panel display.

Unfortunately i should wait for some updates from pmdg or saitek...

Did you go through the SPAD control panel and change everything to an FSUIPC Virtual Button?

Share this post


Link to post
Share on other sites

Hello Pete,

I have a strange thing. I had the problem with the macros, so i download the 4.722 version, and was abble to create the macro for the NGX (available for anybody who wants it as for the Goflight modules in the FSUIPC.in) . I made a flight and was satisfied of the macro. I Closed the flight and FSX. When I reloaded the NGX, the programmed buttons are functionning, but the macro actions are no more recognized, as if I had never created anything. The macro is under:

It was necessary to change some letters, because when you type a G in the macro, the gear goes down and the letter does not write in the line of the macro, so I replaced it with a j, idem for Shift l which actions the panel light.

My FSUIPC.ini works well with all the other planes and the macros also, so it seems to be related to the PMDG NGX only.

Do you have any idea of what could be wrong ?

[Macros]

Module="PMDG_737NGX.DLL"

1=Battery=RX4ca10*Xe8cc

2=Navlits_ON (i have coupled several actions on the same button, so forget the doubbles)

2.1=RX4df00*X8bcc,31

2.2=RX4df00*X8bcc

2.3=RX4df00*X8bcc

3=NAVlits_OFF

3.1=RX4df00*X8bcc

3.2=RX4df00*X8bcc,31

3.3=RX4df00*X8bcc,31

4=Strobes=RX4df20*X8bcc

5=Taxi

5.1=RX4de40*X8bcc

5.2=RX4de00*X8bcc

5.3=RX4de20*X8bcc,31

6=Beacon=RX4df00*X8bcc,31

7=Climb1=RX4ab60*X8b05

8=TOjA=RX4ab60*X8b05,31

9=landin_lits_ON=RX4dca0*X8bcc

10=landin_lits_OFF

10.1=RX4dcc0*Xa1cc,31

10.2=RX4dd10*Xa1cc,31

10.3=RX4dd60*Xa1cc,31

10.4=RX4ddb0*Xa1cc,31

11=Probes

11.1=RX4d1a0*X8bcc

11.2=RX49100*X8bcc,31

12=landin_Alt_Plus=RX4da90*X8bcc,31

13=WindowHeat

13.1=RX4d140*X8bcc,31

13.2=RX490c0*X8bcc,31

13.3=RX4d160*X8bcc,31

13.4=RX490e0*X8bcc,31

14=landin_Alt_Moins=RX4da90*X8bcc

15=Fuel_Fwd_left=RX4cc60*X8bcc

16=FD=RX43230*Xe8cc,31

17=AT=RX431d0*Xe8cc,31

18=speed=RX43350*Xe8cc

19=N1=RX432f0*Xe8cc

20=speed_Plus=RX43440*X8bcc,31

21=speed_Moins=RX43410*Xe8cc

22=lvl_chan=RX43570*Xe8cc

23=VNAV=RX434f0*Xe8cc,31

24=Headin_sel=RX48d00*X8bcc

25=lnav=RX437d0*X8bcc

26=Vorloc=RX43850*X8bcc

27=APP=RX438d0*X8bcc

28=AltHold=RX43920*X8bcc

29=VS=RX48d40*X8bcc

30=Headin_Plus=RX43680*X8bcc,31

31=Headin_Moins=RX43620*Xe8cc

32=Alt_Plus=RX43970*X8bcc,31

33=Alt_Moins=RX43970*X8bcc

34=SPD_INT=RX43490*Xe8cc

35=Alt_INT=RX48d20*X8bcc

36=Vert_Speed_UP=RX439c0*Xe8cc

37=Vert_speed_DN=RX439c0*Xe8cc

38=Disen_Bar=RX43ba0*X8bcc

39=CMD_A=RX43a20*Xe8cc

40=CMD_B=RX43a80*Xe8cc

41=CWS_A=RX43ae0*Xe8cc

42=CWS_B=RX43b40*Xe8cc

43=ear_Down=RX4ace0*X8bcc

44=ear_UP=RX4ace0*X8bcc,31

45=Course_Plus=RX43130*X8bcc,31

46=Course_Moins=RX43100*Xe8cc

47=Autobreak_Plus=RX49b80*X8bcc,31

48=Autobreak_Moins=RX49b80*X8bcc

49=Altimetre_Plus=RX43e10*X8bcc,31

50=Altimetre_Moins=RX43e10*X8bcc

51=Irs_Moins

51.1=RX4e300*X8bcc

51.2=RX4e320*X8bcc

52=Irs_Plus

52.1=RX4e300*X8bcc,31

52.2=RX4e320*X8bcc,31

53=YawDamper=RX4d060*X8bcc,31

54=Apu_Plus=RX4de60*X8bcc

55=Apu_Moins=RX4de60*X8bcc,31

56=Transpon_Plus=RX4c600*X8bcc,31

57=Transpon_Moins=RX4c600*X8bcc

58=Prev_Power=RX4caa0*Xe8cc

59=Power_Plus=RX4caa0*Xe8cc,31

60=Apu_jen

60.1=RX4cb80*X8bcc

60.2=RX49000*X8bcc

60.3=RX4cb80*X8bcc

61=Winj_Ice=RX49120*X8bcc,31

62=enj_Ice

62.1=RX49140*X8bcc,31

62.2=RX49160*X8bcc,31

63=ext_Power=RX48fe0*X8bcc

64=Bus_Off_ON=RX4cb10*Xe8cc

65=PASS_Sins_Moins

65.1=RX4d410*X8bcc,31

65.2=RX490a0*X8bcc,31

67=PASS_Sins_Plus=RX4d410*X8bcc

68=Isol_Valve=RX4d930*X8bcc

69=Apu_bleed=RX4d990*X8bcc,31

70=Primary

70.1=RX4d8b0*X8bcc,31

70.2=RX4d8d0*X8bcc,31

72=emerjency=RX4d3a0*Xe8cc

73=Packs_Moins

73.1=RX4d910*X8bcc,31

73.2=RX49220*X8bcc,31

74=Packs_Plus

74.1=RX4d910*X8bcc

74.2=RX49220*X8bcc

76=jen_left_=RX4d970*X8bcc

77=jen_rijht=RX49240*X8bcc,31

78=enj_Start_Plus=RX4de80*X8bcc,31

79=enj1_Start_Moins=RX4de80*X8bcc

80=enj2_Start_Plus=RX4dec0*X8bcc,31

81=enj2_Start_Moins=RX4dec0*X8bcc

82=left_aft_pump=RX4cc80*X8bcc

83=rijht_fwd_pump=RX4cca0*X8bcc

84=rijht_aft_pump=RX4ccc0*X8bcc

85=fuel_ctr

85.1=RX4cce0*X8bcc

85.2=RX4cd00*X8bcc

87=crossFeed=RX4cd20*X8bcc

88=elec12

88.1=RX4d280*X8bcc

88.2=RX491a0*X8bcc

90=leftjen=RX49180*X8bcc

91=rijhtjen=RX491c0*X8bcc

92=hydrauliq2

92.1=RX491c0*X8bcc,31

92.2=RX49180*X8bcc,31

93=jenerator2=RX49020*X8bcc

94=jenerator1=RX4cb60*X8bcc

Share this post


Link to post
Share on other sites

I am wondering: I installed the first and second hotfix of PMDG, and FSX asked me to trust the module PMDG_737NGX.dll again. So I have now 3 versions of the PMDG_737NGX in FSX.cfg in the section [Trusted] !!!

Does the macro refers to only one specific version of the DLL ??? I could delete the 2 old versions.

In the same way, the 2 hotfix installed each time a PMDG_HUD_Interface.

I have also 2 instances of FSUIPC.dll.

I will recreate my FSX.CFG to see if it changes anything

Share this post


Link to post
Share on other sites

It was necessary to change some letters, because when you type a G in the macro, the gear goes down and the letter does not write in the line of the macro, so I replaced it with a j, idem for Shift l which actions the panel light.

Yes, I noticed that the PMDG code seemed to intercept some keypresses before FSUIPC can get to them. Most odd -- it only seems to apply to a few.

I am wondering: I installed the first and second hotfix of PMDG, and FSX asked me to trust the module PMDG_737NGX.dll again. So I have now 3 versions of the PMDG_737NGX in FSX.cfg in the section [Trusted] !!!

Does the macro refers to only one specific version of the DLL ??? I could delete the 2 old versions.

In the same way, the 2 hotfix installed each time a PMDG_HUD_Interface.

Mouse macros work by determining the address (inside the aircraft DLL or GAU code) of the routine to be called when you press the button -- the same code it determined was called by the mouse click. In the macro encoding, like "RX4df00*X8bcc" the number X4df00 is the offset address of the code to be called from the start of the named DLL or GAU file. Obviously, if a different version with the same name is loaded, the code being called could have moved.

FSUIPC tries to prevent FS crashing as a result of things moving by checking that the bytes at the address are correct. That's the purpose of the check value X8bcc. If the check fails, the macro does nothing.

If you update an aircraft for which you have made mouse macros, you have to remake them all to update these addresses. There's no easy way I'm afraid.

I have also 2 instances of FSUIPC.dll.

You cannot actually have two copies of the same file with the same name in the same folder. Windows won't allow it and renames the second with "Copy" or similar.

I will recreate my FSX.CFG to see if it changes anything

I don't think any of this is anything to do with FSX.CFG

Regards

Pete

Share this post


Link to post
Share on other sites

Thank You Pete

For the letters of PMDG that actions in the making of the macro, it is the G or g, L but not l, and a third one i can't remember. There are only three.

Thank you for the explanation of the code change. That's why I have my problem, for sure.

As you wrote, i have rebuilt my FSX.cfg without any change....

For the 2 instances of FSUIPC.dll, I spoke of the [TRUST]section of FSX.CFG, i have only one FSUIPC.DLL in the Modules Folder. With my rebuild, I have only the latest one now, no problem.

Is there a way to replace the code which changes without rebuilding all the macro file ??

As you saw, my macro has about one hundred lines, and PMDG will issue some more changes of their DLL, because of the remaining problems (autothrottle disengaging, speed maintains not correctly, no pedestal in 2D, which does not to action the fuel CUT OFF levers in the macro and so on...).

Share this post


Link to post
Share on other sites

For the 2 instances of FSUIPC.dll, I spoke of the [TRUST]section of FSX.CFG.

Oh, yes. I have hundreds in mine! FS recomputes that hash number for every small change, so as I'm testing and debugging I get one added each minor change!

Is there a way to replace the code which changes without rebuilding all the macro file ??

If you know what to change them to -- which probably means disassembling both versions of the DLL or GAU file with something like the IDA disassembler and working out where each entry point has moved to. It's the sort of thing i had to do for my FS hooks in FS9 and before, each time MS updated FS. Somehow I think it is easier to rebuild them, letting FSUIPC do all this sort of work!

As you saw, my macro has about one hundred lines, and PMDG will issue some more changes of their DLL, because of the remaining problems (autothrottle disengaging, speed maintains not correctly, no pedestal in 2D, which does not to action the fuel CUT OFF levers in the macro and so on...).

Yes. Others have noted that it might be better to wait until things settle.

Regards

Pete

Share this post


Link to post
Share on other sites

Hi, i just bought the FSIUPC4.

Could someone tell me how to assign certain things? I have the Thrustmaster Warthog HOTAS and i want to assign for example APU to a 2 position switch. Pos1 - APU start, upon release (which means pos2) - APU OFF. Even i managed to find how to set this up in FSUIPC, the PMDG737 doesnt seems to react on the changes in switch position. What did i do wrong or did i misinterpreted the function?

And i see some members are located in or near Stoke on Trent. I just moved here, so if anyone would like to share sim experience or talk about it over a pint, it would be nice. ;-)

Edited by Libor

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

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.