Jump to content
The simFlight Network Forums

Mouse Macros in Version 4.719


Recommended Posts

One more thing. Mouse Macro creation is not working for me since I upgraded to version 4.719. I can use existing macros, but can't create new ones. After I select "Create Mouse Macro" in the GUI and go back to the sim to click on the 2D panel, it starts detecting all sort of spurious inputs and I can't save the Macro

I tried unplugging everything, even my keyboard with the same results. Also tried deleting the ini file and letting FSUIPC build a default one in case it was something in my config. Going back to v4.6 fixes it

anyone else with the same problem please?

Link to comment
Share on other sites

One more thing. Mouse Macro creation is not working for me since I upgraded to version 4.719.

There's been no change in such areas in 4.719.

I can use existing macros, but can't create new ones. After I select "Create Mouse Macro" in the GUI and go back to the sim to click on the 2D panel, it starts detecting all sort of spurious inputs and I can't save the Macro

Can you give me any more details? What are these "spurious inputs"? Where are you seeing them?

If you mean only with the PMDG 737NGX, that's known and is due to the constant FSX control sending the PMDG panels send when the mouse pointer is over a button or switch. I don't think mouse macros will be usable with that aircraft in any case.

I tried unplugging everything, even my keyboard with the same results. Also tried deleting the ini file and letting FSUIPC build a default one in case it was something in my config. Going back to v4.6 fixes it

Do you mean to say you've used no versions between 4.60 and 4.719 and you only just changed from 4.60? Didn't you install 4.70 before 4.719? you should have.

[LATER]

Just to double-check, I just used 4.719 to create several mouse macros for the default FSX Cessna 172. It worked fine.

Regards

Pete

Link to comment
Share on other sites

There's been no change in such areas in 4.719.

Can you give me any more details? What are these "spurious inputs"? Where are you seeing them?

If you mean only with the PMDG 737NGX, that's known and is due to the constant FSX control sending the PMDG panels send when the mouse pointer is over a button or switch. I don't think mouse macros will be usable with that aircraft in any case.

Do you mean to say you've used no versions between 4.60 and 4.719 and you only just cahnged from 4.60? Didn't you install 4.70 before 4.719? you should have.

Regards

Pete

Ok, it only happens in PMDG A/C (tried the NGX and the MD11 and both have the same problem but the Maddog works fine)

Admittedly I just dropped 4.719 in the modules folder, yes, but I just reinstalled with the same results. What is weird is that v4.628 works flawlessly. These NGX mouse macros were created yesterday with that version of FSUIPC4:

[Macros]

Module="PMDG_737NGX.DLL"

1=AP HDG+=RX437c0*X8bcc,31

2=GEAR DOWN=RX4ab70*X8bcc

3=GEAR UP=RX4ab70*X8bcc,31

4=RST=RX43e30*X8bcc

5=MINS-=RX43e50*X8bcc

6=MINS+=RX43e50*X8bcc,31

7=BARO+=RX43ef0*X8bcc,31

8=MINS BARO=RX43e10*X8b05,31

9=BARO STD=RX43ed0*X8bcc

10=BARO-=RX43ef0*X8bcc

11=MINS RADIO=RX43e10*X8b05,14

12=BARO HPA=RX43eb0*X8bcc,31

13=BARO IN=RX43eb0*X8bcc

The problem is that it detects mouse hovers as clicks, yes, and even with the mouse in the middle of nowhere, or once the macro has been ended, the message to name the macro still shows up out of the blue sometimes

I'll keep on investigating to make sure it's not a problem in my end

Link to comment
Share on other sites

Ok, it only happens in PMDG A/C (tried the NGX and the MD11 and both have the same problem but the Maddog works fine)

I think it's to do with their sending of FS controls all the time, at the rate of something like 10-20 per second. I've not seen iyt before, but it certainly occurs with the 737NGX.

Admittedly I just dropped 4.719 in the modules folder, yes, but I just reinstalled with the same results.

reinstalled what? 4.719 or 4.70 using the Installer.

What is weird is that v4.628 works flawlessly.

Yes, it is, and i'd like to know why. I'll need to narrow it down. There's something like 30 versions between 4.628 and 4.719. Can you please install 4.70 using the Installer and re-echeck?

I'll keep on investigating to make sure it's not a problem in my end

Well, I get the problem on the NGX, so you need not do that. I'll try to narrow down which version changed it.

Regards

Pete

Link to comment
Share on other sites

reinstalled what? 4.719 or 4.70 using the Installer.

Tried a complete reinstall of 4.703: deleted the Modules directory and started fresh with the installer + activation

