John Dowson

Fixing the script how? Is this your issue? I don't see this at all and would need to see your logs to see why this is happening. The script works as expected here, although I find it very difficult to control using keys rather than a yoke or joystick... I think I also now understand why the Num5 key isn't working for you - you do not have NumLock on! I just tried with NumLock off, and the other keys still work but not the 5 key. So, either switch numlock on, or change the centreAllKeycode from 101 (Numpad5 with NumLock On) to 12 (Numpad5 with NumLock Off). Looks like the other numpad keys send the same keycode regardless of the NumLock state. Or, you can just add the following line to the bottom of the script to support when numlock is on or off: event.key(12, 0, 1, "flightControl") -- request on initial press only, NumPad5 with NumLock Off John

Can you try this one first - just start MSFS/FSUIPC, once it has started exit and show me your updated FSUIPC7.ini and FSUIPC7.log files and I'll see if a registry edit is needed. John FSUIPC7.ini

How do you want to read this data, and what do you want to do with it? If you want to read all of the CDU data, you can do this using a multi-dimensional array. Something like: -- Define the size of the array - we will start are indeces at 0 to make offset calculation easier CDU_Colums = 24 - 1 CDU_Rows = 14 - 1 -- Initializing the array CDU_data = {} for i=0,CDU_Colums do CDU_data[i] = {} for j=0,CDU_Rows do CDU_data[i][j] = 0 end end -- Read the data: 0x5400 == 21504 in decimal for i=0,CDU_Colums do for j=0,CDU_Rows do CDU_data[i][j] = ipc.readUB(21504 + i + (j*(CDU_Colums+1))) end end I haven't tried this! John

No - the only FSUIPC version compatible with FSX/FSX-SE is FSUIPC4. To determine what control is used for a specific button (FPS panel or otherwise), you can activate logging for Events (non-axis controls), open the logging console and press the button in the virtual cockpit. See if any event is logged, and if so, you can assign to that. If no event is logged, you could try using a mouse macro. However, not all aircraft support mouse macros - from the User guide: This indicates that mouse macros will not be available. If there are no standard controls/events and mouse macros are not available for the aircraft, you could look into using lvars. If you let me know which default aircraft you are using, I could take a look to see what is available for the GPS of that aircraft, John

Btw, if you did this in the FSUIPC_WASM.ini file located under your Community folder, this will get overwritten the next time you update FSUIPC7. Make sure that you have copied this file to your WASM persistent storage area so that this is preserved - see the Advanced User guide for details. John

The folder where the aircraft.cfg files for the FBW A320 are located are called: _FlyByWire_A320_NEO-LIVERY-XMAS FlyByWire_A320_NEO FlyByWire_A320_NEO-LIVERY ,,,(you may have more) So if you have a hvar file called A320.hvar, then A320 is a substring match to those folder names, and so that hvar file will be loaded any time those aircraft are loaded. John

What does this mean? Did you calibrate in MSFS or FSUIPC? Calibration doesn't 'go missing'... Profiles are loaded automatically when you load an aircraft that is assigned to a profile, and when a profile is used for an aircraft the profile checkbox in the axis panel will always be checked and disabled, and if you have profile-specific calibration that will also be checked and disabled. You can only change profile-specific checkbox for button assignments. It is not possible to manually load a profile - you can only assign an aircraft to a profile and these are loaded automatically. And you always need to show me your FSUIPC7.log and FSUIPC7.ini files if you are having issues with assignments or calibration. Please attach them. They are independent. If you assign in MSFS, you use the sensitivity windows in MSFS and such axes will not be calibrated in FSUIPC. It was previously possible to also calibrate in FSUIPC when assigned in MSFS, but this is broken since SU10 - I have raised a bug report on this with Asobo and am awaiting further information in this issue. If you want to calibrate in FSUIPC, then you have to assign with 'Direct to FSUIPC Calibration', and you cannot use the sensitivity oprions in MSFS when doing this. John

I do not need to see screen-shots, just your ini and log files are enough. And you assignment screenshot also differs from what your ini shows, and so is confusing: 2=GR,B,-16254,-11573,66066,0,66067,0 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_ON, Leaving=SPOILERS_ARM_OFF }- i.e. from is not -15734 but -16254. The log file shows no spoiler axis movement at all. This is because you used the aircraft "Airbus A320 Neo Asobo" which is not using your A320 profile, and so has no axes assignments. Either add that aircraft to your profile or go back to using the "TAP-TNR". You also have a missing device to which you have assignments: This has been re-recognised as device G, to which you also have assignments. This is being caused by your throttle quadrant being recognised twice, once with a new and once without: The registry entries for that 2nd entry without the name should be removed. You could try disconnecting, removng any drivers you installed, rebootung and then reconnect to see if that solves the issue. Otherwise I can provide you with a script to remove this from the registry completely and then you can re-connect and try again. This is why you keep having to re-assign to that device, as it is continually recongised as a new device. Anyway, I have attempted to correct a few things in the attached ini if you would like to ty with this, and show me a log file with the spoiler movement. Otherwise, we can correct for your throttle quadrant first. John FSUIPC7.ini

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