Jump to content
The simFlight Network Forums
oldJ3pilot

Mouse Macro Making-odd problem

Recommended Posts

I have made quite a few mouse macros for the Majestic Dash 8 and Duke B60 without any problems. Yesterday, after setting "create mouse macro", etc. I could not get any macros....regardless of which plane or which buttons/switches tried (even for those that I had already obtained)).

After shutting down FSX and restarting it, still no macro. Finally after restarting the PC the process worked as intended.

As far as I recall, there have been no changes made to either the PC or FSX.

Has anyone run across this problem? I hate to lose the mouse macro making, particularly with thes new and complicated planes.

System is Win7 Ultimate 64bit, FSUICP V4.9, FSX Acceleration.

Help appreciated

Neal Howard

Addendum: I just restarted Windows, FSX, and mouse macro still will not work.

Fixed! :D See my last post in this thread for details

Share this post


Link to post
Share on other sites

Make sure your viewpoint is not inside the seat geometry behind where your head is in the game. If you are inside geometry then you can't click anything in the VC and thus it would look like mouse macros weren't working.

Share this post


Link to post
Share on other sites

I failed to mention that all the actions work using the mouse just as they normally do. right/left clicks, wheel rotations make the dials, buttons, and switches function. None of the actions get the green or res dialogue box. I just tried to reproduce the saame macros that were created three days ago but no joy. Just moved to FSUIPC 4.903 hoping for a fix but......no luck

I looked at the FSUIPC4.log file but there were no obvious errors or faults in it. It is a bit beyond me to read and analyze.

Thanks

Neal Howard

Share this post


Link to post
Share on other sites

Problem resolved: I did a new full install of FSUIPC and mouse macros can again be created. I remembered that once before some program stopped working and it was caused by changes in the dll.xml file. Maybe this reinstall corrected it (wish I had looked at it before the reinstall)

If this problem occurs for someone else then perhaps this might help fix it.

Thanks all

Neal Howard

Share this post


Link to post
Share on other sites

Ran across this thread today.  I have been trying to make a mouse macro in some of these same aircraft (B60, Majestic Dash 8, Citation X, Default C172) and it's not working.  I click "Create Mouse Macro", give it a name, click OK and then click on various switches, places in the aircraft but never get the dialog that's supposed to appear.  I see log messages like "Mouse by function:" or "Mouse, 14".  I have FSX SP2 and the latest version of FSUIPC,   I rebooted my computer, Reinstalled FSUIPC twice to no avail.  Any ideas?

 

Gregg

Share this post


Link to post
Share on other sites

Ran across this thread today.  I have been trying to make a mouse macro in some of these same aircraft (B60, Majestic Dash 8, Citation X, Default C172) and it's not working.  I click "Create Mouse Macro", give it a name, click OK and then click on various switches, places in the aircraft but never get the dialog that's supposed to appear.  I see log messages like "Mouse by function:" or "Mouse, 14".  I have FSX SP2 and the latest version of FSUIPC,   I rebooted my computer, Reinstalled FSUIPC twice to no avail.  Any ideas?

 

Mouse macros only work on gauges specifically written using the FS C/C++ gauge SDK. Even most of Microsoft's own gauges don't do this, and more and more modern gauges are written differently, often using XML instead. If the window doesn't appear when you click the mouse on a spot then that gauge isn't amenable to mouse macros.

 

