John Dowson

It will be a false positive. Either temporarily disable your anti-virus or allow it yo be downloaded/unzipped.

Please see the provided README.txt (the clue is in the name!):

That sounds very strange.... Have you extracted the installer from the zip file, and not running it from within the zip file (as can happen sometimes...)? Otherwise try re-installing the VC++ redistributables - instructions in the README.txt. Maybe you previously registered with a different email? Sorry, but I can't really help with this - try the simflight forum support - from the 'Contact Us' link at the bottom of your page. Your FSUIPC license information will be available from your SimMarket account. John

Look ok to me....

Does this mean that when you initially start P3D, its working? Or its not working at all and you need to activate/deactivate to get it to work every time? Could you add the following to the [General] section of your FSUIPC6.ini file: Debug=Please LogExtras=4 This should then log auto-save activity. If you can produce a log file where auto-save isn't working as you expect, show me that file together with your FSUIPC6.ini and I will take a look. I will also test here to see if I can reproduce. John

Hmm, sounds strange...I will take a look. Which version of P3D, and which version of FSUIPC are you using? John

You could run a script on Ctrl+E and then in the script use the event.key function to wait for a keypress (1,2, or 3, so 3 event.key functions) and then, in the keypress function, call the functions to open/close/toggle the appropriate door, based on the key pressed, and then exit. You my also want to add a timer so that if no keypress is received within a certain amount of time, the script also exits. Alternatively, if the time taken to compile and run the lua script on the Ctrl+E keypress takes solong that the 1,2,3 keypress is missed (i.e. pressed before the event.key calls are registered), you could start a script in your DC6 [Auto] section that waits for the CTR+E keypress, and when received add the even.key calls to the 1,2,3 keys, and in the function that handles the 1,2,3 keys you can toggle the appropriate door and then use event.cancel to remove the 1,2,3 key press event. John

Your FSUIPC4 key will still be valid. If you entered your details previously (on your old PC) and they validated there then they will do again on your new PC. Both the name and address/email parts must exactly match those specified in your SimMarket account/purchase email. You can also just transfer the key file (FSUIPC4.key) from your old PC, if available, to your new one. John

Hi Leo, looks like the only issue was the CTD in test 6, but that looks like it was MSFS that crashed, and so FSUIPC exited. Thanks for the update. John

But the ini you posted shows that you have no axes assignments configured at all in FSUIPC7! Have you assigned your axis in MSFS? Have you tried to configure via FSUIPC7? John

In the next FSUIPC7 release, I will add 0x07CE 2bytes - AUTOPILOT HEADING LOCK DIR:3 0x07F8 2bytes - AUTOPILOT VERTICAL HOLD VAR:3 John

Apologies for my previous reply, I wasn't having a very good day... I still don't particularly want to continue this conversation, but I would like to clarify a few points. First, it should be clear the facilities that FSUIPC provides from the documentation. It is also a free-to-use product for many facilities, with additional functionality provided if you purchase a license. I also offer an extended trial license, so all users can try FSUIPC7 before they buy. We recommend that all users actually try FSUIPC before purchasing - it is not a utility that suits all/many users. This implies that you expect me to understand every single aircraft, both stock, add-ons, and all mods, including those aircraft that will be released tomorrow, next week, etc? To look into the code of every single aircraft (no documentation is provided on how an aircraft is implemented or what variables it actually uses) to see what simvars (A, L, H, etc) they use, and then somehow map them to an appropriate offset. This is a completely unreasonable expectation. FSUIPC extracts simvars (or A variables), as well as local variables (lvars) and makes them available for use. It is up to the user to know what variable to use, we only provide the facilities to give access to such variables. There are many resources on how to use such variables, one of the best being the MobiFlight community-driven website https://hubhop.mobiflight.com/#/. You need to use such resources, as well as the Asobo forums and documentation, especially for control of complex aircraft such as the A320. Of those, only AUTOPILOT HEADING LOCK DIR:3 and AUTOPILOT VERTICAL HOLD VAR:3 are currently not held in any offset. They can, of course, be added - I do this on user request. If added, they will be added to specific offsets. As I said, FSUIPC just provides access to such information, it is up to the user to determine how this information is to be used. I know that there is a lot that can be done to improve the usability of FSUIPC, especially FSUIPC7 where there is more of a need to resort to using lvars. hvars and calculator code. I do have various ideas to make this are more user-friendly, but being a one-man team I find very little time for new development these days as so much time is spent on user support....and developing against the MSFS SDK over the past 1.5 years is also very difficult, especially earlier on with the lack of documentation and the constantly changing SDK... I could go on but I don't see much point. Constructive criticism is welcomed, but I think your expectations are way over the top and are missing the point on what FSUIPC is actually intended for. John

@Edoradar Please try the attached version, v6.1.6b. I have added those simvars (read-only) at the following offsets, all 8-byte/64-but floats: 0x7C00 - EMPTY WEIGHT PITCH MOI 0x7C08 - EMPTY WEIGHT ROLL MOI 0x7C10 - EMPTY WEIGHT YAW MOI 0x7C18 - EMPTY WEIGHT CROSS COUPLED MOI 0x7C20 - TOTAL WEIGHT PITCH MOI 0x7C28 - TOTAL WEIGHT ROLL MOI 0x7C30 - TOTAL WEIGHT YAW MOI 0x7C38 - TOTAL WEIGHT CROSS COUPLED MOI I will also add these to FSUIPC7 in the next release. Cheers, John FSUIPC6.dll

