John Dowson

I do not support smartCARS, only FSUIPC. Is FSUIPC running (do you see the FSUIPC7 splash screen when starting MsFS?)? Are you starting FSUIPC7 manually or using auto-start?

Logging shouldn't make too much difference in performance, but that also depends upon the amount of data being logged...throttling the logging can have quite a severe influance on performance. What key repeat rate are you using/seeing? Maybe this needs adjusting.... I will take a ;ppl at the script again later today and try it for more than a few seconds and let you know if I find anything... John

Please don't do this if you don't know what logging to set. You already have WAPI debug level logging set (in your FSUIPC7.ini) and that should be sufficient. Turn the other logging off. From your log, it looks like no aircraft was loaded. You have to have an aircraft selected and be ready-to-fly before you can access or use lvars/hvars/calculator code. So, please try again and make sure that you have an aircraft loaded and ready-to-fly. If you still have issues, please show me your new log, and also what you actually did - was FSUIPC7 auto-started, or did you start it manually? If the latter, what state was MSFS in when you started FSUIPC7? Note that you should NOT start FSUIPC7 if MSFS is in a pause state. John

Ok, great! Not having this aircraft, I cannot really advise, sorry. I think most folks would be using a reverse thrust button for this. Maybe ask about this one on the Fenix A320 support. John

There are 4 presets available related to the Fenix A320 runway turnoff switch (see https://hubhop.mobiflight.com/presets/😞 You can either assign to those, or look at the lvars/events those are using an use those instead. John

You just need to try it... however if the MCDU doesn't recognise the throttle then I'm not sure there is much you can do, except maybe ask about this on the Fenix and PFC support forums. Pete has retired - he won't know anything about the Fenix either, but does know about the PFC driver (as he wrote it!). You could try asking him (using the tag notation with the @ symbol...). He is also on holiday at the moment, back in few days. John

No idea, sorry. Enable logging in the lua script by setting the logActivity variable to true (and re-start)- that should tell you what is happening. John

Those increments/deltas are over 10-times greater than the delta I started with and provided to you, which was 128. They are pretty huge increments and I can't see how you can control the primary flight surfaces with those...but each to their own! This is very strange...are you using any of the MSFS assistance options? If so, maybe they are interfering. Otherwise suitable logging should explain what is happening... You can always update the script to send those controls on a Numpad5 key press: Rudder Center: control/event 65689 Center Ailer Rudder:: control/event 65612 John

Btw, maybe take a look at FSInterrogate (FSInterrogate2std.exe) or Examiner - both available in the Utils folder of your FSUIPC7 installation folder. John

Please show me a log file generated with the relevant logging activated - as I said: You only have 4 buttons assigned - master battery on/off and toggle alternator 1/2. For the G58, there are 4 presets available for the master battery (see https://hubhop.mobiflight.com/presets/😞 They are all using the Toggle Master Battery control, with the parameter indicating the battery number, so you could try that for the G58 - or assign directly to the presets. With Event logging activated and the logging console, you can also flip the switch you want to assign in the virtual cockpit and see what event is logged for that switch and then assugn to that. When assigning to presets or for aircraft specific functions, it is also recommended to use a profile for that aircraft. John

Many people have reported issues with the throttle assignment in the Fenix A320. You have to calibrate the throttle first in the Fenix MCDU, and then assign as 'Send to FS as normal axis' using the Throttle 1/2 Axis Set Ex1 controls. See I'm not sure if the newer *_EX1 axes are available for PFC devices though - not sure how those are assigned/calibrated as I don't have any PFC devices. But first you should consult the Fenix documentation and see if you can calibrate in the MCDU. John

Ok, thanks, There are already presets for these Rotor Brake parameters for the 737-700: PMDG B737 Recirc Fan: 87201 (>K:ROTOR_BRAKE) PMDG_B737-7_PNEUMATIC_RECIRC_FAN_TOGGLE: 19601 (>K:ROTOR_BRAKE) Still no separate preset list for the 737-800 - not sure why this is.... John

No problem, glad you got it sorted and thanks for the update. John

All offsets are documented in the FSUIPC7 Offsets Status document. If nothing was printed in the console, then you forgot to check the Normal log file checkbox - you have to select were you want the logging to go. Never going to happen, sorry. That would be far too much work for little benefit for a very few people. I am struggling to get new functionality in as it is due to the amount of time I am spending on support and just keeping up with MSFS and P3D releases. There are far more useful things for the majority of folks I am planning to implement at some point already. John

In the same places as always - either in the Download Links => Updated Modules page of this from, or from www.fsuipc.com.

Ok, that makes sense. Thanks for the update. John

👍

Files?

In the next release, FSUIPC7 will auto-start luas when FSUIPC7 is started/restarted when MSFS is running and has an aircraft loaded (i.e. it is out of the main menu system). You can also try the attached beta version (7.3.11a) that has this implemented. In this version, I have also delayed the starting of other threads, including WideServer, until and aircraft is loaded and ready-to-fly. John FSUIPC7.exe

But how is the yoke assigned in P3Dv5/FSUIPC6? Presumably in P3D, no? As I have said, it was previously possible to calibrate axes when assigned in MSFS or when assigned in FSUIPC to 'Send to FS as normal axis', but since the release of SU10 this is no longer possible. With P3D/FSUIPC6, this is still possible. John

Are you sure? The yoke isn't even recognised, and this will/should be the same in FSUIPC6... Maybe show me your FSUIPC6.log and FSUIPC6.ini files so that I can check...

Yes I know, that is what I said ('You do have one controller assigned that is now missing:'). Yes, I know, This yoke is not recognised or supported by FSUIPC. It is not an HID joystick type device. John

There is still a minor issue (now corrected, will be released in the next update) that prevents the WASM/WAPI being activated in certain situations. To correct for this, make sure that you have the WAPI explicitly enabled in your FSUIPC7.ini, i.e. make sure you it contains the following section - add or update as needed: John

You ran the installer from within the zip file: Running in folder 'C:\Users\blaur\AppData\Local\Temp\Rar$EXa23188.45475\Install_FSUIPC7' You should not do this - extract the files from the zip folder first before running the installer. Do that and try again. John

These are periods defined by the MSFS SIMCONNECT_PERIOD enumeration type: I know nothing more than that. Yes, you will need a delay, before you can read the value. However, as I said, rather than inserting a delay you should use the idiom: ipc.createLvar("AE_FD", 0) -- create Lvar while (ipc.getLvarId("AE_FD") == nil) do ipc.sleep(50) end -- wait for lvar to be received i.e. wait for the lvar to be available after creation. It is also better to use the event.Lvar function to perform actions when lvar values change rather that changing the value and then waiting for the updated value to be received back - or you could just assume that the value had been updated (depending in the use-case). John