How to create a mouse macro for the 737 NGX ?

bandini · August 19, 2011

Hi,

I wonder if there is any trick to create a mouse macro with the 737 NGX MCP. It doesn't work "as usual"....impossible to have any fonction working.... I had no problem with the Maddog for example. I tried in the 2d cockpit and virtual cockpit.....no difference.

Thanks if you have any advice.

Cedric

Pete Dowson · August 19, 2011

I wonder if there is any trick to create a mouse macro with the 737 NGX MCP. It doesn't work "as usual"....impossible to have any fonction working.... I had no problem with the Maddog for example. I tried in the 2d cockpit and virtual cockpit.....no difference.

That problem was fixed. Try the latest FSUIPC4 update in the Download Links subforum.

Please also check the other threads on the PMDG 737NGX -- folks have been posting solutions using mouse Macros already. For instance see this thread

PMDG 737 NGX and FSUIPC

Also be warned that as PMDG issue updates, the mouse macros will need re-making.

Regards

Pete

bandini · August 19, 2011

Thanks Pete for that quick anwser.....in fact starting in 2D cockpit I can start my macro.....but impossible to save it. As soon as I'm back in the FSUIPC menu, ending the macro (FSUIPC stated that the macro is ended).....I cannot find my new macro in the listing. And when I return in the cockpit, there is still the green window, and the white text, waiting/monitoring for any inputs. Back to FSUIPC menu, I can only start a new macro....

I just update to the latest fsuipc module.....

Any idea ?

Erasing the fsuipc.ini is the trick ??

Thanks

Cedric

Quick edit: same problem with the MD82 !!!! Before no problem.....now I cannot end my macro......!!!!!!!!!!!

I juste reinstalled FSUIPC and the previous fsuipc.dll.......got the same problem: impossible to save/terminate my macro !

Edited August 19, 2011 by bandini

bandini · August 19, 2011

Oh...by the way: sitting in the cockpit after writing the macro's name, if I press Return, FSX crashes.

I already tried to reinstall a previous fsuipc version without success...

Thanks for any help

Cedric

Andydigital · August 19, 2011

You need to install the interim update that can only be downloaded here in the forum from the download links sub forum > updated modules thread. There is a link below to take you there.

http://forum.simflight.com/topic/66139-updated-modules/page__pid__417029#entry417029

At the time of writing this post it is version 4.726

bandini · August 20, 2011

Hi Andy,

Thanks for your help....but already installed !! The probem is now the same with other airplanes...even trying an older fsuipc dll....nothing to do ! Impossible to effectively save a macro ? Maybe there is something to do with EZdok ? Last soft that I installed, version 1.17 ?

Pete Dowson · August 28, 2011

Thanks for your help....but already installed !! The probem is now the same with other airplanes...even trying an older fsuipc dll....nothing to do ! Impossible to effectively save a macro ? Maybe there is something to do with EZdok ? Last soft that I installed, version 1.17 ?

I don't think Ezdok can interfere with any of this. But I need more information in order to help. What exactly do you mean by these statements please?

1. "sitting in the cockpit after writing the macro's name, if I press Return, FSX crashes."

What sort of "crash? What actually happens? Is there an error message from anything?

2. "I already tried to reinstall a previous fsuipc version without success."

What previous version, and by "without success" do you mean exactly the same thing happened?

3. "I can start my macro.....but impossible to save it. As soon as I'm back in the FSUIPC menu, ending the macro (FSUIPC stated that the macro is ended).....I cannot find my new macro in the listing. And when I return in the cockpit, there is still the green window, and the white text, waiting/monitoring for any inputs. Back to FSUIPC menu, I can only start a new macro."

If FSX crashes as soon as you press Return in order to name the last macro, how do you get as far as re-entering FSUIPC options? This one seems to conflict with #1 above.

Please also show me an FSUIPC log file, using the latest update.

Regards

Pete

bandini · August 28, 2011

Hi Pete, and thank you for your support !

I'm at work now but will try to anwser to your questions (I apologize for my bad english):

1. "sitting in the cockpit after writing the macro's name, if I press Return, FSX crashes."

What sort of "crash? What actually happens? Is there an error message from anything?

