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?
Yes
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
JMB VL-3
Brief description of the issue:
The JMB VL-3 now causes an immediate CTD with AAU02 (1.33.8.0) which is probably due to the now incompatible glass cockpit.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
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:
Do you have the same issue if you follow the OP’s steps to reproduce it?
No
Provide extra information to complete the original description of the issue:
Loaded C&D into aircraft. Powered up Master and Avionics. Started engine and turned on various lights & electrical accessories. No CTD & all systems appear to be okay.
MS Store PC version
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
No
Provide extra information to complete the original description of the issue:
Completed a short flight in the JMB after AA02 update, all my mods still in the community folder including FSLTL traffic, we love VFR, and a multitude of liveries etc, and did not experience a CTD.
If relevant, provide additional screenshots/video:
I have solved my problem now !
The solution :
- Rename community folder
- Restart MSFS
- Uninstall JMB VL-3 via content manager
- Reinstall JMB VL-3 via content manager
also after moving all mods from renamed folder to community there are no problems anymore !
(in the beta of AAU02 phase my solution was : revert to the previous non beta built)