richboy2307

Hi, I am using TFRP as well with the A306 and do not notice any such issues. My configuration options are as follows. Can you double check that your TFRP are also set to FLIGHT mode (towards airplane), instead of DRIVE mode (as shown in the screenshot below)?

Thanks I'll add it to the suggestions!

Thanks, reported!

There are 4 versions total, pax & freight, one for each engine. In your SimObjects folder (where the cameras.cfg and state.cfg files are stored) they are defined as: inibuilds-aircraft-a306f inibuilds-aircraft-a306f - PW inibuilds-aircraft-a306r inibuilds-aircraft-a306r-PW These folders are made only after you spawn into the aircraft in the sim for the first time. In your Packages folder (where the "work" folder and various other .cache, .obj, .dll, .lib files are stored) there is only one folder shared by all variants as: inibuilds-aircraft-a300-600 You will find the SimObjects and Packages folder here: MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ Steam: %APPDATA%\Microsoft Flight Simulator\

Yes thats is noted thanks.

Answered here, hope that helps!

Time acceleration is not supported currently, but something we may look into the future. Your suggestion is noted, thanks!

Hi, are you facing this problem on every flight/every time you load in? Please also try to empty the contents of this folder (delete the files inside, not the folder itself) and relaunch the sim. Steam version: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store version: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 This will reset all the generated files & config of the A300 to default. Just to ensure there wasn't some issue on the initial load where it didn't compile properly. Thanks!

Yes, we're looking into these WASM soft-crashes. Thanks!

DME readout is on the gauge left of the ND.

Yes we're looking into these WASM soft-crashes. Thanks!

Yes its logged. Thanks!

Thanks, we're looking in this.

Logged, thanks!

Reported, thanks!

Hi, are you using any tools like MSFS Addon Linker to link the plane into your community folder from some external location? If yes, please move the [inibuilds-aircraft-a300-600] folder to the community folder directly, then re-install. If not, then please ensure you are running the latest version of iniManager (v2.3.3). Uninstall the A300-600 from the iniManager, and check your community folder there is no [inibuilds-aircraft-a300-600] folder inside. Then reinstall the aircraft. Thanks!

Noted, thanks!

Thanks we're looking into these.

Hi For which sim & aircraft?

Hi, Just to confirm, is this for the XP or MSFS version? The FD/FPV switch is three-way, and it centres itself to the ON position. Moving it up again toggles between FD Bars or FPV mode on the display. Once you engage TOGA during takeoff, the FD should pitch upwards (as you can see in the screenshot). Ensure you have also dialled in a higher altitude in the FCU (usually initial climb altitude by ATC or the procedure). You can also arm a "vnav" climb mode by hitting the PROFILE button on the FCU, which will then arm the P.CLB, shown in blue on the PFD below the green SRS on takeoff after you have hit TOGA. So once you are airborne, at the thrust reduction altitude (as inserted on the TAKEOFF page of the MCDU), profile mode automatically engages.

Yes, but it needs to be validated by MS/Asobo and then further by us. No fixed timeline on this. Thanks!

Thanks!

Wow that is quite peculiar. Which version of FSUIPC specifically? I use it myself and haven't noticed this issue, however am a few versions behind (v7.4.6)

Yes, however we cannot answer when as it is up to MS/Asobo when they complete their validation processes.

Could y'all share your simbrief ID with us to try and test/recreate this? Dispatch an A300 flight plan as well, thanks!