Thomas Richter

Hi, you do the same for fsuipc in DLL.xml, set fsuipc to disabled.

Hi, check if you find a new FSUIPC INI file that is used instead when you start in this migration mode. If so you need to copy the key file and rename it to the same as the new INI file.

Hi, I have only P3D v2.5 installed with both hotfixes ,it runs ok and produces correct all files. Make Runways File: Version 4.678 by Pete Dowson Reading SCENERY.CFG ... CFG file being used is: "C:\ProgramData\Lockheed Martin\Prepar3D v2\SCENERY.CFG" ... and so on

Hi, In Win8.1 you need to set Energy saving to OFF and in USB set Selective Energy saving to OFF. Well, some folks say this, but I really don't understand why it should make any difference, as FSUIPC uses similar methods, via DirectInput, as FSX and P3D. In theory they should both get the same results. Any hardware that does the same as Saitek does/ did, have a hardware defined 'dead zone' (not changeable in windows or their driver), so after some time in centre or no movement Win 8.1 (very strong on energy saving designed) thinks the device is no longer used and switches it off. In case FSX/ P3D don't poll the devices but get changes/ events windows doesn't get forced to read the device and keep it alive. As far as I know you (Pete) poll the devices (?) and so FSUIPC keeps them alive, with the correct energy saving options set in Win 8.1. Also people with old spiky controller will not face that problem because Windows will send continuous events to FSX/ P3D and doesn't switch the device off. Would that make sense?

Hi, FSUIPC 4.939 DOES support P3D v2.5 because Pete added that just before he left for vacation. BUT the Hotfix for P3D v2.5 is not included because it was released later. So those special functions they use calls into P3D code will not work and P3D might even crash because they are in the wrong position. So if P3D v2.5 with hotfix doesn't crash that doesn't mean FSUIPC fully functional! It's only couple days and he is back to fix that again. Install complete FSUIPC version 4.939 Install FSUIPC4939 for FSX, FSX-SE and Prepar3D versions 1.4 and 2.0-2.5 -- See changes document for details up to 4.939 -- Adds Support for Prepar3D version 2.5 -- G3D fix as in FSX now also applies to FSX-SE -- Installer labels install problems more intelligently FSUIPC version 4.939 only FSUIPC 4.939 -- If you already installed 4.938-4.938h, you can just copy this DLL into the FSX Modules folder.

