John Dowson

Map them how? There is currently no way to access lvars from FSUIPC7. John

Is this after the latest Asobo update? I've not looked at this yet, but I'll take a look shortly... Yes - I get the same behavior. For me, it only goes into reverse thrust if I toggle when I have some forward thrust applied, but then any movement reverts back to forward thrust. I will report this to Asobo. John

Could you also let me know the name of the PMDG header file that contains a description of the rotor brake parameters that you are using, I don't have the PMDG aircraft but I should have the header files around somewhere... John

Ok, glad your problem is solved. FSUIPC always uses the class name FS98MAIN - for the dll version (FSUIPC4,5,6) it subclasses the FS class window, but for FSUIPC7 it creates its own. John

As you are using Files for profiles, can you also attach your ini file for your B738U profile please. Your log shows that you are using the ROTOR_BRAKE control with various parameters. Are these valid for the PMDG aircraft? I thought PMDG used lvars together with its own FSUIPC offset area, not rotor brake codes which are used by FSLabs and others. Also, which logging entries (if any) show the correct increments when using the mouse? John

I'm not sure why that mouse macro isn't working. You could try with a different mouse flag, or use multiple actions. e.g. try with: or John

I have deleted your post post as it published your registration details. NEVER publish your egistration details on a public forum or your key will be invalidated. I've sent you a PM. You need to uninstall the 2015, 2017 and 2019 versions (any and all that you have installed), then install the 2015 + 2017 + 2019 combo package from here: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads John

Auto-save is already implemented. However, there are currently issues with the MSFS SDK functions that are used to save and load flights - from the SDK documentation: It won't be possible to use the auto-save feature until Asobo have fixed these issues. John

Yes, sounds strange...I've no idea what's occurring. Keep the logging activated, and send me the files the next time you experience your issue. John

Yes, your description of the tests indicates that this is somehow causing your issue. Ok, please do. And attach you FSUIPC7.ini as well. John

There has been a few posts on the MobiGlight WASM module recently, most recently here: Looks very interesting. I'm going to look into this next week to understand this better and see what I can do in FSUIPC7. I'll let you know - please be patient. John

I've heard this mentioned a few times now, most recently here: Thanks for the link. I will look into this shortly to see what I can do. John

Hi Norman, Looks like a Linda issue, so you should post in the Linda forums: https://www.avsim.com/forums/forum/429-linda-support/ John

I'm not sure of your issue.... You can use mouse macros however you wish, but its usual to assign them to a button or switch. You can also activate them via a key press ot from a lua script if you so wish. As for the control of the QW787, I think you are probably better off asking over on their forums. I don;t have this aircraft, and so not sure what they expose i.e. lvars) to control. Maybe try here: http://qwsim.flight1.net/forums/lvar_topic12252.html John

No. But you log is very strange: This shows that closed and re-connected a few times (connected after 8s, disconnected at 11sm connected at 93s then disconnected again at 134s, reconnecting again at 2096seconds...MSFS closed 26s later), but was closed for the majority of your session! FSUIPC7 will change the focus to to MSFS only to send a key press. Do you have key press assignments to buttons on repeat by any chance? Could you enable logging for events and buttons and produce a log file when you have your issue. Attach that, together with your FSUIPC7.ini file and I'll take a look. John

Not without further information. Could you activate event logging and produce a log file showing your problem (complete please - don't start a new log file!). Also increase or decrease using the mouse afterwards, to see hat that logs. Attach that log file, together with your .ini file and I'll take a look. John

First, please update to v7.0.4. Only the latest version is supported. Not! FSUIPC7 will try to assign (by default) ALT-F as a hot-key to open the FSUIPC7 main window. You can change or disable this - please see the user guide for details. Other than that, FSUIPC7 will request key input events for (almost) all keys, but requests them unmasked and so should not affect any other SimConnect clients, let alone other windows applications! And FSUIPC7 still works as expected? Is there any difference in the FSUIPC7 logs when starting your app before or after FSUIPC7? John

You need to know the event ids and assign them as custom events. There is an 'add-on custom events' facility (see p36 of Advanced User Guide), but the event names you mention don't contain a period as mentioned in the documentation. I haven't used that facility up to now, maybe @Pete Dowson can clarify.

@David Brewster Thanks for these detailed instructions. The scripts are already available in the User Contributions sub-forum, but without detailed usage instructions. I have moved your post to the FAQ sub-forum, and will link to this in the script posts. John

Is this after the latest Asobo update? I've not looked at this yet, but I'll take a look shortly... John

What has changed? Can you try with the vanilla A320Neo to see if it works there, and if so you need to report to FBW. I don't have much time today but I can check tomorrow. John

Yes, but I'll be releasing a new version soon with this fixed. I was hoping to release later today but it will more likely be tomorrow.

Have you verified the script is running? Did you add it to the [Auto] section of your FSUIPC ini file? Please attach your FSUIPC7.ini and FSUIPC7.log files and I'll take a look. John

First, you posted in the FAQ section where it explicitly says NOT for support requests. I have moved your post for you this time, but please take care to post in the correct forum for any future support requests. There are so many posts on this topic now. There are dedicated lua scripts for the Honeycomb Alpha and Bravo, please see If using the Bravo, to control the LEDs you can also use this: John

First, you are saying you are using offset 0x66D0, but your script is actually using 0x66E0 - just FYI. But the main problem is that you have wrapped the calls in a function - what is calling the function? If you are assigning the script to a button press, then you don't need the function, i.e. just ipc.macro("RJ85LNAVPress: press") ipc.writeSW(0x66E0,1) Otherwise, you could add an event.button() call to call the button on a button press - this would be more efficient as the script would not have to be recompiled each time it was executed. You are also setting this value as a signed word (SW). Thats fine, but if it is only holding 0/1, you could use an unsigned byte. John