Fornax

Yeah, but not sure why this happens. Could be my system, SU2 beta, SU2 beta telemetry thing, iniAircraft(Wasm heavy), NVidia drivers (new ones for 50xx cards still not the best) etc. At least they have some info. Would be nice to hear if anyone experience the same. I'll check if the same happens in SU1 (non-beta).

Then, in same session (not quitting msfs), select a different AC, load in with different AC, bavk to meny, select A300 again: manipulators going crazy and fps almost halved 80 to 49:

Then just exiting/quitting MS2024, load MS2024 anew, reloading at same position, and A300 is suddenly ok. 2xFG, manipulators much better:

A300 Premium, MS2024, manipulators going wild: 1. A300 no FrameGen(FG) 2. A300 2xFG 3. Fenix 2x FG

Im also having some weird performance issues with the A300 premium (together with the IniA350) in ms2024 SU2 beta 1.4.12.0 Cleared Wasm, Nvidia cache etc. First load-in seems "fine". Fps 50-70 with 2xFramegeneration. Worst among all A/C I have. Next time I load in fps is down to 40ish (2xFG). Exactly same thing happens in A350 - although fps is slightly better (70-80 2xFG in normal load-in) 50ish when it loads in with some bottleneck. CRJ, Fenix, GAs fps 100+. 5090(572.83), 7900x3d, 64gb ram, 4k(5120x1440), hdr. No idea why this happens. Seems to bottleneck for some reason after multiple load-ins. Also the A300+A350, when the bottleneck occurs, seem to have very low GPU+CPU usage - 20% on both. Much higher in other A/C,. Uninstall/reinstall + clear Wasm seem to fix the problem for first load-ins. Will test some more...

Noticed this thread: https://devsupport.flightsimulator.com/t/massive-performance-cpu-issues-in-certain-locations-in-1-2-7-0/12097/2 Seems like some areas/airports a buggy. Of course I had to try the A300Prem at one of those places;) The "stutter" in the video was exactly as I had it. Tried different area/airport and all is good now...

Same here. All kind of problems with the A300 Premium in 2024. Pax GE. Strange stutter (un-smooth) movement as I pan around: like move-stop-move-stop, although fps shows stable. Just trying to select the UPS livery, my system grinds to a halt. 13fps. And this is just in livery selector. And every time I try to go back to Main Menu, sim freezes at it zooms back...just with this AC - seems like any livery. Reinstalled 3 times. Deleted A300 folder completely in Community (as Uninstall doesn't delete it completely?). 4080, 7900x3d, 64GB ram.

Well, I am able to set V2(turn knob V2 speed changes, Mcp speed stuck at ---), or any speed in-flight. It just the Mcp speed indicator is stuck at ---. Also default iniBuilds livery FedEx.

I had this pre 1.0.3 as well. Make sure you load the FPL into the EFB before setting ZFW. It might not be related, but I have not ran into this problem if FPL is loaded first.

Yup. All on. Same procedure as pre-1.0.3.

Yeah, shows speed in PFD (not ND as I wrote 😉)

Trying to set V2 speed in MCP. I can turn the knob, but the MCP doesn't show the speed, stuck at ---. It does update speed in the MCDU though. If I select PreSelect it shows set speed. Same when flying, HDG mode, V/S, trying to set speed: shows ---. The speed bug changes in the ND as I turn the knob/using "set speed bug" keybind. So it is flyable, just it won't show selected speed in MCP.

Thats what Im trying to tell you: There is no pop-up page. Type ex 250/10000 and THEN press the right button where you want to isert the restriction...

I presume thats because you have to INSERT the (revised) restrictions in th correct format. Not just press the button... Like /18000 or 250/10000 etc.

Had some good flight with it now. Bangkok-Hanoi - she behaved very nicely. Generally I feel I have better control of her using LVL/CH initially during departures. Using PROFILE she wont follow level restrictions on SIDs (as the real plane afaik). Also at one airport (was it Haneda(RJTT)?) there was no speed restrictions on departure, so in PROFILE she wanted to accelerate to 315ias at 2000ft. So I usually keep her in LVL/CH to 10000ft/clear of restrictions - better control of speed + restrictions imho. On arrival she followed the restrictions on the STARs/approaches I tried (PROFILE-mode) 👍 Well done. On one flight KMEM-KMCI the Prog page was stuck in CRZ-page. Refused to show DES. This was after changing CRZ alt 3 times. Dunno if that influenced it... Otherwise a good (latest)patch! Sounds, flare(much better now), idle thr 👏👏

How do I edit this thing...;) Another Q: When in NAV + PROFILE mode: if I try to set speed manually in the MCP Im unable to activate the rotary. Stays at ---. Pressing down on the knob. Nothing happens. At work now, but think pressing up had the same unavailability to select speed. At some point it suddenly works again. I guess you should be able to select speed manually in PROFILE mode? Or you have to use V/S?

Loaded SNSHN SID via LAS RWY26R. In NAV and profile mode. At LIVVI the A300 continuous straight ahead, missing the XBBOX WPT. A DCT TO fix fixed the problem. At KSLC I decided to try the RNAV 34R via QWENN 5 STAR via MLF. The FMS didn't even show the QWENN STAR as an option. Inserted the WPTs manually. For the RNAV approach I could not the the plane to descend correctly. Was level before CHEVL (FAF) LVL/CH+NAV and press PROFILE (MCP alt to 6100ft). It would not catch the glidepath. Then MA and tried to set MCP altitude to minima. Again LVL/CH and press POFILE mode before CHEVL. Still not catch the glidepath. Is this correct procedure for an RNAV APP? Thought it was the same as the A310. Not press LAND? A300 freighter. PC. DX12. FedEx livery. Using NAVIGRAPH, so not sure if the missing STAR problem lies with them.