SU2 beta will CTD if Fenix is installed.
I wrote a message in official Fenix discord too.
8 Likes
I can confirm this. This is happening to other addons as well, Kuro 787, DA50, Inibuilds A320neo, etc.
3 Likes
Yep. Confirmed
SU2 changed something about the way how to access the community folder.
To me it looks lile thos is causing the issures with basically any 3rd party addon that jas to access assets from there.
Fenix being the most prominent one, i have the same issue with the FBW A380.
As these are the only aircraft i am flying, i am geounded until either Asobo or the 3rd-party developers solve the issue.
But it does not shed a good light on Asobo regarding their promise about backward compatibility.
3 Likes
For me, it’s absurd that Asobo doesn’t test the only study-level aircraft present. It’s an operation that takes 1 minute.
8 Likes
I do understand that for the first itteration of a Beta they only care about the core program and not about compatibility.
This is why they alwaus advise to test without any addons.
But with a title that was promised to be backward compatible, i do not undersrand why rhey had to chamge the formatting of a file that destroys compatibility fpr every addon that is trying to access the community folder.
4 Likes
The same here, at the moment, the Fenix app is started when clicked on start flying (with a Fenix a3xx selected) I 'm getting a CDT.
See similar CDT-reports here:
https://forums.flightsimulator.com/t/fenix-aircraft-and-inibuilds-a300s-crash/713191/2
https://forums.flightsimulator.com/t/cdt-when-starting-free-flight/713257
there is now a workaround to use the Fenix in SU2b:
Hi all,
Just a quick one to say folks running on 2024 SU2 beta will encounter crashing with Fenix due to a simulator bug (regression) with texture handling.
We have built a workaround for you overnight so you may retain use of the sim, but please be aware it comes with unintended side effects and as ever is considered highly experimental and relatively untested - but it’s there for you if you must use SU2B for whatever reason.
We are packaging a neatly isolated repro project for Asobo to review via the Dev Support forums. For those interested in the details, I asked Dave to provide a summary:
“MIPs fuc- oh, a public summary? Ok. mipmaps are now required for effect textures (e.g. those used by lights). This is a problem with forced MIP-streaming and it means the game engine never loads the full resolution effect texture, leading to 1/16th resolution shadow/light maps. Nothing we have found as a workaround except adding mipmaps for now. It will look pretty awful but it’ll function.”
HOW TO INSTALL:
Open the Fenix Installer, click on the branch icon next to the product title (e.g. A320), type “su2” (case sensitive) as the branch name and then press OK. It’ll scan for new versions then present you with an update. Hit Install, and wait for it to finish. You only need to do this once regardless of whether you have both the A320 and A319 & A321 packs, it’ll apply to all aircraft. To leave the branch, open up the branch icon again and remove “su2”, then hit OK, and you’ll be prompted to install the latest standard version.
If there’s any further updates we’ll post it here but otherwise that’s us for now!
5 Likes
Installed the su2 Fenix branch but nothing changes.
It CTD not immediately but a little later.
1 Like
Yes. Me too. CTD on trying to select airplane, and after restart fenix is somehow selected, but CTD after 5 seconds after ready to fly…
1 Like
Same here. Haven’t been able to stay in the sim for more than minutes until a CTD.
CTDs for me trying to even configure the Fenix A321 and select the right livery.
Faulting application name: FlightSimulator2024.exe, version: 1.4.7.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7283, time stamp: 0x67d4654a
Exception code: 0xc0000409
Fault offset: 0x0000000000f65401
Faulting process id: 0x0x2D70
Faulting application start time: 0x0x1DB9EC0DFC894F8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_9d15b9aa9e1c885b\nvwgf2umx.dll
Report Id: b494a3b4-9c03-4a58-8fa1-090339630457
Faulting package full name: Microsoft.Limitless_1.4.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
I am also unable to load the inibuilds A350 into the sim. It just spins forever, even zooming out before clicking Fly Now…
SU2 is unusable for me.
1 Like
I have Same issue
Faulting application name: FlightSimulator2024.exe, version: 1.4.7.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7283, time stamp: 0x67d4654a
With this aircraft :
- A320 Fenix
- A350 Inibuild
- A400M Inbuild
- A320 Inbuild
2 Likes
Sim update 2 beta kills MSFS and Asobo should deliver a patch for these newly introduced CDT problems as soon as possible. Before that I’m not able to use MSFS 2024 anymore and will use MSFS 2020 instead.
1 Like
Why join a beta if you don’t want to deal with issues? This is a test build, and the whole point is to find these issues before release. This is not early access, this is purely for testing.
10 Likes
1 tag is required - add it in the tag section next to the title above:
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue:
Immediate CDT when starting a flight using the Fenix a320 which worked before the introduction of Sim update 2 beta.
There where severeal similar bug reports like
Fenix and SU2 - Sim Update 2 Beta | MSFS 2024 / External 3rd Party Products - Microsoft Flight Simulator Forums
about CDTs, which are introduced by Sim update 2 beta in connection with 3rd party products which did run without any problems with MSFS 2024 under Sim update 1 and before. The forum admins did move them under “3rd party products” which means to nlame 3rd party developers instead of solving th CDTs clearly introduced with the sim update 2 beta. These Tickets should be moved back under the CDTs section again because they clearly belong there.
Did you experience this issue before you joined the Beta?
No, not before sim update 2 beta.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No, the same items worked fine before Sim update 2 beta.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time I try starting a free flight
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
1.Just use the steps described under the link above.
2.
3.
YOUR SETTINGS
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 User Support Hub.
What peripherals are you using, if relevant:
n/a
[PC Only] Are you using Developer Mode or have you made any changes to it?
Both, I reproduced the bug with and without developer mode.
[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
[PC Only] What other relevant PC specs can you share?
i7-9600, 64 GB RAM, Windows 11 23H2
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
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:
•
Yes, I am ready to deal with the issues but at the moment, when the rolled out beta sim update brings MSFS 2024 to CDT any time it is just unusable - just because of the CDTs.
2 Likes
They will not release with these issues, like in the past SU’s they bring out multiple builds. If you don’t want CTDs you can go back to the live version.
6 Likes
CTD with GAmod models also.
Tried a free flight with Fenix A320 and FBW A320.
Both CTD during Flightplaning with EFB or try with FBW showing liveries.
Could not even start the flight.