Please Help Me Fix This "Line"

[garymcginnis]

Hello,

I am new to P3Dv4.3 after having been out of flight sim for the last 8 months. I have been working on getting P3Dv4.3 up and running but after an "awful" day today (NTDLL.DLL error that I believe was either caused by ORBX vector or a loser in the silicon lottery and general bad OCing i7-8700K) I have been trying to "fix" the sim. I started getting the NTDLL.DLL error in FSX:SE right at the end of my time with it and this is what made me sit out for the last 6 months and invest in a new computer/P3Dv4, so after today I am really second guessing my decision to invest in and continue this hobby; especially since the sim looks like crap with this issue I am having. 

The issue is a weird grey line/triangle that follows the aircraft when in the VC and moving. I have tired a few different suggestions I found that sounded like similar issues but have had no luck. I did find an EXACT posting for the same issue I am having over on the official prepar3d forums but no one answered his question and the post has been locked. I have also tried different PTA presets with no luck.

 

PLEASE CLICK LINK FOR VIDEO: https://photos.app.goo.gl/hXecqtEzrWfwwPZJ9

Specs
i7-8700K (was 4.8GHz but now down to an XMP OC of 4.3GHz because of the possible NTDLL.DLL errors due to heat)

ASUS ROG Extreme MOBO

64 GB 2666 STRIX RAM 

2x 840 EVO 256GB SSD in RAID 1 (OS)

2x 850 EVO 500GB SSD in RAID 1 (P3D)

EVGA GTX 980 KINGPIN

H100iV2

W10 64-bit (all windows updates/Cortana disabled)

 

Addons

FSLABS A319/320

AS 2016

REX 4

REX AIRPORTS HD

PTA

FSUIPC 5 (purchased)

Various ORBX products (minus VECTOR due to possible NTDLL.DLL error)

 

As you can, this computer should be able to handle anything thrown at it and as such wasn't cheap, so please help because I'm ready to take up a new hobby if I can't get this working (especially since I fly for a living to begin with).

Thanks

[F737MAX]

17 minutes ago, garymcginnis said:

The issue is a weird grey line/triangle that follows the aircraft when in the VC and moving. I have tired a few different suggestions I found that sounded like similar issues but have had no luck. I did find an EXACT posting for the same issue I am having over on the official prepar3d forums but no one answered his question and the post has been locked. I have also tried different PTA presets with no luck.

PLEASE CLICK LINK FOR VIDEO: https://photos.app.goo.gl/hXecqtEzrWfwwPZJ9

The grey line in your video is caused by a problem in the cameras.cfg located in C:\Users\[USERname]\AppData\Roaming\Lockheed Martin\Prepar3D v4

Find the first line entry of "Clipmode=None" and change it to "Clipmode=Minimum". If the entry doesn't exist, then add "Clipmode=Minimum" anywhere under the first [CameraDefiniton.xxx].

That works for most people, hopefully for you also.


With regards to ntdll.dll errors, even the best PCs on the market can suffer them if the settings are too high. Most would suggest reducing all of the sim settings to medium and then push the sliders right and test to see where the error reappears to work out the maximum capability of your PC.
Check the CTD forum for ntdll.dll errors https://www.avsim.com/forums/forum/262-crash-to-desktop-ctd-forum/

[garymcginnis]

I forgot to mention I have Chase Plane. Will that fix you offered still work?

As far as the NTDLL issues, yes I also rolled them back a little. However, it wasn't outrageous to begin with. The flight was my third with v4 and the first two where an SXM turn over the water. This third flight was over land, which has me thinking about VECTOR (almost didn't install it to begin with since I guess P3D isn't that bad and VECTOR has always been the most unstable ORBX product). I also happened to be testing a AffinityMask (4092) setting just to see and was monitoring the temps at the time of the crash and it peaked at 80*C with 80% utilization on all physical and logical cores (1/1-5/5) except for 0/0. So it was either that it possibly didn't like 4092 (took out AM altogether) or just hot. I have the CTD guide on my non-FS computer.

I'll test later to see. Same flight. Just annoying this occurs on flight 3 in the sim when I was trying to fit the flight in on a day off before a family event this afternoon. No clue when I'll be able to test a follow up.

Thanks for the help!

[F737MAX]

32 minutes ago, garymcginnis said:

I forgot to mention I have Chase Plane. Will that fix you offered still work?

Thanks for the help!

You're welcome!
Yes, it will work - it did in my P3D and I'm a Chase Plane user.

Everyone has to compromise on their combination of settings. I have a lot of sliders at high or ultra/max settings, but reduce autogen buildings and vegetation to medium, turn-off reflections and hardly use dynamic lighting when flying airliners to help keep things cool and smooth. So be brutal regarding yours, including ORBX products settings, and work upwards to the highest details that your PC can handle and remain stable.

I don't want to get dragged into a debate about whether to use an AM or not, HT on or not, what cores are better than others for P3D, which cores to load other 3rd party programs, etc... Everyone has their own opinions on that, so knock yourself out with these two threads:

 

[garymcginnis]

Like I said. It was just a test. Personally the sliders were at maybe 65%. I've always ran them low with FSX and P3D is no different. That's why I really believe it was either heat from the OC, VECTOR and/or the AM setting. We shall see next time I can fire it up.

I'm not that upset with the crash overall since I'm still in the no expectation/testing stage but it's still annoying.

 

Thanks