Search the Community

good days. I need help, I'm a beginner in these things, I understand very little, I needed someone to tell me how I should do it step by step if necessary and with patience, my problem is that in flight simulator 2020 I bought the Fênix A320 and I wanted to put shortcut keys for some functions, it happens that I enter FSUIPC7 and in the keys assignements I choose the key and choose its function but in the game it doesn't work. What will I have to do more? I already tried using the calculator but nothing works, some works like wing lights and beacon lights but the rest nothing. I don't know if I have to add something in some FSUIPC7.ini file? FSUIPC7.log ? I really don't know what to do. I used the LINDA program and managed to find out what the functions are for each of the buttons but I can't introduce them into the game to make them work, I don't know if you can also do it through LINDA or if you have to use FSUIPC7 or some other. Can anyone help me? Please. Thanks My FSUIPC.INI [Keys] 8=79,8,66053,0,66053,0 -{O: Press=STROBES_OFF, Release=STROBES_OFF }- 10=73,8,65560,1,65560,0 -{I: Press=STROBES_TOGGLE, Release=STROBES_TOGGLE }- 12=80,8,66240,1,66240,0 -{P: Press=TOGGLE_TAXI_LIGHTS, Release=TOGGLE_TAXI_LIGHTS }- 14=112,8,66718,0,66718,0 -{F1: Press=CABIN_NO_SMOKING_ALERT_SWITCH_TOGGLE, Release=CABIN_NO_SMOKING_ALERT_SWITCH_TOGGLE }- 16=32,8,66740,2 -{Space: Press=MANUAL_FUEL_PRESSURE_PUMP }- 20=68,8,66378,0 -{D: Press=TOGGLE_WING_LIGHTS }- >>>> these works 22=70,8,66379,0 -{F: Press=TOGGLE_NAV_LIGHTS }- 24=90,8,66485,0 -{Z: Press=ANTI_ICE_TOGGLE_ENG2 }- 26=88,8,65751,2 -{X: Press=LANDING_LIGHTS_TOGGLE }- 28=67,8,65751,3 -{C: Press=LANDING_LIGHTS_TOGGLE }- 30=86,8,65751,1 -{V: Press=LANDING_LIGHTS_TOGGLE }- 32=81,8,67090,1,67090,0 -{Q: Press=TOGGLE_EXTERNAL_POWER, Release=TOGGLE_EXTERNAL_POWER }- 34=87,8,66484,0 -{W: Press=ANTI_ICE_TOGGLE_ENG1 }- 36=69,8,66485,0 -{E: Press=ANTI_ICE_TOGGLE_ENG2 }- 38=84,8,66706,0 -{T: Press=APU_GENERATOR_SWITCH_TOGGLE }- 42=33,8,67090,0 -{PgUp: Press=TOGGLE_EXTERNAL_POWER }- 44=82,8,66363,0 -{R: Press=TOGGLE_ALTERNATOR1 }- 46=89,8,66364,0 -{Y: Press=TOGGLE_ALTERNATOR2 }- 50=66,8,66719,0 -{B: Press=CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE }- 54=34,8,66889,0 -{PgDn: Press=ANNUNCIATOR_SWITCH_ON }- 56=192,8,67090,1,67090,0 -{'@key: Press=TOGGLE_EXTERNAL_POWER, Release=TOGGLE_EXTERNAL_POWER }- 58=65,8,66240,2 -{A: Press=TOGGLE_TAXI_LIGHTS }- 60=83,8,67172,0 -{S: Press=MASTER_BATTERY_OFF }- FSUIPC7.ini

I have used FSUIPC for many years now, but am switching from Prepar3d to MSFS. I have 3 Joystick interfaces for Yoke's , rudder, brakes and Throttle. With FSUIPC6 no issue's, but with FSUIPC7 my Arduino Micro which connects the Throttle as a joystick cannot be calibrated within FSUIPC.7 I CAN use it directly when configuring the axis directly to MSFS. But i miss the calibration option of FSUIPC,; that's why i even bought FSUIPC7! Regards Roel

NOTE: This guide references an out-dated method for controlling the PMDG aircraft in MSFS. While it might still work, a better method is explained in this linked FAQ: Background PMDG Aircraft for MSFS do not use the normal controls provided by the flight sim. This means that many of the aircraft's switches cannot be assigned to buttons and keys using the list of controls in the FSUIPC dropdown boxes. Assigning a standard control in FSUIPC will likely do nothing in the PMDG aircraft when the button or key is pressed. Solution Instead of using the standard list of controls shown in the FSUIPC dropdown box, users must send codes as a parameter to the standard MSFS 'Rotor Brake' control. The parameter code specifies which switch to operate and what type of mouse click to simulate. The control numbers vary for each aircraft and are listed in the SDK that is installed alongside the aircraft. This guide will show you, step-by-step: How to find the SDK files How to calculate the 'Rotor Brake' parameter codes How to assign the code to buttons/keys in FSUIPC The specific examples shown will be taken from the PMDG 737-700, but the same method works for any PMDG aircraft with an SDK. 1. Locating the SDK From your main Flight Sim install folder, open the PMDG folder. Then select the folder belonging to the aircraft you want to use. e.g. PMDG 737 NGXu Then select the SDK folder Locate the file with the .h extension. For the 737 it's called PMDG_NG3_SDK.h You can open this file with Notepad or your favourite text editor. As an example, the document you need for the 737 will be: [FlightSimInstallFolder]\PMDG\PMDG 737 NGXu\SDK\PMDG_NG3_SDK.h 2. Calculating the 'Rotor Brake' Parameter Code 2.1. Find the control you want to use. Search for the control by name, or look through the listed controls to find the one you want. They are helpfully grouped together by panel. The controls are listed under a comment: // Control Events You can search for this to find where the list of control numbers starts. As an example we'll use the "Autopilot CMD A" switch on the MCP. This is the relevant line in the 737 SDK: #define EVT_MCP_CMD_A_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 402) To calculate the control number for this switch we ignore THIRD_PARTY_EVENT_ID_MIN and take the number after it. In this case 402. NOTE: Some controls reference other controls. For example: #define EVT_EFB_L_BACK (EVT_EFB_L_START + 1) For this you need to find the value of EVT_EFB_L_START and add 1. Searching for EVT_EFB_L_START we find this: #define EVT_EFB_L_START (THIRD_PARTY_EVENT_ID_MIN + 1700) As before, THIRD_PARTY_EVENT_ID_MIN is always ignored. So we get the value of 1700. Adding 1 to this will give us the value for EVT_EFB_L_BACK. Therefore EVT_EFB_L_BACK would be 1700 + 1 = 1701. We have now calculated the control number. 2.2. Adding the Mouse Action Code You now need to add a number to tell the aircraft what kind of mouse interaction you want to simulate. (e.g. left click, right click, scroll wheel up). First multiply the control number you have so far by 100. In our example for EVT_MCP_CMD_A_SWITCH we get: 402 * 100 = 40200 Now you ADD the following number, depending on the mouse operation you want: 1 for left mouse click 2 for right mouse click 3 for mouse move 4 for left mouse button release 5 for right mouse button release 6 for middle mouse button click 7 for mouse wheel up 8 for mouse wheel down For our example, we'll have our key assignment simulate the left mouse button clicking on the CMD A autopilot button. So we'll need to add 1: 40200 + 1 = 40201 Now we have the final code number. 3. Assigning the control to a button or key in FSUIPC Select [Assignments] -> [buttons + switches] or [key presses] in the FSUIPC7 menu. Then select the button or key to program. From the "control sent..." dropdown select Rotor Brake In the Parameter field below type in your calculated code number from the previous step. For our 'Autopilot CMD A' example, we enter 40201 If you're programming a key press, remember to press the [confirm] button. Here is our example control assigned to a button in FSUIPC: Your button or key press should now operate the switch in your PMDG aircraft.

Dear @John Dowson, dear @Pete Dowson, As the Capabilities of FSUIPC 7 grew really a lot since its start and especially working with Presets (events.txt and myevents.txt) and we get more and more great planes in MSFS i have a small suggestion. Within FSUIPC7 there are a couple of places where a command / preset can be chosen with a dropdown menu. As we now already have > 7700 elements in this dropdown it's sometimes quite hard to find what you're searching for - especially if you don't know exactly how it is called. That's extremely time consuming. Do you see a chance to replace that dropdown with a search functionality being capable of searching for all terms entered in there (and split with a blank " ")? I'm sure it would be really of great help. I made a small example online as JSFiddle to show what could be a great improvement: https://jsfiddle.net/Lsyr9fc3/6/show/ Just try within the "Control / Preset" field to find something. For instance for Kodiak the ignition could be found with "kodi ign", or for the Fenix Engine mode just search for "ENG" then extend it to "ENG Mode" to find the engine mode switch options. Or to find the rotaries of the G1000(NXI) just search for "1000_ inc" Could that be an option? Looking forward for your response... Best regards, Joe

I am very familiar with FSUIPC. I have used it for several years with P3D. I recently got MSFS 2020 and when I heard FSUIPC 7 was available for MSFS I immediately purchased it. I downloaded the program and when I start MSFS I see the FSUIPC 7 logo. The problem I have is where is it in game? I have no idea how to access it. Would appreciate help in finding it in the sim. thanks, Jim

It is now possible to run FSUIPC7 (v7.2.13 and later) on a client PC, that is, a 2nd PC where MSFS is not installed. This should allow FSUIPC clients to be ran on the client PC and allow them to communicate to the FS without the need for WideFS/WideClient. Note that this DOES NOT replace or duplicate the functionality provided by WideFS. When FSUIPC7 runs on a client PC, it will maintain its own offset area distinct from that of the offset area used by FSUIPC7 on the FS machine. However, most offsets should contain the same data, as they are populated by the data received from the FS, but be aware of this if/when writing to user offsets (e.g. using lua). Note also that you do not have to have FSUIPC7 running on the FS machine to run FSUIPC7 in the client machine. The following functionality in FSUIPC7 will not work (or is not available) in FSUIPC7 when ran in a client machine: - no installer - you need to manually install/copy FSUIPC7 to the client machine - no possibility of sending key presses to the FS (key presses CAN be received) - no auto-start or auto-connection - .... To have FSUIPC7 running on a client machine, please follow the steps indicated below. 1. Configuring SimConnect on the MSFS computer Locate your MSFS2020 SimConnect.xml file. For steam installs, this should be under <Your User Account>\AppData\Roaming\Microsoft Flight Simulator and for MS Store installs under: <Your User Account>\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Open the file in an editor, and add a Global (remote) IPv4 port by adding the the following entry: where Your Local MSFS PC Address is your 'internal' network IP address, not your outward-facing IP. To find this, open Command Prompt on the MSFS Computer, type "ipconfig" and look for the "IPv4 Address" listed under your active internet connections. You can also change the port number, but this MUST match the port number defined in the SimConnect.cfg in your client PC (see below). Note that you also may need to open this port in any firewalls that you may use (although I did not have to do this when I configured in my LAN). 2. Install FSUIPC7 in the client machine To install FSUIPC7 on a client machine, create an DSUIPC7 folder (preferably not under Documents, Program Files, or any other windows-protected folder) and copy across the following files from your MSFS computer: FSUIPC7.exe FSUIPC7.key (if using a registered version) You can also copy across your FSUIPC7.ini file, but it may be better to start afresh with this in your client PC. 3. Configuring SimConnect on the Client computer To configure SimConnect on the client PC, create a file called SimConnect.cfg in your FSUIPC7 folder on the client machine with the following contents: where Your Local MSFS PC Address is the same address as used in the client configuration (and the port also must, of course, be the same as the one used there). 4. Configure FSUIPC7 to run on the Client computer If you have copied across your FSUIPC7.ini, open this in an editor and removed any unwanted assignments/profiles. If you have not copied across your FSUIPC7.ini, run FSUIPC7 once and exit - this will create a default FSUIPC7.ini file for you. Open this file in an editor (e.g. Notepad++). Under the [General] section, add the following ini parameters: RunningOnClientPC=Yes UseSimConnection=0 and under the [WAPI] section (if using the FSUIPC7 WASM module on the MSFS computer) - create if necessary, also add the following: UseSimConnection=0 And that is all! To use FSUIPC7 on the client machine, you must manually connect once MSFS is up and running. For any issues or questions, please use/comment on this topic. John

Good morning, Is there a key shortcut you can assign with FSUIPC 7 for FS2020 to squawk VFR (1200) in your transponder? Some aircraft have buttons built in to do this, but the one I fly the most, the C152, doesn't. Any help you can provide is appreciated. Regards, Kevin Davis

After watching YouTube video "TBM 930 THROTTLE Control setup in Microsoft Flight Simulator 2020 using FSUIPC7 | TBM 930 TUTORIAL", I bought FSUIPC7, registered it, and created a new profile TBM930 in the Axes Assignments screen, selected "Send to FS as normal axis", and assigned Throttle lever to "Axis Throttle 1 Set" and the Prop lever to "Axis Propeller 1 Set". The throttle in the simulator does not respond/move with movement of the throttle lever although the Propeller lever will shift between Hi Idle and Taxi if I manually move the throttle up from cutoff into Hi Idle with the mouse then move the Prop lever up. I've also tried reassigning the throttle to "Axis Throttle Set" to no aval. The throttle and propeller are not assigned in MSFS 2020 Control Options: Power Management. I'm using the Logitech Pro Flight Yoke System I did not install WIDEFS7 because I am not using networked computers; just a stand-alone PC. It's probable something real simple that I've overlooked... Any direction would be greatly appreciated. FSUIPC7.ini FSUIPC7.log

Hi all, I have a few technical questions before buying FSUIPC7 because I'm not sure about what I can acheive from FSUIPC7/LUA scripts regarding the SimConnect Indexed variables. As example, I take the Asobo Airbus A320 . Someone has already reported that Offset 07D4 [AP ALTITUDE VALUE] is not working. He gave up thinking it was a bug. I found that Offset 281C or 3102 [Master Battery Switch] are not working neither. After having looked into Microsoft SDK and SimConnect, I found that the A320 FCU AP Altitude is linked to an indexed SimVar [AUTOPILOT ALTITUDE LOCK VAR:3] It seems that FSUIPC7 is not natively looking at this SimVar. Both A320 Battery Push Buttons are a bit more tricky: For the left battery Push button: First, set SimVar BUS LOOKUP INDEX to value 10 Then the state of the left battery can be read at indexed SimVar BUS CONNECTION ON:6 For the right battery Push button: First, set SimVar BUS LOOKUP INDEX to value 11 Then the state of the right battery can be read at indexed SimVar BUS CONNECTION ON:6 So here are my questions : Q1. Is it possible from FSUIPC7 (I guess with Lua Scripts) to access the Indexed SimVars and map them to a free FSUIPC7 offset ? I know it *was* possible to access Local SimVars with Lua scripts, but I want to be sure that we can query the indexed variables, for instance like this : ipc.writeXXX("A:BUS LOOKUP INDEX", 10) LeftBattery = ipc.readXXX("A:BUS CONNECTION ON:6") ipc.writeXXX("A:BUS LOOKUP INDEX", 11) RightBattery = ipc.readXXX("A:BUS CONNECTION ON:6") Q2. Is it possible from FSUIPC7 to log all SimVars and Indexed SimVars ? (in order to identify which one is changing after a few clicks in the virtual cockpit) Oh god, the BUS LOOKUP UP thing is not going to help with this kind of feature... --- Regarding the Local SimVar, I understand that FSUIPC7 has no way to access them. And in fact, Microsoft SimConnect SDK does not provide a way to do this. The only workaround for now is to create a fake gauge and put the local SimVar in the Client Data Area. Then FSUIPC7 would be able to read/write the Local SimVar through the SimConnect SDK.

Hi, I tried to assign some buttons of my self made homecockpit to certain non standard controls in the Carenado Mooney M20R and the Just Flight Arrow III. I can read out the names in the model behaviors lvars window in developer mode but the macros I created do not work. I can select the macro in the drop down menu for the button events but nothing happens when I operate the switch. The mcro file is named M20R_Fuel_pump.mcro and contains the lines [Macros] 1=L:M20R_Fuel_Boost_Pump=SET In P3D with older versions of FSUIPC these macros worked fine. Has something changed in the way macros are defined or did I do something wrong?

Hi, I dont know if this behaviour is correct or not: I set the VOR COURSE value with an encoder and 65662 param 0 for decrease value and 65663 param 0 for increase. When I'm NOT in fly (at parking) this works always correct (decrease and increase by plus or minus 1 degree). When I'm in flight and attempt to reach VOR radial the value change plus or minus 5 degrees. The encoder works correctly and not send false impulses. Thanks for suggestions.

Hello I recently bought the Remote Flight AutoPilot from the Apple APP store and have trying to get it to work without success. As you know, part of the process involves installing your FSUIPC7 product which I have done several times. Today I bought the paid product in a last ditch effort to get it working. I am still getting the same error messages that are described below and I am unable to get the RF server program from Remote Flight to connect to the FS 2020. The text below is a copy of a message I sent to Remote Flight for some assistance but have not heard back. TEXT OF MESSAGE SENT TO REMOTE FLIGHT OF 12/1/2020. =================================================== I have been working with the program today and I thought I would bring you up to date on what I have tried. FS 2020 has been installed on the server host computer for some time without problems. Made sure that the latest version of .NET Framework was installed. (It is included in Windows 10) Disabled Windows 10 firewall and anti-virus on FS computer Bought and downloaded RF Auto Pilot on my IPAD Pro without problem Downloaded and installed FSUIPC7 on FS computer (did not register.) Downloaded and installed RF Server on FS computer Started FS 2020 using FSUIPC7 icon which had been placed on the desktop by the program during installation Got the following 3 consecutive error messages that were clicked OK Code execution problem and cannot proceed missing MSVCP14.dll Code execution problem and cannot proceed missing VCRUNTIME 140-!.dll Code execution problem and cannot proceed missing VCRUNTIME 140.dll After clicking OK, FS 2020 continued to load, a departure location selected, and then clicked the FLY button Launched RF Server just to see whether it might connect to FS 2020 but after a short period of time waiting for connection to sim, I got an error message stating that a connection could not be established. The message went on to recommend checking to see whether FS 2020 was running (it was) and insuring that the most up to date FSUIPC7 was installed (it is). I have tried this process with the anti-virus and firewall enabled and disabled with no difference in the outcome. As I have said earlier, I purchased the product today-- the order number is 2550377. I would appreciate any help you can give me. Thanks William Mathers Jorge - Support Date: 12/02/2020 Status: Closed Dear Customer, We are sorry for the trouble. simMarket is only the commercial platform. Due to the technical nature of your issue we advise you to reach support on the official FSUIPC support. Just follow this link and you might get the help you need. https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/ regards

hello everyone , i just wanted to know how to make the tug of the pushback attach to the aircraft without move , i need to make the speed 0 so tried this code Private TugS As New Offset(Of UInteger)("tug", &H31FC, True) Dim SPD as UInteger = TextSPD.text TugS.Value = SPD FSUIPCConnection.Process("tug") it didn't work the aircraft just move forward when it's not attached to the tug . need help with that thank you at all . stay safe

Tried to set tug heading and speed controlled by integer by Private TugH As New Offset(Of UInteger)(&H31F8) Private TugS As New Offset(Of UInteger)(&H31FC) Private TugState As New Offset(Of UInteger)(&H31F4) FSUIPCConnection.Process() Dim HDG as integer = TextHDG.text Dim SPD as integer = TextSPD.text Dim Status as integer = TextSts.text FSUIPCConnection.SendControlToFS(FsControl.KEY_TUG_HEADING, HDG) FSUIPCConnection.SendControlToFS(FsControl.KEY_TUG_SPEED, SPD) TugH.value= HDG TugS.value= SPD TugState.value= Status So for the heading of the tug no one worked it just make the heading of aircraft is 357 degree whatever i change the heading in TextHDG , whatever integer i input just turn the tug to heads the aircraft to 357 . for the speed it doesn't work for the status integer : 0 Pushback Straight 1 to left 2 to right 3 stop pushback any helps plz ..

First. thank you Peter for making Fsuipc7 available, it is wonderful and I would never have thought that this module would be so quickly available. I have Goflight modules GF-46, RP-48, GF-MCP, MCPPRO. These modules are active with FSX-SE and Fsuipc4, but not recognized with MSFS and Fsuipc7. Can anyone think of a cause, is it within Fsuipc7 or due to my own configuration, hardware or software. Thank you in advance for your help. Charles, (please excuse my approximative English)

Hello, I came across the problem where i binded my settings up just like in P3D V5 assigned the axis and etc. however when i closed FS2020 last night and open it this morning the sim recognized the hardware but nothing works in the sim itself. (keyboard, mouses (other than pan movement), saitek yoke and throttle and logitech rudders. FSUIPC7 is open and connected and still get no response out of the sim. Went into P3D v5 to make sure it wasnt my drivers and it wasnt. its odd this happened. Could it have something to do with the new update they just released for the sim?

After successfully installing and using FSUIPC7 with MFS2020 (despite the frame drop), I find smartcars does not connect to v4 any longer. As v7 is not compatible with FSX, I cannot use smartcars to create pireps for my VA whilst using FSX as my simulator, which is the only stable platform to use for longer flights, or large aircraft. All was working well until using v7, which I am not complaining about, as I am satisfied. I would just like to troubleshoot why v4 has stopped working, and if I can fix the issue so I may pursue stable VA flights. The file structure has not changed, all necessary files are located in my Modules directory.

Where can I find the simconnect dll file? I do not have the sdk

FSUIPC7 documentation only (without Installer) FSUIPC7_Documentation --- When FSUIPC7 is Installed, these documents are optionally installed in a folder called FSUIPC7 under your Documents folder FSUIPC6 documentation only (without Installer) FSUIPC6_Documentation --- When FSUIPC6 is Installed, these documents are optionally installed in a folder called FSUIPC6 under your Documents folder FSUIPC 4.975 documentation only (without Installer) FSUIPC 4.975 Documentation --- When 4.975 is Installed, these documents are placed automatically in the FS Modules \ FSUIPC Documents folder Revised list of FSX controls FSX and P3D Controls Note that not all of these necessarily work -- though I know for sure most do! FSUIPC 5 and FSUIPC6 produce are more up to date list as a text file automatically -- check your FSUIPC Documents folder. FSUIPC 3.999z8 documentation only (without Installer) FSUIPC 3.999z8 Documentation --- When 3.999z8 is Installed, many of these documents are placed automatically in the FS Modules \ FSUIPC Documents folder SIMSAMURAI's FSUIPC Tutorial Sim Samurai Tutorial --- Updated on 18th January 2010. FSUIPC 4.60 documentation in FrenchFSUIPC460Francais --- Translation kindly donated by Mr. Philippe Hantzberg, 19th March 2011 WideFS documentation in Frenchhttp://philcl.durand...Utilisateur.htm --- Translation kindly donated by Mr. Philippe Durand, 4th July 2011