kymh

New CTD from Tablet and Mad Lighting problem (since last update)

Recommended Posts

I have reinstalled completely to try and solve the following but the 717 is once again unusable for me despite looking great before the latest update.

I now experience a CTD every time when using the tablet and clicking on Cold and Dark, Ready to Start or Ready to Fly.

Clicking on Exterior, Crew, Documents or Status does not cause any such problem.

If I don't click on the tablet as noted above which causes a CTD, I have this weird lighting effect where I see text from the panels scattered throughout the cockpit.

There is no error report following the CTD.

Cokpit.JPG

Edited by kymh
Found Conflict

Share this post


Link to post
Share on other sites

This problem does not exist if I set FlightBeam KDEN and FlightBeam KSFOHD sceneries to inactive in my addon.cfg:-

[Package.1]
PATH=H:\Documents\Prepar3D v4 Add-ons\FlightBeam KDEN
ACTIVE=false
REQUIRED=false
[Package.2]
PATH=H:\Documents\Prepar3D v4 Add-ons\FlightBeam KSFOHD
ACTIVE=false
REQUIRED=false

I don't understand how this could cause conflict as there are no problems with any of my other aircraft (most of Carenado, Alabeo, FlySimware Learjet 35A, Aerosoft CRJ, PMDG 737 etc.)

Share this post


Link to post
Share on other sites

@kymh This actually adds more fuel to the fire from other reports. We've had growing suspicions that there is a bug with the Prepar3D addon system that causes this. Did you happen to change your texture resolution in your settings? We haven't been able to determine exactly what settings/scenarios cause this.

Share this post


Link to post
Share on other sites

Yes I've tried various resolutions as well as backing off other settings and it made no difference.

I spent many hours on settings before slapping myself in the face remembering I'd installed to two FlightBeam Airports since the 717 was working with the fantastic new lighting.

I've switched Simstarter NG back on and set a profile without the two FlightBeam Airports (I have other FlightBeams and they're OK) and it's as stable as can be flying all day with everything maxed out to stupid levels on my 4K monitor while running chaseplane, AS16, VoxATX 7.4, PFPX, everything currently available in ORBX & FSDreamTeam and Aerosoft, Spad Next and tons of Windows 10 programs running on another screen taking care of business.

Wish I could help more and prepared to try anything you can suggest to help. (I'm constantly well backed up)

Edited by kymh
Forgot to mention

Share this post


Link to post
Share on other sites

Forgot to mention - Buggy add-ons system for sure

I did also find that I have add-ons.cfg in both C:\ProgramData\Lockheed Martin\Prepar3D v4 as well as C:\Users\Kym Harper\AppData\Roaming\Lockheed Martin\Prepar3D v4.

An entry for Flightbeam - KSFOHD had been added in each but removing one made no difference.

Also, most times something is added I get something like the following with [Package.0] getting a double entry:-

(nothing to do with the TFDi 717-200 but confirming your theory on a bug with the Prepar3D addon system)

[Package.0]
PATH=H:\Documents\Prepar3D v4 Add-ons\FlightBeam KDEN
ACTIVE=true
REQUIRED=false
[Package.0]
PATH=H:\Progs\12bPilot\SODE\P3Dv4
TITLE=SODE
ACTIVE=true
REQUIRED=false

 

Edited by kymh

Share this post


Link to post
Share on other sites

With no changes to my system apart from any Windows Updates and ChasePlane Updates and a few new Aerosoft Airports and Carenado Aircraft, as if by magic, this problem no longer exists and I can now have the above two FlightBeam Airports set as active.

Go figure (I can't) :-)

 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.