Well, I get the problem on the NGX, so you need not do that. I'll try to narrow down which version changed it.

Please let me help you with this. Is there a way I can download previous versions and try them out?

Link to comment
Share on other sites

Tried a complete reinstall of 4.703: deleted the Modules directory and started fresh with the installer + activation

You didn't need to go that far. It's only the DLL we're interested in. Just run the 4.703 installer.

What was the result? It's different here, but only I think because of the extra logging it does automatically, which doesn't give Windows time to make the entry window flash at all.

Please let me help you with this. Is there a way I can download previous versions and try them out?

No. I can see the difference -- especially in the Mouse flags it sees -- but I'll have to trace through the code to see why. It needs my debug tools.

I'll get back to you when I've got somewhere. Might take a while.

Regards

Pete

Link to comment
Share on other sites

You didn't need to go that far. It's only the DLL we're interested in. Just run the 4.703 installer.

What was the result? It's different here, but only I think because of the extra logging it does automatically, which doesn't give Windows time to make the entry window flash at all.

No. I can see the difference -- especially in the Mouse flags it sees -- but I'll have to trace through the code to see why. It needs my debug tools.

I'll get back to you when I've got somewhere. Might take a while.

Regards

Pete

Version 4.703 does the same thing as 4.719. I can see mouse macro events within miliseconds in the log triggered just by hovering the mouse over the clickspots:

285607 Mouse by function: RX43ca0*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285607 *** EVENT: Cntrl= 70316 (0x000112ac), Param= 4194304 (0x00400000) <unknown>
   285607 Mouse by function: RX43ca0*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285607 *** EVENT: Cntrl= 70316 (0x000112ac), Param= 4194304 (0x00400000) <unknown>
   285654 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285654 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285654 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285654 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285654 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285654 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285654 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285654 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285654 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285669 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285669 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285669 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285669 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285669 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>
   285669 Mouse by function: RX44090*X8bcc,19 (flags=000CF94C), Module="PMDG_737NGX.DLL"
   285669 *** EVENT: Cntrl= 70007 (0x00011177), Param= 4194304 (0x00400000) <unknown>

So yeah, that's it (not out of the blue like I said)

Pete, take your time, or schedule it depending on what you think is best for you and FSUIPC. We can always use the control events log (what a great little feature this and Lvars) or simple switch back to 4.6 temporarily

Actually I'm done configuring my hardware in the NGX already, even without the SDK thanks to FSUIPC, so no hurries on my part

Link to comment
Share on other sites

Version 4.703 does the same thing as 4.719. I can see mouse macro events within miliseconds in the log triggered just by hovering the mouse over the clickspots:

Yes. I've found it.

The clue was in this value:

flags=000CF94C

which is nonsense for Mouse flags.

It's all down to a Typo, introduced to deal with differences between Prepar3D's first release (which was like FSX and ESP) and the later update. Because of the Typo, FSUIPC was taking the new Prepar3D route for mouse interception, picking up the Mouseflags from the wrong register.

What surprises me is that the facility still appears to work on some panels. I don't know how -- the mouseflags are rubbish, so it cannot distinguish left/right/central clicks, or clicks at all for that matter. It seems it's taken the release of the NGX for folks to find out!

I'm working on the fix now. Will upload an update later. Probably 4.721.

Pete

Link to comment
Share on other sites

Yes. I've found it.

The clue was in this value:

flags=000CF94C

which is nonsense for Mouse flags.

It's all down to a Typo, introduced to deal with differences between Prepar3D's first release (which was like FSX and ESP) and the later update. Because of the Typo, FSUIPC was taking the new Prepar3D route for mouse interception, picking up the Mouseflags from the wrong register.

What surprises me is that the facility still appears to work on some panels. I don't know how -- the mouseflags are rubbish, so it cannot distinguish left/right/central clicks, or clicks at all for that matter. It seems it's taken the release of the NGX for folks to find out!

I'm working on the fix now. Will upload an update later. Probably 4.721.

Pete

Great stuff Pete! Glad to here it's tackled and that it involves a simple fix.

Actually I first came across the issue back in may, but never got round to testing it until now. But who cares :D

Thanks a lot

Link to comment
Share on other sites

Pete,

Version 4.721 works fine. If people are not looking at the macro with an editor after making changes there may be multiple steps that confuse NGX. That happened to me first try. I just edited out duplicates and it worked fine. Also gave me a chance to clean up the key names. I know most users will know that but thought it might to be new to some reading this topic. I posted my MCP macro in another thread.

Ed F.

Link to comment
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
×
×
  • 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.