richboy2307

It was working for a bit. But we're messing with stuff to see whats up. Team's on it. Standby!

Should be resolved now. Try again.

Thanks, the team is already notified. However, due to timezone differences it may take some time to resolve. Will rectify ASAP.

Hi @Green97 Not supported currently. Under consideration, but no timeline/guarantee of this. Known bug. Already fixed for next update. Also already addressed. Improvements to this coming in the next update. Thanks!

Yeah that is just a WebASsembly Module (WASM) crash on load. When the WASM crashes, all code that uses it will basically stop working - end result being that systems freeze/stop responding. Anything NOT using WASM will still continue to function. This was designed by MS/Asobo such that if the code crashes, it will only be contained to things within the WASM, and not CTD the whole sim itself (like in previous simulators). However not all WASM crashes are due to the aircraft's code itself, as sometimes its to do with how the sim interacts with WASM, and where it stores that data specifically on memory. These are hardest to fix as they are difficult to reproduce, and are specific to each client's memory. Anyways, based on testing so far, next A300 update should have some workarounds/fixes that improve WASM stability. However, whenever a WASM Crash happens, only way to resolve is to restart the flight as that resets the WASM. Thanks!

SAT is the Static Air Temperature, OAT is the Outside Air Temperature, and both are basically the same thing. This is the temp that will be shown on your OFP's WIND INFORMATION section, and also what you enter into the MCDU. So using the same example from above: If I was entering the info for waypoint TUDEP, and cruising at FL330, I'd input -50c as temp, and winds 218/80 as shown in red. Thanks!

Have you tried with an empty community folder (nothing but the A300 in it)? Just to rule out some conflict with another add-on or lighting mod? Also perhaps try to use this lighting mod? https://flightsim.to/file/66466/inibuilds-a300-external-lighting-fix

Hi, Unfortunately that is a sim limitation. MSFS only allows one operational jetway per gate, no matter GSX or otherwise. The others are simply static models. Thanks!

INIT B page is only accessible when engines are off. It is important as that is where you set the information about your Weights and Fuel Onboard. So I would try starting from an ON APU panel state, fill in the information, then start your engines.

Glad its resolved. Thanks for reporting back. 👍

Its hard to say what happened without actually seeing a video, as it may have been the right mode wasn't armed, or the intercept angle was too much etc. The proper way to Go Around is to hit the TOGA button, which would kick off LAND on the FCU. So if your LAND mode remained engaged, thats probably where the problem happened. Only A/THR should remain when you hit TOGA or executing a go-around: On the FMA you would see is: On the MCDU, it remains in APPROACH mode, and remains so for the rest of the attempt: Here is me re-establishing, still on APPROACH mode on MCDU, and LAND re-armed: Thanks!

Hi @SimPilot7091 Please ensure you do not have any conflicting bindings. I am also using this with the BravoTQ, with below assignments and not noticing any issues with the gear. Also ensure you do not have any AI Assists enabled (Options > Assistance Options > Piloting). If you are still having problems, please record a video clip of the issue and share here. Both internally showing your ECAM and Gear lever, and also external showing how it extends/retracts. Also provide a screenshot of your bindings. Thanks!

The TOGGLE PUSHBACK button only calls for the default MSFS tug, same as you would through the ATC menu. It may take some time for the pushback to spawn (though sometimes it may not show up at all visually.) Make sure chocks are removed, and parking brake is released. To actually start the pushback you need select AFT, LEFT or RIGHT buttons on the EFB. This will then connect the tug to your wheels and begin pushback in the desired direction. When you are finished with the pushback, click the STOP button. Thanks!

The calibration is done entirely on the EFB itself, using either the actual throttle axis on your hardware, or via buttons if you're using a controller. You move the position of the green vertical bars using this hardware. Some things to note: The "SET XXX" buttons on the EFB define the detent position. The green vertical bars indicate the current position of the axis (0 to 100%). The white horizontal bars with IDLE, CLB, FLX/MCT, TOGA written on them show the currently configured position of that detent on the throttle lever. To calibrate hardware without a reverse axis (e.g. Xbox Controller* or Honeycomb Bravo TQ): Select REVERSE ON AXIS = NO Click 'BEGIN CALIBRATION' Keep the green bar at the very bottom (close to 0%) and click SET IDLE (it will replace the BEGIN CALIBRATION button) Move the green bar to where you want the next detent (normally ~70%) and click SET CLB Move the green bar to where you want the next detent (normally ~80%) and click SET FLX/MCT Move the green bar to where you want the next detent (normally ~100%) and click SET TOGA *Note: For XBOX users, some users have reported that you may need to restart your sim after the calibration is done in order for it to take effect. To calibrate hardware with a reverse axis (e.g. TCA Quadrant): Select REVERSE ON AXIS = YES Click 'BEGIN CALIBRATION' Keep the green bar at the very bottom (normally ~0%) and click SET MAX REV (it will replace the BEGIN CALIBRATION button) Move the green bar to where you want the next detent (normally ~40%) and click SET IDLE REV Move the green bar to where you want the next detent (normally ~50%) and click SET IDLE Move the green bar to where you want the next detent (normally ~90%) and click SET CLB Move the green bar to where you want the next detent (normally ~95%) and click SET FLX/MCT Move the green bar to where you want the next detent (normally ~100%) and click SET TOGA Thanks!

Hi @Мартыненко Борис Always glad to help! If you are only using your Rudders to steer and do not have an axis assigned to the Tiller function, then please select YES for RUDDER CONTROLS TILLER option on the EFB > OPTIONS page : Thanks!

