All Activity

yes this issue still happening as of today. once the auto gpu disconnect was turned off, this not working for me issue still happening Only deleting the wasm folder helps, but only for the first trigger, every other trigger the error repeats.

The DIR page of the A400M has also options like CRS IN and CRS OUT besides the normal direct-to. But how does it work? Where do I set the course that I want to fly to the point I enter there? If I select CRS IN and enter a wypoint, the A400M behaves exactly the same way as if I'd chosen the normal direct-to function. Where do I set the radial I want to fly to that waypoint?

I think I have seen that they are working on fixing that.. to turn it off - press the APU start button then the shut down button.

Rehash of the previous discussion which is extremely important to a number of customers. Finding a way to thoroughly implement this feature would reflect the next generation features that the A350 brings with its MFD and ND functions.

So I don't know if this is just a bug that happens from time to time but I did a flight in the -900 variant and the the exterior lights did not work when I turned them on. Almost the opposite issue when the interior lights didn't work. Now I flew the -1000 variant a few days ago and nothing was wrong. I just want to know if this was an issue that I just need to restart the sim for or are the exterior lights now broken for the -900 variant. P.S. I am on Xbox.

Last image is probably a better example - speed changed as I was moving the cameras to show the difference

Unless this is modeled as wear and tear or something, I have noticed a discrepancy between the CA and FO airspeed indicators. The screenshots exceed max file size, so I will link the photos on imgur below. First photo is CA side, second FO, then both. Photos: https://imgur.com/a/L2786mo

I am also an Xbox simmer and I have found that with the L1011 in particular when I have to use my keyboard I cancel it out and use the normal numbers. Not the number pad numbers. It's a work around for now.

Think I've found an issue regarding APU logic, I can't seem to get it to shutdown. Used the virtual FE to start it, but hitting stop never seemed to work. My friend started his APU manually and was able to shut it off. Currently in flight, still won't shut down.

Second this. I have a bluetooth keyboard and mouse connected to my Xbox, otherwise I would be throwing things, ha. --Nick N.

I have had the same issue today. Completed a flight, which included going through about 3 sets of 9 waypoints with everything working just fine - then completed a turnaround to head off on a second flight... I set all new waypoints 1 through to 9 with my current position 0 being accurate still... the INS did not allow any selection of From/To waypoints other than 0 to 1-9 (could not select 1-2/2-3...ect) and the HSI was stuck on a random direction with the distance also being stuck. I took off to see if it would come around, however no change. I landed and cycled through reseting/realigning the INS - even shutting the aircraft all the way off and turning it back on again.. however no change. On a side note wto add with the HSI if I can add. The distance only ever shows INS wapypoint distance, even when changing to RADIO. Even though the manual indicates otherwise not sure if thats also an issue out there.

The other reverser topic got locked so I'm starting this one. Much like the engine roar during cruise mentioned in another topic, can the sound level of the reversers be looked at again? They are pretty quiet even at max reverse which does not seem correct, especially when seated at and/or in front of the engines. I am including a video here an A350 arrival into Perth and you can hear the difference. There is a loud rushing wind noise from the reversers just after touch down and that is from a vantage point BEHIND the wing. It would be louder at or front of the engines themselves. So can could this please be looked at and the volume increased? I realize it is small detail but it is something none-the-less. The video is below, and touch down occurs at approximately 9min34seconds with the full reverse noise starting at about 9min38seconds. Thanks.

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 tuned a bit?