haza2
-
Posts
548 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Downloads
Posts posted by haza2
-
-
12 hours ago, Hakatree said:
So after finally on second attempt to load the plane and prepare it for flight (first attempt the game just crashed right before taxiing). I started taxing and then oh oh, the nose tiller wasn't turning the plane. The tiller axis movement was being detected, but the plane wasn't turning. From external view the nose wheel was moving as well, but the plane kept on going. Jeezz today was not the day for flying this plane. This was working.. :(. Sorry for the bad video quality,, but you can see here what I mean.
Hello,
Go to the EFB and enable Rudder Controls Tiller, let us know if that works for you.
Kindest.
-
On 4/22/2025 at 7:34 PM, pijnackerpilot said:
Description: I have encountered persistent crashes in Microsoft Flight Simulator 2024 (MSFS 2024) while flying, with the application consistently failing and crashing due to issues with the WTF.dll module. The crashes occur intermittently during the flight, specifically either during the flight loading process or during the cruise phase of the flight. This issue started about a week ago after I installed version 1.0.8 of the inibuilds A350.
Additionally, I have encountered several bugs after recovering a flight via autosave, including:
-
Inability to activate ALT CRZ mode in the FMA.
-
During Open Descent or Climb, the aircraft busts through the set altitude and does not follow the altitude constraints, unless manual level off is used.
-
ALT CRZ mode remains blue in the FMA and does not engage properly.
Crash Details:
-
Faulting application: FlightSimulator2024.exe
-
Version: 1.3.23.0
-
Faulting module: WTF.dll
-
Exception code: 0x80000003 (breakpoint)
-
Fault offset: 0x00000000000023cb
-
Faulting process ID: 0x1050
-
Crash occurs during: Flight loading or cruise phase.
-
Log Entries:
-
First crash: Occurred at 16:48 UTC, with the WTF.dll error, while trying to load or during cruise.
-
Second crash: Another instance at approximately the same time, with the same error related to WTF.dll.
-
Steps Taken So Far:
-
Reinstalled GPU drivers: I updated my graphics drivers (NVIDIA drivers) to the latest version, but the issue persisted.
-
Checked for Mods: No new mods or add-ons were added recently to the community folder, and all add-ons were disabled to test the issue.
-
WTF.dll found at
C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\WTF.dll. -
Problem began: The issue began after installing version 1.0.8 of the inibuilds A350 addon.
-
Bugs after autosave recovery:
-
ALT CRZ mode in the FMA cannot be activated.
-
During Open Descent or Climb, the aircraft busts through the set altitude unless using manual level off.
-
ALT CRZ mode remains blue and does not engage properly.
-
Observations:
-
The crashes do not occur during landing or approach, but only during the flight load process or while cruising.
-
The issue seems to be related to the WTF.dll file, as indicated by the crash logs.
-
The application repeatedly crashes with the same error in WTF.dll, even after troubleshooting steps.
-
The FMA bugs (unable to activate ALT CRZ, altitude busts during open descent/climb, and ALT CRZ staying blue) only appear after recovering from an autosave.
System Information:
-
OS: Windows 11
-
GPU: RTX3080
-
MSFS Version: 2024 - 1.3.23.0
-
Driver version: Latest NVIDIA driver
Request: I am requesting assistance with troubleshooting or a possible fix for this issue. Has anyone else experienced similar issues with the WTF.dll file in MSFS 2024, particularly after installing version 1.0.8 of the inibuilds A350? Additionally, has anyone encountered the bugs related to ALT CRZ mode and autosave recovery? Any advice or solutions would be greatly appreciated.
Thank you very much for your detailed feedback, will send onto the team.
-
-
On 4/20/2025 at 6:30 PM, Kolo said:
What that ? Approach EDDH RWY ILS 23 but no ILS Indication. No LOC or GLS . Only green dot but no Autoland on ILS ?
MSFS2024 . No ILS descent . I`ll reinsatll the AC and the livery
( DLH). We´ll see .
Hello,
Was there a support topic you wished to raise?
Kindest.
-
2 hours ago, Starseed said:
My aircraft is now freezing after implementing the latest update 1.0.8 Even after clean install and deleting WASM file as recommended . Specifically when trying to input information into the FMC, then all buttons freeze in the cockpit.
Sorry to hear this, please could you follow this process for us to best help you. Kindest.
-
4 hours ago, こばと 笠森 said:
First time to have WASM crash on my plane. All screens and buttons are freeze after takeoff.
- Aircraft: A350-900 (v1.0.8)
- Simulator: FS2020
- Navdata Method: NAVIGRAPH
- OFP: attached below.
- WASM Error: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
- Specs: R5-3600X, 64GB DDR4, RTX3060 12GB
- Autosave File: attached below.
1745323111.bin 109.82 kB · 0 downloads RCKHRCTP_PDF_1745319674.pdf 569.35 kB · 0 downloads
Thank you for your report, it will be sent to the team
-
1 hour ago, Marcus1218 said:
i have been submit a inibuild A350 transfer order from microsoft store a long ago but they still not reply
Hello Leung tsz lam
Thank you for submitting a request to transfer - to the iniBuilds Store.Please allow 72 hours for these to be approved or rejected, if you fail to get a confirmation email notifying you of a successful request, you will receive a rejection email with the reasoning as to why the attempt was not successful.Kind regards,iniBuilds Team
this letter receive in 15 April they dont still reply already over 72 hours
i want to play new version of A350 Microsoft doesnt update it thx a logThank you, will raise with the team.
-
22 hours ago, unairspace said:
What aircraft do you fly? A320 family would honor the actual level and automatically change managed speed to 250 when passing FL100.
Yep your right, the A350 should go to 250 knots. Will send onto the team.
-
1
-
-
4 hours ago, danielsousvide said:
WASM crash, repeatable.
CYYZ - SPJC
Import flight from Simbrief
Choose any ILS 16 arrival SPJC.
FMC freeze, WASM crash.Thanks,
Daniel
Hello,
We would need some more detail please. I have attached the reporting structure. Thank you.
-
16 hours ago, Maickpapa16 said:
I'm really happy to say that you've solved my life hahaha thank you thank you and thank you! the problem is that shit Thrustmaster airbus throttle as you say, today after a month I'm finally able to take a long-haul flight from KJFK to EGCC and I wanted to try the A330-300 AA N270AY. after reading your answer I disconnected the Thrustmaster and connected the XBOX series X joystick to the PC and set two buttons to increase and decrease the throttle. and I can tell you that the problem is as you say in the Thrustmaster throttle. usually with the A330 family after 4 hours and 30 minutes of flight the catastrophic event of total shutdown of the systems arrived, and now I'm about to arrive in the EU with my big-bird American Airlines and after 5 hours and 10 minutes of flight I'm starting to extend the approach and it doesn't seem real to me... thank you thank you thank you. I will try to fly with the xbox controller also with the A350 in the next flight which is the plane with which I opened the topic but I am sure that it will be just a quiet flight and no test. thanks again friend, greetings from Italy
Excellent, thank you for letting us know.
-
15 hours ago, YonatanP said:
Actually no, I didn't remember I need to do that after every update.... can't the update installer delete the content of this WASM folder on its own?....
Anyway, yes - after clearing that folder, the engines started and I am now in mid-flight. The only thing still remains, is the way the aircraft shades in the airport look like. They are still blurry and flickering..... (see the last messages in my previous post that is now closed - "retard, retard"). Only with this aircraft.
I will report after landing, its a long one....
How did it go?
-
17 hours ago, FelixM said:
@haza2Here is the crash report if it helps. This is from a longhaul flight CTD after around4-5 hours. Unfortunately I dont have an autosave before that, because I was trying to get the autosave recovery working for a couple of hours and it has overridden the ones before the crash. (CTD only occurs with the INI A350 1.08, MSFS2024 SU1, no Beta)
11 hours ago, Prabin said:I had the same issue after 1.08. 4 hours into the flight, i tried to click on the map and it crashed.
Thank you for your feedback, I have sent this onto the team.
-
12 hours ago, Rainerb said:
Here are the Log from the Issue
- Aircraft: A350-1000
- Simulator: FS2024
- Navdata Method: NAVIGRAPH
- OFP: not loaded
- WASM Error: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty
- Specs: i7-13700k, 4080, 64
- Autosave File: no saved
Interesting thing. If you first press INIT, key over the MCDU. Then the MFD not freeze and you can work with the Aircraft. It happens only when you start directly over the MFD Monitor.
lg Rainer
Thank you
-
12 hours ago, AlexLacolle said:
Hello,
+1, i confirm. After multiple flights since Friday. No ANF activation after touchdown on MSFS 2024 SU2 beta with V1.08 builds.
The ANF auto-open behaviour is disabled by default currently per user request. There will be an EFB option to toggle this behavior per user preference in the next update.
-
9 hours ago, AlexLacolle said:
Hello,
+1, i confirm. After multiple flights since Friday. No ANF activation after touchdown on MSFS 2024 SU2 beta with V1.08 builds.
SU2 Beta is not officially support at this time.
-
31 minutes ago, LukeFF said:
The bumping sounds - they are noticeably absent on takeoff and landing.
While on the subject, the thrust reverser sounds also seem to be missing/much diminished.
Did you clear your WASM folder after the update?
-
29 minutes ago, unairspace said:
During descent, off profile, radar vectors.
Below FL100, managed speed remain 311 kt, have to pull out SPD and reduce to 250 or below manually.
Im just checking with a friend of mine who is a real world A350 pilot if this is correct or not. Because in my aircraft I fly it would be.
-
16 minutes ago, kosta said:
1.0.8 and still no changes on wheel animation? I can’t read absolutely anything in the changelog.
I simply cannot grasp why.
This has been stated before, sometimes 'easy' fixes are by no means easy and take time, the team is aware of issue and will be working on fixes but sometimes it takes time. Thank you for your patience and I hope your enjoying the A350 in the mean time. 👍
-
1
-
-
11 minutes ago, C. Schaffhausen said:
Added to OP
Thank you!
-
19 minutes ago, LukeFF said:
Compared to the latest version for 2020, there are almost no sounds coming from the nosewheel while taking off. In other words, the plane's landing gear is suspiciously quiet while taking off.
Hello! Do you mean the bumps or the retraction of the gear?
-
5 minutes ago, C. Schaffhausen said:
Sorry to hear that. So we can sort it, please could we have some more details.
Step 8. Please provide the following information
- Aircraft: A350-900 or -1000
- Simulator: FS2020 or 24
- Navdata Method: SIM DEFAULT or NAVIGRAPH
- OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes
- WASM Error: The error you copied in Step 4 above
- Specs: CPU, GPU and RAM of your system.
- Autosave File: Please include the latest ".bin" autosave file prior to your crash.
-
20 hours ago, mrjacques1 said:
Bonjour, je pilote l'A350 inibuild, et quand je vole avec des amis, je ne les vois pas sur mon radar. En revanche, je vois l'avion.
Existe-t-il une solution à ce problème ? Merci.
Please speak English, best to use Google translate. Thank you.
-
15 hours ago, Flying Grandpa said:
Hey,
whwn I select the A350 the planne texture inside as well as outside are resqared. How to fix that ? Thank you very much.
Regards Peter Timm
Hello,
Have you updated your liveries? Is this a 3rd party livery?
-
12 hours ago, Peter said:
Should we clear our WASM folder every time after an update?
Yes. Belt and braces. Did it work?
-
13 minutes ago, The_Pharoah said:
I flew a flight on Friday with no issues. Upgraded to 1.0.8 and thats when things went wrong. On launching into the jet, the A350 (both models) is autostarting and its in a loop of starting itself. My EFB has the default panel state in GPU and even when I try to enable any other panels, I get no change. The a/c just keeps starting itself and the starter (including the fuel buttons) are stuck in the on position. When I tried to turn off the APU the button keeps getting pressed (again like its stuck in an autostart loop).
This ONLY happened with the new patch. I've tried reinstalling the A350 multiple times, deleted the WASM folder, deleted the panel state folder (which allowed the a/c to load up normally but no panels - when I reinstall to get the panels, the above starts happening again), and even reinstalled MSFS2024...but it keeps happening.
What can I do to fix it?
Have you changed your key bindings at all? Will send back to the team also. Thank you for the feedback.
CTDs
in Other
Posted
We are aware that some user are experiencing this and investigating. If you have any details you could pass on we would be grateful. Thank you!