MPO910
-
Posts
63 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by MPO910
-
-
100%agree on OP
-
Yes. Me. Today with 1.0.9
Entering star in fms for vhhh 07c I saw my fps going from 78 to 52!
Changing the star did not recover my fps.
Same at HKJK 06 star....also tanked FPS.
Not the case when enting star at nzaa.
Something is wrong with the A350 Star entering seems calculations heavy on CPU.
Msfs 2024 su2 beta
-
Yes. 1.0.6 indeed
-
Yes. I have written this issue AND my thoughts about this half baked releases of features at their discord extensively.
They ask me not to post such things....as it does not help the others with their issues.....
The problem is not my post.....the problem is the way they have decided to roll out unfinished tested products....
-
1
-
-
7 hours ago, SkyKing33 said:
That's not the problem... the problem is I am getting 10 choppy/slideshow frames when landing. Nothing to do with the hardware of the flightstick I am using and everything to do with performance from either Asobo SU2 Beta, iniBuilds a350 1.06 or a combination of both which have to be causing a VRAM leak.
Yes ...1.0.6 has the worst performance at my end with 4090rtx and 9900x3d and 64gb 6000MhZ RAM.
The performance loss compared to 1.0.5 in flight is roughly 25% and over long haul even 50%....
No issues with my tested Fenix at MSFS 2024 su1
-
On 3/25/2025 at 9:11 PM, Samir-1997 said:
Thing is I am not experiencing this with any airplane but the ini a350. If something like FSLTL is causing it this means the a350 is not compatible with some addons and this needs to be fixed.
Exactly what I see too. But i also CtD at climb and approach as well....but mostly mod flight between 3 and 4 hours
Only when using the combination of a350 and fsltl models, regardless the injection method.
Only using a350 without fsltl....no issues....pmdg with fsltl no issues.
Combo a350 and fsltl....CtD every single flight.
I have done 6 flights long haul only a350....no ctd....and 4 pmdg with fsltl long haul....also no issues....
It seems the combination and therefor i assume its a350 issue (TA RA, xpndr....TRaffic ID ad ND?.....as we had with 1.0.3?
-
1 hour ago, Simon Stühlinger said:
check it with arround 90 in cruis.... i think there come no ctd back
Why should I set it so low at a system which is capable of 70 FPS in VR or 90 without VR and 25% cpu utility and lax 60% GPU utilisation?
I have 0.1% low framerates....and 99,9% low framtimes....so a stutter free system
-
75 ground and 150 crz
-
I noticed with 1.0.6 extrem fps lag directly at and short after (1 - 2 seconds) switching views especially from cockpit to cabin or cockpit to external....
The fps losses for those 1 - 2 seconds more then 60 to 70 percent and then recovers
-
Yes. I noticed worse performance with 106 compared to 105 as welll with 9900x3d and 4090 rtx and 64gb RAM.
20% loss of performance
-
3 hours ago, Swisspilot1986 said:
Could you recover your flight entirely with the new feature Autosave?
Partly ..... Bur the issues make this function unusable. .fuel on Arrival isnnot correct....way to high...(44t instead of 9.2 as before the CTD) and CRZ altitude is not recognized by the autopilot anymore... plane ignored the set altitude on the FCU and FMC...it climbs through that set value or descents through it.....doesn't matter. All the time.....so OPENCLB OPENDSC and Managed climb and descent are unusable After a flight with auto save is restored.
Also stored or pinned maps didn't work, radio volume controls not restored as well ....fuel weights (alternate, reserve) not correct ...
-
Used FSLTL and Traffic was shown in PFD.
Repeatable CTD same failure code as below, mostly between 30Min and 4 hours in flight ONLY when using FSLTL
RTX4090
9900X3D
64GB RAM 6000MhZ
No OC
FSLTL with PMDG has no issues at any flight, A350 without FLSTL also no ctd. But in Combination CTD. Like with 1.0.0, 1.0.2 as solved since 1.0.3, 1.0.4 and CTD came back with 1.0.5 and still present with 1.0.6
It happened while I clicked in the enroute map of IOS (maybe that was coincidence)
Faulting application name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 32.0.15.6636, time stamp: 0x674f613e
Exception code: 0xc0000005
Fault offset: 0x0000000000108ba7
Faulting process id: 0x5088
Faulting application start time: 0x1DBA0A7BA73B5A4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_9425e4c3b1ac1c47\nvwgf2umx.dll
Report Id: 036cc186-4216-4a49-927a-f7161dd323b5
Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App -
I see this as well at my end. It did work if I recall correctly with 1.0.5
-
Where does AUTOSAVE stores the DATA?
IN which directory?
How can I delete the stored DATA if I want to clean up?
Why do Radio Buttons and Volumeknobs do not get stored as well?
Why do Battery Knobs (ON/OFF) not get stored?
Why does APU BLEED not get stored?
How can I delete a AUTOSAVE Profile I have created myself?
How can I set a Created Profile as my preferred startup Profile or is this not implemented atm?
Why does OPENCLB and OPENDES not respect my set Altitude AFTER I restored I flight which was saved with AUTOSAVE? The plane does not respect my altitude anymore after restoring...It climbs or descends through the set limits.
Hopefully someone is able to clarify.
Thanks in Advance -
I'm having lots of CtD . The third time when exactly clicking on a pinned Navigraph Chart (2x ILS31L OMAA) after at least 1 hour and mostly after 2,5 - 4 hours into a flight.
Version 1.0.5 is installed clean (WASM deleted and I did uninstall the prior version and installed the new version)
MSFS2024 is a clean install after the phantom MSFS update.
Cleared my shaders, and uses the Nvidia driver 572.83 and also prio 572.42 and 572.16 where tested, no luck
I think the navigraph integration has a bug. After roughly 1,5 hours into flight I see Frametimes quickly spiking (jittering) and my view gets laggy as well in VR, this resolves when zooming in and out different navigraph enroute MAPS, leaving the Charts page, when doing this a while (10 - 15x) the spikes suddenly disappear and everything smooth again.
The times CTD occured, I hat stable 45 capped FPS, my VRAM was at 9.9 GB with my RTX 4090 and 9900X3D. My Frametimes where at below 8.5MS, I have no 1% lows at my system when all runs fine.
MSFS2024 Version 1.3.23.0
Faulty module is coherentuigt.dll. version 2.9.5.0
Exception code 0xc0000005
Fault offset 0x000000000007877c
Repeatable for 3 times now.
Could you have a look into this?
No OC on my CPU at those CTD. After flyiong with FENIX no issues at all. Same A350 issue present in MSFS2020 and also no issues with PMDG777 in MSFS2020
AsoboReport-Crash-1850072491.txt AsoboReport-Crash-3061117772.txt
-
1
-
-
I'm having lots of CtD too. The third time when exactly clicking on pinned Navigraph Chart after 2,5 hours into a flight.
Version 1.0.5 is installed clean (WASM deleted and I did uninstall the prior version and installed the new version)
MSFS2024 is a clean install after the phantom MSFS update.
Cleared my shaders, and uses the Nvridia driver 572.83 and also prio 572.42 and 572.16.
I think the navigraph integration has a bug. After roughly 1,5 hours into flight I see Frametimes quickly spiking (jittering) and my view gets laggy as well in VR.
The times CTD occured, I hat stable 45 capped FPS, my VRAM was at 9.9 GB with my RTX 4090 and 9900X3D. My Frametimes where at below 8.5MS
MSFS2024 Version 1.3.23.0
Faulty module is coherentuigt.dll. version 2.9.5.0
Exception code 0xc0000005
Fault offset 0x000000000007877c
Repeatable for 3 times now.
Could you have a look into this?
No OC on my CPU at those CTD. After flyiong with FENIX no issues at all. Same A350 issue present in MSFS2020 and also no issues with PMDG777 in MSFS2020
-
1 hour ago, Samir-1997 said:
Not exactly, I use Beyond ATC which uses FSLTL models. But essentially, I am not using FSLTL injector.
I had issues with FSLTL Models....it's not the injector but probably the models.
-
6 hours ago, Samir-1997 said:
I do have the latest update 1.0.5 and it’s a full CTD mid flight not a freeze. And yeah my system is powerful I never had issues with flight sim before. It’s only the a350 that’s doing this for me. I don’t even have over clocking in case anyone wondering
Do you use FSLTL? If yes, try a flight without to rule out that it maybe the cause
-
11 hours ago, haza2 said:
I am wondering if that is more of a sim issue tbh.
I need more time to test long haul.
Today I managed 7 hours without CtD. I left FSLTL off after I reinstalled it after a faulty update process in FSLTL FBW App.
I report tomorrow after my next long haul.
-
58 minutes ago, haza2 said:
I am sorry to hear this, are these CTD or freezes to the systems?
Not in my case. complete CTD.
-
58 minutes ago, haza2 said:
What about when you update to v1.05?
I did. The issues persists since 1.0.4 but I have also encountered it in 1.0.5
-
Indeed at my end too since 1.0.4. After beteren 3 to 4 hours into every flight msfs2024 and msfs 2020 CtD. Only with a350. With 320 and 777 no issues.
-
Yes. Also noticed this with 1.0.4. The taxi rolling sound disappeared when switching to external view while taxiing. Switching back the sound is gone.
-
On 3/15/2025 at 3:36 PM, Nace42 said:
more context, this is what it looks like in the white inibuilds livery on a fresh wasm clear, and reinstall. it seems initially it loads in fine, and then for whatever reason it changes over to the borked version
late edit: saw this was logged on the ini discord. is related to zoom levels in the camera settingIs this with Framegen on? You could try (just to test) if this is also the case with FrameGen off. Just interesting to see if this is also the case then
My 2 cents...
in Systems
Posted
I ✅ agree on the OP.
BUG fixing and performance gains should be top priority...
There a too many complains and most of them are common at many users