Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
Yes
Brief description of the issue:
Loading the A310 causes a CTD randomly. Airport location, time of day, livery, graphics settings seem to have no effect on whether the CTD happens. It happens about 75% of the time after clicking the “fly” button. Empty community folder or not seems to have no effect.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Load A310, generic white livery or any custom livery and the aircraft will CTD about 75% of the time. Airport location, time of day, weather, graphics settings do not to seem to have an impact.
Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):
Nvidia 2060super, driver version 546.29
PC specs and peripheral set up:
RTX2060super, I712700k, 32gb DDR4, 4tb M.2 NVME
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Fault bucket 2214139609423773566, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Build Version # when you first started experiencing this issue:
Since SU13, continuing to current build of SU14
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons: