
Him
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Him
-
-
7 hours ago, Him said:
Hi inibuilds developer,
Here is the case for CTD due to WTF.dll (really wtf...), hope can locate and describe the root cause asap
Flight: RKSI-VHHH
Nearest airport when CTD: RCTP
Sim Time from launching MSFS2024 application to CTD: around 2 hours
Navdata: Navigraph
I have tried to delete all folders related to a350 in both community and WASM folder, also disabled realtek audio in device manager as advised by some users encountered WTF.dll error. I can successfully have a VHHH-RKSI full flight without any CTD yesterday (also using navigraph nav data). But the CTD happened today again.
For time being, is it a workaround that delete all folders related to a350 in both community and WASM folder before starting every full flight to prevent such CTD error?
Thanks.
Sadly, I can confirm NOTHING help for delete all folders related to a350 in both community and WASM folder before starting every single flight.
Just CTD again during climb to near TOD for a VHHH-WSSS flight...
-
Hi inibuilds developer,
Here is the case for CTD due to WTF.dll (really wtf...), hope can locate and describe the root cause asap
Flight: RKSI-VHHH
Nearest airport when CTD: RCTP
Sim Time from launching MSFS2024 application to CTD: around 2 hours
Navdata: Navigraph
I have tried to delete all folders related to a350 in both community and WASM folder, also disabled realtek audio in device manager as advised by some users encountered WTF.dll error. I can successfully have a VHHH-RKSI full flight without any CTD yesterday (also using navigraph nav data). But the CTD happened today again.
For time being, is it a workaround that delete all folders related to a350 in both community and WASM folder before starting every full flight to prevent such CTD error?
Thanks.
Bug Report: MSFS 2024 Crashes Related to WTF.dll & FMA Issues
in Systems
Posted
For those who faced WTF.dll error, can try not to click the navigraph chart or enroute section in the OIS (can still use navigraph data in 3rd party section) in the whole flight. I have tried multiple flights (using v1.0.8, flight time around 2-3 hours) by doing this seems didn't CTD again. Not sure if it is related.