Hi, as I said at that time SIOC needs to be installed on the PC where its hardware is connected to. The IOCPServer.dll is not needed, delete and remove its activation in DLL.XML file in ...\AppData\Roaming\Lockheed Martin\Prepar3D v2\DLL.XML And as you said already disable clients in sioc.ini file e.g. [************** IOCP CLIENT MODULE #0 ***************] [ Desactivar el módulo cliente IOCP ] [ Disable IOCP client module ] IOCPclient0_disable=Yes [************** FSUIPC MODULE ***************] [ Desabilitar lectura de las FSUIPC ] [ FSUIPC disable mode yes/no ] FSUipcdisable=No [ Refresco recepción FSUIPC ] [ FSUIPC refresh ] FSUipcRefresh=50 So it will use FSUIPC only.

Hi, just try and see what happens. It might be that FSUIPC ignores just the profiles for not existing aircrafts and only look for a profile when the aircraft is actually selected. Just give it a go, FSUIPC will not do any changes to P3D or its settings anyway.

Hi, just run the latest installer 4.939 (or higher). If the installed version in FSX is already latest the installer will not overwrite the existing DLL. If the Installer version is newer then it will replace the existing one with the new DLL file, but it will not change anything in your existing INI file (your settings). So no worry.

Hi, normally you can do this as long it is the same PC and all controller are in the same place (USB connectors). And of course all aircrafts do exist in the new version. Don't forget to update to latest FSUIPC4 version that supports P3D v 2.5.

Hi, does it physically switch the LUA logging on in FSUIPC Logging section, marked? If so, then a program that runs on the server or on a client is doing this! I found that e.g. Opencockpit software is doing that by using the Offset 3400 for that, for no reason of course. Just log the Offset 3400 (U16) in FSUIPC and check which program (thread number) is doing that. If it is not possible to stop a program doing that then just add this to [WideFS] section in FSUIPC Deny=3400,2 or on the client under [user] section Deny=3400,2 That prevents programs to activate or de-activate logging options via Offset 3400.

Hi, you can write values direct to the throttle lever via Offset 089A for Thr_1 and 0932 for Thr_2. You need to convert of course the value from your Min and Max values to 0 to 16384. If the axis include Reverser then from -4096 (full Reverse) to 16384.

Hi, do you see a chance also to get the heading of the FSstart position? Heading of Start position is simple the RWY heading, take care of Variation. RWY heading and Variation is included in the XML file.

Hi, Pete didn't mean his FSUIPC4 for FSX/ P3D, he meant the P3D version you use. The FSUIPC4 version you bought is for FSX/ FSX SE/ P3D v1.x and P3D v2.x. The latest version of FSUIPC/ FSUIPC4 you will always find above under Download Links->Updated Modules Make sure you use latest installer from that link. Once you bought FSUIPC4 updates are free for FSUIPC4.

Hi Jumachado, what you show and describe 'Works perfectly on Windows' might not be correct because the picture you show is not the Windows GameController software where you can check it will work it that way for FSUIPC, it is the driver from that Mad Catz controller. To check it works ok in Windows you need to go to systems and open GameController, there you will find your controller to check how it works raw in windows.

Hi, I don't think this is neither an FSUIPC problem nor a LM problem. I had this long time ago and it was related to graphics card and driver (NVidia), the problem disappeared with a newer PC and newer graphics card. That doesn't mean you have an old PC or graphics card but may be the graphics driver version is not as good.

Hi, check that in FS Controls setup for that controller no axis is defined automatic by FS, what FS does when you disconnect/ reconnect or change the USB port for that controller.

Hi, the SDK is not the place to look for actual Offset status. The place to look at is \Moduls\FSUIPC Documents\ There you will find the latest FSUIPC4 Offsets Status.pdf that was installed with the latest Full Installation you did.

Hi, I do have that [JoyNames] AutoAssignLetters=No 0=G940 0.GUID={1E55BA40-0D35-11E4-8001-444553540000} 1=Logitech G940 Joystick 1.GUID={1E562F70-0D35-11E4-8002-444553540000} 2=Logitech G940 Pedals 2.GUID={1E56F2C0-0D35-11E4-8004-444553540000} and I didnt actually know I could update it for free hehe silly me. anyways it is now up to date Do you then see in FSUIPC the controller axis you move on that joystick? Sometime you can face the problem that a 'nervous' axis from a different controller is seen only every time you press the Rescan button. So if you have that problem then best is to disconnect the other controller BUT remember their position in the USB sockets.

Hi, why would you have an 'old' ford Mondeo if you can just get the latest one for FREE. Just use latest available FSUIPC4 as it is free to update anyway and Pete can only look into code, if needed, of latest available version. That's why there is 'no support' for any older version than the current one. Then follow precisely the manual to setup axes in FSUIPC. Any joystick controller that is seen in Windows - Game Controller is seen in FSX and also in FSUIPC. But the controller is not named in FSUIPC's UI, it has just a controller number instead. If you did run FSX or P3D then you will find in its Modules folder the FSUIPC4.ini file. It contains the section [JoyNames} where all connected (at that time) joystick controller are listed with its given number and GUID. Here is what it looks like in mine with a connected Logitech Extreme 3D and a PPM controller: [JoyNames] AutoAssignLetters=No 0=Logitech Extreme 3D 0.GUID={0667FA70-5979-11E4-8005-444553540000} 1=PPM 1.GUID={7B1FD020-6F65-11E4-8001-444553540000} So you should find your controller listed in yours, do you?

Hi, makeRwy does multiple files for different programs. The cws files with same or more information in it (depending on which version you use, R4/ R5) are available, you wrote you could use that format to create your own SQL database. As well a XML file with all information is available. MakeRwy is a tool that converts FS information into a file format of the programs it was designed for like FStarRC, RadarContact and many others they just use their formats as they are. Any more information about that special rws binary format you want to convert only Pete could give you, he will be back on 25th.

Hi, did you read the included MakeRwys ReadMe.txt? Runways.xml An XML file providing a database of airports and their runways. FStarRC.rws This is a binary runways database used by my FStarRC program. Airports.fsm This is a binary airports database used by FS_Meteo, at present after re-naming to "Runways.rws". Runways.csv This is a comma-separated text database of all the runways, sorted, and it is in the particular format used by Radar Contact (all versions up until the change to the following: R4.csv This is the same as the previous CSV file, but includes additional runway data added at the end of each line. This is used in Radar Contact 4 (before RC4.3) for more precise ATC operations. R5.csv This is the same as R4.csv but with runway closure indicators in an extra two fields - CL closed for landing and/or CT closed for take-off. This file is used by RCV4.3 and RC5. G5.csv This contains information about Gates, Ramps, Parking places, along with airline lists where specified. It is used by later versions of Radar contact. T5.csv This contains details of all taxi paths.It is used by later versions of Radar contact. F5.csv This lists all COM frequencies and associated names, including the airport name, for Radar Contact 5 or later. F4.csv This lists all COM frequencies and associated names, including the airport name, for Radar Contact 4. If you want to use this with RC4 you must copy it to the Radar Contact 'data' subfolder. Make a safe copy of your original F4.CSV file first (I usually just rename it to "f4orig.csv"). Note that MakeRwys matches frequences as best it can, with the following extra "fiddles" to ensure a good range of frequencies: 1. Clearance Delivery is preferably met by FS type 14 "CD", but else is met by type 7 "CLEARANCE". 2. Multicom is met by FS type 2 "MULTICOM", but failing that by type 4 "CTAF". 3. Approach is from FS type 8 "APPROACH", but failing that from a second Type 9 "DEPARTURE" if there are more than one of the latter. 4. Deparature is from FS type 9 "DEPARTURE", but failing that from a second Type 8 "ARRIVAL" if there are more than one of the latter. Centre, FSS, AWOS and ASOS frequencies aren't used for this file. ...

Hi, you need to contact simmarket for that, they will for sure help. You need to use there Ticket system.

Hi, FSUIPC itself doesn't disconnect the AP and as you said already it doesn't happen with any default AC. - for B737 it is correct, Trim-input will disengage the AP, that will be programmed by PMDG. - for other AC with AP it should be as well because when overriding an automatic system that system should kick out because it is doing something wrong, that's the reason you override it.

Hi, Pete is on Holiday and returns on 25th I think. I suspect this means there is a problem with the sensors inside my Saitek Pro yoke, but I would be grateful if you could give your opinion. If indeed this is the problem, do you know if there some way I could fix it by opening up the yoke black box and cleaning contacts/pitch pots or whtever may be causing the problem? :( Did you calibrate the controller, first of all, in Windows GameController? You can open this Windows tool as well from FSX, Controller -> Calibration. FSUIPC gets the Controller axis position like FSX from Windows API, so the basic important calibration has to be done first there. If you did this already and you have the described problem, then your controller is not ok.

Hi, Also I have checked that the FSUIPC is 4.936. but its still new, As you as well stated before that it works well with FSX but not with P3Dv2.4, it is well known that you have to use latest FSUIPC4 version! The version you use, 4.936, is old and works correct only up to P3D v2.3. So first thing to do in any case, update to current FSUIPC4 version 4.937 that only supports P3D v2.4 and earlier (and FSX of course).