Not sure what UTF-8 is I’m afraid
Ok, so you say you can only enter ‘2’ into the cruising altitude field? Usually one types ‘200’ into the scratchpad and then clicks LSK6 to enter the number. Are you saying that ‘200’ results in a FORMAT ERROR, ‘20’ results in a FORMAT ERROR, but ‘2’ goes in ok?
Can you provide a screen shot of what your MCDU looks like right before you click LSK6?
1 Like
Unfortunately I do not have a picture. But yes, FORMAT ERROR occurs on my MCDU when entering “200” “FL200” “20000” but not “2”
What is LSK6?
You dont enter ‘FL200’ in the airbus Nor do you enter ‘20000’
1 Like
UTF-8 is a text encoding. What it means is that I’m worried that without UTF-8 installed in your PC, the mod doesn’t interpret the value 200 as a valid value, since it doesn’t have the UTF-8 enconding to encode the input with. But this is purely speculation.
Have you tried with a higher altitude like 380 or 390? I do find that I can’t set the CRZ ALT with 400, 410, or 420. But 390 is working.
1 Like
Oh… no wonder it reads out FORMAT ERROR
Well… now that you mentioned it, it seemed to have accepted FL390.
I entered “39000” and it accepted that on the MCDU. However “20000” among other numbers apart from “2”, just did not seem to work!
Yeah, then it looks like there’s some issue with the acceptable range to the entered into it. You should report this to their Github page if it hasn’t.
I never really fly at cruising altitude other than 390 or 380 really, so it always accepted it.
1 Like
I usually fly around 330-350 but have flown at 250 for short hops
1 Like
It is quite a strange issue. It likes it when I enter
“2” as in 2 feet. (Like I will be cruising an A320 at only 2 feet)
And 39000ft
Other numbers, seem to display the FORMAT ERROR. Obviously over 39000ft, it would display ENTRY OUT OF RANGE
I can obviously still fly within any Altitude. But if I tried to enter in any other number other than “2” or “39000” It would simply display the FORMAT ERROR message.
Normally I would fly at FL180-FL250 for short trips and around FL390-FL420 for long haul
Its a very strange bug. However developer releases can sometimes have bugs. Its been a few hours, try updating the version again?
1 Like
That’s another problem…
FlyByWire’s A32NX has 2 versions:
Stable build and unstable master build.
I am using the unstabled/developer build because the stable version does not display ANY screens. No MCDU, no PFDs, no DUs and no ECAM screens load up. Just the air conditioning, packs and the electrical systems in the overhead panel.
Look at the date of the stable build. Then look at the date of Sim Update 3. Since the stable build was made before Sim Update 3, obviously it will be broken by Sim Update 3. When the stable build gets updated, then it will work again.
1 Like
I should probably keep checking on Github to see if they have released a newer version of the Stable build.
Unfortunately I can only use the Developer Build until they work around the bug regarding all the screens
The developer build gets updated several times a day. They may have fixed it already.
1 Like
I’m using the developer build now. The developer build works perfectly.
It is the Stable build with the screen problem. I’m awaiting for them to update their stable build before I can delete the developer build and download the stable version
For me, I have to use the Custom FBW version, because the Stable version isn’t cutting it, it’s too old and too much missing feature even if it’s without the blank screen problem. As a TCA Quadrant user, the Custom FBW throttle configuration for me is something that I can’t live without to give me perfect throttle detents. Then, the Rotate Law and the Flare mode flight controls is only available in Custom FBW version. These two allows me to do take off properly and flare on landing with more stability.
Even the dev version is very twitchy on the controls when I flare which is no different than the stable version when I used it months ago. I don’t find the developer to be buggy or unstable really. It’s more like it changes so often even in one day, that people have to play catch up with the changes and have to keep on their toes adapting and embracing the changes that happens pretty much every day. I have to disagree if people are claiming that dev version is full of bugs. It’s not, and using the term Stable and Unstable version would be a misnomer too. Since the unstable version is not buggy.
It should probably be more appropriate to call them as Main release and Preview Release.
1 Like
To be brutally honest, the preview version doesn’t seem to cause too much “Crash To Desktop” issues. Only when my FPS reduces significantly at times during an Approach.
But apart from that issue and the small issue of the MCDU’a FORMAT ERROR message on CRZ FL, I personally think that the Preview Version works absolutely fine
And the stable version is probably going to take a while. They’re working on version 0.6.0 as the next stable version and it’s about 79% complete.
But then again, if the dev version has a FPS drop, chances are, it may also flow through the stable version if these aren’t reported and addressed early on.
I do get those stutters and FPS drops myself, but it’s probably because I also have the PMP A330 installed with the A32NX Compatibility mod at the same time. I’ll be removing that aircraft and use purely the Custom FBW version if I’m planning to fly the A320. And will only install the A330 if I’m planning to fly it. Otherwise, I’ll move it outside of the community folder.
1 Like