Thomas Richter

Hi, to register FSUIPC4 or FSUIPC+WideFS there is no need of internet access. After you bought a registration key just copy and paste the information i.e. to a text file and copy that text file to your FS-PC. When running the FSUIPC4 installer copy and paste the information into the fields rather than typing to avoid type or reading errors. PMDG doesn't use FSUIPC, it communicates via SimConnect direct with FS/P3D. Thomas

Hi, WideFS(7) is part of FSUIPC4 that means it is inside FSUIPC4. So when you update to latest FSUIPC4 you have automatically latest WidFS7. The only thing you should then as well is updating WideClient on your client PC's to latest version. But same thing as with FSUIPC4, WideClient when replacing it with a newer version will NOT change settings in its INI file, so its save to do so. Just copy and paste the files out of the ZIP into the WideClient folder on your Client PC's. WideClient 6.999z2 BTW- It is always good practice to have a copy of any INI and CFG file from FSUIPC4.ini / WideClient.ini / P3D.cfg ... just in case a possible change you might have done doesn't work or something goes wrong, so you can always revert or crosscheck. Thomas

Hi, the FSUIPC4 version number of your installed FSUIPC4 you will find in the FSUIPC4.log file (you can open with any text editor, i.e. Windows Editor). The file is located in your P3D main folder\Modules\ (i.e. YourDrive:\Prepar3D v3\Modules\). Direct in its first line i.e. ********* FSUIPC4, Version 4.959 ... You should be able to access the file i.e. from your Instructor Station PC over the network, normally you have to Share the FS folder. But if your version is older than 4.959 you have to use the installer in any case. Most correct information about behaviour of FSUIPC you will get / find here in the forum! FSUIPC4 Installer does NOT modify or create a new INI file or it's content like your settings/ definitions/ calibrations. DownLoads There are free programs like TeamView or TightVNC you can handle your Server PC(FS) from a different PC, that's was the very most with a FlightSim do/ use. No need to change your screen setup or anything!! Thomas

Hi, looking at function Armrest_Toggle() ipc.writeLvar(nToggleVal(ipc.readLvar("L:Twot_Armrest"), 0, 1)) end the write should of course have the L:"LVariablename" you want to write to but you don't supply any, just the returned nVal1 !? ipc.writeLvar(“name”, n) Thomas

Hi, in C/C++ you need a forward declaration to have the definition below the actual call. So you write bottom up if you don't do this, means you might need to have the local function Armrest_Toggle()... above the calling part. The error says you are looking for a global function, that means your actual function is not visible when you call it. Thomas

Hi, are all the axis ONLY defined and calibrated in FSUIPC and Controller use in P3D is switched OFF? Does that happen as well without any Lua and Linda? Thomas

Hi, No. FSUIPC(3) works with FS2000 / FS2002 / FS2004 and limited with Microsoft Combat Flight Simulator(CFS1 and CFS2). FSUIPC4 is for FSX / FSX-SE and Prepar3D only. Thomas

Hi, as I said before I would just start without ANY add-on to find the problem. Here I neither see a problem with P3Dv3.4.14...(Hotfix 1) nor with P3Dv3.4.18... (Hotfix 2) BUT I don't have add-on installed. @gypsyczar you say you only have GSX as add-on installed that runs at the same time but this is from your log file!? 44562 LUA.1: *************************** STARTING LINDA ************************** 44562 LUA.1: LINDA:: [START] Loading System Configuration files 44594 LUA.1: LINDA:: [START] VRInsight MCP Set = mcp 44609 LUA.1: LINDA:: [START] System Configuration files loaded 44750 LUA.1: LINDA:: [START] ************************************************************* 44750 LUA.1: LINDA:: [START] New Aircraft Selected - restarting... 44750 LUA.1: LINDA:: [START] ************************************************************* 44750 LUA.1: LINDA:: [START] Current Aircraft: F-22 Raptor - 525th Fighter Squadro 44906 LUA.1: LINDA:: [START] Aircraft module detected: FSX Default 44922 LUA.1: LINDA:: [START] ************************************************************* 44969 LUA.0: LINDA:: [INIT] Starting Initialisation... 45016 LUA.0: LINDA:: [INIT] Loading Libraries... 45016 LUA.0: LINDA:: [LIB] AivlaSoft library loaded... 45016 LUA.0: LINDA:: [LIB] ATC library loaded... 45031 LUA.0: LINDA:: [LIB] FSX standard library loaded... 45031 LUA.0: LINDA:: [LIB] FS2Crew library loaded... 45047 LUA.0: LINDA:: [LIB] FSX Functions loaded... 45047 LUA.0: LINDA:: [LIB] IVAO library loaded... 45047 LUA.0: LINDA:: [LIB] RealityXP library loaded... 45062 LUA.0: LINDA:: [LIB] Saitek Functions loaded... 45062 LUA.0: LINDA:: [LIB] VATSIM library loaded... 45078 LUA.0: LINDA:: [LIB] VRInsight Function Library loaded... 45078 LUA.0: LINDA:: [LIB] Weather library loaded... 45078 LUA.0: LINDA:: [LIB] A2A MAP library loaded... 45078 LUA.0: LINDA:: [INIT] Initializing Common Variables... 45125 LUA.0: LINDA:: [INIT] User GLOBAL config loaded... 45141 LUA.0: LINDA:: User's modifications script is loaded... 45141 LUA.0: LINDA:: [INIT] User FUNCTIONS loaded... 45156 LUA.0: LINDA:: [INIT] Finalising Initialisation... 45312 LUA.0: LINDA:: [COMM] Checking VRI 45328 LUA.0: LINDA:: [INIT] Module: FSX Default Started... 45469 LUA.0: LINDA:: [INIT] Ready to go, Captain! 45469 LUA.0: LINDA:: [INIT] *************************************************************** Lots of stuff loading there, also I remember problem with this Linda couple weeks ago? Disable this and the Lua file first. Also the P3D version you use came out after the FSUIPC release and maybe Pete didn't know about it. Thomas

