Jump to content
The simFlight Network Forums

Thomas Richter

Moderators
  • Posts

    1,506
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by Thomas Richter

  1. Hi, As you can find it in the FSUIPC manual, located in YOUR FS FOLDER\Modules\FSUIPC Documents, you just increase the number. Just search for RunIF in the FSUIPC4 for Advanced Users.pdf file.
  2. Hi, he doesn't add those two lines to program or use GF via FSUIPC, he just adds those lines (actually only one is needed to start and close the application) to start and close the GF driver via FSUIPC. The reason seems to be that the GF installer is not done for P3D v2 and cannot find and implement the needed lines into the dll.xml file and so the GF driver will not start automatically when P3D starts. If in your FSUIPC4.ini file is no section [Programs} then just create one somewhere below [Programs] RunIF1=Ready,Close,LINK TO GF DRIVER Where LINK TO GF DRIVER means that is the actual location + file name.exe. The following line links i.e. to an MCP driver. RunIF1=Ready,Close,F:\FSTools\pmMCP\mcp.exe
  3. Hi, My question is how with a leo bodnar the overhead will work all together? could be that possible only add in the bodnar the items that doesnt work ?? and also add part of the FWD OVHD that is not wired. No that is not possible because the BOB is connected to different Inputs and Outputs (Annunciators). In Cockpitsonic driver you cannot disable some functions of a BOB and others not but only the whole BOB of a gauge. That means the driver would always overwrite those switch inputs with what it believes is the actual state. The only way then would be to disable the BOB of that gauge and connect all Inputs and Outputs of that BOB to a different I/O board. Or getting a replacement BOB.
  4. Hi Pete, no he has apparently the standard version where the switches are connected to the BOB of the pressure gauge. As he describes that the Start-switch 1 not showing changes in Offset 5610, also not after re-soldering and replacing the rotary, it looks like the common cable for the rotary doesn't work or the BOB is broken for that function. There are SMD diodes/ resistors on the BOB for the coded connections (lines/ rows).
  5. Hi Pete, your Start-switches are connected to a separate start-switch board from Cockpitsonic that controls also their solenoids.
  6. Hi, - for pmFileCheck, you might not use latest version of it. That error has been in it couple times but is NOT related to FSUIPC / WideClient. - for pmInstructor, if I remember correct it was as well an error but solved from PM. You should contact PM support about that.
  7. Hi, was the registration email address the same for both?
  8. But what shows FSUIPC in FS when you open it from Addons tab?
  9. Hi Gerrit, there is not really a special procedure. Just open FSUIPC and in the registration fields you paste the copied email and key's. Do you get an error message that WideFS doesn't register or it 'just' doesn't work? Btw- there is nothing to download and unzip into Moduls folder where FSUIPC is located other than FSUIPC itself. That was only needed with FSUIPC3 and its WideFS for FS9.
  10. Hi, make sure you bought the correct WideFS version for FSX/ P3D (WideFS7) as you FSUIPC is. The WideFS version for FSUIPC3 (FS9) will not work with FSUIPC4.
  11. Hi, first of all you version of FSUIPC doesn't suit P3Dv2.3. Download and install latest FSUIPC version 4.936 Install FSUIPC4936 after that download and install as well latest interim 4.936a Then try again.
  12. Hi, just use the FSUIPC4 installer and it will install FSUIPC4 into any FS version correct installed on your PC (FSX, P3D and P3Dv2.x), The log will show which version was found and that FSUIPC was installed.
  13. Hi, "0894 2 Engine 1 combustion flag (TRUE if engine firing)" the "2" gives the length of the offset, in this case it is int16, what is in C# a short. private Offset<int> eng1Ignition = new Offset<int>("AcarsData", 0x0894); should be private Offset<short> eng1Ignition = new Offset<short>("AcarsData", 0x0894); (TRUE if engine firing), rmember computer do only know 1 and 0, 1=true / 0=false. So the offset will return in that case value ONE (1) for true.
  14. Hi, any licenses like FSUIPC are personal licenses. Personal license means it is only linked to the person who bought it and can not be transfered. Btw- you say you sell your 'full size 737 sim' and that means as long you didn't buy e.g. the Professional version of ProSim / Project Magenta or SimAvionics for between 5,000 to 10,000 Euro then you cannot transfer those licenses either because they are for Private /Personal use only ! Even if a Private person buys your sim he/ she will have to buy a new license.
  15. Hi, as Pete already said the program (in your case Saitek) try to connect to FSUIPC before it is ready. Because of bad handling of 'FSUIPC is not ready' it throws an exception instead of 'quiet' trying again ... But anyway. Saitek programs are in FSX started via exe.xml file, just Disable both programs in exe.dll (if in your case there are two to start) via FSUIPC <Launch.Addon> <Name>Saitek Panel(s) Plugin for FSX</Name> <Disabled>True</Disabled> <Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> <Launch.Addon> <Name>Saitek Panel(s) Plugin for FSX</Name> <Disabled>True</Disabled> <Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanelsFS9.exe</Path> <CommandLine>-run</CommandLine> </Launch.Addon> In FSUIPC start the program(s) with [Programs] RunIf1=Ready,CLOSE,C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe RunIf2=Ready,CLOSE,C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanelsFS9.exe That makes sure the programs are never started before FSUIPC is fully up and running and so they can not throw the exception. Don't forget to disable <Disabled>True</Disabled>
  16. Hi, Fuel Selector is not the way to feed the engine with fuel, you need to use the Fuel Cutoff lever. In FS it is the Offset for Fuel Mixture. 0890 2 Engine 1 Mixture lever, 0 – 16384 0928 2 Engine 2 Mixture lever, 0 – 16384
  17. Hi, Nonetheless, it is so strange to me to register the software for one computer on another computer that I didn't make the connection that the event took place on the server computer. Not strange really because WideFS6/7 is part of FSUIPC and even in FSUIPC4 integrated (not a separate DLL anymore). The advantage of having it registered on the FS PC in FSUIPC is that there is no need to register any client PC. So if it is once registered you can connect multiple Client PC in your simulator setup just by configure WideClient on the Client PC you want to connect.
  18. Hi, are you sure you ordered the correct version? Above you were talking about P3D! - FSUIPC(3) and WideFS6 is for FS9(2004) only - FSUIPC4 and WideFS7 for FSX/P3D only. You can not mix their registration keys!
  19. Hi, I remember I had the problem years ago and the error was that simple that for the throttle in FSX setup for controller the effectiveness for throttle was set to default like other axes, that means set to half. And so the throttle will also only give you half power. Make sure for throttle the effectiveness is set to max (full right) and its zero zone (null zone) is set to min (full left).
  20. Hi, when you start a program (Process) via WideClient, you need to close it as well via WideClient befor you can start it again via WideClient. The reason is that WideClient doesn't see any reason to start the same Process again when it already running and wasn't closed. WideClient remembers that it didn't closed the process and so it believes it is still running. When you define also a button or key to send the Close function then you will be able to restart the same process again.
  21. Hi, on SimKits page (www.simkits.com) --> Support --> Software Centre (http://www.simkits.com/software.php) you will find their driver software for their devices. If you use those they connect via USB, each instrument, then you need their Simkits USB Aircraft Gauge setup software (http://www.simkits.com/downloads/software/SimkitsUSB127.zip) It contains the software to drive the instruments from Microsoft Flight Simulator 2002, 2004 (FSUIPC needed) or Flight Simulator X Deluxe Version (FSUIPC not needed) and the software to calibrate the gauges. It has been updated from the previous version to support Windows Vista 32-bit and 64-bit and contains the value for a G-Force gauge. This version number is 1.27 and the date of release is September 1, 2011. Some minor bugs have been solved and Rotor RPM Gauge function code has been changed.
  22. Hi Luis, Windows 7 for example, C:\Users\YourUserName\AppData\Roaming\Microsoft\FSX\DLL.XML or for LM v2 C:\Users\YourUserName\AppData\Roaming\Lockheed Martin\Prepar3D v2\DLL.XML
  23. Hi Luis, you can do this. Modules folder inside FS is just the easiest and best way to know where evrything of FSUIPC/WideFS is located. Just edit the DLL.XML file with full path to its location for example: original: <Path>Modules\FSUIPC4.dll</Path> If you for example install the Modules folder (or what ever name to choose) on Z: drive. In this case here I used a LAN Network drive without any trouble. new: <Path>Z:\Modules\FSUIPC4.dll</Path> That works without any problem.
  24. Hi, easiest way is to use a different browser than Internet Explorer (MS). e.g. Mozilla Firfox
  25. Hi, it's just the window that pops up with any knew FSUIPC update when you run it the first time, just click OK because you want to run FSUIPC. It should come up another message to confirm as well. It is not an Error Message because FSUIPC didn't even start to run.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.