All Activity

1.0.8 does appear to address the dsrtk issue, however TK and HDG still both display heading, and DA is still the difference between heading and DSRTK (again DA should be the difference between heading and track)

Just horrible, didn't have a problem before and now facing this after the latest update

Well, I play by default with MSFS's headphone mode disabled, so having the noise canceling option is good to have.

Attached is a video showing what I mean about the throttles. It seems like it wants to keep a certain airspeed and automatically adjusts the throttles even though I am not doing anything. (Sorry for the bitrate, I needed to compress down the video to fit) MicrosoftFlightSimulator20242026-07-0120-03-40-ezgif.com-video-compressor (1).mp4

Hello, Not sure if this is the best place to put this kind of suggestion but the flaps sounds on the a350 is way too low. It needs to be quite a bit louder.

Just purchased this as my very first Inibuilds aircraft and also haveing the small clickspot issue. I note it's a known issue from Asobo however my PMDG and FSlabs dont have this issue (for now)....just sayin. Ian

Hi, I just confirmed that the engines starting was sucessful after removed 3rd party livery. :-) Special thanks for pete_auau

H Jamil, Hi Jamil, Thanks for the update. Transferring our market place purchases to the Ini Manager is a good and very welcome move! Thanks for that. I'll try and be patient on the Tristar. On the 300 yes starting on the runway with the engines running works .. but that's no fun :( lol. Is there nyway to get a copy of the previous version? Before this last update at least with careful mouse/angle positioning I could trigger those overhead click spots :) Also anyway to twist your guys artist arms to get some glass and reflections over the faces of your round analog gauges in the Tristar and A300? Ive been on the flight decks of both quite a bit over the years .. and you definitely notice the glass over the round gauges as well as PFD, HSI, etc. Thanks again :)

Maybe I can be wrong but I saw on Instagram that the A300 got an update recently? I used the ini desktop app and the A300 keeps showing the latest as 2025, first is there a new version and also why I cannot update, I use it for my MSFS2024, I even reinstalled and same thing unless theres not really an update, I did a ticket but no answer now for 2 days, thanks!

Yup, I can run an entire flight at 8x with it and not a single issue. It's so frustrating they won't just add 8x to the OIS as an option with correct fuel burn and time elapsed. For anyone on PC, give this a try JP Jump Ahead – A tool to skip long cruise segments as an alternative to simrate acceleration. - Utilities for MSFS | Flightsim.to. It provides you with simrate controls and has a "sync to simbrief" feature for auto-adjusting the fuel. So you can use the buttons to go to 8x and then when you slow back down to 1x it syncs the fuel level to simbrief. Saves manual tinkering. Also works with the A340, A300 and some other aircraft that don't natively support 8x.

Then it is a controller binding issue, most likely a double assignment with another control device.

As mentioned, this was just a quick test to capture the intermittent bug without wasting time on a full flight setup. the Airbus flybywire system handles basic stabilization (Normal Law) completely independently of the MCDU. Even with an empty flight plan, the aircraft is supposed to maintain its bank angle when the stick is centered. it should never violently move the control surfaces on its own. The video clearly shows the flight control computer generating an uncommanded roll signal regardless of navigation data.

After going through all the steps I listed above (full reinstall, cleared WASM cache, rolling cache rebuild, empty Community folder test, driver updates, etc.) and additionally removing all liveries, I was finally able to complete a full flight with no WASM crash.

I would suggest configuring the MCDU and flight plan properly and test it again. Your Cockpit setup is quite weird.

Let us know if the issue pops back up :)

Hello, For those encountering this issue, can you test the A300 Isolated as the only Addon in the Community folder, we want to see if it's occurring due to 3rd Party as I am not able to reproduce this nor 2 other team members. Thank you.

I was expecting the N1 cruise values to be corrected in v.08 but alas no. I did open a support ticket regarding this matter - is the team still looking in to this? There is absolutely NO WAY this plane cruises with an N1 value of only 75%. I have seen photos and a video where the N1 value is around 84 - 86%. I sincerely trust this matter is still being looked into.

Try again in 1.0.8 update and let us know please. Usage of Greater Circle distances is one of the updated items.

Hi, so I just got MPTO. Awesome scenery! The only thing I found missing, is the Parkingposition 204W for Terminal 2. Since it's the one used for example the KLM Triple-7 I'd love to see it implemented. Since the ground Marking is already there... Unfortunately I can,t select it so it must be missing in the BGL of the Scenery. Thank you :) Kind regards Jota

I suggest double-checking your FMS setup and keeping your software up to date, as updates can sometimes resolve such issues. On another note, I've recently got into introductory flying lessons near me, which turned out to be a fantastic way to understand flight systems firsthand. It made me appreciate the complexity and precision of these systems even more.

the INS dsrtk does not follow the great circle path and instead stays on the initial track calculated at the from waypoint (this may or may not be the same problem as AP in INS is offset in 1.0.7 - Systems - iniBuilds Forum) the aircraft is flying between NZCH (43°29.4‘S 172°32.1E) and AN07/AT07 (69°26.2S 076°19.0E), these are the only 2 waypoints loaded in the INS, a 3121nmi leg. DSRTK stays at 207.9 the entire way, which also shows on the HSI the aircraft also deviates from the track continuously, maybe if DSRTK is fixed this problem will go away on its own as i'm guessing the INS uses DSRTK as a reference and adds corrections (may or may not be limited to 45°, aircraft may eventually fly a straight heading given long enough leg) on top of it based on crosstrack deviation track on TK/GS and heading on HDG/DA is the same number (this should only be the case when below 75kt groundspeed) drift angle seems to be the difference between heading and DSRTK, it should be the difference between heading and track and a question on the displayed XTK, the manual says the LTN72 displays the XTK offset set by the crew, are you guys sure that's true? because on CIVA units it displays crosstrack distance to current leg (outputs to HSI deviation)

the TriStar has rapidly become one my favourites in the sim. However, the one thing that really irritates me is when I rotate at my Vr speed, almost nothing happens. I need FULL back pressure and then the nose will rapidly rise. It will only rotate once it’s beyond its calculated takeoff speed. I can’t get that smooth 3 degrees per second. my weights and speeds are set and accurate so I am not trying to rotate too early. My thrust is set accordingly, and flaps are where they’re supposed to be. Spoilers are not up either. once in the air, it’s very nice to hand fly. same applies for landing. Once the mains touch down, tying to keep the nose up for a smooth touchdown on the nose is a full back pressure process and even then, it slams it down. Even without auto brakes.

Second this. I don't care about the printer and don't pay much attention to it. Noise cancelling also doesn't really cancel about much, alot of things are still audible just slightly muffled, I don't know if the approach to it was similar as the a350 but things are still audible.

Yeah I've noticed this to. Yesterday I loaded up an autosave from Johannesburg to Perth and the LNAV was always 0.1R with minimal wind that would cause that. And it was wonky with some turns as well, The plane also oscillated with 4x time acceleration left right, down up so on so forth. However it was working perfectly fine before I went to bed and loaded the autosave the following day. I don't know if the performance degrades after loading an autosave but it was a factor.

I don't know what it was, but this issue has finally been resolved, as the correct version is now showing up in the app. 👍