davidzill

Put me in the club of CTD error when exiting P3D V4.2 only after flying the QOTSII. This even happened after a fresh Windows 10 install and vanilla P3D. Not a show stopper, but indicates something isn’t jiving between P3D and QOTSII. Not saying the problem is PMDG’s, could be coding error on Lockheed Martins part. Just hope there is dialogue between the two to troubleshoot the error.

Not sure if this has been discovered or known yet. Fresh install of Windows 10 64, fresh install of Prepar3d V4.2, NO mod tweaks, stock .cfg's, fresh install PMDG QOTSII. Everytime I exit Prepar3d V4.2, I get a BEX64 CTD, ONLY in the QOTSII.

Jim thanks your reply. I took clouds from 4096 to 2048 and brought my clock from 5.3 to 5.2ghz. Need to test it tonight. Been running it for months without issues. I think lots of 4096x4096 clouds took its toll.

Been getting stackhash CTD frequently out of the blue. The only big system change was recently installing REX Skyforce 3D. Haven’t had time to take to any testing yet, but I’m suspicious Active Sky may be involved since it is the weather engine itself.

Thank you very much!

That would be amazing. Thanks!!!

I'm posting here in hopes someone may help me figure this out, or even upload your GSX 777F configuration file. I believe this is more of a GSX problem: I've never had issues in the past. I'm used to cargo being loaded into the main deck (Large rear left door) and aft lower cargo door. I've auto-updated several times since the FSDT Auto-updater has been going on, and today I noticed when I call for the aircraft to be loaded I not only get the vehicles carrying the two loads of cargo, I get two additional empty trucks and trailers, as well as two passenger luggage vehicles which appear and drive around the aircraft aimlessly before disappearing. I uninstalled GSX in the control panel add/remove programs, then subsequently reinstalled it to find the same oddity. Is this a known issue? Also, I read on the update list I can use up to *3* cargo loaders now, which allow me to load cargo into the forward lower cargo access too, but I'm at a loss on how to do that. I've used google to search for a user 777F GSX profile, however on every forum where the question is asked it is stated GSX already provides a profile. Thanks for your assistance.

Still running tests to narrow it down. What I came up with was I can fly the NGX in and out of any airport, including Orbx without an issue, except LOWI. The LOWI apphangB1 occurs about 40+ miles from the airport, during the descent near transition altitude. I’ve flown to Orbx LOWI about 40 times in the NGX, and this happened just after installing the Orbx Germany South. I contacted Orbx. Their customer service is horrible, dismissive, and unprofessional. I’m not ready to pin the blaim on a PMDG issue, but this has only happened in the NGX.

Windows 10 Pro 64 (Without fall creators build update). I’m receiving consistent apphangB1 CTDs...ONLY when flying to Orbx LOWI (Innsbruck). I consulted Orbx, did some testing, and discovered 2 important things: (1) Only happens while descending into Orbx LOWI while crossing into the Orbx scenery, and (2) This only happens in PMDG aircraft. Any ideas?

I ran Sfc, etc, no errors. For now I’ll stay with the previous build. My windows 10 runs absolutely great...so if it’s not broke, why fix it lol? Also ran CCleaner registry repair which found a full page worth of errors which were fixed.

P3D V4.1 // Windows 10 Pro 64. Updated to Fall Creators Build update 2 weeks ago. Immediately experienced issues; when starting preflight in the NGX, if I looked over either shoulder or up at the overhead, my FPS cut from a solid 60 to 30 FPS. And I’m not talking about a smooth 30, screen was lagged looking around. Uninstalled Nvidia drivers, did a clean install and same issue. Rolled back the driver problem went away. I went on the Nvidia forum, severe game performance issues regarding Fall Creators build are very well documented...the problem is I experienced this after the “fix” mid November.

It was an odd occurrence this happened, but that did the trick. Thank you!

Received a yellow 'Saved Data Error' when I started Fs2 Crew Reboot in Prepar3d V4 today. Also, SDK error in QOTSII and SDK error in the 777. All audio drivers up to date, (SDK) Enabledatabroadcast=1 in all three of the options.ini files.

Yes I did and was not able to determine the root cause. I took to deleting FSUIPC, same thing. There is only one controller button set for elevator/aileron trim. Checked all controllers and axis settings, as well as keyboard assignments.

I have the same problem, posted yesterday (Didn't see this post). Did you have positive results deleting FSUIPC? In the NGX, I can hear the trim wheel and have to constantly readjust my trim setting which is perpetually moving noise-down. In the 777 and QOTSII, the trim moves full nose down quick. It wants to stay there and goes right back when I adjust the trim back up. Never had this issue before, but from what I've read, it's somewhat commonplace.

Prepar3D V4 // Latest FSUIPC // Thrustmaster HOTAS. While performing 25-minute preflight on the ground, the trim wheel continuously and intermittently adjust nose down. After I set takeoff trim, by the time I make it to the runway, my trim ends up being at full nose down. How do I correct this?

Good afternoon, I am finally preparing for my first 747F flight. After I planned my flight through PFPX and had the weight and balance settings set in Topcat, I entered the FMC to manually set the payload data and ran into a dilemma; the QOTSII FMC has 5 assigns cargo stations, Topcat has just 2. How do I correctly set my payload?

I was just illustrating how changing to Windows 10 made a huge difference.

I love not anticipating an OOM

My differences are explained in my initial post, however I will say Windows 10 appears far more optimized for performance than Windows 7. No editing or performance tweaks needed, it's good to go out of the box.

A lot of visual differences come from the DX11/12 rendering internal HDR textures, volumetric fog rendering, etc. Textures overall appear sharper, higher resolution. Runs much smoother than FSX (Which I swore by religiously for years). Prepar3d V4 takes advantage of the most current DirectX, and is also SLi capable. In FSX to even come close I have to create an Nvidia control panel profile, Nvidia Inspector profile, and the DX10 fixer. I was very hesitant at first, however at this point I don't see how I could go back to FSX.

I've been using FSX since it's release. Prior to V4's release, I've never used any version of Prepar3d. Using a Windows 7 system, I purchased V4 and was perplexed at the poor performance. I inquired in the forums, a rare minority of people reported the same issues. At the same time, I was experiencing frequent crashes in FSX; APPHANG 1b crashes virtually every time I started a flight in the NGX. I determined my Windows 7 was corrupted either by my own user error or other means. I upgraded to a I5 7600K at 5.3ghz, fast DDR4 memory, and two 1080 Ti's. I also installed Windows 10 Pro 64, and one single M.2 pcie 2 TB SSD. I installed Prepar3d again. My settings are configured pretty high, although I set autogen to normal and dynamic lighting off for now, I'm using 4096 textures in 4K, 4SSAA. With the PMDG NGX, REX TD, AS4, I'm getting a solid 60fps at Flightbeam's KSFOHD V2. The terrain looks so much better than FSX, and flying looks and feels much smoother, immersive, and realilistic.

I recently upgraded from windows 7 to 10. So far Prepar3d V4 performance has been good, keeping my fingers crossed.

That's what I was doing, one at a time for each individual livery I have installed. However, when adding the aircraft via 'Add aircraft' and "Add aircraft from template,' the 747-400F variant has only one engine option.

Thanks for adding this link. Not entirely related to the 747, but with the PMDG 737-700W, the updated aircraft file has the correct engine (CFM56-7B24/26). TOPCAT's aircraft file has the CFM56-7B22 engine (Used in the -600). Will this be an issue with flight planning?