John Dowson

This is usually due to a faulty button that keeps firing. You can ignore this in the assignments panel by using the IgnoreThese ini parameter in your [Buttons] section - from the Advanced User manual:

Sorry, but do you have any issues? What am I looking for?

Is this aircraft specific or a problem with multiple aircraft? If specific, which airplane are you using? Also maybe try logging both events and axis controls (also open console to see the log messages in real-time) to see what axes movements are logged when this occurs.

No, I don't think that is an issue. You shouldn't do this really. No admin privileges are needed by FSUIPC7 or the installer. If any privileges are required then you will be prompted to authorise anyway. I will investigate that error nest week and get back to you. However, i've a feeling that it maybe due to one of your devices or device drivers. Check your connections and any usb hubs, make sure power management is disabled on all your hubs, and that all your drivers are up to date.

Why are you using DirectAxesToCalibs: Try disabling that by removing the line from your FSUIPC7.ini], although using this this shouldn't cause any issues. Can you a check if you have an event logged in the windows event viewer when FSUIPC crashes, and if there is an entry please post the details. If you disable WideServer, do you still get crashes?

It means that FSUIPC7 will not work when MSFS is running on an xbox console. It only works with MSFS running on a windows 10 pc. MSFS, like many games, runs on both xbox consoles and in a PC running windowa 10. If you are using MSFS on a pc then you are fine.

You initially reported that your FPS dropped when you try to create a mouse macro. Now you seem to be saying that your FPS is dropping when you have more than a total of 20 commands in your mcro files (presumably you are still talking about mouse macros, no?)? This just doesn't make sense. Mcro files don't do anything, and a macro itself only takes effect once invoked. As Pete says, you need to clarify what your actual issue is and provided further information.

Hi Rod, Yes, I should be able to add them so that they can be assigned, but only as 'Send to FS as normal axis'. There will be no calibration or offset area for these axes. These must be newer controls that aren't yet flagged in FSUIPC as axes controls. I'll look at this in the coming days and post an updated version of FSUIPC6 for you to try/test. John

@ark1320, @pilotjohn I've added this feature in the attached build. To use, you must specify the offset (starting with 'x' not '0x') as the MaxSteerSpeed ini parameter, i.e. MaxSteerSpeed=x66C0 The offset should hold (and is read as) a signed word (2 byte) integer. The maxSteerSpeed will be updated on every change of this user defined offset, so you can have a profile-specific auto-started lua to set this for your profile, or a long running lua monitoring the aircraft name (or stall speed) and updating the value when this changes. I've not had time to do too much testing so please report back once tried. John P.S. Changes to the MaxSteerSpeed are logged when Extras logging is activated. FSUIPC7.exe

Ok. That has been reported to Asobo. Ok. I can add [AUTOPILOT ALTITUDE LOCK VAR:3] if required. What about [AUTOPILOT ALTITUDE LOCK VAR:2] ? Its not an issue to add new offsets which can then be used for specific aircraft. However, I can't change the behavior of existing offsets if they are still functioning for other aircraft. I don't like the idea of allowing any simvar to be requested via lua - it would be very problematic. Its far clearer to identify any needed simvar and add it to the offset area. The long term plan is to provided access to lvars via an internal WASM module, and have an inter-process communication mechanism between the WASM module and the FSUIPC7 application. Whether this i done via a SimConnect client data area or using standard windows communication protocols is still to be decided, and depends on what facilities are provided on the WASM side. This is one of the larger development areas still to be addressed. John

La instalación de FSUIPC7 es independiente de la instalación de MSFS. La única dependencia de la instalación de MSFS es el 'Desktop shortcut' (que inicia MSFS junto con FSUIPC7). Si no tiene MSFS instalado en su PC, no lo instale desmarcando la casilla de verificación en la página final del procedimiento de instalación.

Sorry, I have no idea. Something must have changed. All the link/batch file does is start MSFS and then start FSUIPC7 after a short delay. What happens when you start MSFS directly (using the MSFS provided shortcut or start menu entry)?

@johnk515 Yes, that is what that lua script does. Try it - you will need to adjust the button numbers first. The alternative way (not sure if its any easier!) is to add the assignments via the ui and then overload the assignments by editing the ini file, to add the extra press/release controls as indicated in my last comment. To use this method, you will need to use the updated FSUIPC7.exe provided (still not officially released) as this has the necessary additional pause control added.

If by 'indexed variables' you mean standard simconnect variables that are indexed (i.e. in an array), then I don't understand your worries as they are no different from standard un-indexed sim variables. The A320Neo is known to function quite differently than most other aircraft, with many controls/events and sim variables currently not functioning for that aircraft. Reported here? Reference would be useful. Many AP variables (and controls) are currently not working, especially for the G1000. Maybe. But using offsets is tied to a specific control (or simvar) that may not be working for that particular aircraft. You have to choose a method that works for the controls provided for each aircraft. If they do not respond to the 'generic' controls, then other mechanisms should be used. If available, any simvar can be added to the offset area on request. No. Only simvars known to FSUIPC and published in the offset area can be accessed. If there are simvars not currently requested by FSUIPC that you require, then I can add these upon request. Thats local variables, or lvars, not simvars. There is currently no access to lvars in FSUIPC7, pending facilities to be provided. A simvar is a simvar, indexed or not does not make a difference. The included offsetStatus spreadsheet contains the simvars used for each offset (where applicable), together with a list of available simvars not currently held in the offset area (at the end of the document, after the offset list). Please take a look at these. For the definitive list of available simulator variables, please see the MSFS SDK documentation. Note also that they are documented in two sections, one is the complete list of simvars, and the other is the list available via SimConnect. FSUIPC7 obviously (?) uses the latter, although I have had some success requesting variables in the former not in the latter, i.e. simvars not yet documented as being available via SimConnect.