This is normally done using the tiller located on the side console. The tiller can be controlled via the 'NOSE WHEEL STEERING AXIS' binding. For simulation purposes, this can also be linked to the rudder pedals for easier use. To do this, go to the aircraft EFB 'Options' tab, then select 'YES' for the 'RUDDER CONTROLS TILLER' option.

Hi @Felipe Lobo What display settings are you using? Can you try changing your Antialiasing settings? Also DX11 vs DX12 to see if theres any such setting causing conflict? I'm not seeing such issues on the A300 with DX11: Here are my settings: Also try with an empty community folder, to rule out any conflict with another addon. To run with a blank community folder without losing your addons: Rename your existing community folder to ``_Community`` Create a new ``Community`` folder in its place. Copy only the ``inibuilds-aircraft-a300-600`` folder inside it. Run the sim and see if same problem persists. If yes, then you can close the sim, and restore your original folder as follows: Copy the ``inibuilds-aircraft-a300-600`` folder back to ``_Community`` Delete the new ``Community`` folder you made Rename the ``_Community`` folder to ``Community`` If no, then that means there is some other addon conflicting with the ini A300. Usual suspect is bad liveries, so you could try by adding only some of the other a300 liveries in until you can reproduce the problem. Same process for other addons till you find the culprit. Thanks!

Hi @DutyDollar Hmm. Not seen that personally or reported by anyone else before. Could you please record a short video clip of it happening, also please include screenshots of your control setup for the rudders & tiller, as well as EFB settings page? Personally I use TF Rudder Pedals + Bravo TQ + Logitech Yoke + TCA Airbus Stick (for tiller), also configured to not link up in the EFB, without issues on the A300 so far. Thanks!

Hi @Bazz The plane used the default sim navdatabase, unless you install navigraph on top (for the whole sim, not any addon-specific one), in which case it will use that instead. That being said, as for NZQN, the issue is with the way in which the code is implemented. Ours uses the internal MSFS WASM API, which has been known to skip some data. I'll share this quote from one of my colleagues that was posted on discord, discussing a similar issue: So that is something for MS/Asobo to resolve. Other addons get around this by using their own custom navdatabase set compiled by Navigraph. However with this being a Microsoft product, that is not possible. Thanks!

Should be resolved in the next update already as I'm not able to reproduce that in the testing build. Thanks!

When you're in cruise, on the MCDU hit MODE button, then you'll find DES FORECAST> on LSK 5R. Click it to go to the DES FORECAST page where you can enter the winds at desired altitudes, and also the destination. As for this data, you'll find it from your OFP's WIND INFORMATION section: Please checkout this helpful interactive guide to the OFP for more information: https://dispatch.simbrief.com/guide#interactive-ofp-sample Thanks!

That is the plan, yes. If all goes well, might even make it into the next A300 update.

Hi @NebraskaFarmer Shared your findings with the team, which includes real world pilots of the type, with access to real tools for this same type of stuff. The results seem as expected, the speeds shown have margin built-in and are way above the minimum take off speeds anyways, and are valid as long as they are not below VMCA & VMCG. Also remember, these are "optimal" speeds, as opposed to "absolute minimum" speeds for the aircraft to takeoff (or not stall in takeoff configuration). So coming back to your EDDF Rwy 25C scenario, I've run it through the A20N EFB, see screenshots below (click to expand): TORA 4368m: TORA 2000m: You'll note the difference in the limiting factor for the speeds on the yellow band. TORA 4368m - the speeds are limited by '2nd Segment' climb gradient primarily. TORA 2000m - the speeds are limited by 'Runway Length' primarily. With a longer runway, with nothing else "limiting" (aka deciding) the calculation, it will normally optimize for a better (than bare minimum 2.4%) 2nd Segment climb gradient, taking advantage of the extra runway till it achieves the best speed for it to do, whilst still maintaining proper stop margins etc. Having a 20 kts difference in this case is totally normal then as it starts to bring the speed back to accommodate the shorter TORA, so it will sacrifice the climb gradient after takeoff instead (target the bare minimum 2.4% one instead). Hence the runway length becomes the "limiting" (aka deciding) factor, as opposed to the 2nd segment climb gradient. If the computed values end up being less than the "minimum" speeds, then it will return 'UNABLE TO FIND SAFE PERFORMANCE DATA' alert instead. So assuming proper technique is used, the aircraft shouldn't be stalling even on shorter runways, as even the bare minimum values it will push out has some margin built-in to them, and if it couldn't retain that margin, it wouldn't calculate any speeds for you in the first place. So if you're noticing issues, please record a video clip of your takeoff and initial climb, and share here so I can show the team to understand if something else might be the issue. Thanks!

Hi @meierblom Apologies for late reply. It won't go into managed (---) mode if information is missing on the MCDU. You need to fill in the following required info: INIT B page (Weights, CG and Payload) INIT A page (Route, CRZ FL, CI) F-PLN Page (Waypoints with an active RWY/SID selected) PERF Page (V-Speeds, Flaps/THS) See below 2 videos of the behaviour when information is filled in, compared to when the information is missing. F-PLN, INIT B, PERF info all filled in: 2024-07-02 17-30-33(1).mp4 F-PLN, INIT B, PERF info missing: 2024-07-02 17-31-09(1).mp4 Thanks!

Hi @Peter ESSA You can lower it using the following volume knob on the radio operators station (behind captain' seat) 2024-07-02 16-20-50(1).mp4 Thanks!