You could also try expanding the console that is minimized to your task bar and see if there are any errors. Wrong IP, wrong port, etc…
The size of my install directory went from 10.4 GB to 4.2 GB after this update.
After you update the plane, be sure to go back and reset this if this is the way you choose to disable the cabin.
Where can I find the 4K download?
Installer gives you two choices, just search fly by wire. Hope that helps.
New version out to fix a bug which I also ran into this morning with v0.12.2
A380X Alpha Release v0.12.3
This update resolves the issue that prevented the deletion of discontinuities in the flight plan.
Does Simbrief have a limit on this plane with 510,000kg maximum takeoff weight?
IIRC, the limit is set by FBW and not Simbrief. FBW has mentioned that the current modelled edition of the A380 is the 510’000 KG MTOW version.
I knew something is wrong when I could not clear “discontinuity” as I did before. Thankfully there was a workaround by clicking the last waypoint before “discontinuity” and selecting INSERT NEXT WPT from the menu.
Yes that was my workaround this morning too. Otherwise I’d have had to take off with the discontinuity and do a direct to instead.
Found it in the new installer.
There is definitely an intermittent battery/external power problem with this aircraft.
I loaded in at LFBO this morning. EXT lights AVAIL (illuminated), but turning on EXT power and the BATT lights don’t illuminate (or respond). Enabling APU in EFB makes no difference. Restarting flight makes no difference. Restarting a new flight at a different airport makes no difference. So it’s a ‘sticky’ condition in the entire sim session. I also notice that while the aircraft is in this ‘state’ the nose wheel is squint when you load in at the gate. Repositioning the aircraft doesn’t fix this.
I find that only a complete sim reboot seems to rectify this situation - nose wheel straight and EXT power & BATT working as expected.
I also see no sign of this intermittent bug on their list of known issues.
I currently load with a default state of cold&darkwithGPU, from memory, and that seems to make the external power lights always say available or on, regardless of whether the GPU is connected or not.
That’s probably not 100% correct, but at least it always ensures that it is instantly available when turning up on a stand. Useful when you’ve forgotten to start the APU, during taxi.
and that seems to make the external power lights always say available or on, regardless of whether the GPU is connected or not.
It is intended. It works in the same way in the fbw A320. IIRC the FBW have described it as a simulation of external power coming from the jetways (even if you are on a remote stand), a way to get power without a GPU.
Fair enough.
So do the avail lights appear as soon as the parking brake is set?
There would still need to be a connection from the jetway and it’s still technically ground or external power regardless if it comes from a mobile cart or a more permanent source. The question I guess is does the real aircraft differentiate and if so how.
More often than not the EXT power lights say AVAIL as soon as you boot in with no jetway or GPU connected. Sometimes it’s ‘AVAIL’ but in the bugged state where the batteries won’t respond.
This isn’t an option in the EFB it just says ‘C&D’ or ‘Powered’, ‘ready for pushback’ etc which area all a bit more than just GPU (BATT+APU etc). So how do you set it to a C&D+GPU only state?
Something that would be nice (at a later stage) would be a simpler to use paint kit.
The likes of PMDG (and others) have had much easier to use paint kits where you have a full fuselage (and other sections) and apply your paint scheme to it, then chop that up as indicated and apply to the individual texture sections (which is easily done in Photoshop).
I had intended to do some paint schemes for this plane but when I downloaded the paint kit I decided against it.
of course, but my point is that it’s a design choice by the FBW to have this way.
IIRC, there’s another page of states to choose from.