Jump to content
The simFlight Network Forums

Thomas Richter

Moderators
 View Profile  See their activity

  • Posts

    1,506

  • Joined

  • Last visited

  • Days Won

    26

 Content Type 

Posts posted by Thomas Richter

  5. Confusing Installation

    in FSUIPC7 MSFS

    Posted

    Hi,

    there is no need to un-install any other FSUIPC installation as FSUIPC7 is only for MSFS 2020 but not for any other FS/ P3D. So you just create a new folder of your choice and place the files from FSUIPC7 into it. If you want to use a already setup of i.e. FSUIPC6 for P3Dv5 you can copy i.e. the FSUIPC6.ini file into that folder and rename it to FSUIPC7.ini, so FSUIPC7 will use this. Other content that will work with MSFS and was placed into your i.e. FSUIPC6 location can be copied into this folder as well. You will have to try if it already works correct.

    Thomas

  6. MSFS 2020 Update is out!

    in FSUIPC7 MSFS

    Posted

    Hi,

    there is no FSUIPC update special for the MSFS 1.7.14.0 update needed as the SDK has no update. The SimConnect interface within MSFS has been updated/ fixed internally. This doesn't mean there is more functionality available via SimConnect but at least the stutter/ FPS drop is fixed.

    It has to be checked now if there has been done more work already to SimConnect or just the FPS drop problem fix.

    Hopefully a new SDK will be available soon as well!

    Thomas

     

    • Like 1

  7. fsuipc 5.103 p3d v4.0 problem

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi,

    you will need to at least give some information, attaching the following files or copy and paste.their content to your message.

    FSUIPC5.log, FSUIPC5.ini, FSUIPC5 Install.log and if you have any controller in use as well the FSUIPC4.JoyScan.csv file.

    You can as well first try to delete WXR files of saved files and add the following line to your FSUIPC5.ini file within the [General] section. 

    [General]
