All Activity

Yes I have tried a reinstall. Problem also happens with the MS ATC. I see the frequency that I need to contact ground for clearance but it just won't work. The aircraft is the A320 Neo that comes with MSFS 2024

This sounds like frame gen, what are your specs and in-game settings?

Hey, thank you for this. I'll pass the media along to our team however do you think you could additionally attach a video either through YT or Google Drive showcasing this as well as the imagery. Thank you!

No. If your referring to the comment about the fans not spinning it was back in version 1.0.8 where you would start the engines and get the full sounds and everything but the fans wouldn't spin. It was a bug. This plane has just been a headache since it's update after release. Then again, 2024 has been an absolute nightmare for me in general since SU4. My biggest gripe has to be the Navdata issues that have plagued Xbox. Both PMDG and Inibuilds haven't fixed this issue yet. Something big must have broke after SU4.

Hi, Something weird with the refueling of the plane. If I quickly go to EFB to import Simbrief, then select Instant Refuel, it works. However, I can't understand why, if I'm too long (or doing any other action I can't identify), the button cannot be used anymore. In my screenshot, you can see that the dropdown for Set Fuel is overlapping the CWCG information. When I try to click on it, nothing happens. If I'm fast enough to configure fuel, dropdown list is not overlapping. Thanks,

Same here. The spinner looks blurred.

For the engine did you replace the oil in the efb maintenance page? Im having no issues on Series X.

It would be nice to have individual pop out instrument for us cockpit builders...

I don't like doing posts like these but as a consumer I feel a little let down. This A350 has been a thorn in my side since version like 1.8 I think. WASM crashes every time I try a flight over 4 hours. Haven't been able to update the navdata using navigraph in for what seems like eons now. STAR waypoints corrupt and if you try and fix them you run the risk of a WASM crash. Engine fans at 1 point just straight up didn't spin. Now after SU 5.1 we have panel / flood lighting issues. The list just gets longer and longer. I get it, Xbox isn't easy to code but you committed to having an Xbox version and I paid to have the plane. When it first released it was almost flawless. I love the A350 but right now it's just not flyable on console. I want to fly it so bad. I think if there is 1 thing that bugs me the most, it has to be the navdata issue. It worked fine on release and the broken or corrupt STARs. Inibuilds please fix this plane because I'm starting to get the feeling is console simmers are getting out on the back burner. I love your products but I'm not going to lie...they have been an absolute nightmare to fly since SU4.

While there is no native way to pop out the panels I use Glassout and it works great. There is a free tool called pop out manager too that will allow you to crop the big pop-out to individual displays.

Hi @IniJamir any updates on this? Would really like this system logic on the 340 and 350 please I guess it's probably a lower priority item, however I think it's a very basic thing. If it is known and will be implemented soon hope it's put on the a380 before release to. The current logic is just unrealistic and weird currently

After nearly three months, the TriStar still has flight model and autopilot issues that make it unrealistic at best, and less than flyable at worst. The issue of the GPS turn commands coming in late at higher speeds annoys me to the point where I use the INS for everything, including SIDs and STARs. The issues of unrealistic vertical speed in the climb, unrealistic deck angle during cruise and approach, and autopilot VNAV pitch commands coming in late during the climb annoy me to the point where I don't even want to fly the aircraft until they're fixed. To expand: The GPS seems to issue turn commands too late at higher airspeeds, which causes the aircraft to consistently overshoot turns when using the GPS - I've seen this at any airspeed above ~180-190 knots. The vertical speed in the climb seems to be nearly constant above ~10,000ft, suddenly drops off when the PMS switches from CLB1 to CLB2 around 20,000ft, then stays almost constant again until the switch to Mach hold. Vertical speed should simply gradually decrease with altitude. This has been reported previously by others. The aircraft's deck angle should be a couple of degrees lower during cruise and at least a couple of degrees higher during approach. This was also reported previously. In VNAV mode, the autopilot commands pitch increases too late and too gradually during the acceleration phases of the climb, which results in the aircraft overshooting the set speeds by a minimum of 10-20 knots, and consistently ending up breaking the 250-knots-below-10,000-ft speed limit by at least 20 knots. The autopilot seems to currently be commanding the pitch increases just as the aircraft reaches the set speed - it should start commanding the increases sometime before reaching the set speed - and the pitch increase is also far too gradual to successfully capture the set speed. My question to the iniBuilds team: is it unreasonable to request that solutions to these issues be prioritized over everything else with this aircraft at this time? The visual and systems fixes you've made so far are much appreciated, and overall, I like the TriStar, and I want to be able to fly this rendition of it realistically... but I don't feel I can fly it realistically as long as such fundamental issues as these exist - hence, I don't fly it at all except to test fixes released in updates. Thank you for reading.

Hi, When you are in the Free Flight Menu selecting the aircraft. It will display one variant however upon selecting the Aircraft and entering the Configuration Menu, the multiple cabin variants as well as EIS Options should appear. Just to verify that you've followed these steps? Additionally as for the pop-out instruments; This is by design for stability and performance reasons, as all instrumentation is being drawn in a single layer rather than its own separate gauge (as previous planes). Thank you for understanding and let me know if the above helps with the Variants of the aircraft.

Hello, what you're seeing here is LOD Culling due to the current console memory management implementation. Thank you for understanding.

That's a big one for me. As much as I like the CIVA, it has big limitation. The UNS-1 is really necessary. There is already one built by Working Title that can be fitted into the TriStar. The upcoming much improved Boeing 707 will have it! Why not the TriStar too?

Not sure, I do know it's been effecting people for years. Maybe make sure no firewalls antivirus is Tryna stop it. I got a pretty quick response from customer service, and they got me sorted, so might pay to raise a ticket with them. Sorry couldn't be more help

Hello, I recently purchased the A340, but I am experiencing two issues. 1. Only the VIP version is availableAfter installation, only the VIP version of the aircraft appears in the simulator. I tried reinstalling the aircraft, but the problem remains: only the VIP version is displayed. 2. Multi-monitor / remote cockpit setupI would like to set up a remote cockpit using multiple monitors. However, when I pop out the cockpit instruments, they all remain grouped together in a single window. I am unable to separate them into multiple windows and move them individually to different screens. Please find the attached screenshot illustrating the issue. Could you please advise how to: Make all A340 versions appear in the simulator; Display and separate the instruments into multiple windows for a multi-monitor cockpit setup. Thank you in advance for your assistance.

Any news on that? The issue still exist, as I found after bying the L1011 yesterday and as you can see in the screenshot provided (on Xbox-X).

Totally agree. In a climb there should be a gradual and steady decrease in the vertical speed. This one behaves like a yo-yo!

Does anyone know the price of the Ini A220 thats coming out or any predictions based on other releases?

Thank you for the information. But despite the installation of those .NET packages, my IniManager is still not running. I can see that it is loading, but then it closes right after.

No, I gave up... it seems to me to be a visual only bug

Aircraft: A350-900 Default Cabin (JA01XJ) v1.2.6 Simulator: FS2024 SU5.1 Navdata Method: Sim Default OFP: I wasn't able to powerup the aircraft. WASM Error: Orange screen in the autopilot module... the only thing displaying something for some reason since the aircraft was cold and dark Specs: Ryzen 5 7500F, 32 GB of RAM at 6000 MT/s, 1TB of Samsung 990 Pro, Radeon RX 9070 16GB of VRAM. (System has operated without issues before and framerate is around 50 FPS in 4k medium-high settings with aircraft) Autosave file: Unavailable from the flight I just loaded, attaching the last ones I had that occurred a few days ago. Observation I had a WASM crash while just loading the aircraft in RJFF gate six using the SamScene3D airport. This is an airport I constantly fly, so I think is unrelated. What I think is related and maybe how the WASM may had been affected is that the previous flight I had swapped to a secondary flight plan to divert to RKPK (Gimhae) due to weather and failed landing attempt at RJFF (Fukuoka). A few minutes later after landing in the alternate (RKPK), I created a new flight plan to the original destination (RJFF) and proceeded as normal. Another thing to note, before this flight, the aircraft had already handled 3 flight plans (2 short legs of 1-2 hours around Japan and 1 long leg of 7.5 hours from Heathrow to Toronto Pearson). The aircraft never presented any symptoms of the WASM deteriorating (as I have experienced other times). Next Steps. Maybe replicate a flight like this to see if that deteriorates the WASM enough to have a crash after a session like this. Below I am attaching the RJTT to RJFF initial planned route and then the one I did to return to RJFF after landing at my alternate from Simbrief and from the flight plan folder of the WASM module of the aircraft. Load the flight plan from RJTT to RJFF as normal. Create the engine out procedure out of RJTT in 1st secondary flight plan. Create the alternate in the 2nd secondary flight plan. Make the flight from RJTT to RJFF as planned until you reach 3000 ft approaching Runway 34R of RJFF. Go around up to 4000 ft 2 minutes after initiating the go around phase, review the secondary flight plans Initially almost swap the current flight plan for the 1st secondary flight plan. Cancel the action. Choose correctly the 2nd secondary flight plan that has the alternate route. Deviate and land at RKPK. Wait around 30 minutes (the time I waited for RJFF weather to be nice). Load the flight plan from RKPK to RJFF Fly it normally and land in RJFF runway 34R. My apologies for not recording the Debug menu... I forgot and now I can't really prove it. Additional Information A few things I want to note on what addons I have: FlyTampa CYYZ SamScene3D RJFF Drzewiecki Design EPRA IniBuilds KMKE ACO Design ROAH I do not have any other airplane or anything else that interfaces with the WASM besides what the default sim has. 1783312043.bin RJTTRJFF_PDF_1783297068.f14cad5e.pdf RKPKRJFF_PDF_1783307661.a4cc3e9c.pdf RJTTRJFF_INA_1783297068.fpl RKPKRJFF_INA_1783307661.fpl

Are you guys still having this problem?

If this is still occurring I'll pass this along to the team, I know it should be fixed for 2024. If a fix is need for 2020 as well let me know