All Activity

Its not to late for me😁 T.O performence calculated at simbreef, OIS and via INIT page in the fmc, and 3 difrent results. OIS: V1: 131 VR: 140 V2: 147 FLEX: 57 FLAPS: 2 INIT PAGE: V1: 135 VR: 138 V2: 146 FLEX: 47 FLAPS: 1 SIMBREEF: V1: 135 VR: 141 V2: 147 FLEX: 52 FLAPS: 2 Airport: VTSP RW:27 TEMP: 25 WIND: 290/08 QNH: 1011 Takeoff Weight: 229.2 TONS OIS still give the higest FLEX temp, but the difrens from my findengs at HAAB some days ago are alott smaller now than that time i did the HAAB_OMDB flight. But we must have in mind that this product have got 1 main update and 1 hot fix in the mean time. I have no clue if the team have hade time to look at the problem at all before wee go this updates. I did some tast at ENGM after my flight from HAAB, and that test allso give me 2 totaly difrent results. Tonights test show results with only smal variation in the T.O Perf.

Here I am following a STAR to EDDL 23L. Every single WPT has 220 kt constraint, yet the aircraft doesn't care and places its managed target at 250. Before I got down to FL100, it was even faster than 250. I have noticed things like this happening when changing approaches or arrivals in the flight plan while enroute. It gets corrupted somehow, like old route data is left, and the aircraft ignores both the lateral and vertical profiles, ignores altitude and speed constraints, and so on.

I have the latest update installed. When I load up the flight I can neither walk around or enter the aircraft. Anyone else have this issue? Thanks!

I think this may have been fixed in today's hotfix. A changelog would be great actually!

Were you in CLB or DCLB? There's a bug that switches to CLB from DCLB (https://forum.inibuilds.com/topic/41853-127-aircraft-switches-from-dclb-to-clb/)

Hi，i always use the straight line，I also consulted real-life pilots for verification, and the control feel in version 1.26 is also fine.🙂

Lovely with your reply and team's work. Send my regards to them. Cheers!!

I just meant if there is any discrepancy between V1/VR/V2 from TO from the APP (OIS), or if the T.O. PERF gets the same values if you fill the ZFW and so on. :-) Trying to find the core of the issue :-) I mean now it's obviously late for that, but next time please just try to compute from INIT page where you can put ZFW and block fuel, you can compute the fuel there by "T.O. CPNY" or something like that, it leads you to a menu, where you fill up all values and hit compute and it just computes the values for you. If you could compare the values from this and from the OIS computed and from the Simbrief from Takeoff Performance tab :-)

Can't wait! 💓

I had a flight from EGLL to KATL on the A350 v1.27. The flight plan called for 2 step climbs. Both time the aircraft behaved like it was taking off as opposed to a gentle climb. Also the speed dropped significantly and took a while to come back up.

215Tons are 215tons at any airlines in the world. I get my ZFW from Viturale Emirates and the pax numbers to. I putt in paxnumbers and ZTW into simbreef when i create the flightplan. Company T O Perf. referare to the standar weight on bags and pax. If my weight on pax in simbreef is wrong, and i have given simbreef the ZFW and pax numbers, will the weight on bags and cargo be adjusted to mach my given ZFW. So in this case have that nothing to say.

Hi Kyle 🙂 thank you for replying to the post it was my first time trying to do my first flight and the first time it happened. Would you know some of the common reason why this has happened to me . :)

When I was intercepting the F-G/S, the aircraft pitched down a massive amount and I was fully configured and stabilized right before the FAF, and the aircraft pitched down to like -5° AOA. It overspeed and then at some point it pitched back up to a norm lol pitch to follow the glide.

Thanks Kyle! You're doing a really great job here. The fact that ini has someone at these forums always ready to test stuff and answer questions is a big reason why I keep buying your stuff. And despite my only posts here recently being bug reports, I think 1.2.7 made some really big improvements overall. Performance is overall much better for me, the screens feel so much better to interact with (I didn't see it mentioned in the patch notes, but it's clear you changed the whole interface) and I'm super excited for v2.

Ejets: https://youtu.be/thRBoggrqKA?si=25n4RXsVkeBnJ-Q3&t=419 Couldn't find any airbus ND footage during the approach.

It shows the runway graphically, but does not connect the approach to it. Otherwise, the aircraft would turn into the wrong direction when initiating a missed approach at MDA in IMC. https://youtu.be/rugPvAqiKzs?si=hUCZJO7Do_QugG06&t=1737

At RJTT, RJTT22 is not part of the LDAX22 Approach (1:28)

Hi Kyle, Another update from my end: I took the ultimate step and did a complete, clean uninstall and reinstall of MSFS 2024 from scratch. To ensure zero third-party interference, I installed ONLY the default iniBuilds A340-300 on the default house livery (no other add-ons, scripts, or sceneries added to the sim). Unfortunately, the problem STILL persists on the A340, while my A350 continues to import SimBrief plans flawlessly under the exact same environment. Here is the exact behavior on this 100% clean setup: 1. The EFB successfully connects and downloads the SimBrief OFP. 2. The payload files simbrief.json and the .fpl route file) ARE successfully written to the local WASM work/ directory. 3. However, pressing INIT REQUEST on the MCDU immediately returns "ERROR DOWNLOADING DATA" or fails to populate the route. Since the files actually generate in the aircraft's WASM work folder, the EFB-to-API communication is working, but the A340's WASM FMGC gauge is failing to ingest or parse the local .fpl payload into the active session. Since this issue survives a full MSFS 2024 reinstall on a stock setup (and is isolated strictly to the A340 FMGC module vs the A350), could the team look specifically into the WASM route ingestion/parsing logic or file handle/permissions within the A340 gauge code? Let me know if there are any specific WASM log files or debug traces I can grab for you. Thanks again for your help!

Same here.

It refers to having selected ‘none’ as player character in the identity options ui, with the intention of removing the first Officer when in cockpit view.

I can't seem to get the terrain working. It's running but not showing, and there's an error. Log attached. toolbox.log

Already did it, nothing working. But the cabin is working in the A350-1000 version ; with flight attendant panel not working

Hi all, i am not longer hearing the flaps sounds in the cockpit after the latest update. Did something change here? Sincerely, Felipe

When flying SIDs, it is very common to have instructions of the kind "Takeoff runway 28L: climb heading 284 to 520 [feet], then..." For instance, the TRUKN2 departure out of SFO runway 28L and 28R (https://resources.globalair.com/dtpp/globalair_00375trukn.pdf). When loading into the FMS, this shows up properly as an ARINC 424 CA or VA segment (with a white "520" as the waypoint). I've purchased the ini A380 (1.0.5) and ini A350 (1.2.6). Neither of these auto-sequence these legs - when you takeoff, the FD guidance just indicates you should fly heading 284 forever. I have to manually find the next waypoint and use direct-to functionality to sequence past the altitude segment. Is this expected - is there some quirk of the FMS on the A380 / A350 that works like this? Otherwise it breaks immersion for me every time. The Fenix A320, PMDG 737 and 777, and the Toliss A320 and Flightfactor 777 on X-Plane all automatically auto-sequence these segments. Once you've climbed to 520 feet (as in SFO TRUKN2), it automatically advances to the next segment. The ini planes do not. Is this a known bug? It is super irritating that all the other systems are modeled reasonably well but this basic behavior on so many instrument departures doesn't work properly.

Just updated to the latest build and I noticed the option for the dropdown in the CDU to select say intentions,etc for the connect to datalink is no longer there. I am able to connect, get atis info, but when I try and request departure clearance, it doesn't seem to be communicating. I have tried resetting my say intentions api key as well