All Activity

There seems to be an uneven splash of the strobe lights. The right wing splashes the light onto the fuselage brightly with multiple flashes whereas the left hand does not. The splash from the right wing on to the fuselage looks unnatural also. I have had this effect consistantly on multiple flights.

Don't know why but every update is one step forward and 2 steps back. How come something worming normal in one build and breaks in the new update. This is quite annoying. @iniBuilds need to look into to it deeply. It's been more than an year wirh 24 updates and many bugs still exist or appear with new updates.. It's a good airplane, please keep it good. Regards

I ran into a similar mismanagement 🙂 You need to manage the fuel load so that tanks 1, 3 and 2L/R are equal. If there is a greater fuel load than tank 2L/R capacity, then you need to turn off 2L/R and feed ENG 2 from 1 and 3 (including using 1A and 3A accordingly to feed tanks 1 and 3) untill the fuel load of 1 and 3 is equal to 2L/R, then you can feed from all at once. Cycling the crossfeed valves before turning off any fuel pumps is a good idea to make sure that they are definatley open. Essensially if everything is right and you have a low fuel situation in 2L/R, then you should also be low fuel in 1 and 3.. which sounds like an emergency. See the manual reference below. Check out page 76 https://forum.inibuilds.com/applications/core/interface/file/attachment.php?id=25570&key=7bd0b1032193c7941af5a613dac51bf6

I have a similar issue with the trim speed - During climb or just after takeoff using either VNAV or IAS, the aircraft will shoot straight past the targeted speed... I also have instances where the aircraft will miss the ALTSEL then slowly trim to recapture - only to miss the ALTSEL again and porpoise around the ALTSEL (+/- 1000ft!). The times where the aircraft really does this is when there is a higher rate of VS when approaching the ALTSEL generally due to the aircraft high performance, which can be most departure climbs where a level off may be required for a SID. In general though, if the rate of VS is calm approaching the ALTSEL the aircraft captures the ALT pretty well... so at the moment a more manual approach is needed to attack the issue rather than allowing the AP to handle vertical navigation when approaching ATLSEL with a high rate of VS whilst the trim speed is slow... but then again that might just be the normal to manage that type of scenario with the older aircraft. Was messing around with the AP yesterday trying a bunch of departures and ILS approaches (and other wild manouvres) - definatley needs fine tuning in some areas, but I can see in other posts that they seem to be working on these sorts of things in future updates 🙂

Indefinitely delayed per their Discord.

This would be nice -- especially if you could select the acceleration height for thrust reduction so as to respect different operators procedures

Seconding this

I would like the PFB and the speed card on the panel to have their emissive lighting (or whatever the proper terminology is) to be removed -- optionally! -- so that they're only lit by cockpit lighting as real paper charts would be. Even with the brightness lowered, backlit paper is always going to look weird in my view.

+1

Flying the L1011 in the climb, with the autopilot in VNAV mode and holding 320 knots indicated, the transition to Mach happens too early - the AP switches to a target of Mach 0.82 at around 25,000ft, when the indicated Mach is still 0.75 or so, which causes the plane to speed up and come very close to exceeding the "never-exceed" airspeed in trying to capture the Mach target. Had this happen twice now, and I've double-checked that everything seems to be configured correctly in the PMS. The correct behavior should be that the AP holds 320 knots until the indicated Mach is 0.82, then transitions to Mach at that point and maintains 0.82 until reaching cruise altitude. On a semi-related note, the autopilot seems to change the stabilizer trim far too slowly, causing the plane to overshoot speed targets in the climb. I know this is a vintage plane, but I'd think it should still be able to capture and hold a target speed far better than it does.

Just going to bump this in the hope that the iniBuilds team sees it... Probably should've posted in the Support section instead, but it's a bit late to change that now.

Ok so, how do I fix this? Is it an msfs issue or is this my graphics card being a piece of junk?

Hi. I feel the wing flex a tad to much on takeoff, possible to get that tuner a bit?

Typical framegen issue. Nothing to do with the plane/model

WASM Crash Report – iniBuilds A350 (FS2024) I encountered a WASM crash after vacating runway 25 at EDDS following a diversion caused by a dual engine shutdown. Flight Details: Route: LFPG 26R BUBLI6A BUBLI DCT LUVAL DCT MIRGU DCT BEGAR DCT TRA DCT GAMSA DCT UMVEG DCT DIMLO/N0485F350 DCT INVED DCT DINRO DCT UDROS UM859 KARDE UN644 ROLIN DCT TETRO DCT BARAD M747 SUBUT T916 LEYLA/N0499F370 N161 GASBI/K0919F370 N161 SARIN/K0889S1130 A368 SALMO/K0885S1190 A368 FKG W188 LIKMI W270 DKO W69 HUR B339 LADIX W34 VAPGU W100 ORAVA W201 UNSEK A326 SANKO/K0906S1250 A326 DONVO G597 AGAVO/N0487F410 Y644 EGOBA G597 LANAT Y71 XAC XACL RJTT16L Aircraft: iniBuilds A350-900 v1.2.4 (with cabin) Simulator: FS2024 Navdata: Navigraph Issue Description: A dual engine shutdown occurred unexpectedly between LUVAL and BEGAR. I initiated a diversion to EDDS via REUTL5A arrival for runway 25. After landing, I disconnected the autothrottle at approximately 50 knots to vacate the runway via taxiway I. The WASM crash occurred during runway vacating. Error Message: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty WASM: Error during MFD_gauge_update execution. Error code: 0xc0000005 System Specs: Ryzen 7 9800X3D, RTX 5070 Ti, 64GB RAM 1775397464.bin

The Compressor “disks” look terrible under power…almost as though they are not exactly “centered”. Will this be addressed in the next update?

There is no logic to understand. Their desire to combat piracy against the 8% of pricks that do that sort of thing, is stronger than their need to provide the 92% who actually purchased the damn thing with a platform that actually works and is reliable in Updating and Improving the product.. it’s stupid, yet here we are 🤷‍♂️. I do believe eventually it will come to the inibuilds manager…at least one can hope.

Bonjour comment se fait-il que l'A350 n'affiche que le plancher cabine et quelques détails que ce soit dans le hangar ou sur l'AD? En vue cockpit rien en répond. tous les boutons s'allume en meme temps. Ou est l'Erreur? Voici quelques capture d'écran. Merci de votre retour Cdt GB

I'm really hoping for a freighter.

I sure hope so too! The Tristar is by far my favorite aircraft of all time!

I personally would love to see and hear the engines windmill and “clack” as the blades shift, especially during a walkaround. ☺️

Issue is logged, locked the thread so that the topic doesn't go off-topic regarding clearing MSGs

I'll log this for the team, thank you for including the comparison images 🙂

Hi, sorry for the delay. Were you able to remedy the issue or is it still occurring, if you are unable to path in the settings section, something might have corrupted during the Manager Download and Installation. Try logging out and then back in to see if that refreshes the manager, and if that doesn't work. A full reinstall. Let me know if either of those help. Thank you

Trying to download this livery, I seem to get the sand coloured zd951 instead. Tried everything Google has suggested but still not able to get the White version. Any help please.