Jump to content
The simFlight Network Forums

Thomas Richter

Moderators
  • Posts

    1,506
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by Thomas Richter

  1. 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?

  2. 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.

  3. 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.
    ...
    
  4. 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.

  5. 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.

  6. 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).

  7. 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 

  8. 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.

  9. 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).

  10. 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.

  11. 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.

  12. 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.

  13. 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>
    
  14. 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.

×
×
  • 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.