Reinstalling FSUIPC never achieves anything, because all you are doing is replacing the DLL with the same DLL (unless you are updating ... that's different).

 

Pete

Share this post


Link to post
Share on other sites

Mouse macros only work on gauges specifically written using the FS C/C++ gauge SDK. Even most of Microsoft's own gauges don't do this, and more and more modern gauges are written differently, often using XML instead. If the window doesn't appear when you click the mouse on a spot then that gauge isn't amenable to mouse macros.

 

Reinstalling FSUIPC never achieves anything, because all you are doing is replacing the DLL with the same DLL (unless you are updating ... that's different).

 

Pete

 

See, that's what I was thinking too.  But when I saw that someone was able to create macros for the B60 and Dash 8 I thought that maybe there's something wrong.  Also, another person told me that they have had success making mouse macros for the Citation X for their hardware (which is the only reason I'm trying this at all...this is not my preferred method of doing this stuff).  Is there any clue in the fact that I am getting the log messages or is that just log noise?

Share this post


Link to post
Share on other sites

See, that's what I was thinking too.  But when I saw that someone was able to create macros for the B60 and Dash 8 I thought that maybe there's something wrong.  Also, another person told me that they have had success making mouse macros for the Citation X for their hardware (which is the only reason I'm trying this at all...this is not my preferred method of doing this stuff).  Is there any clue in the fact that I am getting the log messages or is that just log noise?

 

Show me the log messages please.

 

Pete

Share this post


Link to post
Share on other sites

Here's from the Turbine Duke...

Console Started ...

   157047 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   162164 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   167717 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll"
   167717 *** EVENT: Cntrl= 66364 (0x0001033c), Param= 0 (0x00000000) TOGGLE_ALTERNATOR2
   172631 Memory in use: 1956Mb, Avail=2140Mb
   176235 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   179058 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   179058 *** EVENT: Cntrl= 66338 (0x00010322), Param= 0 (0x00000000) TOGGLE_PROPELLER_DEICE
   181492 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   181492 *** EVENT: Cntrl= 65560 (0x00010018), Param= 0 (0x00000000) STROBES_TOGGLE
   184550 Mouse by function: RXf230*X8bcc,14 (flags=00004000), Module="window.dll"
   184565 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN
   188528 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   191835 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll"
   193957 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   197155 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   199401 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dll"
   199401 *** EVENT: Cntrl= 66855 (0x00010527), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_5
   202209 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
   204097 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_1
   204097 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 64 (0x00000040) VIEW_ZOOM_SET

From the Q400...

412233 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
413122 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
413731 Memory in use: 2349Mb, Avail=1747Mb
425805 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
427162 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
427771 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
429331 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
430704 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
431998 Mouse,14 (flags=00004000), Module=""
434526 Mouse,14 (flags=00004000), Module=""
435867 Mouse:  (flags=20000000), Module=""
435883 Mouse:  (flags=20000000), Module=""
436476 Mouse:  (flags=20000000), Module=""
437006 Mouse:  (flags=20000000), Module=""
437583 Mouse:  (flags=20000000), Module=""
438519 Mouse:  (flags=20000000), Module=""
441171 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
442139 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
443433 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
444323 Mouse:  (flags=20000000), Module=""
444853 Mouse:  (flags=20000000), Module=""
445883 Mouse,13 (flags=00002000), Module=""
446522 Mouse,14 (flags=00004000), Module=""
446694 Mouse,14 (flags=00004000), Module=""
446897 Mouse,14 (flags=00004000), Module=""
448862 KEYDOWN: VK=70, Waiting=0, Repeat=N, Shifts=0
448862 .. Key not programmed -- passed on to FS
448862 *** EVENT: Cntrl= 65569 (0x00010021), Param= 0 (0x00000000) DME
448862 *** EVENT: Cntrl= 66514 (0x000103d2), Param= 0 (0x00000000) ATC_MENU_C
448909 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMER
448909 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 65 (0x00000041) VIEW_ZOOM
449003 KEYUP: VK=70, Waiting=0
452138 Mouse by function: RXedb0*X8bcc,13 (flags=00002000), Module="window.dl
453573 Mouse by function: RXedb0*X8bcc,14 (flags=00004000), Module="window.dl
464088 *** EVENT: Cntrl= 66851 (0x00010523), Param= 0 (0x00000000) VIEW_CAMER
464088 *** EVENT: Cntrl= 65701 (0x000100a5), Param= 62 (0x0000003e) VIEW_ZOOM
468097 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
469735 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
473994 Memory in use: 2353Mb, Avail=1743Mb
474010 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
475772 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
476740 Mouse,14 (flags=00004000), Module=""
477395 Mouse,13 (flags=00002000), Module=""
478346 Mouse,14 (flags=00004000), Module=""
478861 Mouse,13 (flags=00002000), Module=""
479891 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
481186 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
481872 Mouse,14 (flags=00004000), Module=""
482402 Mouse,13 (flags=00002000), Module=""
483448 Mouse,14 (flags=00004000), Module=""
484586 Mouse,13 (flags=00002000), Module=""
486162 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
486240 *** EVENT: Cntrl= 65751 (0x000100d7), Param= 1 (0x00000001) LANDING_LI
486880 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
489500 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
490358 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
490452 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 1 (0x00000001) TOGGLE_NAV
491809 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
492683 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
493541 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
494149 Mouse by function: RXedb0*X8bcc (flags=20000000), Module="window.dll"
494742 Mouse,14 (flags=00004000), Module=""

From the Default C172 (tried in both 2D and 3D cockpit...

 777915 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
 783937 Mouse Event=65883
 783937 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 0 (0x00000000) KOHLSMAN_I
 785294 Mouse Event=65884
 785294 *** EVENT: Cntrl= 65884 (0x0001015c), Param= 0 (0x00000000) KOHLSMAN_D
 786043 Mouse Event=65883
 786043 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 0 (0x00000000) KOHLSMAN_I
 786698 Mouse Event=65884
 786698 *** EVENT: Cntrl= 65884 (0x0001015c), Param= 0 (0x00000000) KOHLSMAN_D
 789350 Mouse:  (flags=20000000), Module=""
 790114 Mouse:  (flags=20000000), Module=""
 791550 Mouse Event=65560
 791550 *** EVENT: Cntrl= 65560 (0x00010018), Param= 0 (0x00000000) STROBES_TO
 792205 Mouse Event=65858
 792205 *** EVENT: Cntrl= 65858 (0x00010142), Param= 0 (0x00000000) PITOT_HEAT
 793297 Mouse:  (flags=20000000), Module=""
 793297 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV
 794841 Mouse Event=66239
 794841 *** EVENT: Cntrl= 66239 (0x000102bf), Param= 0 (0x00000000) TOGGLE_BEA
 795840 Mouse Event=66339
 795840 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELE
 797790 Mouse:  (flags=20000000), Module=""
 797790 *** EVENT: Cntrl= 66242 (0x000102c2), Param= 0 (0x00000000) TOGGLE_MAS
 797790 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 0 (0x00000000) TOGGLE_MAS
 809755 Mouse Event=65877
 809755 *** EVENT: Cntrl= 65877 (0x00010155), Param= 0 (0x00000000) GYRO_DRIFT
 810582 Mouse Event=65878
 810582 *** EVENT: Cntrl= 65878 (0x00010156), Param= 0 (0x00000000) GYRO_DRIFT
 811190 Mouse Event=65877
 811190 *** EVENT: Cntrl= 65877 (0x00010155), Param= 0 (0x00000000) GYRO_DRIFT
 813265 Mouse Event=65880
 813265 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BU
 813717 Mouse Event=65879
 813717 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BU
 814872 Mouse Event=66240
 814872 *** EVENT: Cntrl= 66240 (0x000102c0), Param= 0 (0x00000000) TOGGLE_TAX
 815761 Mouse Event=66379
 815761 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV
 818397 Mouse Event=66317
 818397 *** EVENT: Cntrl= 66317 (0x0001030d), Param= 0 (0x00000000) TOGGLE_ALT
 835745 Memory in use: 2199Mb, Avail=1897Mb
 837180 Mouse:  (flags=20000000), Module=""
 837195 *** EVENT: Cntrl= 66464 (0x000103a0), Param= 0 (0x00000000) COM2_TRANS
 838116 Mouse:  (flags=20000000), Module=""

Share this post


Link to post
Share on other sites

All of the mouse macro log entries which trap a call show that the function being called when you use the mouse are in FS's generic screen utilities module, "window.dll", not in a specific GAU (gasuge) file. I'm afraid those functions, in those panels, aren't susceptible to mouse macros.

 

Your attempts with the C172 all use normal FS controls, as you can see.  For example:

 

815761 Mouse Event=66379
815761 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV

 

No need for Mouse Macros for functions you can simply assign to a control!

 

Pete

Share this post


Link to post
Share on other sites

Welp, shrugs then.  I clicked on lots of stuff in each...how/why the other person had some success in those planes is a mystery then.  I'd rather program hardware other ways anyway.

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

×

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.