.
.
.
NoWeatherAtAll=Yes

    Thomas

  10. FSUIPC vs SimConnect

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi,

    Quote

    Does SimConnect exists for both FSX, P3D, FS2020, ...? Is this the same API, or are they all have their own version?

    They all have their own version of SimConnect, even updates of the different FS versions deliver always/ most new SimConnect versions. FSUIPC is as well in different independent versions available, FSUIPC3 for FS2004/ FS9 / FSUIPC4 for FSX, FSX-SE, P3Dv2 - v3 / FSUIPC5 for P3Dv4.x / (FSUIPC5 for P3Dv5.x) / FSUIPC6 for P3Dv4.x and P3dv5.x

    FSUIPC7 will be released for MSFS but is already as a free Beta Version available.

    MobiFlight questions should go to their support as they can answer best.

    Thomas

  11. Wideclient occassionally quits

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi,

    Quote

    The main app uses the AI table access to just trigger some sound effects outside of P3D.

    I remember in the B737 SIM here I had the problem on the Systems PC that WideClient crashed always 1 or 2 minutes after starting. This was in relation to DirectX where the System program has axes and sound control. The way that solved that problem was by using a Starter program that starts the System program first and 35 seconds later the WideClient. The WideClient then starts other programs and closes them when receiving the close flag. The Starter program starts automatic when Windows starts.

    This line, I think I sent earlier already, should have solved that problem with the DirectX problem but I 'think' it didn't 100%. And so I kept the start sequence, that works now since ish 10 years with that PC and software.

    ButtonScanInterval=0

    Thomas

  14. PFChid64.dll support for ms2020

    in FSUIPC7 MSFS

    Posted

    Hi,

    that's my file

    Quote

    [Options]
    FlashAPcapts=Yes
    FlashMarkers=Yes
    FlashTransponder=Yes
    FlashADFindicator=Yes
    DMEuseRMIselect=Yes
    UsingProsim=No
    PSUchecklistTimer=0
    [Debug]
    Console=No
    LogComms=No
    LogData=No
    LogDecode=No
    LogDevices=Yes
    LogDeviceChanges=Yes
    LogToDebugger=No
    LogIPCwrites=No
    LogMacroNames=No
    LogTxData=No
    LogReadCounts=No
    LogLoopActions=No
    [Config]
    TrimRange=256
    ApBeepWave=sound\Caapdis
    AlertWave=sound\AltAlert
    MacroFilename=PFC
    Ailerons=FSUIPC
    Elevator=FSUIPC

    Thomas

  15. PFC C2 Pro mostly working, no throttle quadrant

    in FSUIPC7 MSFS

    Posted

    Hi,

    the hardware is recognized in MSFS but to configure there. The configuration you do for the not automatic assigned axes in FSUIPC. Those axes to set up are the Throttle quadrant axes, THR / PRO / MIX. Check the Axis Assignments in FSUIPC manual if you have a problem with that. To set up those axis in FSUIPC7 go to Assignments-->Axes tab and move the relevant axis. If the one you looking for is not shown the press Rescan button and move again. Select its function and do the next.

    If you want to calibrate as well the Yoke axes you will have to follow this instruction by modifying first the PFChid64.ini, located as well in FSUIPC7 installation folder, file as here described.

    Thomas

  17. PFChid64.dll support for ms2020

    in FSUIPC7 MSFS

    Posted

    Hi,

    we have an interim solution for the Yoke axis problem.

    By adding the following lines to the [Config] section it will force PFC to send the Aileron and Elevator axes to its PFC offsets instead and not hard coded to FS direct as raw value. This way FSUIPC will recognize the axes on axis tab and when assigned you can calibrate them on Axis Calibration tab as usual. Nothing to remove or to change, just adding those lines to that section.

    [Config]

    Ailerons=FSUIPC
    Elevator=FSUIPC

    The other both not recognized axis in FSUIPC but still hard coded sent to FS are the both TRIM rotary knobs, AilTrim and RudTrim. If you want them different programmed/ usage you can as well add in addition the following lines to send them to FSUIPC the same way. They are then as well in Axis tab recognized and you can send them i.e. to an Offset bey selecting "Send to FSUIPC Offset"

    [Config]

    RudderTrim=FSUIPC
    AileronTrim=FSUIPC

    You should be now OK with that. Any other axes, Throttle quadrant are anyway correct sent as Axis and in FSUIPC recognized as that.

    Thomas

  18. WideClient terminates

    in FSUIPC Support Pete Dowson Modules

    Posted

    Hi,

    as you know already the Offsets you could even try which one it really is bey using Deny= in WideClient.ini under [User]

    Quote

    Deny=: This parameter can prevent all programs on the current client changing specified areas of the FSUIPC offsets. The format
    is:
    Deny=<offset>,<size>
    where the offset is in hexadecimal and the size is a number of bytes in decimal. If you only want to watch one byte, you can omit
    the ",<size>" part.
    For example
    Deny=2EE0,4
    This makes WideClient prevent and changes to this location from this client. This one is the Flight Director switch.
    You can Deny access to up to 8 different offset areas. Just list more <offset>,<size> parameters on the same line, thus:
    Deny=04E0,88,48F0,10,5400,512,5600,256,5B00,128
    which means 88 bytes at 0x04E0, 10 bytes at 0x48F0, and so on.
    AllowShutdown=No: Set this to Yes only if you want to allow client

    Thomas

  19. PFChid64.dll support for ms2020

    in FSUIPC7 MSFS

    Posted

    Hi,

    I picked up and connected the C2 Pro here now.

    The C2 has for axes they are different, Ail / Elev / Ail-Trim / Rud-Trim.

    The Controller are seen by both MSFS and FSUIPC but neither can see those axes. You will find that you will not see any axes working in Windows Game Controller panel.

    Can you confirm this?

    Quote

     I really just need to verify if the yoke axes show up in FSUIPC7 yet for assignments

    Only the Throttle axes will be recognized in FSUIPC but not in MSFS.

    Thomas

  21. Massive FPS Drop

    in FSUIPC7 MSFS

    Posted

    Quote
      11 hours ago, Pete Dowson said:

    But Expect a release date for the patch in our August 27th update.

    Unfortunately all that means is that we won't know when we get the patch until August 27th, but the patch release date the then announce may well be weeks later. They're not promising fixes on the 27th.

    😞

    Pete

     

    Exactly...

    It's always a problem to deal with german background with certain words of the English language, one of those is "expect" that has a different meaning in the other language.

    Thomas

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