Usually, creating macros for the MD82 was not a problem, but now for some reason after typing the macro's name (green window, white text), then going back in FSUIPC menu, hitting "Stop the macro" button....altough it is stated that the macro is stopped, I cannot find my macro in the listing (when I want to use a key combination); as if the macro were not effectively saved. And going back in the cockpit I still have the green window active, waiting for the macro's name ! At that time when I hit "Enter/Return", FSX crashes (CTD). As soon as possible I'll send you the windows event log.

2. "I already tried to reinstall a previous fsuipc version without success."

What previous version, and by "without success" do you mean exactly the same thing happened?

I was initially interesting in upgrading the fsuipc module to use it with the new NGX. Having the above described problem I initially cleared the fsuipc.ini, and also reinstalled the 4.70b version....

3. "I can start my macro.....but impossible to save it. As soon as I'm back in the FSUIPC menu, ending the macro (FSUIPC stated that the macro is ended).....I cannot find my new macro in the listing. And when I return in the cockpit, there is still the green window, and the white text, waiting/monitoring for any inputs. Back to FSUIPC menu, I can only start a new macro."

If FSX crashes as soon as you press Return in order to name the last macro, how do you get as far as re-entering FSUIPC options? This one seems to conflict with #1 above.

As stated above, when I discover the macro function in FSUIPC I never used to hit "Return" to end a macro but just went directly in the FSUIPC menu and stopped the macro for there. I just recently tried to hit "Return" to end the macro, thinking that it will maybe solve my actual problem.....and discover that doing so FSX crashes.

Please also show me an FSUIPC log file, using the latest update.

ASAP.......

Cheers,

Cedric

bandini · August 28, 2011

Hi Pete,

Here is the windows error log when FSX crashes....and it's each time when I hit "Return" when finishing my macro (sorry, in french !!!) :

Nom de l’application défaillante fsx.exe, version : 10.0.61637.0, horodatage : 0x46fadb14

Nom du module défaillant : FSUIPC4.dll, version : 4.7.2.6, horodatage : 0x4e4b0613

Code d’exception : 0xc0000417

Décalage d’erreur : 0x00082008

ID du processus défaillant : 0xd24

Heure de début de l’application défaillante : 0x01cc65b3f959998a

Chemin d’accès de l’application défaillante : G:\Flight Simulator X\fsx.exe

Chemin d’accès du module défaillant: G:\Flight Simulator X\Modules\FSUIPC4.dll

ID de rapport : 373876b6-d1a8-11e0-a414-bcaec592bce3

And I can notice that this is preceded by tree other errors containing "DWORD" error:

Les chaînes de performance dans la valeur de Registre Performance sont endommagées lors du traitement du fournisseur de compteurs d’extension Performance. La valeur BaseIndex à partir du Registre de performance est le premier DWORD dans la section Données, la valeur LastCounter est le deuxième DWORD dans la section Données, et la valeur LastHelp est le troisième DWORD dans la section Données.

Le déchargement des chaînes de compteurs de performances pour le service WmiApRpl (WmiApRpl) a échoué. Le premier DWORD de la section Data contient le code d’erreur.

