I do have an issue with VR though… when pressing the reset toggle (space bar) it puts me down low to the left in the cockpit. Also the frame is not perfectly centered whenvreset, I have a black border on the left lens
Hi , I can’t run the Bonanza G36 anymore . It dies a few second after starting . But Asobo is still generous enough to give me the option of hitting Ctrl+E then it won’t die . Is the Bonanza OK on your side ?
Thanks, but yea all up to date, worked perfectly before the 1.12 and all my other Steam games work fine. Other default planes work.
Crucially it doesn’t crash if you start up from the gate.
I have tried both dev and stable 0.5 FBW versions and I am getting some mighty odd issues, the plane seems very broken, APU won’t start, all of the 2nd fuel pumps for each fuel tank wont turn on. I tried Ctrl-E but the engines die during start up.
I’ve tried emptying my Community folder and reinstalling. Going to try a full system restart and package clean now.
I love these people who can absolutely NOT diagnose my system without even being here.
It clearly is NOT a bandwidth or network problem.
The FBW mod is known to be incompatible with this update.
Was it? Well I know now anyway
Basic troubleshooting: The default A320 does not have any captain announcements, and AUDIODG.EXE is a Windows thing. What’s your conclusion?
IT’S A MOD CAUSING THE PROBLEM!!!
And just to reiterate in case you missed in the gazillion posts after every update, the Working Title and FBW mods usually break after each update, but they also usually fix them in a matter of hours.
Always clear your community folder before updating, and always test the default aircraft before blaming Asobo for something.
No offense. I wrote this with all the brotherly love and holiday good cheer I could muster!
Merry Christmas and happy flying
I understand all of that and of course its the mod, thanks for stating the blindingly obvious.
If you bothered to read the messages you would understand.
Tried clearing out my community folder as well as a fresh install and it’s still happening.
Loving the update!! You can switch from knots to mach and back again! Engines turn off and turning off the battery brings the log.
ILS perfectly lines up, and the frequencies now are working at Third Party Airports.
Finally I have just done a succesful “Travel to” flight. Manchester to Toronto, set off, got myself to Cruise height. Set “Travel to Descend” loaded the flight perfectly with all navpoints as before. Had to reset the AP details but it was flying perfectly to where it was supposed to be.
Can’t fault the update
What happened to the snow on the ground feature that was supposed to be rolled out today? I’ve been to a number of spots that SHOULD have snow on the ground, but there isn’t any
Anyone else seeing a large drop in FPS after update? I’m running 7680x1440 and normally get a steady 30-34fps. In a flight now and getting 20. What’s weird is that none of the graphics settings are helping. Turning render scaling down should improve fps but isn’t. Not sure if this is a FBW a320nx problem or a core problem. CPU and GPU utilization are both down. Guess I need to check with a vanilla aircraft.
It has been updated already. These guys are quick!
Asobo can TEST it, even thoroughly, and maybe even tell FBW what to do to fix it, but they dont own the code to “fix”, and even if they wanted to, LEGALLY they would not be able to fix anything on a third party mod.
Unfortunately this is purely up to the FBW team to fix it, and whilst I am sure in recent months, the Asobo team is communicating more with the FBW team, its now over to FBW.
Would you please explain exactly how you fixed it, step by step? Thank you.
and how exactly is this done? I don’t see Rudder Triggers to Rudder Axis in the menu. Would you be able to explain the fix step by step? Thank you.
Clear the bindings first.
Then search for Left Rudder Axis and assign it to Left Trigger etc.
How do you change it back exactely?