I think the issue is that you are using a .lnk, which is a shortcut file. Try creating a proper symbolic link instead, which is handled by the file system. See https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ I find the following utility very useful for creating symbolic links and folder junctions (via Windows Explorer): https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html I could look into interpreting shortcut (.lnk) files, but this will be low priority so I am currently not sure when i will have time to look into this (but I will add to my list). But for now, try symbolic links instead. John

Why not just Run xx="a program link" Doesn't that work? I must admit I haven't tried it - the string is just passed to Windows to execute/run in a separate process. I will take a look when I get time (possibly next week) and can maybe convert the link to the destination, if needed. I will report back once I've taken a look. John

Then please do not purchase FSUIPC. I find it quite incredible that you expect that from any software..... I see no point in discussing this further. Topic closed. Regards, John

@Joe67 Please try the attached version, v6.1.6a. The gear type flags have been added to offset 0x05D6, as in FSUIPC7. FSUIPC6.dll John

What FS are you using? Is a Runways.txt file generated - if so, please attach so Pete can take a look - if it is large, you can zip it. John

It seems that the Fuel Selector Set Command works with the following parameters: 0 - turns left and right off 1 - turns left and right on 2 - turns left on, right off 3 - turns right on, left off So, turn one off without changing the state of the other, the command to send would depend on the state of the other. So, if left and right were both on and you wanted to turn left off, use parameter 3, and parameter 2 turn right off. If left was on and right was off, to turn off right you would use parameter 0 (both off). etc So you need to know the actual state and send different controls if you want individual control. I haven't checked any of the many other Fuel Selector controls. Activating logging and flipping the switch in the UI shows the Turbine Ignition Switch Set Ex1 control being triggered, with a parameter of 2 for On and 1 auto Auto. However, sending these controls via SimConnect/FSUIPC doesn't have any effect. I've had a quick look at the available lvars as well and there doesn't seem to be anything there that works either. You could try to see if you can assign for this to a key press (or key press combination) om MSFS itself. If this works, you can then assign your button/switch to the MSFS assigned keypress. Have you tried the Avionics Master 1/2 On/Off/Set controls? Is anything logged when you switch them in MSFS? The general method is the same - see if anything is logged and try them. If they don't work, try the various available controls. If non work, see if they work via MSFS assignments, and if so, assign to a keypress in MSFS and then assign your button to that key press in FSUIPC. Also, check available lvars and try setting those (initially using the Add-ons->WASM->Set Lvar... menu option to see if they work). Note also that many stock MSFS aircraft are missing quite a bit of functionality. There are various mods available for this aircraft (and most others) that improve on the stock functionality. Check for any available mods (SU6 compatible) that may improve on these functions. John

Try activating logging for both events and axes controls and open the console window. This may help show you what is sending the throttle control commands. You can also attach your FSUIPC7.log and FSUIPC7.ini files and I'll take a look to see if I can see anyhing. If assigning in MSFS, it is best to create a new empty profile in MSFS for that controller. John

Ok, thanks: **** FindWindowEx error 1400 (578) **** Error 1400 is 'Invalid window handle', which means it just can find the window with the class name 'AceApp', which is what the MSFS main window class name should be. You can delete/remove that version now and revert to the previous version I posted. I will release that version in a few days. Cheers, John

Ok, that is interesting.... sounds like that thread is somehow preventing the main thread from closing... ...hmm, then maybe not! You could also try renaming that file and uncommenting the ipc.runLua command so that it is re-created, and see if that provokes the crash, or not, as the case may be. Anyway, I will wait for further information. I am not sure if the changes in those above versions will be kept for the next release or not, we'll see how it goes with your tests. John

Yes, it looks like this is no longer working, if it ever was....! The lvar L:XMLVAR_ElecGen doesn't even exist anymore! You can just use the Toggle Alternator1 control to toggle between off an main, and offset 0x3B9C will hold the state, but only main (1) or off (0). It looks like the standby state is currently missing. You should ask about this on the Asobo forums. For the starter, bind to Set Starter1 Held, with a parameter if 1. That is what is monitored when you log the events, and also works if I bind that to a switch/button....later, tried it again and it no longer works...very strange. There are various mods available for the TBM930, which should fix/improve the stock functionality. If I were you, I would look for the latest SU6 approved mod and try with that (e.g. https://flightsim.to/file/8288/tbm930-improvement-mod) to see if that helps. I cannot comment on these products. However, they will rely on the underlying SDK that MSFS provides, so if you cannot do what you want to achieve in FSUIPC, I very much doubt that it can be done with any other products. If you are new to lvars/hvars/calculator code, it may be easier to installer the MobiFlight WASM module (via the MFConnector app) and use the provided event files. However, as the MF presets just execute the calc. code defined for that preset, if the calc code doesn't work, neither will the preset. Sorry I can't be of more help. I'm pretty sure I looked into the TBM930 starter previously, so maybe this got broken in a subsequent update. I'm pretty busy at the moment, but when I get more time I will look into the this in more detail. You can also try looking on the Asobo forums for information on how to control the TBM930, or the MobiFlight discord channel. John

I am sorry but I cannot give you step-by-step instructions. There are plenty of posts on how to use MobiFlight and the FSUIPC7 event files if you want to go down that route. And, as I said, if you want to use that calculator code directly (instead of via a MobiFlight preset), then you have to use in a lua script via the lua ipc.execCalcCode script. You should first test the code to see if it works. You can do this using the Add-ons->WASM->Execute Calculator Code... menu entry. If you want to use lua, see the provided documentation.

Please replace the contents of your EXE.xml file with what I posted earlier. Why have you attached that other file? Have you tried starting FSUIPC7 manually? At least try that to make sure it can run.