This is the log, when I made a macro for the CPT FD switch (again no macro saved, and back in the cockpit, the green textbox is still there and receiving any input from the keyboard, waiting for me to enter the macro's name):

********* FSUIPC4, Version 4.726 by Pete Dowson *********

User Name="Cédric Bandelier"

User Addr="bandelier@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

101057 System time = 28/08/2011 21:16:44, Simulator time = 13:29:54 (13:29Z)

101182 Button changed: bRef=0, Joy=1, Btn=20, Released

105300 *** Entered Keys option page ***

117063 *** Exiting Keys option page ***

120183 Mouse by function: RX7a030*X8bcc (flags=20000000), Module="maddog.GAU"

130089 *** Entered Keys option page ***

148123 *** Exiting Keys option page ***

What's interesting: when I quit the active flight, switch to another aircraft.......the FSUIPC macro "mode" is still active......the green box open up and wait for the macro's name.......

So for the test I switched to the 737 ifly, hit "Esc" to quit the macro mode, tried to create a new macro with the ifly......same problem, hitting "Return", and FSX crashes. Here is the full log, containing the previous plus the end of my story....

********* FSUIPC4, Version 4.726 by Pete Dowson *********

User Name="Cédric Bandelier"

User Addr="bandelier@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

101057 System time = 28/08/2011 21:16:44, Simulator time = 13:29:54 (13:29Z)

101182 Button changed: bRef=0, Joy=1, Btn=20, Released

105300 *** Entered Keys option page ***

117063 *** Exiting Keys option page ***

120183 Mouse by function: RX7a030*X8bcc (flags=20000000), Module="maddog.GAU"

130089 *** Entered Keys option page ***

148123 *** Exiting Keys option page ***

261301 Sim stopped: average frame rate for last 113 secs = 58.2 fps

263953 Weather Mode now = Theme

263953 C:\Users\ACH0386\AppData\Roaming\Microsoft\FSX\Vol précédent.FLT

316104 G:\Flight Simulator X\SimObjects\Airplanes\iFly 737-700\iFly737_700_26k.AIR

344575 Aircraft="Boeing 737-700 AirChild VA (Wide screen)"

362468 Button changed: bRef=0, Joy=1, Btn=20, Pressed

362468 [buttons] 5=P1,20,C65752,0

362468 FS Control Sent: Ctrl=65752, Param=0

362499 Button changed: bRef=0, Joy=1, Btn=20, Released

363170 Button changed: bRef=0, Joy=1, Btn=20, Pressed

363170 [buttons] 5=P1,20,C65752,0

363170 FS Control Sent: Ctrl=65752, Param=0

363950 Button changed: bRef=0, Joy=1, Btn=20, Released

365541 Button changed: bRef=0, Joy=1, Btn=20, Pressed

365541 [buttons] 5=P1,20,C65752,0

365541 FS Control Sent: Ctrl=65752, Param=0

408083 KEYUP: VK=27, Waiting=0

411125 KEYDOWN: VK=70, Waiting=0, Repeat=N, Shifts=0

411125 .. Key not programmed -- passed on to FS

411281 KEYUP: VK=70, Waiting=0

479781 KEYDOWN: VK=120, Waiting=0, Repeat=N, Shifts=0

479781 .. Key not programmed -- passed on to FS

479874 KEYUP: VK=120, Waiting=0

480452 KEYDOWN: VK=121, Waiting=0, Repeat=N, Shifts=0

480452 .. Key not programmed -- passed on to FS

480732 KEYUP: VK=121, Waiting=0

486770 Sim stopped: average frame rate for last 127 secs = 62.0 fps

486801 Button changed: bRef=0, Joy=1, Btn=20, Released

487581 *** Entered Keys option page ***

494289 *** Exiting Keys option page ***

495864 Mouse by function: RX196330*Xa1cc (flags=20000000), Module="iFly737-700.GAU"

502354 *** Entered Keys option page ***

552196 *** Exiting Keys option page ***

And the same win 64 log errors: tree times "LoadPerf" as source error and about 2 min later the "Application Error" containing the module name FSUIPC:

Nom de l’application défaillante fsx.exe, version : 10.0.61637.0, horodatage : 0x46fadb14

Nom du module défaillant : FSUIPC4.dll, version : 4.7.2.6, horodatage : 0x4e4b0613

Code d’exception : 0xc0000417

Décalage d’erreur : 0x00082008

ID du processus défaillant : 0xd24

Heure de début de l’application défaillante : 0x01cc65b3f959998a

Chemin d’accès de l’application défaillante : G:\Flight Simulator X\fsx.exe

Chemin d’accès du module défaillant: G:\Flight Simulator X\Modules\FSUIPC4.dll

ID de rapport : 373876b6-d1a8-11e0-a414-bcaec592bce3

If you need some screenshots I can send them maybe per email ?

Again thanks a lot for your help.

Cedric

Pete Dowson · August 28, 2011

Here is the windows error log when FSX crashes....and it's each time when I hit "Return" when finishing my macro (sorry, in french !!!) :

Nom de l’application défaillante fsx.exe, version : 10.0.61637.0, horodatage : 0x46fadb14

Nom du module défaillant : FSUIPC4.dll, version : 4.7.2.6, horodatage : 0x4e4b0613

Code d’exception : 0xc0000417

Décalage d’erreur : 0x00082008

ID du processus défaillant : 0xd24

Heure de début de l’application défaillante : 0x01cc65b3f959998a

Chemin d’accès de l’application défaillante : G:\Flight Simulator X\fsx.exe

Chemin d’accès du module défaillant: G:\Flight Simulator X\Modules\FSUIPC4.dll

ID de rapport : 373876b6-d1a8-11e0-a414-bcaec592bce3

Hmm. Thanks. Error 0xC0000417 is "STATUS_INVALID_CRUNTIME_PARAMETER #An invalid parameter was passed to a C runtime function." which is interesting. A worry, though, is the address: 0x00082008, which cannot be in FSUIPC4 -- that's part of FSX.EXE I think (I'll check). FSUIPC loads at "Module base=61000000", so possibly it means 61082008. I'll see if that's feasible.

