John Dowson

So this only happens with the FVW experimental? As I said: It shouldn't, but maybe try activating logging for Lua Plugins and send me a log with that. You can also try temporarily disabling it (just rename the lua file before you restart FSUIPC7) to make sure. That lua could also do with an update - it should really use event.lvar rather than an infinite loop with a delay...

No, sorry, but this has been reported before, but not sure what can cause this...

So, FSUIPC7 does not auto-start? If that is the issue, see the post I reference in my first comment on your issue. This I don't understand...why would FSUIPC7 auto-run the 2nd time but not the first? Each time you start should be the same as the last...and why restart MSFS and not just run FSUIPC7? Your use of the word load is what is confusing...and when you say 'restart it' do you mean MSFS or FSUIPC7?. And what happens the third or on subsequent attempts to run MSFS? The MSFS menu is only (obviously...) available if FSUIPC7 is actually running... All the information is in the User manuals or in the posts I have referenced... But I still don't understand your issue... Could you tell me EXACTLY what happens when you run MSFS - do you see an FSUIPC7 splash screen? If not, it is not auto-starting, and if this is the case you should try to start manually by double-clicking the FSUIPC7.exe. What happens when you do that? If it runs ok then, then your issue is with auto-start and you should refer to the link I posted on this issue. Otherwise, it could be a problem running FSUIPC7 - which is documented in the README. But please explain your issue, without using load. A program either runs when you start it or not - do you have FSUIPC7 running? If it is in your system tray, it is running.

Also, did you auto-start FSUIPC7 with MSFS, or start it manually, an if so, when? Does it crash again if you restart FSUIPC7? If so, can you show me the log, as well as your FSUIPC7.ini. After a few tests, it seems ok here. Maybe also check that you are using the latest experimental release. Can you also let me know if this is the only aircraft/version in which this occurs, and maybe switch to the stable or development version temporarily and check with that version.

Not sure if I can do anything if this is just with the FBE A320 experimental version, but I will switch to that and take a look. Looks to be using something new called SimBridge - are you using that as well?

From Saturday for 9/10 days... The log you attached shows the lvar names were received - when this happens, a message should be logged in the FSUIPC7 main window with the number of lvars/hvars/presets loaded, and the WASM menu items should be enabled. I can't see how the menu items cannot be enabled once the lvar names have been received... Make sure the user is checking after this message is logged... 7.3.9b. John

Does this only happen with the FBW A320? If so, which version (dev, stable or experimental) are you using - and is it up to date?

So this just happened the once? Your log shows that the WAPI interface was not started. I'm not sure why this happened - the next version will have additional messages relating to the WASM/WAPI - you could try this (attached) and show me your FSUIPC7.log file if this happens again. The WASM is the module in your Community folder that runs with MSFS, and the WAPI is the interface in FSUIPC7 that communicates with the WASM. The WAPI is now enabled by default if the WASM is installed, and your ini file shows this is enabled anyway: [WAPI] EnableWAPI=Yes So I'm not sure why it didn't start... John FSUIPC7.exe

No, they are completely separate and will not interfere. I run FSX, MSFS, P3Dv4 and P3Dv5 all on the same machine with different versions of FSUIPC. You can only have one FS/version of FSUIPC running at a tune though. John

For the auto-start issue, and if FSYUPC7 is not just auto-starting and then closing, please see If FSUIPC7 closes after starting, please show me your FSUIPC7.log file. John

You are using an extremely old (and unsupported) version of FSUIPC7 (7.0.3). The latest version is 7.3.8 - please update. Also, if you think that FSUIPC is crashing, I need to see your FSUIPC7.log file, John

Can you check that you have the following in your FSUIPC7.ini file and if not add it: [WAPI] EnableWAPI=Yes The WAPI is now enabled by default, but if that section isn't there then the presets will not be loaded. I will fix this in the next release.

This sounds like the rudder axis has been changed to a digital on/off axis in the registry. See the following FAQ entry to resolve this: John

I think that depends on the dll. There seem to be various solutions around for using dlls with lua - for example, see https://stackoverflow.com/questions/2835716/how-do-i-call-functions-inside-c-dll-from-lua https://blog.devgenius.io/how-to-add-your-c-library-in-lua-46fd246f0fa8 https://lua-users.org/wiki/LuaProxyDllTwo I don't see why this wouldn't work in an FSUIPC7 lua script, but best to try it - there is a trial license available at the top of this sub-forum if needed. John

