Jump to content
The simFlight Network Forums

WebMaximus

Members
  • Content Count

    70
  • Joined

  • Last visited

Everything posted by WebMaximus

  1. OK, thanks for the quick reply. Haven't had the chance to install the NGX in P3Dv4 yet but hope I will the next coming days being able to do some testing. I read someone said it was a bit better in P3Dv4 vs in P3Dv3 so no reason to start messing around with hex editors unless absolutely necessary. About LM and posting in their support forum I'm not really sure what to say in such a post to make them understand what I'm talking about since I barely understand this myself :D
  2. Being late to this party I just wanted to ask what the current status is? I just got P3Dv4 and realized I'll need to buy FSUIPC5 but will I then be able to use the DynamicFriction.lua I've been using in P3Dv3 for the PMDG NGX? I also found this thread where people seem to fix this themselves by editing a dll file. It's starting with this post.
  3. Hi Thomas, Since writing my last post I already restarted P3D meaning the FSUIPC4.log file has been overwritten. I've now done some cleaning of my P3D installation and will do some more testing and if the problem persists I'll post the log here.
  4. My last two flights ended in CTDs which I haven't had in quite a while. They both happened at the new Aerosoft version of EDDF (v211) so maybe the problem is with the scenery. The first one happened after I landed and was taxing into the gate. Looking in the Windows Event Viewer Application log this first crash resulted in two error messages as seen below with only a 1 second delay and in both the faulting module reported is KERNELBASE.dll Log Name: Application Source: Application Error Date: 2017-04-10 15:27:28 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: TheNest Description: Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d Exception code: 0xe0434352 Fault offset: 0x000da882 Faulting process id: 0x2ad8 Faulting application start time: 0x01d2b1fde0f751df Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 41694ab5-252b-4816-9092-a8227a990f00 Faulting package full name: Faulting package-relative application ID: Event 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="2017-04-10T13:27:28.385894500Z" /> <EventRecordID>33402</EventRecordID> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data>prepar3d.exe</Data> <Data>3.2.3.16769</Data> <Data>56df48ce</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.14393.953</Data> <Data>58ba586d</Data> <Data>e0434352</Data> <Data>000da882</Data> <Data>2ad8</Data> <Data>01d2b1fde0f751df</Data> <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data> <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data>41694ab5-252b-4816-9092-a8227a990f00</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 2017-04-10 15:27:29 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: TheNest Description: Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d Exception code: 0xc000041d Fault offset: 0x000da882 Faulting process id: 0x2ad8 Faulting application start time: 0x01d2b1fde0f751df Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: f4901ae3-7dd7-44b3-bd07-c6b2bae9e1ef Faulting package full name: Faulting package-relative application ID: Event 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="2017-04-10T13:27:29.312859400Z" /> <EventRecordID>33404</EventRecordID> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data>prepar3d.exe</Data> <Data>3.2.3.16769</Data> <Data>56df48ce</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.14393.953</Data> <Data>58ba586d</Data> <Data>c000041d</Data> <Data>000da882</Data> <Data>2ad8</Data> <Data>01d2b1fde0f751df</Data> <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data> <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data>f4901ae3-7dd7-44b3-bd07-c6b2bae9e1ef</Data> <Data> </Data> <Data> </Data> </EventData> </Event> The second crash happened shortly after I took off from the same airport during initial climb. This second crash resulted in the below error message checking the Windows Event Viewer Application log and as you can see this time the faulting module is reported being MSVCR80.dll Log Name: Application Source: Application Error Date: 2017-04-10 22:46:43 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: TheNest Description: Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce Faulting module name: MSVCR80.dll, version: 8.0.50727.9268, time stamp: 0x573d297f Exception code: 0xc000000d Fault offset: 0x00008aa0 Faulting process id: 0x9ec Faulting application start time: 0x01d2b232e12dedfa Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll Report Id: cd66835f-a209-42f5-80be-fb2b40aaea18 Faulting package full name: Faulting package-relative application ID: Event 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="2017-04-10T20:46:43.025698200Z" /> <EventRecordID>33492</EventRecordID> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data>prepar3d.exe</Data> <Data>3.2.3.16769</Data> <Data>56df48ce</Data> <Data>MSVCR80.dll</Data> <Data>8.0.50727.9268</Data> <Data>573d297f</Data> <Data>c000000d</Data> <Data>00008aa0</Data> <Data>9ec</Data> <Data>01d2b232e12dedfa</Data> <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data> <Data>C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll</Data> <Data>cd66835f-a209-42f5-80be-fb2b40aaea18</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Today I quickly launched P3D for the first time after the last crash above and first everything seemed to be fine. However after a while I noticed how the sound stopped for about a second and then came back. Almost like when the simulator window looses focus. This happened a couple of times. I then decided to check the FSUIPC4.log looking for any hints and found one thing I thought looked a bit odd. At the end of the log I had multiple Sim stopped statements and I thought normally you would only have one of those indicating your exit out of the simulator. I need to do more testing and the first thing will be to perform a flight where the new version of Aerosoft EDDF is not involved but if you have any other tips or input and could explain the multiple Sim stopped statements in FSUIPC4.log that would be most appreciated.
  5. Ah, that explains I had trouble finding it. Thanks for opening my eyes, should of course have found it in the doc myself.
  6. Thanks, and what about the update routine - how are the updates applied?
  7. Sounds good and may I ask how often is the aircraft fleet in MT updated and how does the update procedure work, is it automated within some kind of GUI or are updates distributed separately outside the application?
  8. Would be very interesting! Maybe you could just put it in a zipped text file and attach the zip file here for anyone interested to download?
  9. I'm thinking of buying MT6 so great guide how to install it correctly into P3Dv2.5, thanks! One question, when it comes to adding MT to the scenery library what's the reason behind this step? I guess that's for the included airports to show up and nothing to do with the AI aircraft models? Since I'm doing all my flying online on VATSIM I will only get this package for the AI models and nothing else I guess that step won't be required in my case?
  10. Thanks for confirming NAX B788 is included. As for the house liveries maybe those won't be needed with all MT models installed. I've used them as default liveries with the IVAO MTL models whenever I encounter an aircraft online where the correct livery is missing.
  11. Is there a complete list somewhere what aircraft models and airline liveries are included in MT6? For instance I would like to know if Norwegian B788 is included? I also wonder if Boeing and Airbus house liveries are included?
  12. I'm thinking of buying MT6 and I'm only interested in the aircraft models since I do all my flying online on VATSIM. What's the recommended way accomplishing this with MT6 without having MT6 change lots of other stuff in my P3DV2. 5 installation? Read somewhere else that one way is to install MT, copy the aircraft folder and then uninstall MT. However using that approach I guess you'll be in trouble when it comes to updating aircraft models and liveries? Or are such updates released as stand alone archives not requiring you have the full product installed?
  13. Ah, just checked the FAQ...thought the File= should be in the FSUIPC4.ini file hence the question under what section. I know...RTFM... :wink:
  14. No, there are several sections in the file! I'll check the FAQ.
  15. Sorry for waking up an old thread here but just wanted to ask will this work also for P3Dv2.5 by placing the file in the ...\Documents\Prepar3D v2 Files folder? I'm trying to figure out a problem I have with TrackIR crashing as well as a stuttering issue. And where should that File= line go, into FSUIPC.ini? And if so, under what section of the file?
  16. Unfortunately the luck didn't last...just experienced really bad stuttering on my return leg to Stockholm from Copenhagen. Checking the FSUIPC log file there's still no error messages so I guess that means whatever was causing them that was not the cause of my stuttering issue. Right now I'm thinking maybe the stuttering issue is related to another issue I have with TrackIR that for some reason stop working mid-flight and has done so a couple of times now. Reason I'm suspecting there's a relation between these two issues is on today's flight everthing started when I noticed how the stuttering got worse and worse during the approach and then on final when the stuttering was really bad all of a sudden TrackIR stopped working. Not sure how TrackIR is communicating with P3Dv2, if it's via SimConnect or FSUIPC. Was thinking if it might be a SimConnect flooding issue causing both the stuttering and then eventually the TrackIR software crash where the head movement stops working totally instead of just being jerky. Don't you just love these kind of problems spoiling the fun in flying...
  17. I'm very happy to tell you I just completed a flight and this time without any stuttering and no error entries in the FSUIPC log file. Since I changed several things I can't know for sure what was actually the culprit but at this point I don't really care to be honest, I'm just happy my performance is back to normal. I've come to the conclusion that I often spend far more time tweaking and troubleshooting vs flying and I intend to change that...at least that's my plan :wink: What I changed before this flight include: - disabled the extended battery option in FSUIPC - did a clean install of the Nvidia drivers (347.88) - upgraded ASN to the latest private beta version - flew to FlyTampa Copenhagen rather than Aerosoft Oslo Now I'll make sure to perform a complete backup of my PC to make sure I'll be able to revert to this point should I face any additional issues... Thanks again Pete for your interest in my issue!
  18. 32.000 lines in a minute...now that's what I call some serious logging :LOL: Right now I think my main problem is trying to track down what could actually be causing this stuttering I've seen. As for the FSUIPC logging maybe I was unclear but I don't think the logging in itself is to blame but more just like you mention what is actually causing all these errors to end up in the log. Clearly something is not right, I just need to figure out the culprit. First I thought it might have been related to the latest beta build of Active Sky Next because I'm part of that team and these stuttering happened shortly after I upgraded ASN to the latest build. For that reason that was my first stop asking about this but no one else seem to have seen the same problem so doens't appear to be ASN causing my problem. In situations like this one where you all of a sudden get a problem 'out of the blue' and you can't really figure out why I wish there was some kind of "superlogging" feature in FSX/P3D you could enable that would help you troubleshoot exactly what is causing your issue in my case stuttering. Imagine how nice it would have been in a situation like this one to have a log where you clearly could see the stutters listed somehow marked as 'Poor performance' entries or something like that and then an explanation what is the reason/bottleneck...that would really be awsome! Oh well...will not bore you to death with my issue but instead I'll keep trying to exclude one thing at a time doing more testing and hopefully I'll find the culprit eventually. Problem is the testing is rather time consuming since I don't see this until I'm up in the air and have been flying for some time and time currently isn't one of my biggest resources. Many thanks Pete for trying to help me out, much appreciated!! Here's what my simulator looks like and this is my hardware config.
  19. Well...1 hour and 40 minutes isn't much in my case doing online flight in Europe. As for the stops I'm not 100% sure but might have been when I've been accessing the P3D menus trying out various settings in an attempt to get rid of some stuttering I've seen on my last couple of flights and so far I haven't been able to track down the cause of them. Most annoying and was thinking maybe what I've seen in the fsuipc log could explain the stuttering considering the number of entries found in the log. Took all of the lines containing this error message and pasted them into an online web service that will let you count the lines and almost fell out of my chair when I realized there were almost 32.000 of them... Very strange all this because I've been using FSUIPC for years and same thing goes for the NGX and never seen anything like this before and have always had the extended battery option set to '0' for infinite but I've now disabled that option for testing purposes so will be interesting to see if I get the same thing on next flight. Did a quick test earlier today and just fired up P3D with the NGX and switched on the battery to see if that would log any errors but nothing.
  20. Either the other thread somehow disappeared or I'm going crazy because I did create a new thread asking about this yesterday but now I can't find it. Anyway the first occurrence of the error message in the log file is the one seen in my posted log file above. Have only checked with PMDG's NGX since that is the only addon a/c I've installed, haven't tried with any of the default P3D a/c. Haven't tried disabling the extended battery life option but will do and report back.
×
×
  • 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.