Search the Community

Following the instructions in the Introductory Flight for the 100. Every thing goes great until I advance the throttle to taxi. Then all sorts of errors pop up; Flaps Error, YD off, Fuel, etc. I then have to shut off and restart the engines, then it proceeds okay. Last night I decided to not engage the flaps and trim until I was actively taxing and the only error that popped was 'A-I E1 Fail', which isn't listed in the manual. Doing an Internet search it appears to be a 'Anti-Ice failure in Engine 1'. I know it's an old aircraft, but wondering if anyone else has experienced such errors on the initial taxi. Thanks, Ernie

Here is a Lua file that progressively apply and/or disengage brakes, adjustable in both directions, for those who only have a button for brakes. [INSTALLATION] FS closed Copy the complete code block below, paste it into an empty .txt file & rename it Smooth_Brake.Lua Place the above file in the FS/Modules folder Add the following to the [Auto] section of the FSUIPC(4).ini file - X=Lua Smooth_Brake - Where X is the next available number in the [Auto] section. (pg. 42 - FSUIPC4 for Advanced Users.pdf) Comment out ( ; ) or remove the original brake button listing in the [buttons] section. Start FS Make sure the button is not programmed through the FS assignments dialog. For a simple, non-complex assignment to the joystick button see the picture below. For a complex assignment see pg. 22 - FSUIPC4 for Advanced Users.pdf - Using something similar to this for a button press - xx=CP(-0,11)0,0,CL6:S,211 and this for release - xx=CU(-0,11)0,0,CL6:C,211. Where 6 is the numbered lua under the [LuaFiles] section of FSUIPC(4).ini in my case as an example. Use the FSUIPC facility, "Reload Buttons", from the user interface in the Buttons tab to confirm assignment. Adjust user settings to ones own liking. Assign a keyboard key to reload the file using Lua Smooth Brake as the control sent to use for reloading tuning modifications. One can use the Logging facilities in FSUIPC, using the right hand side of the dialog (FSX + only), using 0BC4, 0BC6 & 0BC8 with a type of U16, display to FS Window, to help in adjusting user settings. The above settings result in this - 1=P0,0,CL6:S,211 2=U0,0,CL6:C,211 [USAGE] Basically all this does is gradually increase (depending on settings) the brake strength as the assigned brake button is pushed. It also works in reverse, on brake disengagement. One could, for instance press the brake button for only 1 second and after that toggle the brakes on & off at a repetitive rate to keep, lets say, ~ 50% brake strength. It's much better than full on or full off. The settings as given below give around a 2.75 second span between brakes off to full brake strength. Smooth_Brake.Lua - --------------------- USER SETTINGS rate_on = 300 -- RATE AT WHICH BRAKES ARE APPLIED minimum = 3500 -- MINIMUM BRAKES ON FIRST APPLY = REQUIRED PERCENT * 16384 rate_off = 300 -- RATE AT WHICH BRAKES ARE RELEASED dis_pbrake = 1 -- DISENGAGE PARKING BRAKE ON BRAKE APPLICATION? REQUIRES A REAPPLY FOR BRAKE ACTIVATION! diff_brake_override = 0 -- !!!! GIVES AN ALTERNATE DIFFERENTIAL BRAKE AXIS PRIORITY OVER BRAKES -- EXAMPLE - THE "T_FLIGHT HOTAS" ALTERNATE AXIS ON THROTTLE SECTION -- SEE PG.1 "FSUIPC LUA LIBRARY" - "n = ipc.axis(joynum, "axis")" FOR MORE INFORMATION. --------------------- END USER SETTINGS function stop() brake = ipc.readUW(0x0BC4) -- Get Parking Brakes If Button Pressed And Parking Brake Disengage Is Active if ipc.testflag(211) == true and dis_pbrake == 1 then p_brake = ipc.readUW(0x0BC8) -- Disengage Parking Brakes If Set if p_brake == 32767 then ipc.control(65752, 0) end end -- Brakes On while brake < 16383 and ipc.testflag(211) == true do -- Differential Braking Override if diff_brake_override == 1 then -- REQUIRES CUSTOM ATTRIBUTES FOR SPECIFIC HARDWARE special = ipc.axis(0,"S") if special > 1000 or special < -1000 then brake = 0 break end end brake = math.min(16384, brake + rate_on) brake = math.max(minimum, brake) brake_shift = logic.Shl(brake, 16) + brake ipc.writeUD(0x0BC4, brake_shift) end -- Brakes Off while brake > 0 and ipc.testflag(211) == false do -- Differential Braking Override if diff_brake_override == 1 then -- REQUIRES CUSTOM ATTRIBUTES FOR SPECIFIC HARDWARE special = ipc.axis(0,"S") if special > 1000 or special < -1000 then brake = 0 break end end brake = brake - rate_off brake = math.max(0, brake) brake_shift = logic.Shl(brake, 16) + brake ipc.writeUD(0x0BC4, brake_shift) end end event.flag(211, "stop")