No, that is just a warning - you should be fine as all your 11 devices are identified correctly. Maybe try using presets first - there are presets available for most most Rotor Brake controls which are easier to use. check the preset link I previously provided (has a good search interface for finding presets). John

I wouldn't do that. Just keep it anywhere for now - the official version should be released at some point. No. That file is not used at run-time - you just need it to determine the Rotor Brake parameters. 👍

A compound button condition applies to the actual state of a 2nd (or more) button (or latch flag) when the assigned button is pressed or released. This is described in the Advanced User guide, page 21. This functionality is normally used, for example, to control what an increase/decrease knob sends depending in the position of another selector knob (e.g. the Alt, VS, HDG, etc selector knob on the Bravo).

I cannot tell much from that log - and I have no idea what you mean by "I think it might be a dupilcate listing in the registry, there seems to be an item 10 listed 2 times." Please also attach your FSUIPC7.ini file when you attach a log. What toggle switches? For many switches, you need to use the Rotor Brake control (the PMDG 737 custom controls are using this, different from the FSX/P3D versions) or presets - please see https://hubhop.mobiflight.com/presets/. Also see the following FAQ entry: There are also many existing posts on the PMDG 737 for MSFS - maybe review some of those. Any further issues, please be more specific and show me your .ini as well as .log files. John

The SDK for the MSFS PMDG 737-700 has still not been released, and so there is no SDK header file (*.h) at the moment. Folks are using the PMDG header file at the moment, which I have attached. Although you may be better looking on the PMDG support forums - I believe there is more information there on the Rotor Brake parameters, although I haven't checked for a while... John PMDG_NG3_SDK.h

I can see the issue, in fact it the aircraft jumps quite suddenly from reverse to forward motion (not just thrust!) for me when de-activating the reversers. I have also tried with the eng1/2 reverse thrust kill presets but the same thing happens. It should be possible to go to reverse idle before cutting - I will keep looking. If anyone else has this working more correctly/efficiently, please advise! Note that I also found it useful to add a compound condition to the thrust detent, so the throttle decr isn't sent unless the reverser button is on. If you don't do this, the reversers are also activated when you move down through the detent without activating reverser lever first.

But how have you configured? Maybe attach your FSUIPC7.ini file and I can take a look... Assign as follows for Throttle1 (and mimic for throtttle 2): - assign your throttle1 axis to the 'Direct to FSUIPC calibration' control Throttle1 - calibrate throttle 1 - set the min/max and you will also need to reverse - go to the button assignments panel and activate throttle1 reverser (this will show up as button 8 ) and assign the press to Throttle1 Decr with a parameter of 1 (no repeats!), and release to Throttle1 Cut. - move throttle 1 through the detent. This will register as button 24, and assign to Throttle1 Decr with a parameter of 1 and select for repeats. With this config, you can activate reverse idle with the reverser, then push the throttle down to increase to max reverse thrust, and also use the reverser off to kill reverse thrust. Let me know how it goes. John

I can't help without seeing your log and ini files... Please show me your FSUIPC6.log, WideServer.log. WideClient.log and WideClient.ini and FSUIPC6.ini files. I don't understand this - there must be a WideServer.log in your FSUIPC6 installation folder, and a WideClient.log in your WideClient installation folder... John

It would help if you could attach your FSUIPC7.ini file so that I can see what assignments you have made,,, I've installed the PMDG 737-700 on my system with the Bravo attached now, and will look into configuring the throttle later today and will report back. I will use the other thread for this issue, and will close this thread now, so please use that topic/thread going forward. John

You can always compress/zip a log file if too large to attach... From the log you attached, it looks like either the WASM hasn't been installed or the WAPI has not been enabled. Please check both, and attach your InstallFSUIPC7.log and FSUIPC7.ini files (as well as your latest FSUIPC7.log file) if you still have issues. John

For the third time, you need to delete (or rename) the file C:\Users\josem\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt and then install FSUIPC7 again. As that file exists, the installer thinks you have a Steam installation, when you in fact are using an MS Store installation. I presume that at some stage you installed via steam, and that file is a remnant of that installation and needs to be removed.