Hi, when you say the only solution is to run the installer again, then there is something that changes when you run P3D up to it crashes. So what the installer is doing is it places the DLL and PDF's in the module folder, it DOESN'T do any changes to your FSUIPC4.ini file and there is NO registration in Windows of FSUIPC4 at all. In addition it checks the correct registration of P3D in Windows Registry and if need and possible it will correct it. The only file it actually changes is the DLL.XML file in C:\Users\YourLogin\AppData\Roaming\Lockheed Martin\Prepar3D v3\ where it adds the launch part for FSUIPC4 and the end. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> As you all say the solution is to re-run the installer you might check the DLL.XML file after the installer and again when P3D starts crashing if there is a change. Also I would advise for testing that all installed add-ons, other than FSUIPC, are disabled and a default A/C is already launched on start-up of P3D. Thomas

Hi, the Key's list is on page 21 in FSUIPC4 for Advanced Users.pdf, wrong page No. Open Button + Switches tab and press the joystick button to program, then select on the left Key press to repeat while held Now select Set button and press Ctrl key plus a key (could be any), Close FSUIPC with OK button and then close FSX (P3D). Open the FSUIPC4.ini file and go to [Buttons] section. Here I used Ctrl + A key so I have the line x=U0,10,K65,10 -{Key press: ctl+A}- (the x is just the number in your case). Now just change the K65 to K0, that means it will send Ctrl without any kay just Ctrl, save the file and restart FS. The new line here then looks like 1=U0,10,K0,10 -{Key press: ctl+(null)}- Thomas

Hi, as it says you provide in offset 0x0D6C (4 byte Int) the address (offset) you want to get your value from the L:var and then write into offset 0x0D70 the string of the L:var with zero termination. I.e. using Offset 0x66C0 (8 byte length, double or FLT64) Write to Offset 0x0D6C (4 byte Int) the value (hex) 0x66C0 Write to Offset 0x0D70 and onwards (max 40 byte) the ASCII values of "ACDoor1" with NULL termination, 65, 67, 68, 111, 111, 114, 49, 0 Now process FSUIPC, do not process before both Offsets have been written. Now you should be able to read the value in Offset 0x66C6 (8 byte length as double or FLT64). If the L:var is correct you should get the correct value Thomas

Here that works ok, nothing else I can do. The link above is the latest version and the key as well as above just, www.technicalservicerichter.com Nothing else is needed Thomas

Hi, as I said I would first start FS with a default A/C and not loading already an Add-on and then switching to a default, just to eliminate any interference of an Add-on. You still have the A2A loaded first. 52891 C:\Users\ESCORCIAW10\Documents\Prepar3D v3 Files\LEVC A2A C172 AHS GA PARKING.fxml 52891 C:\Prepar3Dv3\SimObjects\Airplanes\A2A_C172\C172.air Thomas

Hi, when you open FSUIPC and select the Button + Switches tab that will already answer your question. Otherwise the FSUIPC4 User Guide.pdf contains a description, by searching in it for "key press" you will end up on page 40 and following. Thomas

Hi, there is no standard control for that in FS and so FSUIPC doesn't provide one because it is related to the specified Add-on A/C. Don't they provide any info for that Add-on, i.e. an SDK? May be they use L:vars and you can use Lua to create that function. Thomas

Is this the full content after closing or crash? First thing I would do is to start with a default aircraft to eliminate errors that could come from an add-on A/C. Thomas

Hi, still no FSUIPC log file? The log file gives information about what is going on within FSUIPC. Thomas