I'll get back to you if i need more information, but it won't be until tomorrow now.

Regards

Pete

Pete Dowson · August 28, 2011

I'll get back to you if i need more information, but it won't be until tomorrow now.

I'm just having a quick look at my code for macro file finalisation before I go to bed.

The only extra information I think I need from you is the NAME of the macro file you ask for, and some examples of the names of the macros you are attempting to create. I've a strong feeling it's to do with the naming.

[LATER]

No, it isn't naming as far as I can tell. I managed to reproduce it only once, but i did manage it. it seems to be timing. There's a delay after selecting "End macro making" and the macro name entry window being cleared. It's hardly noticeable here, but if you catch it before it disappears, then you get the problem. If your disk system is slow to check and update the files being manipulated it will probably give more time for this to happen, and the complexity and continual activity of the NGX exaggerates this.

I can put safeguards in to stop this, and will do so. Meanwhile could you simply wait a while after selecting End macro in the Options, stay in the options for a few more seconds, then, when exiting to flight mode, wait a few more seconds.

This is just as a test. Let me know if it still occurs even then, please.

Regards

Pete

bandini · August 29, 2011

Hi Pete,

I found something interesting.....and quite sure FSUIPC is'nt the culprit: as stated previously I had a problem with DWORD - LoadPerf..when I checked the windows log. I did a quick research on the web, found that link (http://forums.majorgeeks.com/showthread.php?t=118418) and tried the command Lodctr /r ...and seems it did the trick. No more error in the windows log, and managed to create a macro.....only once because I dont have much time right now !

Will try later or tomorrow and let you know if everything works.

I'm really a newbie, so I absolutely dont understand what is the problem (LoadPerf, DWORD, BaseIndex etc....)......if you know about that, would be interesting to know why I got this problem suddenly ? Any addon ? Any firewall or antivirus ?

Anyway, thanks a lot for the time that you take for solving my problem.

Have a nice week

Regards

Cedric

Pete Dowson · August 29, 2011

I found something interesting.....and quite sure FSUIPC is'nt the culprit: as stated previously I had a problem with DWORD - LoadPerf..when I checked the windows log.

Yes, but I don't understand those words and you didn't show the error log entries.

I did a quick research on the web, found that link (http://forums.majorg...ad.php?t=118418) and tried the command Lodctr /r ...and seems it did the trick. No more error in the windows log, and managed to create a macro.....only once because I dont have much time right now !

Hmmm. Interesting.

I'm really a newbie, so I absolutely dont understand what is the problem (LoadPerf, DWORD, BaseIndex etc....)......if you know about that, would be interesting to know why I got this problem suddenly ? Any addon ? Any firewall or antivirus ?

Well, I'm not really a newbie, but I don't know anything about all that either. But checking the reference you provided, this part:

To rebuild the string tables, on the computer that displayed the message, at the command prompt, type Lodctr /r
The contents of the string tables are automatically rebuilt.

basically points to the diagnosis that an important system file somehow became corrupted. Maybe you had a complete system crash at some pooint, or sudden loss of power? Those are the usual occasions you get sudden file corruption, when it coincides with some disk write action.

Anyway, having seen exactly what can happen in FSUIPC, I've taken steps in my code to prevent an FS crash in the circumstances you encountered. As I said, I even managed to reproduce it once -- but without your three "DWORD - LoadPerf" errors. The next interim update for FSUIPC will be "crashproof" in this regard.

Regards

Pete

bandini · August 30, 2011

Hi Pete,

It seems that my problem is solved with the previously mentionned tips...."my macros are back".....

And by the way....no "latency problems"....

Again thanks for your kind support !

Have a nice week,

Cheers

Cedric

How to create a mouse macro for the 737 NGX ?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Important Information