Jump to content
Sign in to follow this  
Piotr007

Haunted by a strange CTD when starting at Flytampa Rebooted in P3D V4

Recommended Posts

Hi guys,

I have strange CTD's occurring only when I start a flight at OMDB (Flytampa Dubai Rebooted). As soon as I change view or start panning around the sim crashed. When leaving on without touching nothing crashes. This is strange. I have installed:

P3D V4 base

ORBX Global

Ultimate Live Traffic

SODE

GSX

Flytampa Dubai Rebooted

Addon Manager

Flytampa Amsterdam

 

A flight from Amsterdam to Dubai went without problems. However starting a flight at Dubai with whatever airplane I choose, it starts to CTD as soon as I start to pan around or using space +mouse for changing view zoom.

 

Any help and any insights on this issues would be helpful. I suppose no addon is interfering, as these issues do not happen at the other Flytampa airport I own.

EDIT: it simply crashes using Flytampa Dubai Rebooted.

 

EDIT2: Approach traffic is causing the issue! It seems to overlap the regular traffic.

Peter


I9 12900K @ 5.1ghz P-cores/ 4.0 ghz E-cores fixed HT off / Corsair iCue H150i Capellix Cooler/ MSI Z690 CARBON WiFi / 32GB Corsair DDR5 RAM @ 5200 mhz XMP on / 12GB MSI 4090 RTX Ventus 3 / 7,5 total TB SSD (2+2+2+1+0,5 all NVMe)/ PSU 850W Corsair / 27" (1080P)

Share this post


Link to post

There might be FS9 models in that traffic package which are incompatible with V4. Try with traffic off.

  • Upvote 1

Lee H

i9 13900KF 32GB Ram 24GB RTX 4090

 

Share this post


Link to post

did you delete the 4 files named ******papi.bgl? 

Share this post


Link to post

Try removing ULT.

For me P3d v4 was acting strange, in slow motion,  with ULT. I removed it and all went normal.

Share this post


Link to post

If its ai traffic then check you don't have any invalid values in [flightsim.xx] sections of ai aircraft.cfgs for those being injected. I had one of the aircraft with tail number pasted in parking codes which was causing crash at another airport that fixed after correcting that line. It didn't cause any problem in v3 so went unnoticed. No info showed up for this in content error logging which made it complicated to figure.

  • Upvote 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
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.
×
×
  • Create New...