Jump to content
The simFlight Network Forums

UniformAlpha2014

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by UniformAlpha2014

  1. Sorry I forgot the lines. My fault, I wanted to include it in the previous post. 

    Just search for Exception, there you have the deletions. I have some at line 8125. I monitered that live in P3D, and it was a Dash8 from Austrian. On the afcad for LOWW would be enough space to park for it. 

    As you wrote, the AI has to get deleted either from P3D or AIS. Is there any other logging codes to get more/other information? 

  2. 3 hours ago, John Dowson said:

    I am sorry but I cannot support AIS. I do not have or use this add-on.

    You could try with

    Debug=Please
    LogExtras=x10000

    This should log a lot less and may help.

    That offset is really usefull. I keep watching this on my flight to Shanghai now. I call you back with more information later.

     

    11 minutes ago, Pete Dowson said:

    I never found AISeparation worked very well

    yeah it has its ups and downs. But did a great job on my system.

     

    22 minutes ago, Pete Dowson said:

    new programs AIFlow and AIGround

    I have seen these as well, but I'm a little sceptical. Have you tested it yet? What is the difference to AIS?

  3. Hey, 

    I'm starting this topic because I need your help with this. It may be, that AI Separation has a bug or something has changed with the FSUIPC versions lately. 

    The situation basically can be found here: 

    However: STB is not the issue in this case. But I'm testing around where this errors occur. As it is still there.

    Uninstalled EDDF, ORBX sceneries. Reinstalled the full P3D Scenery, and Client. Deleted the P3D.cfg. Tested FSUIPC version 5.155 and FSUIPC6

    Still AIS deletes AI on separation action. Then I noticed that AIS invokes commands to FSUIPC to force a separation. Maybe there is some error in float numbers, because it mostly deletes AI, when approaching from the west. I don't know seriously, what is the case of this. 

    Question now is: Did you change some commands or anything, that stop AIS doing its job? And what commands is AIS invoking during separation?

     

    Thanks for you help

  4. So I checked the new 5.151a version. The distributed COM Error is done. But fsuipc still crashes:

     

    - System
       
    - Provider
          [ Name] Application Error
       
    - EventID 1000
          [ Qualifiers] 0
       
      Level 2
       
      Task 100
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2019-05-02T13:10:14.662405900Z
       
      EventRecordID 4559
       
      Channel Application
       
      Computer xPredator
       
      Security
    - EventData
          Prepar3D.exe
          4.4.16.27077
          5bfdbb35
          FSUIPC5.dll
          5.1.5.1
          5cc9b3ed
          c0000005
          00000000000e1088
          23b0
          01d500e56184c209
          D:\P3Dv4\Prepar3D.exe
          D:\P3Dv4\Modules\FSUIPC5.dll
          681a8ce7-d9f1-4119-a5ae-bdcc7f2ad735
           
         

    Errorcode: 1000

     

  5. 14 minutes ago, John Dowson said:

    Thats very strange. Did you try a different aircraft? Are you sure FSUIPC is running (can you see it in the 'Add-ons' menu?)

    Yes I tried with the default F-22 and PMDGs 777. I noticed that the commands with key memos are working fine. See in the picture below. The left side is working, but the right side not. 

    14 minutes ago, John Dowson said:

    If you already have FSUIPC installed, you can just replaced the FSUIPC5.dll file. The files attached in the posts above are dll files, just download them, rename to 'FSUIPC5.dll' and copy (replace) to your sims 'Module' folder (which is'D:\P3Dv4\Modules\'). If you've re-installed the sim, you may first need to re-install by running the (latest) installer first.

    I just reinstalled the academic client for v4.4. No complete reinstallation. 

     

  6. Hey John,

    I was testing the fsuipc v5.15 for a few days now. I was wondering why all my switches on my x55 hotas aren't working. I checked the log files but there was nothing strange. fsuipc send the command to the sim. But nothing happend on the aircraft (FsLabs A320). 

    I was wondering how. I downgraded my sim to P3Dv4.4 again a few days ago (because of performance), but the switches still don't work properly. 

    Now my addition question is: When I upgrade fsuipc to another version, what do I have to reinstall?

     

    Edit: Yes I take a look on that 5.151a

  7. 8 hours ago, John Dowson said:

    Did you try disabling Active Sky (as_connect) by editing the dll.xml, as explained in Pete's last post above?

    Yeah I just tried it one more time. But I noticed something.

    Before every crash there is a "DistributedCOM" Error. It says it cannot start a file called "coredpussvr.exe" somewhere in the Windows/System32 folder. Right afterwards P3D crashes.

    Eventlog:

    - System
       
    - Provider
          [ Name] Microsoft-Windows-DistributedCOM
          [ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
          [ EventSourceName] DCOM
       
    - EventID 10000
          [ Qualifiers] 0
       
      Version 0
       
      Level 2
       
      Task 0
       
      Opcode 0
       
      Keywords 0x8080000000000000
       
    - TimeCreated
          [ SystemTime] 2019-04-26T14:54:34.143684500Z
       
      EventRecordID 3021
       
      Correlation
       
    - Execution
          [ ProcessID] 964
          [ ThreadID] 14448
       
      Channel System
       
      Computer xPredator
       
    - Security
          [ UserID] S-1-5-21-1236235040-2779368353-1591499981-1001
    - EventData
        param1 C:\Windows\System32\coredpussvr.exe -Embedding
        param2 0
        param3 {417976B7-917D-4F1E-8F14-C18FCCB0B3A8}

     

    Edit: Maybe you can provide me the previous 5.1.5.0 version of FSUIPC. That should be more stable than the new one. 

     

    Patrick

  8. 21 minutes ago, John Dowson said:

    Hi Colin,

    your log file after the crash, together with the ini.  would have been useful!

    Have you tried the other solutions in this post before posting? i.e. removing wx files, and also disabling weather? If not, please do so.

    Was the change only from FSUIPC 5.150 to 5.151, or is this also with P3D updated from 4.4 to 4.5? What add-ons are you using? Were any of these updated?

    So, please try solutions mentioned and report results, and if you are still having problems, post your ini and log files together. Also, if its a CTD, then the windows event log information would also be useful.

    Thanks,

    John

    P.S. what do you mean by 'lags very hard'?

    Hey,

    so I was updating from FSUIPC version 5.11 to 5.151. The upgrade from P3dv4.4 to 4.5 haven't caused any problems.

    I was trying to delete the previous wx file and edited the FSUIPC.ini file as mentioned above with no different result. 

    Addons are quite a lot: ActiveSky, ASCA, ENVTEX, ENVSHADE, ORBX (base,vector,openlc,germany north + south,netherlands), PMDG737, 747, 777, FsLabs A3xx, and lots of payware airports.

    On my last crash, windows 10 says: 

    Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.5.11.29713, Zeitstempel: 0x5ca56c53
    Name des fehlerhaften Moduls: FSUIPC5.dll, Version: 5.1.5.1, Zeitstempel: 0x5c920d17
    Ausnahmecode: 0xc000041d
    Fehleroffset: 0x00000000000df637
    ID des fehlerhaften Prozesses: 0x34a8
    Startzeit der fehlerhaften Anwendung: 0x01d4fb9c5d29e473
    Pfad der fehlerhaften Anwendung: D:\P3Dv4\Prepar3D.exe
    Pfad des fehlerhaften Moduls: D:\P3Dv4\Modules\FSUIPC5.dll
    Berichtskennung: 73fd8d21-5662-4482-98a8-af31b951a807
    Vollständiger Name des fehlerhaften Pakets: 
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

    xml:

    - <System>
      <Provider Name="Application Error" />
      <EventID Qualifiers="0">1000</EventID>
      <Level>2</Level>
      <Task>100</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2019-04-25T20:25:36.289729100Z" />
      <EventRecordID>3421</EventRecordID>
      <Channel>Application</Channel>
      <Computer>xPredator</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>Prepar3D.exe</Data>
      <Data>4.5.11.29713</Data>
      <Data>5ca56c53</Data>
      <Data>FSUIPC5.dll</Data>
      <Data>5.1.5.1</Data>
      <Data>5c920d17</Data>
      <Data>c000041d</Data>
      <Data>00000000000df637</Data>
      <Data>34a8</Data>
      <Data>01d4fb9c5d29e473</Data>
      <Data>D:\P3Dv4\Prepar3D.exe</Data>
      <Data>D:\P3Dv4\Modules\FSUIPC5.dll</Data>
      <Data>73fd8d21-5662-4482-98a8-af31b951a807</Data>
      <Data />
      <Data />
      </EventData>
      </Event>
     
    And btw the sim crashed without a "Prepar3D has stopped working" message, but rather crashed without any message. 
    "huge lags" are milliseconds, maybe seconds with 0-1 fps 
    (the .ini file is the same as above)
     
    Patrick
     

    FSUIPC5.log

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