pytteros

I would really like to hear if other fellow simmers here on AVSIM experience the same, what I described in the post #7 above. I have now flown multiple NGX legs without any problems. 2 months of investigating and head scratching has ended! I also checked my event logs, and appcrash logs and found out that almost all CTD's with this case were kernelbase, .net framework or virtual memory related. Now without using 2D viewpoint at all, zero crashes.

I have found the problem! I was inspecting VAS consumption with Process Explorer as I was flying from ESSA to LDSP. Blackout happened over Poland. I noticed in the Process Explorer that "commit charge" was at 99,97%. I closed all other programs quickly and blackout went away as Commit Charge dropped to 96.something %. I flew for a minute, black out came back and CTD happened. Free VAS vas >1,5 Gb. https://en.wikipedia.org/wiki/Commit_charge I started to wonder what caused the increase in Commit Charge. I flew same time with my friend, who uses FSX, and he reported that his Commit Charge rarely exceeded 40% on his machine. I started a new flight, same fligthplan and everything. I kept my eye on Commit Charge all the time, and I found out that when I cycled view "S" through 2D cockpit, Commit Charge jumpted up a little. I continued to press "S": 2D -> Wingview -> Spot -> 2D -> Wingview -> Spot -> 2D.... and so on. After doing this for a minute, Commit Charge went to 100% and everything went black. I tested this with Majestic Dash Q400 and default F22 Raptor. Majestic has a 2D panel and I was able to recreate the blackout with it. Default Raptor doesn't have a 2D panel, but I was able to recreate the blackout with it too. All this makes sense now - I love using NGX 2D panels. During my flight I change views multiple times between 2D, 3D and spot view. This slowly builds up Commit Charge and when it his 100%, blackout happens. - All my blackout experiences have happened with NGX, because I use the 2D panels (In 2D view). With Majestic Q400, I never use the 2D panels, so I never cycle views through 2D cockpit. That's why blackout never occured with Q400, until I maliciously caused it with cycling views. - Black out doesn't require plane to have physical 2D panels, only changing to 2D view causes jump in Commit Charge. That's why also Raptor can cause the blackout. - I added CycleHidden=Yes to cameras.cfg cockpit-section and flew ESSA-LDSP again and guess what= Commit Charge never exceeded 50%, VAS remaining at Split was >1.0 Gb and I was able to fly from point A to point B! - By disabling cockpit view, view cycling goes: 3D -> wingview -> Spot -> 3D and so on... This way Commit Charge does not build up, even when cycling with "S" for a minute. It looks like there is problems with 2D view in terms of memory usage. Possibly just on my machine, or in P3D itself. I have had this same problem before and after fresh install of Windows. Can some of you try to replicate this and report results? I can capture a video from this phenomenon to visually demonstrate what I've said in the text above.

I think the point is that P3D 3.3.5, with similiar and/or significantly lower settings than FSX, will cause CTD. In my case fresh OS reinstall, newest P3D with medium or low settings and mimimum ammount of addons, still same crash happens. Reducing settings does not help. VAS is not the problem, never has been, even with FSX. I'm changing back to FSX, for now.

Same here. FSX worked like a charm, no OOMs ever. P3D 3.3.5 + NGX causes CTD on every flight. Not an OOM as free VAS >1Gb. I agree with the source of the problem, but according to AVSIM it's not possible. Logs point to windows resource exhaustion and virtual memory, in my case.

You are not alone - I too have experienced this. Last flight with NGX and P3D 3.3.5 ended the same way with the display driver error. No idea where the problem is, I have stopped flying till P3D gets updated to see if the problem continues. Definitely something wrong with either W10, P3D or NGX, as problem occures with minimal ammount of addons and totally untweaked and clean .cfg. I could try to install fresh P3D and NGX only, and test if this still happens. And I don't use EZCA. I have created a topic about this in the CTD-forum area while ago, but I really have no interest to solve this problem, I'll check again when P3D gets updated.

Thanks for your fast feedback. Here is the latest blackout's log in Event Viewer. AppCrashView shows nothing related to P3D. Unfortunently, log is in Finnish, but I hope the important stuff shines through the language barrier. (Note to self, upgrade OS to English in future, everything will be easier for everyone.) I'm actually little ashamed to post this Finnish log to English forum, but that's all I can do. Fast translation provided in the log. Seems like log is all about virtual memory. No SweetFX's or ENB Series' are installed, I don't like those. I bet small frustration is visible in my first post, I literally ran out of ideas. I'll perform another test flight testing those "mandatory things" and report my findings to this thread, if I find the potential culprit. I agree my FSX-date fligthplans were quite suicidal, at least for a 32bit program like FSX, but I just flew in the limits of my PC and sim. I'm still wondering how I could fly 6-7 legs around Europe on FSX without restarting between legs, using heavy addons and sceneries, sliders to the right, and yet without any OOM's ever... And what comes to the FSUIPC VAS logs, till now, I've only used the remaining VAS indicator in the upper left corner in P3D. I will also activate the log-file logging from now on. Job first, then back to P3D. I'll report soon!

