could someone explain to me what is the difference between development and custom version of fbw?
is there a list of both what had been done up till now?
sorry I made a first answer, I didn’t understand the question, I don’t know too much about bugs :), I know that in the development version I couldn’t turn on the tablet and in the custom version, yes.
Hello,
I have put your question in the Third Party Addon Discussion section. This is the best place to ask about third-party aircraft and mods to default aircraft.
Custom version has it’s own fly-by-wire system compared to the default development. The custom handles the aircraft much more realistic it can scale your throttle scaling to have perfect detents, as well as implemented new laws like the Rotate Law and autoland.
The development mode is based on the default A320 ASOBO code which is quite limiting.
As NEO says, the Custom FBW has written their own, basically from the ground up.
Eventually the plan is to merge the progress made with the development version with the Custom FBW version and get rid of the legacy ASOBO code, creating a top quality sim.
For now, both are essentially a work in progress.
Both get improved/added to daily, so there are constant changes.
There are quite a few users that prefer the Custom FBW version.
It will be the base for the final version.
Try it, if you don’t like it , it is very easy to change.
I like the experimental version- very good rotation logic now. However, it has also been very buggy over the past few days. Dev version is good too- not as smooth on rotation, but a lot of features are included that aren’t in the stable version. In both versions, there are currently serious problems in the navigation system. Waypoint tracking issues are back once again, along with some speed glitches on descent too, among other things. It’s been a buggy week.
Yeah, that’s the nature of development I’m afraid. There’s always going to be bugs here and there. And that’s why it keeps getting updated daily. Report issues to their Github page or seek help from their discord. So they can keep cracking on these bugs and bring life to the mod once again. In the mean time, either switch back to the stable version. Or you do some workarounds. I’m really good at doing workarounds and flexible when issues pop in here and there. So I’ll stick with the custom version. Hahaha.
You’re right about that- not knowing what to expect is part of the adventure…but it was nice to be able to let the AP do its thing for the past couple of weeks without a lot of intervention. We got spoiled haha.
Right now they are starting on the new autopilot, so issues in that respect are probably to be expected for the next while.
thanks a lot for the info to share with me. I will try the custom version and looking forward becoming more stable regarding fps, auto pilot with navigation .
Don’t forget to set the throttle up properly.
It is needed with the Custom.
Here is the guide.
where can I fill in the throttle details. is that via c drive user app or something else?
could you show me the path?
The path is mentioned in the document, but here it is.
In case of Microsoft Store version, the configuration of the throttle can be found here: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\<name of a32nx folder in community folder>\work\ThrottleConfiguration.ini
In case of Steam version, the configuration of the throttle can be found here: %APPDATA%\Roaming\Microsoft Flight Simulator\Packages\<name of a32nx folder in community folder>\work\ThrottleConfiguration.ini
You need to start the sim with the mod installed first, then exit the sim.
The files aren’t there untill you do that.
Is this needed with any throttle or just to set up ones with detents like the thrustmaster ones mentioned in the guide? Like would you use it with an x52?
With the Custom FlyByWire it is required for all throttles.
This is because the idle detent is not at the bottom of the throttle travel.
Hmmm, guess I’ll wait for a better guide for the config to come out then. I don’t know what I’d do with the reverser detent settings since an X52 doesn’t really have a reverse setting like that. For reverse thrust now I push the keybind that switches to reverse thrust and then push the throttle forward again.
Ok that’s good.
Use example #1 for the Thrustmaster TCA and change yours to those settings.
1 Like
Hey thanks for tip! I’ll check that out. I’ve installed the Experimental version through the installer before, but there was no mention in it that this was needed. I swear I tried a takeoff to test the new FBW and didn’t have any issues but maybe the throttle thing was added later, it’s been a couple weeks since I installed it and went back to the Dev version figuring it was more stable for general use.
It may be the same as the default, I didn’t check to be honest!
I just checked, it’s not, the example one is slightly different. I already had a “default” one in there from installing the experimental version once apparently. I’ll have to play with those settings and see which one feels best to me it seems.
1 Like