John Dowson

@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

The ASNwxRadarPath parameter should be the complete path to the file. Does the folder 'Sim-Avionics' exist? To test. just try ASNwxRadarPath=c:\radar.bin

There's the offset status spreadsheet, included in the downloadable zip file. Currently at version 11. The controls list is generated at runtime and will be in your FSUIPC7 Documents folder. However, this is just a list and many are not currently working, and some work in some aircraft but not in others.

When you turn your rotary, what do you see in the Button & Switch assignment panel? You should see the 'Joy#' letter, which is the letter that is assigned to your device, and a 'Btn#', which will change when you turn the rotary switch. The example I gave was for when the rotary is linked to buttons 17 and 18. To program the rotary correctly, you need to determine what button numbers your rotary is using, and when/if it is sending the press & release events. To check this, you can activate logging for 'Buttons & Keys'.

The .bat file just contains a html page with an embedded javascript section which I guess is the problem. Not sure why Kaspersky (and also Malwarebytes flags this as a virus. Other virus scanners seem to be ok, although I have had one report of Windows Defender marking it as suspicious, which is strange... I'm not sure there's anything I can do about this, you just need to add an exception or restore it once quarantined, however the virus checker works. I don't have or use Kaspersky, so I can't really advise. John

@Don777 You are quoting a post over 15 years old! And if its a direct question to a previous posted, a good idea to tag them which gives it a better chance of being seen. But your answer should be in this post...did you try?

You could try offset 0x0B49 instead - Autopilot Flight Level Change. See the following previous posts which may be relevant:

Btw, have you tried writing to this offset? If so, does that change the A/S hold state?

Ok. So it reads 0 when A/S hold is active? how about 07E2, is that correctly populated with the speed set? How about the other A/P Hold/lock variables/offsets? There are various known issues with the G1000, with various key events having no affect and simvars not being populated correctly. I'll take a look at this in more detail, but I suspect that it is another G1000/SDK issue.

I've checked this now and FSUIPC7 is requesting this data, but it seems that the following AI string variables received via simconnect are always empty: AI Traffic State AI Traffic Assigned Runway Ai Traffic FromAirport AI Traffic ToAirport AI TRAFFIC ASSIGNED PARKING I will raise this with Asobo. I'm not sure at the moment why TrafficLook is showing an integer in the 'To' column when this should be empty.... John

Which aircraft/autopilot are you using? You really need to specify the aircraft for all queries on offsets or controls.

What controls are you using, and how does your 3-point switch function? In the C172, you should the control Fuel Selector Set, with a parameter if 1 for center, 2 for left and 3 for right. And how you assign depends on the button/release events that your 3-point switch uses. For example, I have a 3 point switch that when moving from center to up, triggers a button 17 press, from up to center, a button 17 release, from center to down, a button 18 press, and from down to center, a button 18 release. To use this for the fuel selector switch, I would assign a Fuel Selector Set with parameter 3 on button 17 press and a parameter of 1 on 17 release, and a parameter of 3 on button 18 press and again a parameter of 1 on release.

Yes. The latter - create the text file, addthe content and rename it with a .reg extension.

You can use the default hot key (Alt-F) to display the main window, double click the FSUIPC7 icon (in your system tray), or right-click the icon to select the required function. Please see the provided documentation - as well as the Installation and Registration guide + README.txt available in the zip file you downloaded, the main FSUIPC7 documents are installed under your Documents folder in an FSUIPC7 sub-folder.

Do you know when this occurs? Can you provide steps to reproduce? I have been using FSUIPC7 on a multi-monitor set-up (3 monitors) with FSUIPC7 positioned on different monitors and I haven't noticed it losing the monitor or correct position so far. Are you maybe using nvidia surround configuration? Are your monitor ids changing? If you can let me know how I can reproduce I'll look into it.

Ok, thanks for reporting back.