I'll do that as soon as I can and report my findings. I'm quite confused with this black out-phenomenon, as It seems to be more like a Windows or system related problem, rather than P3D-application related. This problem isn't normal application crash with error messages and faulting module names.

This June I bought new PC parts and built a new PC. I installed P3D v.3.3 and after few days I installed the just-released hotfix 3.3.5. During this month I have flown five flights, but I have landed the plane zero times -- I have never been able to fly to the destination due to this behavior: 1) Everything is fine, cruising at FL370 in 2D cockpit 2) I switch to VC, whole screen is black. 3) I change to spot view, it's also black. 4) P3D continues to fly and work, as I can hear the engines, and I'm able to disconnect the autopilot and trim the aircraft. (I can hear ap and trim sounds.) 5) Back to 2D, which has also became black. 6) Everything is black in P3D, windows and other programs are working normally 7) Sim runs for a while, then freezes and I have to hard reset my PC EGSS-ESGG Addons in use: PMDG NGX, UK2000 EGSS, RCFlight ESGG, MT6, FTX Global Base, Ultimate Terrain Europe 2.0, FreeMesh X Global, GSX, FSUIPC Flying on: Offline CFG: AffinityMask=15, UseGlobalTerrainView=True, AlwaysFullLoad=1, FFTF=0.01 VAS remaining at crash: Unknown Black out occured for the first time when I was established on the localizer at ESGG rwy 21. Everything went black the same way as described way above. No error messages and no data in AppCrashView or Event Viewer. I thought this was just bad luck. EGSS-LHBP, take 1 Addons in use: PMDG NGX, UK2000 EGSS, LHSim LHBP, MT6, FTX Global Base, Ultimate Terrain Europe 2.0, FreeMesh X Global, GSX, FSUIPC, ASN Flying on= Offline CFG: AffinityMask=15, UseGlobalTerrainView=True, AlwaysFullLoad=1, FFTF=0.01 VAS remaining at crash: Unknown Black out occured over Belqium after passing the Canal. This time I got a weird fisheye-effect for few seconds in spot view with dissapeared aicraft before the black out happened again. I suspected this might be a VAS and OOM problem, since I'm currently on 3440x1440 resolution after years flying with 1920x1080. This is the first time I started to monitor VAS with ProcessExplorer and FSUIPC. Just for remark: I have never experienced OOM on FSX with Windows 7 64bit. On FSX I had loads of sceneries and addons activated in scenery library, and I was still able to fly on 4096x4096 texture resolution and sliders to the right, flights like ESSA-ESMS-ESSA-LFPG-ESSA-LGAV with NGX on one go without restarting FSX and without disabling anything in scenery library. With P3D now, my sliders are centered, LOD_Radius is 4.5 and texture resolution is 1024x1024. At this point I updated my GPU drivers. EGSS-LHBP, take 2 Addons in use: PMDG NGX, UK2000 EGSS, LHSim LHBP, FTX Global Base, Ultimate Terrain Europe 2.0, FreeMesh X Global, GSX, FSUIPC, ASN Flying on= VATSIM CFG: AffinityMask=15, UseGlobalTerrainView=True, AlwaysFullLoad=1, FFTF=0.01 VAS remaining at crash: ~1,1 Gb I got a windows warning: "Close programs to prevent data loss. Your computer is low on memory" or something close to that. I decided to ignore that, and after ten secods, black out occured shortly after passing EDDF. I also got a Prepar3d.exe error: "The instruction at 0x00000000675C4C60 referenced memory at 0X0000000000000014. The memory could not be read." Still, only Vpilot.exe crash was visible in AppCrashView and I didn't find anything remarkable in the Event Viewer linked to this. I studied the CTD guide guide here on Avsim and I decided to raise the size of the paging file. It was system managed to this point. EGSS-LHBP, take 3 Addons in use: PMDG NGX, UK2000 EGSS, LHSim LHBP, FTX Global Base, Ultimate Terrain Europe 2.0, FreeMesh X Global, GSX, FSUIPC, ASN Flying on= VATSIM CFG: AffinityMask=15, UseGlobalTerrainView=True, AlwaysFullLoad=1, FFTF=0.01 VAS remaining at crash: ~0,9 Gb Black out occured near Hungarian border, shortly before Top Of Descend. No memory errors or pop ups this time, just the black out. I decided to rebuild the shared cache, fly with minimized addons and a clean .cfg: EGSS-LHBP, take 4 Addons in use: PMDG NGX, FTX Global, Ultimate Terrain Europe 2.0, FSUIPC, ASN Flying on: offline CFG: clean VAS remaining at crash: ~0,7 Gb I was on downwind for 31L in LHBP, when I got the same "Close program to prevent data loss..."-error. Everything got black, again. I decided to comply and closed P3D. No freezing or PC reboot was required. --- So far, what I have done and seen: - Not a VAS problem - Updated graphics drivers - Larger pagefile.sys -> not the solution -> back to system managed (virtual memory, not VAS-thing) - "Zero tweaked .cfg"-test flight - "only necessary addons"-test flight - Rebuilt shader cache - sfc /scannow - all was ok - RAM diagnostics - all was ok - Drivers are up to date - P3D run as administrator - Latest FSDT Addon Manager - Nothing is overclocked - DirectX diagnostics - all good - UAC disabled - Daily CCleaner - Disable unneeded addon sceneries I know P3D isn't supported on W10, but I've seen that many people can do it. Help is needed, before I devide to format and install Windows again.