Hi, the flight-plan .WX gets sometimes corrupt and forces FS to crash while loading a flight, i.e. on FS start-up. The wxstationlist.bin gets updated when loading real-weather and can get corrupt when loading over the internet, but it will be recreated by FS (or P3D) when it doesn't exist on start-up. So by deleting it makes sure you will get a fresh default one. The added line in FSUIPC INI "NoWeatherAtAll=Yes": 14. A diagnostic facility to make FSUIPC avoid all weather reading and writing activities has been added. This is invoked by adding “NoWeatherAtAll=Yes” to the [General] section of the FSUIPC4.INI file. That means FSUIPC doesn't care about the weather, so it will not read or manipulate, like wind smoothing ..., the FS weather. What external programs like ASN... writes into FS(P3D) is not effected because it is not written via FSUIPC, they use SimConnect direct. Thomas

Hi, the very first thing to do is to set your PC date correct, FSUIPC shouldn't work because the release date is 13 years later than the actual PC date! 7187 System time = 08/01/2003 01:09:51 In addition, FSUIPC doesn't send data to any program but it provides data in a memory area other programs can read or write to. Thomas

Hi, it is always the FSUIPC log file needed to see how far or what FSUIPC logs, always copy and paste the full content of the log file to your message. @qquertz: When you successfully installed latest FSUIPC4 the log will show the installed version, here: ********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson ********* The DLL version No. seems to be not updated in the latest version 4.959 and show still 4.958. Did you try the above suggestion, here more detailed? Most likely it is a corrupt weather file problem or the weather station file itself that is corrupt and forces a crash as soon it is loaded. It is only happening when FSUIPC is present because it still causes SimConnect to read the weather. You can try deleting the wxstationlist.bin and the .WX files? That's fixed such problems in the past. For FSX the wxstationlist.bin file you will find under: C:\Users\TSR\AppData\Roaming\Microsoft\FSX\ For P3Dv3 the wxstationlist.bin file you will find under: C:\Users\YourLogin\AppData\Roaming\Lockheed Martin\Prepar3D v3\ The .wx file of the flight that currently is loaded is located in your saved flights folder, i.e. C:\Users\TSR\Documents\Prepar3D v3 Files\ To stop that entirely you'd need to set/add "NoWeatherAtAll=Yes" in/to FSUIPC4.ini file. Thomas

Hi, sorry, already too long ago that I maintained the software and removed the original key system. The key is just: www.technicalservicerichter.com Thomas

Hi, didn't you just check the FSUIPC4 Offsets Status.pdf, the very first one I would look into when searching for an Offset? There you will simple find this by searching for Lvar: 0D70 40 Macros and Lua requests ... L:Var read and write requests First write the offset address to which the resulting value (an 8- byte double or FLT64) will be written (for a Read) or the value to be written can be found (for a Write). This MUST be one of the user offsets, i.e. in the range 0x66C0 to 0x66F8. Then write to 0D70 the name of the LVar, preceded by just one : (colon) character for a read or :: (two colons) for a write, and terminated by a zero byte. The reason for the use of user offsets is to avoid corruption when more than one application is running which reads L:Vars in this way. It is a matter for the programs, probably with user cooperation, to avoid clashes. Both 0D6C and 0D70 can be written together or at least in one Process call, and the result of a read can be read immediately, even in the same Process call. For a write the value to be written can be placed in the stated offset in the same Process call too, provided it is before the writes to 0D6C and 0D70. If the Lvar does not currently exist the result of a read will be 0.0. There’s no way to detect if a write succeeded other than to read the L:var afterwards. If the offset provided is invalid the request is just ignored and the offset value unchanged. I think simple enough and your program just checks if the Doors Offset or User Offset is set. Thomas

Hi, the reason was that actually P3D wasn't included in FS version list. I just changed that, you can download the latest version here. The key is also removed, freeware now. Technical Service Richter-TSR was closed in February 2016. ECL_1.0.2.176.zip Thomas

Hi, FSUIPC will not be the faulty module. It is only listed because it runs within the P3D process, like any other P3d module (DLL) is listed of course. Most likely it is a corrupt weather file problem or the weather station file itself that is corrupt and forces a crash as soon it is loaded. That this happens with FSUIPC depends on that FSUIPC forces P3D (or FSX) to load the weather. It is only happening when FSUIPC is present because it still causes SimConnect to read the weather. You can try deleting the wxstationlist.bin and the .WX files? That's fixed such problems in the past. To stop that entirely you'd need to set "NoWeatherAtAll=Yes". Thomas

Hi, if you didn't register at installation, just start FSX and open under Add-On the FSUIPC. On its first page that opens you will find on the right side registration buttons that will open the same panel as shown on the installation sequence. You can also start the installation again without any harm and do the registration there. Also make sure you use the latest installer Install FSUIPC4.959 Best practice as described in the installation manual is to copy and paste the details (name, email and key) instead of typing it in, gives very often error. Thomas