Mavericko Posted April 23, 2017 Report Share Posted April 23, 2017 So I switched to P3D in mabye september and I can't get FSUIPC to work in a bit larger airports. If I just launch the default P3D Scenario it loads fine. I can then switch to the Aerosoft Airbus fine. And I can switch to any smaller airports. But when I try to change to Kastrup EKCH it freezes after 5-10 seconds and crashes. The log claims that it shuts down the sim because of low FPS but the FPS is fine. Haven't found any fix other then removing FSUIPC. P3D runs fine on any airport as long as I don't have FSUIPC installed. In the log below I loaded the default scenario, and after letting it sit for a minute or so I switched to EKCH and it freezes as soon as it has finished loading. Quote ********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson ********* Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0) Prepar3D.exe version = 3.4.22.19868 Reading options from "C:\Spel\Prepar3D v3\Modules\FSUIPC4.ini" Running inside Prepar3D v3 on Windows 10 Module base=23790000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 15 System time = 23/04/2017 11:47:42 15 FLT path = "C:\Users\sonny\Documents\Prepar3D v3 Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 3.4.22.19868 15 api.dll: 3.4.22.19868 15 controls.dll: 3.4.22.19868 15 fs-traffic.dll: 3.4.22.19868 15 G3D.dll: 3.4.22.19868 15 language.dll: 3.4.22.19868 15 sim1.dll: 3.4.22.19868 15 visualfx.dll: 3.4.22.19868 15 weather.dll: 3.4.22.19868 15 window.dll: 3.4.22.19868 15 ---------------------------------- 15 Trying C:\Spel\Prepar3D v3\Modules\SimConnectP3D3.dll 15 Found it: trying to connect 47 FS path = "C:\Spel\Prepar3D v3\" 140 LogOptions=00000000 00000001 140 ------------------------------------------------------------------- 140 ------ Setting the hooks and direct calls into the simulator ------ 140 --- CONTROLS timer memory location obtained ok 140 --- SIM1 Frictions access gained 140 --- FS Controls Table located ok 140 --- Installed Mouse Macro hooks ok. 140 --- Wind smoothing fix is installed 140 --- SimConnect intercept for texts and menus option is off 140 --- All links okay (except older global weather setting method) 140 ------------------------------------------------------------------- 140 SimConnect_Open succeeded: waiting to check version okay 140 Trying to use SimConnect Prepar3D 140 Opened separate AI Traffic client okay 5500 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.22.19868 (SimConnect: 3.4.0.0) 5500 Initialising SimConnect data requests now 5500 FSUIPC Menu entry added 5500 ... Using Prepar3D with Professional License 5515 C:\Users\sonny\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml 5515 C:\Spel\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 74109 Aircraft loaded: running normally now ... 74109 User Aircraft ID 2 supplied, now being used 74812 System time = 23/04/2017 11:48:57, Simulator time = 11:47:48 (16:47Z) 87859 Starting everything now ... 87922 ASN active function link set 87922 Ready for ASN WX radar 89156 Advanced Weather Interface Enabled 106844 Sim stopped: average frame rate for last 33 secs = 33.4 fps 106844 Max AI traffic was 78 aircraft (Deleted 0) 123469 ---------- Making INI JoyNames Section ---------- 123484 ------------------------------------------------- Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 23, 2017 Report Share Posted April 23, 2017 10 minutes ago, Mavericko said: So I switched to P3D in mabye september and I can't get FSUIPC to work in a bit larger airports. If I just launch the default P3D Scenario it loads fine. I can then switch to the Aerosoft Airbus fine. And I can switch to any smaller airports. But when I try to change to Kastrup EKCH it freezes after 5-10 seconds and crashes. The log claims that it shuts down the sim because of low FPS but the FPS is fine. What LOG claims that? Nothing I know will shut the sim down just because frame rates are low. That's ridiculous! Perhaps you mean VAS is low (memory). That's the most likely thing if it is only happening at large airports. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 23, 2017 Author Report Share Posted April 23, 2017 I meant this line at the bottom of the fsuipc4.log "106844 Sim stopped: average frame rate for last 33 secs = 33.4 fps" Shouldn't be a memory issue. I can fly fine around big airports and long flights - as long as I don't have FSUIPC installed :/ Been looking a lot but haven't found anyone with the same problem Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 23, 2017 Report Share Posted April 23, 2017 28 minutes ago, Mavericko said: I meant this line at the bottom of the fsuipc4.log "106844 Sim stopped: average frame rate for last 33 secs = 33.4 fps" That just means SimConnect signalled a pause in simulation like when you go into a menu or load a flight. You went to a different location. It's only FSUIPC's way of giving you average performace for the last running period. 29 minutes ago, Mavericko said: Shouldn't be a memory issue. I can fly fine around big airports and long flights - as long as I don't have FSUIPC installed Possibly it's a corrupted weather entry in either wxstationlist.bin or in the currently loaded wx file. Those are binary files which are read without any checking (by the sim itself, not by FSUIPC) so when corrupted can cause such problems. It only happens with FSUIPC because FSUIPC regularly gets weather data from SimConnect. You provided no crash data. Don't you think that might give a clue? Use the Windows Event viewer to find the crash data. It will show which module crashed and what sort of error it was. In order to prove it is this problem you can stop FSUIPC asking for the weather by having "NoWeatherAtAll=Yes" in the [general] section of the FSUIPC4.INI file. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 23, 2017 Author Report Share Posted April 23, 2017 Yeah I read about the issue someone else had with the weater file last year when I first came upon this problem. I believe in his case deleting the file and letting it create a new one fixed it. I did not fix it for me. I tried changing in FSUIPC to remove all weather or whatever it says, no change. Yeah sorry, forgot. The following three logs are from my attempts these past 2 hours. Had trouble getting a log because most of the time it doesn't give me "P3D.exe has stopped working", it just froze then closed and then I didn't get a log file. Quote Prepar3D.exe 3.4.22.19868 588f7cbf menus.dll 3.4.22.19868 588f7c3f c000041d 00004c70 31e8 01d2bc2c752b0ff7 C:\Spel\Prepar3D v3\Prepar3D.exe C:\Spel\Prepar3D v3\menus.dll 2dfed022-f6db-4c53-933e-183f96d9432f - <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="2017-04-23T12:26:32.292932400Z" /> <EventRecordID>17247</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-QETN7K1</Computer> <Security /> </System> - <EventData> <Data>Prepar3D.exe</Data> <Data>3.4.22.19868</Data> <Data>588f7cbf</Data> <Data>menus.dll</Data> <Data>3.4.22.19868</Data> <Data>588f7c3f</Data> <Data>c000041d</Data> <Data>00004c70</Data> <Data>31e8</Data> <Data>01d2bc2c752b0ff7</Data> <Data>C:\Spel\Prepar3D v3\Prepar3D.exe</Data> <Data>C:\Spel\Prepar3D v3\menus.dll</Data> <Data>2dfed022-f6db-4c53-933e-183f96d9432f</Data> <Data /> <Data /> </EventData> </Event> Quote Prepar3D.exe 3.4.22.19868 588f7cbf menus.dll 3.4.22.19868 588f7c3f c0000005 00004c70 31e8 01d2bc2c752b0ff7 C:\Spel\Prepar3D v3\Prepar3D.exe C:\Spel\Prepar3D v3\menus.dll 8b2f6070-ad1a-4e81-96b4-5f28539b25aa - <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="2017-04-23T12:26:22.902626100Z" /> <EventRecordID>17245</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-QETN7K1</Computer> <Security /> </System> - <EventData> <Data>Prepar3D.exe</Data> <Data>3.4.22.19868</Data> <Data>588f7cbf</Data> <Data>menus.dll</Data> <Data>3.4.22.19868</Data> <Data>588f7c3f</Data> <Data>c0000005</Data> <Data>00004c70</Data> <Data>31e8</Data> <Data>01d2bc2c752b0ff7</Data> <Data>C:\Spel\Prepar3D v3\Prepar3D.exe</Data> <Data>C:\Spel\Prepar3D v3\menus.dll</Data> <Data>8b2f6070-ad1a-4e81-96b4-5f28539b25aa</Data> <Data /> <Data /> </EventData> </Event> Quote Prepar3D.exe 3.4.22.19868 588f7cbf KERNELBASE.dll 10.0.14393.1066 58d9f07f c0020001 000da932 38dc 01d2bc26657cf1ae C:\Spel\Prepar3D v3\Prepar3D.exe C:\windows\System32\KERNELBASE.dll 7839e870-ba09-48ac-adab-ebd9ffa0d870 - <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="2017-04-23T11:44:54.150939900Z" /> <EventRecordID>17222</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-QETN7K1</Computer> <Security /> </System> - <EventData> <Data>Prepar3D.exe</Data> <Data>3.4.22.19868</Data> <Data>588f7cbf</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.14393.1066</Data> <Data>58d9f07f</Data> <Data>c0020001</Data> <Data>000da932</Data> <Data>38dc</Data> <Data>01d2bc26657cf1ae</Data> <Data>C:\Spel\Prepar3D v3\Prepar3D.exe</Data> <Data>C:\windows\System32\KERNELBASE.dll</Data> <Data>7839e870-ba09-48ac-adab-ebd9ffa0d870</Data> <Data /> <Data /> </EventData> </Event> Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 23, 2017 Report Share Posted April 23, 2017 I've never seen an error reported in P3D's "Menus.DLL". FSUIPC really has nothing whatoever to do with menus. I think you must have some sort of corruption in P3D which involves addressing memory which may just be in a different place, and not crash, when FSUIPC is not loaded. The error is "String binding invalid" which is associated with Managed code. Are you running any add-ins which use manage code as far as you know? what other add-ins apart from FSUIPC (which uses no high-level or managed stuff itself) are you running. With a crash in Menus is seems possible that it is one which adds or changes menus, almost certainly the Add-Ons one. As well as corrupted modules or an error in one of the add-ins, actual memory hardware could be responsible, so if stopping the other add-ins and, if there's still a problem, uninstalling and re-installing P3D (just the Client should do, so not destroying anything else you installed) doesn't solve it, get some memory test on your RAM. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 23, 2017 Author Report Share Posted April 23, 2017 Yeah indeed the Menu was new for me too, had never showed up earlier, I think that one was just a coincidence. I'm not sure but I think when this problem showed up when I got P3D I did a few reinstalls without any success. I'm not sure what 'managed code' means. Well I've gotten the crashes with default aircraft with really only some ORBX Scenary active. 2 More tries with crashes but without getting the "P3D.exe has stopped working" only produced the following. Everything I use is up-to-date btw. Quote - System - Provider [ Name] .NET Runtime - EventID 1026 [ Qualifiers] 0 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2017-04-23T13:42:23.022796500Z EventRecordID 17261 Channel Application Computer DESKTOP-QETN7K1 Security - EventData Tillämpningsprogram: Prepar3D.exe Framework-version: v4.0.30319 Beskrivning: Processen avslutades på grund av ett ohanterat undantag. Undantagsinformation: undantagskod c0020001, undantagsadress 74D4A932 Stack: vid <Module>.ShowMessage(SByte*, Int32) Quote - System - Provider [ Name] .NET Runtime - EventID 1026 [ Qualifiers] 0 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2017-04-23T13:49:16.070765600Z EventRecordID 17262 Channel Application Computer DESKTOP-QETN7K1 Security - EventData Tillämpningsprogram: Prepar3D.exe Framework-version: v4.0.30319 Beskrivning: Processen avslutades på grund av ett ohanterat undantag. Undantagsinformation: undantagskod c0000005, undantagsadress 69994C70 Stack: Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 23, 2017 Report Share Posted April 23, 2017 .NET is absolutely not related to FSUIPC in any way. Sorry. You do need to look elsewhere. I think you have something seriously corrupted. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 23, 2017 Author Report Share Posted April 23, 2017 Okey I give up then, I have absolutely no idea what it could be since everything has been reinstalled except windows. I appreciate your support though, thanks. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 23, 2017 Report Share Posted April 23, 2017 23 minutes ago, Mavericko said: I have absolutely no idea what it could be since everything has been reinstalled except windows. Might have been better to reinstall Windows first. could be a registry problem. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 23, 2017 Author Report Share Posted April 23, 2017 Yeah well can't be bothered, it is (or rather was at the time) a brand new computer I bought shortly before I got P3D Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 23, 2017 Report Share Posted April 23, 2017 Hi, just as a side note, since P3Dv3 Hotfix 2 you need .Net Framework 4.6.2 installed, where your error shows an error in .Net Framework 4.0... and your installed P3D version is the latest v3.4 with Hotfix 3. Do you have the from LM minimum requested .Net Framework installed? PLEASE NOTE THAT YOU MUST HAVE MICROSOFT .NET FRAMEWORK 4.6.2 INSTALLED TO UPDATE TO HOTFIX 2 PLEASE NOTE THAT YOU MUST HAVE MICROSOFT .NET FRAMEWORK 4.6.2 INSTALLED TO UPDATE TO HOTFIX 3 Thomas Link to comment Share on other sites More sharing options...
Mavericko Posted April 24, 2017 Author Report Share Posted April 24, 2017 I did download the latest framework yesterday when I found that error, but I already had 4.6.2 installed - even though the error is complaining about 4.0 Edit. Did another complete reinstall for other reasons, and seems to be working now - though I have not installed all add-ons yet. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 24, 2017 Report Share Posted April 24, 2017 3 hours ago, Mavericko said: Did another complete reinstall for other reasons, and seems to be working now - though I have not installed all add-ons yet. Add add-ons one by one and always test between. Best to start with FSUIPC anyway, as it might be interaction with that. It takes longer to find the culprit if you add them all in one go, then have to take them out one by one. Pete Link to comment Share on other sites More sharing options...
Mavericko Posted April 24, 2017 Author Report Share Posted April 24, 2017 Yeah that's the plan, though only one or two things I haven't added yet so, hopefully it will work. Thanks again for your time and effort. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now