So I upgraded to v0.8.0. Didn’t like it so I went back to 0.7.5. However I now have the dreaded power loss on engines after take-off.
I have tried v0.7.5 and v0.7.5-RC2 and the same fault happens.
Any suggestions?
1 Like
Most likely, in game assistance settings are causing your issues. All flight assistance settings must be off .
0.8.0 was released to help fix that issue, as some people still couldn’t get 0.7.5 to work properly on SU9.
What didn’t you like about 0.8.0? You should focus on working with the latest stable version, in my opinion.
1 Like
0.80 doesn’t work well for me either, it’s still not stable
Adding to my woes, having a lot of problems with the AP. It seems to have pre-determined AP settings which cannot be changed in flight…
From what I know, version 0.8.0 requires to “study” the aircraft a lot more than previous versions. After having to use the Experimental version this whole time, I can safely say that I have to use it completely different way compared to how I used to do things in earlier versions.
Since 0.8.0 is incorporating the new features and functions from the Dev version. You have to go through the same process as the rest of us to study the aircraft and the new functions a lot more.
For example: The new flight management function doesn’t work the same way as previously. So if you built your flight plan from the MSFS flight planner and have it synced with the aircraft. It usually cause a lot of issues with the NAV and the autopilot, because it’s not interpreting the same data the same way.
Instead, you have to learn how to use SimBrief to build your flight plan and integrate it with the aircraft while setting the MSFS flight plan sync to None. Using it will allow the aircraft to manage your flights more properly, reducing issues in AP, and NAV, etc while preventing the flight plan built in the world map from conflicting with the custom FMS. But you have to do this whole learning process to understand it. You can’t just keep doing the way you’re used to and hope that the aircraft still behaves the same way as it always was.
This is the reason why I prefer to use the Dev/Experimental versions, the changes introduced are mainly small and incremental, allowing me to learn small things everytime there’s an update which also lets me to “get used to it” a lot easier due to the small incremental changes introduced everyday. If I use stable version, the update is delivered so much and there’s so many changes, that it can caught people off-guard on how much it changes and how different it is compared to previous versions.
2 Likes
Issues with the NAV fonction here too:
-Tested it on DEV and stable version
-Both on MSFS FP and Simbreif FP
The AP doesn’t follow the FP. It did for the 2-3 first waypoint and then loose track.
Alt, speed and the rest is good.
I also got an issue with the transponder that the ATC could not catch. Tested every modes and with the right number.
1 Like
Well, you have F-PLN DISCONTINUITY on the F-PLN page. You have to clear this by pressing the CLR button, and click on the button next to the F-PLN DISCONTINUITY. This action will clear the disconnected flight plan, and have a flowing connected waypoints.
Like I said, this is a process that everyone needs to learn how to do, I’ve done this process since the Dev version for the last few months, and I’ve got used to doing this, once you have this process in your pre-flight activities, where you have a full Departure pattern, waypoints, and arrival pattern and approach setup without any disoncinutity, the AP NAV will always follow through no problem.
But again, this is a process that you have to do in the MCDU before you leave the gate. And it’s something that everyone needs to learn how to do.
This is a good resource for you to learn from: Discontinuities - FlyByWire Simulations Documentation And there are a lot of topics in there that are useful to learn from.
3 Likes
Neo has you very well covered. I will just pile on and say that the documentation on the FBW website is very good, including fully documented tutorials with pictures that will take you from cold and dark to 39,000 ft.
Learning the procedures is part of the fun for me.
1 Like
Great, thanks! I was not there yet but knew it exists from a few flights in the CRJ, where it was not an issue. I’ll get tamed…
the fly-by-wire 0.8 a320
It has several errors, it does not follow the flight plan, you must set the waypoints manually, the plane’s map has a route and on the ND screen it has a turn contrary to the plan
The FBW A32NX version 0.8.0 now has a separate FMS that works independently from the MSFS flight plan. You need to learn how to create a proper flight plan, either manually or through SimBrief and use that SimBrief flight plan to load into the sim, that way, the VFR Map and the ATC is using the same flight plan as the one from Simbrief.
3 Likes
thank you very much…the flight plan created directly in msfs is no longer compatible with flybywire? your recommendation is that I export it directly from simbrief
Yeah, you can enter your SimBrief username through the EFB Flypad, and the aircraft can just pull the flight plan from there directly. There’s a lot of tutorials on how to do this.
2 Likes
Try to delete the entire aircraft folder from Community folder and install the 0.7.5 manually into the Community folder after you have downloaded it.
Regards.
Before flying allways check your flightplan in the FMS by using the up and down-arrows. Select Plan on the EFIS control panel and watch the ND as you scroll through.
So can I go back to v0.7.5. I’ve tried but I get the ‘throttle back’ problem on takeoff. I just wanna fly.
Did you perform a throttles re-calibration?
Yep done that.
Flew with v0.8 last night & liked the new features. The new FMC was nice. Like Neo has said learn to remove (clear) any discontinuities, I had to do this last night a few times, but I’m used to doing this on the CRJ and now the 146. Other than that V0.8 behaved as expected.
Don’t be afraid to interact with FMC and how to manually add/edit in STARS and approaches, it’s the only way to get familiar with it. I find I can now find my way around most of them these days. The latest FMC (on V0.8) seemed more intuitive than the last version to me.
■■■■■■. It was ‘Assisted Takeoff’ all along. So I’m back to v0.7.5 and I’m happy again.