Jump to content

Sign in to follow this  
Johnny19

P3D 4.1 CTD near Labrador

Recommended Posts

10 hours ago, CaptKornDog said:

Try the exact same flight WITHOUT restarting Couatl.  Kill it via Task Manager.

Of course I just realized that that means landing in KSFO will be screwed up because I have Flightbeam's KSFO HD and it requires COUATL.

No way to restart COUATL once you've killed it in Task Manager, is there?

- Daniel

Share this post


Link to post

Daniel. 

Where exactly did the CTD happen please near which waypoint? 


 
 
 
 
v63vq9-5.png

Share this post


Link to post
20 minutes ago, tooting said:

Daniel. 

Where exactly did the CTD happen please near which waypoint? 

Sorry, didn't exactly see that... but was likely near the east coast of the UK.

Possibly: MIMVA, TOLSA, OKAMA, EMLON, ROVNI, TENDO?

- Daniel

Share this post


Link to post

Thanks what FIR are these waypoints in.  Which country? 


 
 
 
 
v63vq9-5.png

Share this post


Link to post
4 minutes ago, tooting said:

Thanks what FIR are these waypoints in.  Which country? 

EGTT?  Does that make sense?

- Daniel

Share this post


Link to post

It does Daniel.  Its  not the Canada issue we are talking about. That's some 2500 miles away. It could be a million different things causing that CTD.  Are your UK2000 sceneries the P3Dv4 versions?? Do a scan in your uk2000 folder for any fs9*** bgls.  These cause ctds. Belfast being a big culprit. 

Also I see you have ultimate traffic live (so live its not been updated in over a year)  have you added any 787s to it??  Namely the camsim 787.  This causes ctds 


 
 
 
 
v63vq9-5.png

Share this post


Link to post

Thanks!  I'll check all my UK2000 sceneries - no, not all are P3D v4, some I brought over from v3.

I haven't added any UTL models, though.  Are the stock models okay?

- Daniel

 

p.s. Redoing the EHAM - KSFO flight now.  Killed Coutal in task manager and no CTD.  Currently on approach to KSFO

Edited by Daniel Baker

Share this post


Link to post
1 hour ago, Daniel Baker said:

Of course I just realized that that means landing in KSFO will be screwed up because I have Flightbeam's KSFO HD and it requires COUATL.

No way to restart COUATL once you've killed it in Task Manager, is there?

- Daniel

Not without restarting the sim.


Kyle Weber (Private Pilot, ASEL; Flight Test Engineer)
Check out my repaints and downloads, all right here on AVSIM

Share this post


Link to post

Definitely check your uk2000 scenery folders for any . BGL files with fs9 in the titles the ones you 'brought over' from version 3.

Id be willing to bet money thats what caused it. 


 
 
 
 
v63vq9-5.png

Share this post


Link to post
6 minutes ago, CaptKornDog said:

Not without restarting the sim.

So killing Couatl in the Task Manager is not going to work as a long-term strategy, unfortunately

Share this post


Link to post

No there is no long term strategy. You'll find Umberto on the next page promoting is KORD update topic but not in this topic. And Rob and Poppet from LM won't get involved because they also don't want to be associated with it.  What you have here is a prime example of a big Developer with an issue and LM not working together with him to try and resolve the issue as they will claim " its not their problem" good this liability stuff isn't it


 
 
 
 
v63vq9-5.png

Share this post


Link to post
2 hours ago, Daniel Baker said:

So killing Couatl in the Task Manager is not going to work as a long-term strategy, unfortunately

Yep, agreed.  You’ll lose scenery associated with Couatl for the flight.


Kyle Weber (Private Pilot, ASEL; Flight Test Engineer)
Check out my repaints and downloads, all right here on AVSIM

Share this post


Link to post
6 hours ago, Daniel Baker said:

Of course I just realized that that means landing in KSFO will be screwed up because I have Flightbeam's KSFO HD and it requires COUAT

No it doesn't Daniel. FB ditched the FSDT addon manager when they updated all their sceneries. It now uses the Flightbeam Manager. Have you updated ?


System: MSFS2020-Premium Deluxe, P3D 5.0, ASUS Maximus XI Hero,  Intel i7-8086K o/c to 5.0GHz, Corsair AIO H115i Pro, Corsair Spec Omega Case,Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, 32Gb Corsair Vengeance DDR4 3200Mhz RAM, EVGA 850+ Gold PSU,Win 10 Pro 64-bit, LG 43UD79 43" 4K IPS Panel., Logitech X56 Hotas Stick and Throttle, Logitech/Saitek Flight Yoke System, Multi, Radio, Switch Panels

 

Share this post


Link to post
15 hours ago, tooting said:

Definitely check your uk2000 scenery folders for any . BGL files with fs9 in the titles the ones you 'brought over' from version 3.

Id be willing to bet money thats what caused it. 

Actually, after checking I forgot I've actually purchased/upgraded my UK2000 scenery to P3D v4 versions.  Sorry - getting confused between FS9, P3Dv3, P3Dv4 etc., etc.  So many add-ons and sim configs over the years...  So no issues here

10 hours ago, ZKOKQ said:

No it doesn't Daniel. FB ditched the FSDT addon manager when they updated all their sceneries. It now uses the Flightbeam Manager. Have you updated ?

Actually I saw that after I successfully landed in KSFO, much to my pleasant surprise.  

 

 

So... I'm not closer to understanding what's causing this - other than it seems couatl could be a culprit.  Restarting it once in the air often helps... but sometimes not, I guess?

- Daniel

Share this post


Link to post

Just left the NAT, heading west to CYYR, P3D disappears. Windows error log says ntdll.dll again. I am done with this. Most flights I load P3D and reset couatl and rebuild airport cache but today I skipped it.

Edited by Boeing or not going

Share this post


Link to post
Guest
This topic is now closed to further replies.
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    31%
    $7,835.00 of $25,000.00 Donate Now
×
×
  • Create New...