Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

15 Neutral

About Kwakadilly

  • Birthday 06/06/1992

Contact Methods

  • Skype

Profile Information

  • Gender
  • Location
  • Interests

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Nope, no memory leak for me. This driver had my sim running about 100MB higher than the 376.33 driver and 500MB less than the 378.66 driver. It is stable for me, however others are saying it leaks. It seems to be hit or miss and I think it is a system/settings/addons issue to be honest. You just need to test them and see what works for you.
  2. I reported the issue to Nvidia and was asked to try the hotfix driver. Everything seems to be great now. Get 378.72 https://forums.geforce.com/default/topic/994534/geforce-drivers/announcing-geforce-hotfix-driver-378-72/
  3. Hmmmm.....obviously? I don't know what you think I am suggesting. Both 378 releases have had leaks, so we'd better hope they fix it because later builds will hold the same issue and prevent a lot of people from updating in the future.
  4. http://www.prepar3d.com/forum/viewtopic.php?t=123697 378.XX leaks. I hope a solution is found soon.
  5. A little update, I think the problem has to do with Windows Antimalware Service Executable (at least for me). I'm on Windows 10 Pro 64bit. I did a shorter flight today and monitored all kinds of different things to try and see if I could understand the problem better. For me, it seemed as if P3D would lock up when I clicked a 2d popup, and then would subsequently crash. Event Viewer gave me the KERNALBASE.dll error as the reason behind the crash. With that in mind, I wanted to see why it was locking up. I noticed that every time P3D had locked up, Antimalware Service Executable was jumping up in resource usage. When it went away the sim unlocked and everything was fine a second later. I even tried to spam click the displays and force a crash but had no luck when the Antimalware Service wasn't taking up resources. I'm lead to believe this must be the cause of the problem. The Antimalware Service Executable is scanning the system for malware, and in turn using a lot of resources and locking up the PC since the system can't handle P3D, my external addons, and this service. The solution..I'm still working on it. Sadly, although Windows has the option to disable it, it will re-enable if left off too long (I don't know how long). You can get around that in a much more technical way, however I'm going to try something else. I want to see if excluding the P3D.exe, as well as the others I run when I am flying, has any effect on this or not. I've already had their directories excluded for some time now, but not that actual exe. Perhaps if it doesn't scan the running process it won't use as much resources, or won't affect the program. If it doesn't work, I think disabling the service all together will likely fix the issue.
  6. I've had this issue with both the NGX and 747 now and it always happens on a long flight when I click the 2d pop outs. It has never happened to me with any other addon. I still have yet to complete a flight in the 747 because of it. I have FSUIPC installed and registered, however it was v4955. I've installed v4962 so we'll see what happens I guess... I'll give the CTD guide a shot too.
  7. FWIW I haven't had any issues with the wing flex and turbulence I am using AS2016/ ASCA in P3D. Here are my settings in regards to turbulence... Maximum Wind Turbulence: 20 Turbulence Effect Scale: 10 Enhanced Turbulence: unchecked Wake Turbulence scale: 50 (I fly on Vatsim and don't see this often, but I might end up turning it down)
  8. The United States is doing this now too. Most of the nations major airports have been updated to utilize RNAV SIDs and STARs, some are still in the process of getting this done, like Southern California. The arrivals allow for an optimize profile descent, and usually end on an IAF for either an ILS or RNAV RNP approach. A good example is San Francisco and the SERFR or DYAMD arrivals.
  9. At the risk of jinxing it.... So, I've had this problem for a while and it drove me mad. It was never an issue on older versions of the NGX or when I used FSX Boxed. But once I started using SE and Windows 10, it seemed fairly regular. I actually stopped using the NGX for the most part. But, it's a great plane and it drives me crazy to have an aircraft that I shelled out as much money as I did for it and not be able to use it, so I've been trying to see if I can solve the problem, and I think maybe I did.... First off, I did two things at once so I can't say for sure what it is that potentially solved this issue for me. The first thing I did was disable selective suspend like the above link says. I do not think that is what fixed it, but maybe it is. I turned it off simply because I forgot to disable it on this Windows install and I normally do not like to have it on. The second thing I did was switch to low res vc textures, vc model, and vc displays as I was experimenting with alternate inspector settings. Perhaps somebody from PMDG can say if there is any technical difference in the low res vc model, but after I switched to low res the problem went away. I've flown all week long doing 3-4 flights in a row without issue. Previously that was impossible as the problem would have developed before the end of the second flight. Something that I realized while flying yesterday was that the problem seemed more likely to happen when I was arriving or departing a payware scenery. For example, Flightbeam KSFO, which is a pretty heavy scenery, would be a regular area that I'd see the click spots go away. If I was flying at another airport that I was only using an afcad and had no add-on scenery anywhere close I wouldn't lose them. In fact, I can't even remember the last time I lost the click spots without arriving or departing a payware scenery (or being in the vicinity - like KOAK). So, I guess the next thing to do is to have others test it and see if this indeed solves the issue. Use the link above this post to disable selective suspend. Then, open the PMDG operations manager, select the NGX, and then select performance settings. Set all the check boxes to low res and fly for a while. Like I said, I am a week in now with 10 flights, many back to back turn and burn legs, and I've flown to my big sceneries like SFO and LAX, and I haven't had a single issue yet. Fair warning, turn textures and all of that to low res will be noticeable, the textures and vc model aren't really that bad, but the displays are obviously lower quality.
  10. Right as I am typing up a post about the new livery it is posted! +1 penguin 1
  11. Awesome work, Treva! It's mmm, mmm, good.
  12. Oh duh, I knew that. Not sure why I put SW. Oh well I think it'd be a great one to have
  13. Anybody interested in a challenge? N214SW, have at it!
  14. I normally don't request paints, but since I really want this, and since I always seem to screw up Southwest paints... Colorado One anybody? http://www.blogsouthwest.com/video/soaring-mile-high-introducing-colorado-one
  15. The LR is nice, but the ER is more common (and it's all I fly). I'd like to have an ER for sure.
  • Create New...