All Activity

Using the debug overlay, the runway surface is reporting: • Surface Type ML: ML_DIRT_AND_MUD • Type Meta: DIRT This appears on paved airport surface areas where dust effects should not be triggered. What I’m observing: • Dust FX appears on pavement • The runway visually looks correct • The sim debug surface readout indicates the ground is being treated as dirt/mud rather than a hard paved surface This suggests a possible surface classification, ground polygon, or terrain overlap issue in the airport package. Please investigate runway/taxiway surface definitions and any underlying terrain or apron/runway overlap at KDFW for MSFS 2024 compatibility. IMG_0506.webp IMG_DEA920C7-0AE4-413A-880D-28A3F5B0B808.webp IMG_F8F95ABA-5F72-4E4D-A491-1E3D26282115.webp

Saw the update, wanted to try it and then saw these immersion breaking bugs... keep freezing the A350 then

Additional services click that you can remove gpu

The VNAV and speed calculation are crazy. I am trying to land at CYVR 26L RNP AR (Tried other runways and other airports at different continental) As the picture shows, the auto-calculated path is 5000 feet higher than restriction and 5000 feet higher than the runway height. I checked all the pathway point limitations, and the information is all correct. Only the calculated height is far higher than the CSTR. And also for the incorrect speed, e.g., CSTR is 250 or below, but the calculated and actual flying speed is 350. Tried to clear SWAP, but there is no difference. This kind of problem appeared after 1.0.7 and has never been fixed.

Glad it's not just me. Title edited. After the 11 hour flight, descent phase and approach went without issue.

Hello I recently went to visit LAX and I own your LAX scenery so there are a couple things I could ask that you update. •Terminal 3 does not exist in your scenery and there are just remote stands where it should be. •Tom Bradley terminal interior does not match one in real life. •The LAX gateway pylons are not there anymore and the scenery shows them still there. Thank you.

I understand the people complaining about the RA callouts quality, that wasn't good either but once again the tonality is all wrong The inibuilds sound team have once again stripped the callouts from those videos online of all the alerts and stuff, and they are mostly incorrect. Boris has made that mistake before, would be nice if inibuilds ever has to gather more references (not from a simulator) and record the loudspeaker with the ambience A minor thing to complain about, but here we are.

Worst day ever - 4x flights - every single had the Xbox equivalent of CTD almost all an hour into fight. So annoying. This has never been so bad.

Same for me. Latest update.

This has been a problem on Xbox on 1.2.1 and 1.2.2 (we don’t have 1.2.3 yet). Interestingly, took off from Glasgow tonight and started from the gate - no problem after takeoff - NAV engaged successfully. Typically, I spawn straight onto the runway. I wonder if starting from gate, for some reason, makes a difference?

I just had the same Wasm crach after a fresh reinstall with new update... With GSX Pro, during boarding sequence, while using the OFP page of the EFB. Regards

This is exactly what just happened to me climbing out of WSSS on the TOMAN3A. The aircraft went into descent mode after setting climb thrust. Even had Cabin Ready pop up.

Can confirm. Same bug here. Only when you set the cruise altituted in the MCP will it go into clb mode, anything below it it stays in descend mode, for whatever reason. And this isn't a "minor" issue. It's a MAJOR bug. No it does not. When you reenter the cruise altituted again it just blanks the entry and you remain in DES mode.

Another thing I noticed now twice is that upon climbout the aircraft deletes the cruise flightlevel and goes into descend mode. As a result you end up in open climb and have a green dot with the number 99 at the top of the altitude band indicating the flightpath vector. This was on the TULNA8C SID out of VOBL. Later in the climb it returned to normal. Very odd.

I've got another one. Changing, while in setting up flight in LEMD, ATC gives me 36L while I was planning 32L. Changing from 32L to 36L did the crash

How often has it to be repeated? Cabins are not supported any more!

Hi team @iniBuilds I did a couple of test flights on the V1. 2.3. In the new update VNAV has some serious issue. About 25-50 miles or so before TOD on dialing the cdu alt to about 3000 feet, the TOD disappears from the ND as well as from the OFP on the FMS without pressing the ALT knob button(activating the Des). This is a serious VNAV issue requiring an immediate hotfix to make the plans fly able. Regards

Same here.

Same here. Did 2 flights on 1.2.3 and had this problem on one flight where after take off route line on ND becomes dashed instead of solid, and you have to manually Dct to next way point to turn it to solid. It's a bug in 1.2.3

v1.0.7 addressed a previous issue where both pilots were rendered outside the aircraft for the outside view (and the copilot was rendered outside from the inside view), which is a big improvement. Now when pressing the escape key to go make settings changes such adjusting traffic volume or turning on/off aircraft labels, the captain might be rendered outside of the aircraft in the outside view. However, if you change back to the inside view there are no pilots hovering outside the front of the aircraft If you press the escape key to go back to settings, the issue might resolve itself. You may need to escape to settings several times or wait some period of time for the captain to no longer show up in the outside view

I had this iisue before and the solution was to choose "No Cabin" and yes, I see the Cockpit again but I lose the cabin (so a workaround, not a solution). I recently totally reinstalled my A350 due to endless different stability issues and, for sure, it helped with stability, but this issue still exists. I tried to combine a British Airways cabin with a British Airways livery (highly logical) and again, no cockpit. Fresh reinstall, new WASM, aircraft rebuilt from scratch (a 15 minute wait was necessary for it to compile). Is this issue fixed or not yet ?

Must have happened within the last 2 updates... Not an error message that it's not available, simply a black screen. Resetting Navigraph access has not helped. Any ideas?

The same happened to me. For some reason, the plane forgot the cruise altitude after takeoff. If you set it again manually at INIT page, it remembers and you can engage the CLB mode by pushing the ALT knob.

Hi having the same problem. And this isn't a minor issue. As soon as I take-off the VNAV reverts to descent mode, it ignores any STAR restrictions. The only way I managed to get it back in climb mode was to set the cruise altitude in the autopilot. I don't understand how ini releases updates with such basic bugs. Its like they don't bother with a basic test flight before releasing an update?? See picture

Same here. Had to force an altitude change to get climb back.