It’s been that way since the A310. But the A310 on launch was even horrible on my end almost 20fps lower. I think it was the second update that they improved performance but it was still 10fps lower than its other payware peers.
Does anybody know how to get out of a EFB hardlock situation? This isn’t something that happens very often, but I got myself into a nasty situation on my last flight where the EFB wasn’t actually “on screen” but all inputs into the sim had seized-up completely, presumably because the EFB thought I wanted to type something into 1 of the fields…
I’m pretty sure I tried every single key on my keyboard and every input on my flight yoke/throttle (and of course I couldn’t click on anything since the EFB was off-screen) - Nothing I did seemed to get me “unstuck” from this situation. Going in and out of the ESC menu and devmode didn’t make a difference either.
I can’t be the only one this has happened to… any ideas?
And if any devs are reading this, please for the love of god, fix this flight-ending bug in the next patch.
Is it me or is this plane very sensitive on the controls? I use a honeycomb alpha with linear sensitivity and it’s very pich and roll sensitive that way. What is the experience of others?
Secondly, engaging the AP causes the plane to react very violently, even if I was following the FD perfectly. Is this normal?
New update dropped today
iniBuilds A300-600R Airliner for MSFS v1.1.2 Released - Updates - iniBuilds Forum
And an interesting promotional price for today
My initial quick load in at JFK and test seems to have a really good performance improvement for the A300. Anyone else confirm better performance?
Yes, the new update is really good. Other than the wind request function being a bit screwy, it runs really smooth now.
I can’t seem to get any ATC side communications or even ATIS although the copilot calls and responds audibly. Compared other radio settings and mine look to be the same. The A310 works fine. Reinstalled just in case but no change. Any suggestions?
Before anyone asks - yes, I did try VHF1 CALL pressed and illuminated plus volume knob pulled out and turned up. Same setting in the A310
Hello All
I just had a very strange issue with the 300-600… I was on approach when all of a sudden nothing in the cockpit was clickable. I could not change any button/setting at all… The plane was not reacting on any of my inputs but I could still steer her and reduce/increase speed. But no way to disengage AP or do anything else.
Is this a known issue?
I have the same problem.
I had it too, yesterday. After a go-around I quickly needed to select a new approach and poof the whole cockpit stopped working.
the same thing happens on the A310 which probably shares the same coding
had the same thing last year during cross the pond in the a310 (while changing the approach during the first approach) lead to an emergency landing on Sardinia instead of Rome
Does this plane support time acceleration like the PMDG products?
You can manually set the sim rate using the sim’s keybindings. However, last time I flew this, fuel consumption did not change with sim rate so landing fuel (and weight) would be much higher than it should have been. 2x-4x sim rate usually works fine besides the aforementioned fuel issue.
Alright, thanks for their info.
Is it me, or is this airplane very sensitive on the rudder? Especially takeoff roll it is very delicate work to keep it on the centerline. I even made the curves less sensitive but it’s still tricky.
I believe there is a setting in the EFB to change what the pedals do. I had a similar problem where it was really twitchy on takeoff or landing, but changing that setting fixed it for me.
Sorry I can’t be more specific, I’m not at my PC at the moment!
I have rudder controls tiller set to no and have nosewheel steering axis assigned to the left stick of an xbox controller and that helps a lot. It is a bit twitchy compared to other aircraft but the A300 was notorious for having a very overpowered rudder - see American Airlines accident that led to the Stop Rudder Input warning sound and sign being added.
I have TFRP rudder pedals and set 30% extremity dead zone (as never need full deflection) and -30% sensitivity and it feels pretty good
The A300 has a huge hit on my system compared to the FBW A32NX or the PMDG 737-600. I can’t fly the A300 with AI aircraft and Track-IR and maintain 60fps with MSFS NVIDIA Frame Generation On. Maybe in 5 years
5800X3D/ TUF 4090/ 64gb RAM