All Activity

Final Update - reversers now working. Despite selecting "Reversers on Axis" = "Yes" on the EFB, the ThrottleData.ini was not updated and had it set to "False". Manually editing the TrottleData.ini file to "True" now has the reversers working on the Ursa Minor. Issue now closed.

O a320 neo foi prometido uma nova opção de motores da pw pois aumenta nossa versatilidade como na vida real e vocês enrolam e nunca trazem é uma coisa simples tanto no 2020 quanto no 2024

O A400M nao responde com rapidez aos comandos da tela sendo que é necessário clicar diversas vezes pra funcionar pra exercer um simples comando nas telas e no mcdu

"Os Airbus da inibuids no ms 2020 e ms 2024 precisam de melhorias urgentemente como prometido as novas operações de motores da pw para os a320 e 321 e a simulação do fan rodando com o vento com o motor desligado pois no ms 2020 o "A320 neo tem isso mas no 2024 isso nao acontece

Há uma demora absurda pra lançar o a350 no Market place do xbox no MS 2020

Hello, thank you very much for taking the time to reply so quickly. The issue I am experiencing is the following: before Sim Update 3 of the main simulator, everything was working normally. When I clicked once on the FMC to enter the flight plan and flight data, the input was detected correctly. Since that update, I now have to click twice very quickly for the action to be recognized. If I don’t double-click fast enough, the input is not detected at all. Additionally, since Sim Update 3 (and even after several simulator and aircraft updates), it is no longer possible to import the weight directly from SimBrief using the A350’s interface. The weight seems to be stuck, and we now have to enter it manually. Previously, a single button press would automatically load all the weight information, including passengers and payload. This situation is quite frustrating, especially during approach phases, as having to double-click quickly adds unnecessary stress. Unfortunately, this has really discouraged me from flying this aircraft, even though I truly enjoy it otherwise. Thank you for your understanding, and I hope this feedback can help.

Hmmm not sure what’s going on there with your set up. I tried the same ABN checklist on my side, forgot to record at the first few items but here’s mine - seems to be working ok.

Hello, Ive recently as of last week gotten the A350 for Xbox Series X, not sure if this has anything to do with it, but I generate simbrief flight plans as one does, with the plane itself and the dispatch client on the web, and the flight plan has thousands of miles between waypoints on SIDs, STARs, and IAPs. I’ve noticed this to be more prominent on ILS approaches than RNAV. I’m currently running a flight from LAX to HNL and initially configured an ILS approach to 8L which has ended up as an RNAV to 8L. The ILS flight plan has a total mileage at 38,400. It also has about 8000-10000 extra miles between top of descent, the transition from STAR to IAP initial approach fix, and the final approach fix to the runway. The intermediate fix has 8000 miles between it and FLAP1. As well as an additional 300 miles from DECEL to FAF. On the RNAV, there is only 18,100 (5 hours in) additional miles that looks to be stemmed from only the transition between STAR and IAP and the fix after the IAF for the IAP. I’m not particularly sure why there is a difference between RNAV and ILS, but it seems to be quite large. I don’t have a photo of the SID, but I departed out of LHR on the UMLAT1G and every single waypoint had like 9000 miles between each one so I had to go direct to the enroute fix just to not run out of fuel on the first fix. Now, I have done some research before reporting to the forums (couldn’t find anything that was tailored to this), but I’m just wondering if this is a well known bug or not. I did see a video from British Avgeek on PC when he first got his hands on the A350 and it seemed to be suffering from the same issue and he noted not to worry about it. And I only ask because I’ve done like 8 flights with it now and only 1 of them hasn’t added all these miles. Additionally, it seems to move the coordinates for all these waypoints to who knows where, and I don’t even know where to look to see if I can manually move them back to where they’re were supposed to go. I do have the latest Navigraph AIRAC. Also, this doesn’t happen on PMDG 777 so I’m thinking it doesn’t have a whole lot to do with Navigraph. It’s really messing with T/D and EFOB, and ETA to different waypoints and destination Any help or guidance is appreciated. Thanks!

Hi Steve, I have found a solution and for the benefit of others, this is what I did: I had to invert the 3/4 throttle bindings, and I recalibrated (again) in SAP. The only thing remained is my reversers don't work despite the assignments and calibrations done, so at least we're getting somewhere.

Did you calibrate them in SAP and then in MSFS24?

The issue is on the plane itself im guessing. When im manually applying the step climbs and not placing in the FMS, it doesn’t give me a negative value or a crazy value. only happens when applying in the FMS

Hi Steve, Thanks for your help. I have attached my settings and the result with my Urse Minor throttles at Idle is shown with the misalignment of 1/2 & 3/4 thrust levers

Just got this also....

I am on S

We haven't changed anything drastically that would cause this. It might be worth flushing the package cache (uninstall/close sim/restart sim/redownload) of the aircraft to see if there was a conflict between versions. While I don't expect that to occur it wouldn't hurt.

for info, I've mapped a button to this and turn off taxi ribbon, as I find these two return indiscriminantly!!

Thanks. Can you share the procedure as well as exact steps just before the crash? Additionally, attach the autosave just before the crash if avail.

During filling in my appr i suddenly got a WASM crash. I had my MSFS debug active,so i was able to find the ofllowing two errors: WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty

Hi. While we understand the frustration, much of what you're taking issue with has nothing to do with the aircraft and more a byproduct of the platform. (We don't turn off screens or hamper basic functionality with any xbox-specific performance culling) Unfortunately, we can't prioritize how the console prioritizes memory handling so sometimes what gets removed in one flight won't be the case on the next. Knowing that I can assure the Xbox builds have received the same updates and refinements as with their PC counterparts (as much as possible) We test each build as much as possible but it's inevitable things may sneak through. Can you share specific examples of switches that are requiring more than one input so we can take a look? Thanks.

I was near South Africa, but shortly after that the Sim froze and crashed.

Hello. Which Xbox are you on? (X or S) The S is pretty constricted in the way it handles memory management and it will cull (turn off) objects as required to prevent lockups or crashes

Where you in or near a region with active GPS interference? If not, did you inadvertently turn off one of the ADIRS switches on the overhead?

Hi. I have these throttles. You should configure them in SAP as follows - Select Single-stroke double shaft as this will allow full range of the axis to transmit as a single fluid motion. Then in MSFS you should config them as follows - (Mirror RaxisX controls to Throttle 1 & 2 and RaxisY controls Throttle 3 & 4) Now in the A340 EFB you should set them up as "2Axis" and assign the points as desired This should resolve any conflicts and allow use as intended with full reverse range.

Has anyone been able to successfully calibrate the Ursa Minor Metal throttle for the A340? This is what I have done: a) Started SimAppPro and calibrated within the app - both throttles test OK to full travel b) Started MSFS and loaded the A340 c) Testing the throttles within SimAppPro shows the RY axis (engines 3&4) not going to full travel on the test page d) Created a 4-Engine profile e) Engines 3 & 4 are not in sync with 2 &3 which appear to be working normally f) I have tried the "In-Sim" calibration on the EFB (some say not to do this and it should only be done within the app) but this does not change anything I have read several sources that indicate this should be a simple process.

I got this message on ND after 6h Flight. What happened?