Upon starting FSX today, I encountered the error message shown below. It happened early last month, at which point I updated to the most current version of this software, but today the problem came back. Even after running this program in compatibility mode (which only worked for a few hours) this error message keeps popping up. My FSX Autosave and FSGlobal Real Weather engine depend on this software in order to function and I want to know how I can fix this error once and for all. Any suggestions would be appreciated. I would also like to underline that I have the most recent version of FSUIPC installed. I also have a copy of the FSUIPC4 Log file if you need that (see below) FSUIPC4 Install.log

Background PMDG Aircraft for FSX and P3D do not typically 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 use a different set of controls provided by PMDG for the specific aircraft. These are known as custom controls (or custom events). The custom controls 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 custom control numbers How to work out the parameter value How to assign the control to buttons/keys in FSUIPC The specific examples shown will be taken from the PMDG 737NGX, but the same method works for any PMDG aircraft with an SDK and custom controls (e.g. 777, 747). 1. Locating the SDK From your main Flight Sim install folder, or your MSFS Community folder, and open the PMDG aircraft folder Then select the folder belonging to the aircraft you want to use. e.g. PMDG 737 NG3 or pmdg-aircraft-737 Then select the SDK folder or Documentation\SDK folder for MSFS2020 Locate the file with the .h extension. For the 737 it's called PMDG_NG3_SDK.h (or maybe PMDG_NGX_SDK.h, depending on the sim and variant you are using) You can open this file with Notepad or your favourite text editor. As an example, the document you need for the 737 in MSFS2020 will be: [Community]\pmdg-aircraft-737\Documentation\SDK\PMDG_NG3_SDK.h 2. Calculating the control numbers 2.1. Find THIRD_PARTY_EVENT_ID_MIN The first thing to find is the definition of THIRD_PARTY_EVENT_ID_MIN. Search for the following text: #define THIRD_PARTY_EVENT_ID_MIN You will find a line like this (from the 737 file): #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 Note the decimal value at the end. In the case above it's 69632. You will need this value to calculate the control number in the next step. 2.2. 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 swtich 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 just add 402 to the value of THIRD_PARTY_EVENT_ID_MIN we found earlier. 69632 + 402 = 70034 We have now calculated the control number. We will use this in step 4 to program the button/key. 3. Finding the parameter value PMDG controls need a parameter value. These can one of type types: 3.1. Mouse Click Codes (Shown in the example) You can use these to simulate a mouse click on the particular switch. Mainly it will be the left mouse button, but other clicks types are available (e.g. Right button, left double click etc). To find the codes for each type of click, search for MOUSE_FLAG You'll find a block of #define statements for each type of mouse click. Here are a couple of examples from the 737 sdk: #define MOUSE_FLAG_RIGHTSINGLE 0x80000000 #define MOUSE_FLAG_LEFTSINGLE 0x20000000 Find the click that you want to simulate and get the code. For example, we'll have our key assignment simulate the left mouse button clicking on the CMD A autopilot button. So we'll need 0x20000000 as the parameter value for the control. 3.2. Direct Values (Not shown in the example) Alternatively, some controls can accept a direct value to set the switch to a specific position. To find the direct values you need to look at the top part of the .h file to find the switch definition. These are named differently than the events so you need to search. Taking the battery selector switch as an example, we find the control: #define EVT_OH_ELEC_BATTERY_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 1) For the parameter value we can find the same switch in the top part of the .h file: unsigned char ELEC_BatSelector; // 0: OFF 1: BAT 2: ON This tells us that in addition to mouse clicks, we can also send direct values. In this case: 0 for the OFF position, 1 for the BAT position and 2 for the ON position. It's possible to make a key or button set the Battery Selector directly to the ON position by setting the parameter value to 2 instead of a mouse click code. Simple ON/OFF switches will not have values listed (and will be declared as 'bool'). For these types of switches you can just pass the value 0 for OFF and 1 for ON. 4. Assigning the control to a button or key in FSUIPC Select the [buttons + swtiches] or [key presses] tab in FSUIPC and select the button or key to program. From the "control sent..." dropdown select <custom control> (it's near the top of the list) A popup window appears asking for the control number. Type in the control number you calculated in step 2. For our 'autopilot CMD A' example, we enter 70034 and click OK. The controls dropdown box will now show the control number in angled brackets. In the "parameter" box (below the controls dropdown), enter the parameter value from step 3. This can be a mouse click code or a direct value. Mouse Click Codes: Do not include the first 0 from the number listed in the PMDG SDK. Start with the x. With our example, we would enter x20000000 for the left-button single-click. Note that this code is in hexadecimal. FSUIPC will convert it to the equivalent decimal value. This is nothing to worry about. It's the same number. Entering the value in Hex is more convenient. Direct Values: Just enter the value as a number. Do not add the x at the start like mouse codes. 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.

I am try to install the Aerosoft's GA28R simulator on a new Windows 7 computer with FSX installed with all service packs. Aersoft has informed me that they no longer support this device. Have several problems: Where can I download GA28R.dll 1.00? When I lauch the GA28R software, it is only looking for FS2002 or 2004, and there is no option to point the software to FSX. Does anyone know of a work around for this? Thank you

Hello, I unfortunately suffered an FSX CTD at 1,500 feet on my approach and I'd like to figure out what the issue was and if it was related to FSUIPC at all. Everything was going normally until the simulator locked up around 1,500 feet, froze for a minute or two, and then closed. This was on VATSIM in a busy airspace, though my sim will usually just stutter in such instances without crashing. The Windows crash details indicate FSRecorder as the faulting module, though it seems to always throw up the same .dll as the faulting module after a CTD. I was not using FSRecorder at the time, nor had I used it at all during this particular flight. Here's the report anyway: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc0000005 Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: 50e32fd4-f1f9-45a1-9845-d7b065db7543 Faulting package full name: Faulting package-relative application ID: Here's another one from less than a minute later. Looks almost identical. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc000041d Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: a2d2cafe-1c8a-4005-93b0-43fc01b60d80 Faulting package full name: Faulting package-relative application ID: Here's a final one from 13 minutes later, perhaps when I tried to relaunch FSX. This one lists ai_player.dll as the faulting module. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57 Exception code: 0xc0000005 Fault offset: 0x00037399 Faulting process id: 0xfe4 Faulting application start time: 0x01d6e23a68099c7d Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll Report Id: 810a2d1a-9dbc-4473-b32d-9b30b28fc566 Faulting package full name: Faulting package-relative application ID: I've attached the FSUIPC4.log file to the post. This is an unregistered copy of FSUIPC and I just updated it the other day through DVA ACARS. I was flying an addon 717 (can look up developer later if needed). Addons I was using were ASN, DVA ACARS, projectFly, vPilot, and Self Loading Cargo. I had also used FS Real Time early in the flight but was not at the time. I know it doesn't look like FSUIPC was at fault, so I'm just trying to get to the bottom of what happened. Self Loading Cargo users have been reporting issues with a recent version of FSUIPC, but it may be for MSFS, I'm not sure, or if that's related to my issue. Any help would be appreciated. Thanks in advance. FSUIPC4.log

This lua script was done only as an interesting project in response to this thread, requiring that autosaves not occur during the most critical phase of flight in an advanced aircraft.. The landing. For FSUIPCv4.xx only. FSUIPCv5+ already has facilities to toggle off/on its own built in AutoSave. A lua script has also been made for FS9/FSUIPCv3.xxx, introducing auto save for this older sim where none was available beforehand in FSUIPC. If there is interest I may finalize the script with more substantial testing and then upload it. You may get it here. Roman

Hello , I received the cockpit trainer from VRinsight and wanted to use MSFS 2020 on windows 10. I found out that it didn't work with Windows 10. To test at least my cockpit I installed the cd version I had SFX. Working ok, but when I download the registered version of FSUIP (FSUIPC4) and start up FSX the start screen of FSX come up and shutdown directly. I'm not a expert and can't figure out the problem. Like to have a solution because I paid a lot of money for the cockpit and wanted to replace the real cockpit of the chessna fusilage I have. Thanks in avance!! Rudolf from France

I made a new installation of fsx and installed and registered FSUIPC4. Now when I run FSX the game crashes to desktop. I delete the FSUIPC4 in the modules folder and FSX runs without problems. I am including my log files for any help. Thank you. FSUIPC4.log FSUIPC4 Install.log

Folks, I am new to the forum and am trying to use Cirrus PFC yoke, rudders, power and radio console (Used with Elite) with FSX. I purchased and downloaded FSUIPC4. I can't find PFC under controls, and seem to believe I need to download drivers for it, i.e. pfcfsx.dll. Not sure if I am correct, and where to find it. If someone can point me in the right direction, It'd be greatly appreciated. Thank you.

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.

Hello guys, is there anyone who uses FSUIPC4 SDK on LAZARUS platform? Lazarus is FREE Pascal IDE (it is GNU), looking nice, easy to develop, but trying to port FSUIPC4 SDK, I have encountered several points which keep me off using it with [microchip_HW <=> Lazarus <=> FSUIPC4 <=> FSX] I have tried to use FSUIPC SDK for Delphi, but altough the Lazarus offers tools for converting the Deplhi project into Lazarus one, there are still features e.g. GlobalAddAtom, GlobalDeleteAtom, etc. (there is whole list of "Identifier not found" errors) which seem to remain in the code (these seem to be declared e.g. in FSUIPC.bas). As I have never programmed in Delphi, this becomes challenging (but surely not something which couldn't be sorted out after some investigation). I guess if I spend more time with it, I'll probably make a new library for Lazarus<=>FSUIPC, but if there is someone who has already done this step, or made some other part of FSUIPC SDK working in Lazarus environment, it might save me much effort. note: or I'll go for Visual Studio (VB or C++) - still considering programming effort - I used to program in Pascal many years ago, that's why it attracted my attention Thanks, Lubor

Hi Paul, After my query the other day about sending key presses to FSX, my code is working perfectly, BUT I am using both simConnect and FSUIPC Client. This seems a bit over the top, since the only thing I want to do in simconnect now is move the aircraft to a give latitude and longitude. FsLatLonPoint fsLatLonPoint = new FsLatLonPoint(lat,lon); FsAltitude fsAltitude = new FsAltitude(0); //Send Structure to simconnect to position aicraft //simconnect.SetDataOnSimObject(DEFINITIONS.Struct1, 0, SIMCONNECT_DATA_SET_FLAG.DEFAULT, s); FSUIPCConnection.MoveAircraft(fsLatLonPoint, true, fsAltitude, 0, 0, 0, 0, true); As you can see above, I commented out the simconnect instruction and replaced with the FSUIPCConnection instruction. Whilst it works, FSX then Loads Terrain, ATC etc after each move. Any idea why and how I can stop this? Many thanks Martin

Greetings Pete, I am using registered version of FSUIPC and use the auto-save feature which is very useful.However, i find that fsx will freeze for about 5-7 sec after every 300sec (as set) to save the files. I realize that aerosoft airbus fsx being a complex add-on, Fsx will need time to process it to save the airbus state as well as fsx situation which is fine. I don't see the freezes when using FSX default aircrafts. I have also excluded fsx, its addon and related folders from windows defender in win10. I scanned through many post related to this in various forums. Alas!!! i was unable to find a working solution. What happens is that ; Like yesterday and many other times ; when i was landing i was less that 10FT RA and fsx froze. Concentrating so much on the sim, I didn't realize fsx had frozen. . As lot of control inputs were already given when FSX had frozen; FSX had to process that. After the 7th sec FSX resumed, The aircraft hit very hard on ground (315 FPM), which actually spoils all the fun of landing an aircraft. Changing or increasing the time interval for auto save won't help because if the time period ends at the critical phases, Fsx will definitely freeze. What I suggest is if you can introduce a new feature which can carry out below functions:- 1.If we can disable auto-save feature (as per user choice) automatically when certain conditions are met like:- (i can remember only of this) a. landing gear extended (when G button is pressed). b. when below a certain altitude (like disable autosave when below XXXXFT) or between certain altitudes. c. at a press of a key or joystick button. It is upto the user prerogative whether to use such a feature or not. Because, if fsx freezes permanently or crashes when the auto-save is disabled. Then, no way of restoring FSX and other complex add-ons to the desired state. I got this idea from weather addon opusFsi which has a nice feature to stop weather update when certain conditions are met like on approach, on certain distance from arrival airport etc. Hope you can shed some light into this. Please advise if more info needed.

Hey, I recently reinstalled FSUIPC since I had some troubles with my sim and thought it could be related to FSUIPC. Now FSUIPC isn't working at all. So basically what's happening is that I click "fly now" in FSX-SE so it loads in, after it successfully loaded in, it crashes to desktop after a couple of seconds (about 5 secs). PS: Thanks for any help in advance (FSUIPC log is attached) FSUIPC4.log

MOVED FROM "USER CONTRIBUTIONS" SUB0FORUM (A REFERENCE SECTION) TO THE SUPPORT FORUM< SO IT CAN BE ANSWERED. Hello everyone! There is an inactive Frasca 131 simulator in our aeroclub with fully functional panels/instruments but unfortunately the "old times" computer with DOS has fallen apart along with its ISA graphics accelerator. I believe that the drivers of Frasca software are specific for this ISA card but I can't find it anywhere to buy it. Therefore, I have the physical instruments and hardware of Frasca 131 but I can't display anything on the screen with the software. Soooo, I came up with the idea to connect the Frasca 131 's serial port to a modern computer which will run the FSX and have the FSUIPC being the connection bridge between the serial data transmitted from the Frasca and the FSX simulator. Do you have any ideas if this is even possible or how to make it happen? I presume that there has to be a program (written in any language) with no graphics that will run before the FSX and read all the traffic from the serial port and afterwards push it to the FSUIPC and then to the simulator. And probably vice versa in order to have the instruments displaying the actual measurements. Any help is very welcome Thanks!

Hello guys, Im trying to learn more how to take more advantage of fsuipc and founded the "Controlling A Brand New Decade of Flight Simulation Hardware" tutorial, I just want to know if this is still applicable for p3dv4.5 or if any other detailed tutorials are available, thanks! here some break time at work so im reading! thanks.

Dear Experts and members, I am new to this forum and also don't have much idea about how FSX & FSUIPC interconnect, specially what is the output format of FSUIPC. I read on different forums and threads that we can build a simulator using FSUIPC software and arduino but no one talked about the PLC and i want to do this. All i want to know that which type of output FSUIPC software provide and how can i get the data from this software. For example if i have PC with FSX installed and i bought the license of FSUIPC then how can i get the data or which file give me the values to control my motors and different gadgets etc? Your earlier response will be highly appreciable. Thanks in advance

I am getting some problems in my Main.cpp file, I have attached my whole fime, if someone could help me out, it would be really appreciated. Here's mu main.cpp file : #include "mainwindow.h" #include <QApplication> #include <QDebug> #include <windows.h> #include <conio.h> #include <stdio.h> #include <string.h> #include <math.h> // Universal data #include "universal.h" // FS interface #include "FSinterface.h" #include "FSUIPC_User.h" // for setting the timer #include "timer.h" // for Serial RS232 #include "tserial.h" #include"universal.h" #include "types.h" const char *pszErrors[] = { "Okay", "Attempt to Open when already Open", "Cannot link to FSUIPC or WideClient", "Failed to Register common message with Windows", "Failed to create Atom for mapping filename", "Failed to create a file mapping object", "Failed to open a view to the file map", "Incorrect version of FSUIPC, or not FSUIPC", "Sim is not version requested", "Call cannot execute, link not Open", "Call cannot execute: no requests accumulated", "IPC timed out all retries", "IPC sendmessage failed all retries", "IPC request contains bad data", "Maybe running on WideClient, but FS not running on Server, or wrong FSUIPC", "Read or Write request cannot be added, memory for Process is full", }; char buffer_fsupc[25000]; char buffer_reception[12]; char bufftx[40]; int main(int argc, char *argv[]) { QApplication a(argc, argv); MainWindow w; double Attitude[NROT]; FSAttitudeType FSAtt; DWORD dwResult;// a pointer to receive an error number if the operation fails. Tserial *com; // Serial declaration int SampleTime; // Sample Time in ms Timer timer; int capsam=0; int pousseeL, pousseeR; int pousseeOldL = 0, pousseeOldR = 0; char car; int vret,index=0; int oktrame=0; int pousseeTmp; char x[]=" \\\\.\\com3"; if(FSUIPC_Open(SIM_ANY,&dwResult)){ // Declaration des variables locales const char *pFS[] = { "FS98", "FS2000", "CFS2", "CFS1", "Fly!", "FS2002", "FS2004" }; // Change made 060603 // Okay, we're linked, and already the FSUIPC_Open has had an initial // exchange with FSUIPC to get its version number and to differentiate // between FS's. printf ("CapSim: Link established to FSUIPC\n") ; // printf ("Sim is %s,FSUIPC Version = %c.%c%c%c%c\r%s\n",(FSUIPC_FS_Version && (FSUIPC_FS_Version <= 7)) ? pFS[FSUIPC_FS_Version - 1] : "Unknown FS",'0' + (0x0f & (FSUIPC_Version >> 28)),'0' + (0x0f & (FSUIPC_Version >> 24)),'0' + (0x0f & (FSUIPC_Version >> 20)),'0' + (0x0f & (FSUIPC_Version >> 16)),(FSUIPC_Version & 0xffff) ? 'a' + (FSUIPC_Version & 0xff) - 1 : ' '); /* ///////////////////////////// une autre maniere de faire ///////////////////////////// */ // Timer //printf("\nEnter the Sample Time in miliseconde\n"); //scanf("%d",&SampleTime); SampleTime=100; // RS232 com=new Tserial(); if( com!=0 ) com->connect (x,9600,spNONE); // com Initialisation else printf("Error Setting COM"); }else{ //Openninig FSUIPC failed printf ("CapSim: Failed to open link to FSUIPC:%s\n", pszErrors[dwResult]) ; FSUIPC_Close(); // Closing when it wasn't open is okay, so this is safe here // com->disconnect(); // Closing the port return 0; } while(true) { Sleep(40); //if(timer.elasped((clock_t)SampleTime)) if(1){ /* -------------------------------------- Sending Data -------------------------------------- */ // Read from FS data structure FSUIPC_Read(0x000,25000,buffer_fsupc,&dwResult); FSUIPC_Process(&dwResult); // Process all the request(s) // sprintf(bufftx,"%4u %3u %6u %3u",*((unsigned int*)(buffer_fsupc+0x2BC))/128,(unsigned int)(*((double*)(buffer_fsupc+0x2CC))), // (unsigned int)floor((double)(((unsigned int)*((__int64 *)(buffer_fsupc+0x570))*(double)3.2808)/((double)65536.)+0.5)),0); /*(unsigned int)floor(((unsigned int)*((unsigned short int*)(buffer_fsupc+0xcc))*360.)/65536.+0.5),(unsigned int)*((unsigned short int*)(buffer_fsupc+0xe2)), (unsigned int)floor((double)(((unsigned int)*((unsigned int*)(buffer_fsupc+0xd4))*3.2808)/65536.+0.5)));*/ /* sprintf(bufftx,"%6u %01u %01u\n", *((unsigned short*)(buffer_fsupc+0x5682))&0xffff, *((unsigned char*)(buffer_fsupc+ 0x568A))&0xff, *((unsigned char*)(buffer_fsupc+ 0x568E))&0xff); printf("%s\n",bufftx);*/ if(_kbhit()){ car=_getch(); switch(car) { case ui->Alt : printf("To change Altitude turn the Dial"); capsam= (capsam*(65536./3.2808)); *((unsigned int*)buffer_fsupc)= capsam; FSUIPC_Write(0x7D4,4,buffer_fsupc,&dwResult); FSUIPC_Process(&dwResult); break; case ui-> Spd: printf("To change Speed turn the Dial:"); scanf("%u",&capsam); capsam = (capsam*16384)/100; *((unsigned int*)buffer_fsupc)= (unsigned short int) capsam; FSUIPC_Write(0x88C,2,buffer_fsupc,&dwResult); FSUIPC_Process(&dwResult); break; case ui-> Hdg : printf("To Change Heading , turn the Dial"); scanf("%u",&capsam); capsam= (capsam*65536)/36; capsam += ((capsam%10)>=5 ? 10 : 0); capsam= capsam/10; *((unsigned short int*)buffer_fsupc)= (unsigned short int )capsam; FSUIPC_Write(0x7CC,2,buffer_fsupc,&dwResult); FSUIPC_Process(&dwResult); // Process all th break; }} w.show(); return a.exec(); } } } The errors I am getting are these: Tserial: undeclared variable. line 59 com : undeclared variable. line 91,93, syntax error; identifier ' Tserial'. Ui undeclared variable., Alt undeclared variable. mainwindow.cpp main.cpp fsinterface.cpp

Hi Pete, Can't believe after all this time I haven't used profiles. With all my lua files (30+) made for specific aircraft it was starting to become a nightmare - not any more! 👍 One thing I noticed, and was the assumption it would work, is the use of [General] ShortAircraftNameOk=Substring along with UseProfiles=Files. I have in the main .ini - [Profile.T-6 Texan] 1=A2A North American T-6 Texan RTW_9 2=A2A North American T-6 Texan RTW_5 [Profile.Bearcat] 1=F8F-2 Bearcat FSX V2 Worn OD RTWR Panel 2=Grumman F8F-2 Bearcat VF-61 RTWR Panel [Profile.SHRS] 1=22_SHRS_YFB-111A 2=17_SHRS_F-111F If I select any other SHRS, Bearcat, T-6 Texan other than what is listed specifically, the profile doesn't engage. Otherwise it works for the specific listed aircraft. Is this the way it is supposed to work? Just realized something but don't have time to test, is the following the key to it working? [Profile.T-6 Texan] 1=T-6 Texan [Profile.Bearcat] 1=Bearcat [Profile.SHRS] 1=SHRS Thanks, have a great day.. Roman EDIT -- The latter was true.... 👍👍👍😄

I am trying to find out how to change the panel.cfg or whatever, so that I do not get the flickering mouse and loss of FPS. I am using a 3 monitor Eyefinity setup.

Moved to Main Forum. Please ask questions related to FSUIPC always in Main Forum! Is there a way to get the ground elevation for a given latitude/longitude position. I need to get the current ground elevation (representing the scenery) at a given position, which is NOT my own aircraft's position and NOT the position of another AI aircraft. I know how to do it with FSX and P3d/simConnect, but need a similar function for FS9. Any hint how I can do it (if possible)?

hi all I want to integrate external switches and buttons to FSX Steam to control an FSLABS A320 add-on. Therefore I bought and installed FSUIPC4.x to assign key strokes to certain FSX controls. Unfortunately the "Mouse Macro" feature seams not to work for the FSX steam edition (there is no "green pop-up confirmation" after recording the action). Any idea what is wrong with my setup? Any ideas or guidance how to solve my challenge?

I have installed FSUIPC onto a W10 machine and added the following to the FSUIPC4.ini file: [Monitor] Display=4 Monitor0=0,024C,4,0 on XP it correctly displays the VAS, but on W10, the value is zero:

Good afternoon, I’ve been slowly working on assigning overhead switches to switches on my throttle quads. As I don’t have LINDA, I’ve been using the List Var command. When I do this for both the Dornier 228 or B1900 by Carenado, I run into issues. I’m copying the command from the log created and placing it in a macro file. I then go back into FSX and FSUIPC. In this case, I’m using the Dornier and attempting to work one of the battery switches. This is what I have in the macro file: 1=L:ASD_DO228_SWITCH_BATT_1_METALIC=Toggle I use FSUIPC to tie the above macro command, but back in the sim the switch does not move. I have used this process with other aircraft and have had no issues. Has any else had issues with Carenado planes? Cheers, Colin Gray