John Dowson

Yes - I will update the offset document to make this clear. John

That is just the section where the auto-save file names are saved when using P3Dv4 when you have auto-save feature activated. As you have this feature disabled, it will be empty - apart from the Next parameter which is always present.

Yes - that's the crash event for MSFS.

That goes in the FSUIPC7.ini. But you don't need to add this any more, and the WASM is now enabled by default. It will only not be enabled if you have it explicitly disabled in your FSUIPC7.ini file, i.e. and if that is the case you can enable it by using the Add-ons->WASM->Enable menu entry. But really you shouldn't need to do anything. John

I don't know NeoFly but I have just downloaded it and will take a look at some point, most probably over the weekend. Are you using 3.13? That version is quite old now (11 months). I see there is an early-access version of NeoFly4 - maybe try updating to that. There are only minor changes from 7.3.9 -> 7.3.10 and from 7.3.10->7.3.11. What version were you previously using? 7.3.9 was the initial version I released for SU10 compatibility. John

If MSFS is CTDing, then it is either an issue with MSFS or more probably NeoFly. FSUIPC7 is a separate application/executable and in no way can/should cause MSFS to CTD. If you check your FSUIPC7.log file, you will see that FSUIPC7 exits normally as MSFS is no longer available. I cannot help with MSFS CTDs, sorry. John

Once an aircraft is associated to a profile, to remove it from that profile you have to manually edit the FSUIPC7.ini file. Find the [Profile.xxx] section (where xxx is the profile name) and then remove the aircraft name (or names) from the list of aircraft associated to that profile. Do this when FSUIPC7 is closed/not running. John

De nada - ¡Saludos! John

As Pete said: You would need to consult the FSCREW RAAS documentation (or support) to find out how that accesses those files. Cheers, John

👍

The problem is in the WASM - it will be corrected in the next release. In the mean time, you can use the attached - use these to replace the files in your Community\fsuipc-lvar-module and your Community\fsuipc-lvar-module\modules folders. The WASM version number is the same - I will update this when released. John layout.json FSUIPC7_WASM.wasm

It seems that writing lvars as negative integers isn't functioning correctly. I will look into this. but you can get it working by using a decimal value, e.g. "-1.0". John

Please see the provided MakeRwys README.pdf: John

By default, hvar files are loaded when a *.hvar file is found whose name (without the extension) is a substring match to the name of the aircraft, as logged by FSUIPC7, Sometimes when using a livery you don't get the full aircraft name - for example, here's what is logged with the TAP livery: 72563 Aircraft="TAP-TNR" So, to load hvars for that livery, the *.hvar file would need to be called something like TAP.hvar. You would need to duplicate the A320.hvar files to match the various liveries. There is a better way to match the aircraft to the hvar file - using a substring match on the aircraft.cfg folder name. To do this, you need to set the WASM ini parameter UseAirLocForHvars to Yes, and you would also need to update the *.hvar filename to match the folder (e.g. FlyByWire_A320.hvar), Please see the Advanced User guide for details. Note also that you don't need the *.hvar files if you use calculator code or presets. So, you can create your own presets to activate hvars, by adding lines of the form My preset#(>H:hvarName) to a myevents.txt file, and then you can assign directly to the preset. John

The FSUIPC7 installer will install the WASM module into your MSFS community folder if you select to install this component (selected by default). There is no WASM module or settings in your FSUIPC7.ini file (not FSUIPC8.ini!). You don't need yo do anything else. If you check your InstallFSUIPC7.log file, that will tell you what is installed and where - and also the Installation and Registration guide. John

They will only arm when the spoiler axis enters the range. As the range starts at -16384, the axis will never enter the range from below, only from above. Try increasing that to -16000 or so. Also, you need to activate logging for Events to see the controls logged, as they are non-axis events. John

If FSUIPC7 is running and smartCARS isn't connecting, then the issue is with smartCARS, not FSUIPC7. You can attach your FSUIPC7.log file and I will take a look to see if I can see anything, but you probably need support from the smartCARS developer/provider. John

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