@Ray Proudfoot Interesting! My usual test flights usually involve Bilbao (from/to/or via Asturias, Vitoria or Vigo) and I've never noticed an issue, though I only fly during daylight (no lights) and normally GA. For the Dynamic Lighting issue, presumably SIMStarterNG also handles this, which I think you also use, no? But I guess that only handles the initial state, not changing during a session. I've had SIMstarter a while now but not gotten around to setting it up yet (too much time developing rather than flying!), but was planning to use it to switch settings between flying in photo scenery vs autogen.

@zorzini For cabin lights, there are four MSFS controls under INTERIOR LIGHTS: CABIN LIGHTS OFF CABIN LIGHRT ON SET CABIN LIGHTS TOGGLE CABIN LIGHTS You can assign a key press (or more) to one or more oft those MSFS controls, and then assign a button/switch to that keypress in FSUIPC7. You can also try activating event logging to see if any event are logged when those controls are activated, and if so try to assign to those events instead (although this is not guaranteed to work - if not, use key press assignments). John

There is a Parking Brakes control - did you not see/try that? It works as a toggle control, no parameter. The brakes control is for the differential/toe brakes, not the parking brake.

By "programming" I meant assigning... You can, but you have to select the control that works. As I said, in the C172, the control that works is Fuel Selector Set, so 'Select FS control' and then 'Fuel Selector Set', and add the parameter that you want for center (1), left (2) or right (3). BUT, you need to know how your three way switch works to assign correctly, as a 3-way switch is normally 2 "buttons" (i.e. the button number that registers in the FSUIPC assignments panel when you flip the switch). So, usually a switch would register as a button press when moved in one direction (e.g.left), a release for the same button when moved back to the center, and different button press when moved to the right, and then a release of that button press when moved back to the center. If thats how your switch works, then you need to program/assign both button numbers (in FSUIPC) to the 'Fuel Selector Set' control on both press and release, with a parameter of 2 on one press and 3 on the other press and a parameter of 1 for both releases.

Ok. However, for the Doors, most of the older controls don't seem to work, as in MSFS the doors are linked to ground services, so requesting catering services opens the catering door, requesting boarding opens the main door, etc. However, an extra control was added that bypasses this - TOGGLE_AIRCRAFT_EXIT_FAST. There's an existing topic on the doors offset: I'm pretty sure there are also topics on some of the other functions you are trying to add that may be useful (although difficult to find in these forums!).

What do you mean by this? In FSUIPC, you can assign an action to the button press and the release. If you don't assign to the release, no action will be done on the release. How you assign to buttons/switches depends on how the button or switch functions. You can also activate logging for 'Buttons & Keys' (and maybe also 'Events') to see what is happening - you need to be connected to the sim with an aircraft loaded for the logging to function, and at least one assignment on the button (press or release). What are you trying to assign to your switch? How does your "switch" function?

Ok, definitely a windows permissions issue then.

FSUIPC7 is for MSFS only. For FSX-SE, you need FSUIPC4. This is documented in the provided README.txt: Do you actually have MSFS installed? If so, do you have it on Steam or via MS Store? P.S. when requesting support, please give your post a relevant title. You name doesn't mean anything to most people! I will update this time.

You are confusing controls with offsets. Controls (or events) are "commands" that you send to the FS. The number (decimal) isn't really important. This is just the number/id that the "key string" has been assigned. The offset "area" is a block of memory that holds sim data that you can read, and an equivalent block of memory that you can write to. These "offsets" are populated (usually) from simulator variables. Writing to an offset can result in either a direct update of a simulator variable (documented in the FSUIPC offsets document as 'Ok-SimC') or the sending of a 'control' (documented as 'Ok-SimE'). Nut really, as an end user, the distinction isn't important. An offset will have a size and a type (as defined in the documentation). A control is just a command with an optional parameter. Many controls can also be activated/sent by writing to the offsets. So, to set the parking brakes, you can either send the Parking Brakes control (which I believe is a toggle control), or you can (try) writing 1 (for on) or 0 (for off) to offset 0BC8 as a 2-byte (unsigned) integer. I say try as I'm not sure if this is working with MSFS. If you try this, let me know if its working or not and I can update the offsetStatus spreadsheet accordingly. There is another related simulator variable called BRAKE PARKING INDICATOR, which I guess just controls (or shows) the state of the parking brake indicator light. This simvar has not yet been added to the offset area - its one of those towarsds the end of the spreadsheet under 'The following simvars are available but currently not requested: ' John

Btw, I also checked the 'To' airport field. When the ICAO for the destination airport is empty, FSUIPC substitutes this for the AI aircrafts transponder code (when available).

Hi Dave, not until these issues have been resolved by Asobo. I'll raise a zendesk ticket on those AI sim variables being empty. All current SimConnect functions for weather have been deprecated, and we are waiting for a new interface to be provided. John