Morning! I'm having some problems with my Nvidia Inspector-settings. I followed Word Not Allowed's tweaking guide here: http://forum.avsim.n...-guide-for-fsx/ I selected AA-mode: 8xs [combined: 1x2 SS + 4x MS]. With that, my performance is good, but I got some serrated edges. Solution for those was to select AA-mode 32x [combined something, doesn't really matter now]. With 32x, absolutely no serrated edges and performance was pretty much same what I saw with 8xs. Only problem was, that when GPU temperature hits 55*c, I get artifacts. 32x seems to really take a hit even on my GTX670. (Fan 100%) So, the actual question is, am I able to somehow get rid of serrated edges with 8xs? And my specs: Intel i7 2600k @ 4,5GHz | ASUS P8P67-M B3 | Palit Nvidia GeForce GTX670 JetStream 2Gb | Corsair XMS3 DDR3 2000MHz 8GB | Intel 520-series SSD 120GB | 750W PSU | Antec Kühler H2O 620

Thank you for your answer. Before formating I used to have very fast loading textures etc. Everything related to texture loading worked just fine. But after formating, texture loading has slowed down. They used to load in a matter of second. (Approx <1 second) And now loading takes over three seconds. I know, it sounds small difference, but I'm just wondering why does it take so long? Yes I have. It seemed to have no difference. I also tested my SDD's performance with CrystalDiskMark, and here's results: Read-time seems fine, so if the problem is in the simulator? I don't know, that's why I'm asking. :)

Hi I've just formated my entire SSD-harddrive and made a clean install of FSX on it. Now, while flying with for example with NGX, my texture loading seems rather slow when comparing it to my previous flight with this SSD, before formating it. Please ask if you need more information to help me with my problem. :) Edit: My SSD is Intel Solid-State-Drive 520 series

Hi! I have problems with my FSX. I've tweaked it and now I've succeed to get steady FPS @ 30 with the NGX's virtual cockpit at Aerosoft's Mega Airport Arlanda. The problems is, that a weird flickering has appeared, and it's pretty annoying. I know that it's caused by some "command" or wrong value in fsx.cfg, but I have no clue what command it is. Please see this youtube-video, And ignore the soundtrack on it: I was watching PewDiePie's gaming video while recording it. http://youtu.be/7BBPGedJ5mk

Venetubo actually lowered my fps. (That's funny though...)Almost all my sliders are at 80%.

Yes I have. While taxiing at ESSA, I get ~25 frames. But at some point it suddenly jumps to 15fps, and stays there.

Hi!I have upraged my computer with new components:Intel core i7 2600k @ 4,8GHzASUS P8P67-MASUS Radeon HD6950 1GBCorsair XMS3 DDR3 2000MHz 8GBAntec Kühler H2O 620850w PSUMy framerate is very low for example with NGX + Aerosoft Arlanda.I'm seeing only ~15 fps, when few people have reported over 30 fps in the same situation.I think I have something wrong with my fsx.cfg / fsx settings.Can you guys help me?