seb851

Is not true Tolis run in WASM like PMDG, is not like Fenix or FSLAB run in external software

Is NOT native version, is only compatible version. Check Manifest.JSON, and folder scructure and texture format.

LFMO, release a Aircraft in 2026 without a Native version for FS2024 is a JOKE ...

F IIRC, before the service was shut down, Aerosoft NavData Pro worked perfectly fine with PMDG and other aircraft that rely on external NavData. The database structure was standard, so compatibility wasn’t an issue. I really hope PMDG and others eventually add an option to use the default NavData instead of forcing Navigraph. The default NavData is rock‑solid—aside from airport‑specific information (runways, SID/STAR procedures), which is always overridden anyway by airport autogen or third‑party airport addons.

LMFO FSLab nevers annonced any aircraft for MSFS before mid 2022 ... and FSLAB release Concorde for P3D late 2023. so your argument is invalid

Not to mention that Fenix hasn't released an update in 8 months, not to mention that it doesn't officially support MSFS 24 (no support from Fenix) unlike FSLab which is officially compatible and supported by FSLab. And a lot of people word not allowed on PMDG, but they're one of the first to release addons that are 100% native to MSFS 24 (Fenix, FSLab, iFly and Aerosoft's CRJ are not native).

Fenix is overated asf

MSFS 24 SU3 get a overhaul for IFR SID and STAR procedure/flow , but still some issue for Runway and Sid assignation still use vector instand a normal SID.

"Resource usage exceeds gpu memory capacity" error message trigger like 1GB free, is useless message imho, many time never overun my VRAM budget

LMFO, .ktx2 format is more volatile and better performance than DDS format. FSLAB and Fenix is more eat more VRAM than PMDG 777 (use .KTX2 format) The VRAM issue is affecting more addon use DDS instead KTX2 format

I've just come back from a one-month break due to frequent CTDs (crash to desktop). I'm not sure whether the issue was caused by my clean install or the NVIDIA drivers. Since returning, I’ve completed 15 flights without a single CTD—quite a contrast to the constant crashes I was experiencing after just 10–15 minutes of flight time before the break. VRAM usage now hovers around 10 GB out of 12 GB when flying the 777, A321, A321NX, and A350 (with the Low Texture Pack), using High texture settings instead of Ultra. My setup: CPU: 9800X3D RAM: 64 GB GPU: RTX 5070 Resolution: 5120×1440 (roughly equivalent to 4K pixel count on a standard aspect ratio screen) As for stuttering, it seems to be related to the PSO (Pipeline State Object) compilation in DirectX 12—similar to what happens with Vulkan. I'm wondering whether shaders are being compiled in real time during gameplay or if they’re precompiled during the loading phase.

According Matt from Working Title, Vision Jet is make developed by several teams. Avionics side is Working Title is redonne all avionic system for 2024 But support is make by Microsoft (like for all MSFS content)not by asobo