All Activity

I've completed 2 flights now in the L-1011 and I find the tint still needs to be toned down.

The barber pole on the FO airspeed indicator seems to always show about 10 knots lower than the airspeed indicator on the CPT side.

Somehow I can’t stop the APU. Tried several things but the damn thing keeps on running. Assistance is all off. My guess is that I missed something. Help is appreciated

Hello ini-team! Let me start by saying congratulations on a very successful release of the beautiful Tristar! One suggestion if I may suggest is an option to have the FE manage throttles during takeoff and when reducing to climb thrust. Unless there is a way that I am simply not aware of?

Thank you for replying to my list of systems inaccuracies here. If I come across any more, I'll list them here. I'd be happy to help if you need any further assistance with the systems I've flagged. Kind regards, Joshua757

Hello ini, hello readership, i just bought the inibuilds A350 on this sunday and do report an WASM crash as following. Flight: LEPA to KJFK. During the flight navigraph informed me, that the arrivalrunway ist not used. It was prior 22R and now 22L. I clicked on "KJFK" in the FMC and clicked on "runway" and selected RW22L. After this selection i initially wondered, that Approach, VIA and STAR are already preselected from the prior RW22R. Therefore i did not entered any Approach, VIA or STAR as it was already preselected and confirmed my input in the FMC. Nevertheless the approachselection was "greyed" and not selectable, only the STAR. After this i checked the flightplan via the PLAN MODE. There i could identify a MANUAL, which i deleted and also a following discontinuity, which i also deleted. After checking the flightplan i recognized that the STAR leads directly to the "new" RW22L without any approach. I clicked on "KJFK" again and repeated the procedure: selected RW22L. And after selection of RW22L i was able to change/confirm the approach as it was not greyed out anymore. I selected ILS22L and then PARCH4 for the STAR. After selection of the STAR i got a WASM and all Screens went to "orange WASM fault color". Kind regards Stefan Blei

Hi, I've purchased the L-1011, but cannot find liveries on the inimanager. When I go to liveries, all I see is the A300 options from when I purchased that. Please advise. Thanks

I have to agree with these posts. This is by far the worst performing plane in the sim for me due to the VRAM usage. I had 7 fps on landing rollout at ORBX ESSA in the Tristar. With all other aircraft in the sim I'd have at least 30. This is on a 3060 Ti with 8GB VRAM and all settings on low or medium

Hello Inibuild, Will the TriStar be available for direct purchase other than MS Marketplace? Thank you, Ed

Had the same problem, looks like the "100" nm doesn't move on the copilot's side.

Yes, an option to enable or disable the tint effect would be nice. What I especially do not like is the blue hue the tint adds to the outside world, although this might have been realistic for the Tristar. Apart from that I like the Tristar very much. I think it is a great product from what I have seen from my little flying so far. Thank you iniuilds!

I think the OP and the others (incl. myself) meant the tint effect when you look through the windows at the outside world is too strong. I do not think that the tinted windows have any effect on the brightness within the cockpit.

12-13 GB is also too much for people with 12GB cards. I even use AutoFPS to tweak my TLOD and OLOD during flight. I have no problems with other Addon Aicraft, like PMDG, FSLabs; Toliss, TFDi or the 3 Inibuild Airbusses (A300, A340 and A350) So please if You use 8K textures, make a Lite version with 4K.

Hey, Thanks for your suggestion. As the sim does not have support for this natively, it is quite an extensive undertaking that is beyond the original scope of this product line. I won't promise to you that this is something we are going to do, however I understand the interest and take note of the suggestion for future development of this product line. Thanks!

Thanks for your suggestion. Will pass it along to the team for consideration.

INS Only config with drift, waypoints loaded from PFB. Made an E/W error in position update on INS 1, but still tracking route reasonably well. Attached screenshot, INS2 has been updated to correct position within last 2 mins so is accurate. Littlenavmap plot shown to show how on track we are!

Pilot/Copilot DME readout mismatch as per attached screenshot. This was just after retuning NAV2. Once the pilot DME clicked under 100nm, the Copilot DME caught up.

Hey Not as yet but will prod the team for one. We'll add it to the FAQ section once its ready. Thanks for your patience meanwhile!

So could potentially be something to do with downloaded content after the recent city update and core content updates. Those who stream most of the files may be unaffected.

Hi, thanks for your report. Team's already working on this for an update.

Add me to the list. I only fly the A359 in MS2020 and its frustrating because you can't stop it. So annoying especially when you have spent 45 mins setting up, and on VATSIM. Has anyone had this experience on other aircraft or just iniA350. If not, then i'm back to flying the A380 until this issue is fixed

Ok thanks we'll have a look.

That click spot doesn't work properly as far as I can tell. With the aircraft set to LBS and a GW of approximately 316 000 LBS, pressing the click spot set the gross weight dial to 145 000 LBS. It's like the click spot sets the weight in KGs even though the gauge is in LBS

No matter what you set on the CABIN PRESSURE CONTROL panel the pressurization system will always pressurize the cabin to a cabin altitude of 0ft until reaching the maximum delta P. At that point the cabin will start climbing rapidly (needle maxed out) and maintain maximum delta P instead of slowly climbing to the cabin altitude set on the pressurization controller.

There is an issue where cycling between views will cause the audio to... not function as intended.