Jump to content
The simFlight Network Forums

UniformAlpha2014

Members
  • Content Count

    20
  • Joined

  • Last visited

Everything 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. Does the traffic limiter delete aircraft, even if there aren't too many aircraft around? I did not touch anything there. Should be the default settings. I included the complete log of 10 min LOWW. There were some deletions as well. Runways active: 29/34 FSUIPC6.log
  3. That offset is really usefull. I keep watching this on my flight to Shanghai now. I call you back with more information later. yeah it has its ups and downs. But did a great job on my system. I have seen these as well, but I'm a little sceptical. Have you tested it yet? What is the difference to AIS?
  4. Thanks for your reply John. You are right, these log files can get huge. There are a few examples in the log below. When you search for GS=2968 you get the AI, that gets separated by AIS. But I can't figure it out why. Maybe you see more in this log. That could be hard, because there is no support left. FSUIPC6.2.log
  5. 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
  6. A shame I can't access to code of AIS. As the program is quite old. Maybe this is a good feature for STB some day? I mean a reliable one 😄
  7. Thanks for your answer. I was testing around the last few days and I found out that neither STB nor AIS is the origin of the deletions. There is a new (at least new to me) function called Traffic Zapper by the latest version of FSUIPC5. The manual of FSUIPC says, that it deletes AI in some cases in a certain range. I think that should be the case at EDDF. Fun fact #1: If runway direction 25 is active, there are less deletions than on direction 07. Anyway thanks for your help! edit: Previous versions were: 2017.21200 -> 2019.12100 -> latest
  8. Hello, after the latest update 4.2.2020.4000, STB is causing some strange things in my sim. The following situation: P3Dv4, Aerosoft EDDF with edited AFCAD, AIGAIM traffic, STB and AI Separation. Weather and Shaders shouldn't have an affect on this. STB and AI Separation have worked well together in the past. When AI arriving, they are sometimes too close together, without going around. Instead of moving them to the gate (as STB would do this), I use AI Separation to pull them few miles away, so that they all land safely. Now the strange part: In EDDF the plane, that gets separated, despawns immediately (STB says: diverted, FS State: terminated). I checked several things in my AFCAD, but they have enough space to park. Rwy is long enough and ILS and Approaches I didn't touch at all. I don't know why it does that, but it happens with the new update of STB. Is there anything incomp with AIS?
  9. I have tested the version in my simmarket account and the one's you posted on this other post some time ago. They aren't working for me 😕
  10. Hi Guys I had that same crash with AIM OCI and FSUIPC the last days as well. So I tested around a little bit. For me, I found out, when going back to FSUIPC version 5.11, it works fine with the AIM OCI. The only downside is, I can't see the complete runway assignment of approaching AI aircraft in AISeparation. It is only somthing like: "EHAM 18", when it should be "EHAM 18R".
  11. Hello here is a quick update on this: I found out that the AIM OCI traffic program makes FSUIPC crash. When I deactivate it in the Addon.cfg there is no crash at all. So, do you know about a instability between AIM and FSUIPC, and maybe how to fix it?
  12. That should be the one. which logging should I turn on in fsuipc? FSUIPC5_prev.log
  13. 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
  14. 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. I just reinstalled the academic client for v4.4. No complete reinstallation.
  15. 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
  16. 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
  17. 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: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <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
  18. Hi Pete, I was also updating to version 5.151 and get that crash. I noticed that the sim (P3Dv4.5) lags very hard. I tested that on several scenarios all around the world with different aircrafts. Always the same result. Here is my FSUIPC.ini file: FSUIPC5.ini
×
×
  • 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.