Pushback works fine for me but like you, did not.
I would never have thought to blame a freeware grass strip, but when I disabled my add-ons, all of a sudden the pushback tug appeared.
After a 5 hour process of elimination, I found one bush strip (LFQD ARRAS ROCLINCOURT » Microsoft Flight Simulator) had removed ground services not just from their little strip but for the entire simulator.
Of course there could be a number of other offending add-ons but rest assured, pushback does work from the EFB.
Once that had been found and deleted, pushback for the Fenix A320 works just fine.
Hey, I have a slight issue (I am pretty sure it is TCAS, or the thing that shows the pitch, altitude, speed, etc.). Basically, every time I go to pushback, as soon as I start to move, the “TCAS” just breaks. When I stop moving to fix it / reset it, it will sometimes come back and then when I go to move forward this time, it breaks again. And keep in mind, my failures are turned off in the MCDU. Any ideas on how I can fix this?
Thanks again. I did find a video from a CEO A320 study app for the iPad showing startup from a US-based airline. I was pretty confident that I’ve never seen stable internals with a rising EGT.
If I did, I’d be ready to abort thinking possibly a hot start developing, or worse. Surprised the Airbus Pilot streamers haven’t caught this.
I too am having issues with push back. The option is sort of “dimmed” in the EFB and says tug unavailable. You can click it and it turns green (still dimmed) and the start button bcomes available, but then immediately the tug disconnects. By spamming the tug button and start button, I can get it to very slowly push back, whicheventually works, but is a total pain.
This is from the Fenix knowledge base and shows exactly what I see:
Absolutely. I think I might count how many times different people have asked exactly the same question, “the EFB won’t start” or “I can’t load a Simbrief flightplan” for example.
I’m sure that Discord is good for some uses, but providing support to a large number of users is definitely not one of them.
A forum, not necessarily Fenix provided if they don’t fancy it ,needs to be provided, where discussions can be better classified and control over off-topic posting can be far better.
Hello @everyone (I’ve used “Hello Everyone” like 5 times in a row now, someone please think of something new and send in suggestions on a postcard) - sorry it took us so long to get this patch out to you. We had some very complex changes to make with a large knock-on impact to other areas.
TL;DR The big things worth noting:
More performance improvements (up to 25% w/ an average of 16% across our testers - CPU on Quality/Balanced showing the most improvement)
Installer fixes/improvements
Lots of crash fixes (start-up etc)
Better panel state behaviour (spawning at gate will be truly cold & dark now)
Keyboard F/CTL support added, we’re continuing to work on hardware bindings etc
Added cockpit texture quality option to reduce VRAM usage (low VRAM cards will see FPS improvements from this)
EFB general stability and load-in improvements, pushback fixes amongst others
As we’re starting to clear the usability issues we’re setting our sights on product improvements; expanding hardware support, save states, autoflight - basically anything that we think could be better. To keep everyone looped in with our current roadmap, the current priority order looks like this:
Deployment, Stability & Performance. Get as many customers running the Fenix A320 without significant errors, crashes, or performance issues.
Clean & Tidy. All the little things that’ve come up over time that weren’t super high priority, but regardless should be addressed.
Improve & Build-upon. Start improving what we have, treating the release as a ‘base’ to add more features, improve existing ones and generally keep the aircraft cutting-edge. This will include external engine modelling, autoflight enhancements, displays improvements and more.
Expand. Once we have a CFM A320 that lives up to our expectation, we will then be strapping some more bits to it. Some pointy bits on the ends of the wing, and some more powerful bits under the wing. From there who knows…
Oh and PayPal is working now.
We’ve also bolstered our support team by a factor of 3 due to the much-higher-than-anticipated number of support tickets. We apologise if you’re still waiting on a reply, but the response times should only improve from here.
Thanks again to everyone for being so patient with us, the dev team haven’t yet had a day away since launch so I’m really hoping this patch gives us a bit of ‘clear air’ to let them see the sun for a few minutes. Unless it’s Dave, in which case he has no interest in seeing the sun and would probably just point and shout at it.
Full patch notes available in the Fenix App. Thanks!
○ Several startup crash fixes
○ Kill gateway if already running
○ Add graceful gateway shutdown
○ Reduce Hoppie request rate, stop requests if invalid logon
○ Fixed issue with autolaunch not working
○ Set parking brake initial state in more reliable way
○ Add messages about incompatible 3rd party add-ons
○ Force initial state for Runway spawn to Ready
○ Tiller blending adjusted, ramps off at a shallower rate
○ Sign in error messaging improved
○ EGT to ambient temp during cold and dark
○ Suspended hang when closing the MSFS is fixed (requires working exe.xml)
○ Suspended hang when entering or exiting the flight is fixed (requires working exe.xml)
○ Parking brake is now reliably set when loading plane
○ More reliable external power hook-in in Cold&Dark
○ Platform multithreading option is now automated
○ Optimized displays
○ Fixed misaligned displays in certain GPU configurations
○ Improved default state stability when spawning
○ Fixed certain instances of Fenix Launcher crashing on startup
○ Fixed certain instances of “bad load ins” with semi functional systems
○ Keyboard F/CTL support added
○ Config option added: Thrust Handling: Detents/Incremental
○ Future-proofing setup improvements (should show a message if Fenix is open, but requires open Fenix to be 1.0.2 or higher)
○ Fixed default panel state being reset when applying settings in launcher
○ Dave no longer allowed to use company microwave
○ Default panel state being applied much faster
○ Cold&Dark now doesn’t leave some stuff unset
○ Fixed engine glitches on Cold&Dark start
○ Improve MSFS perf when running Displays on CPU or iGPU
○ Process priority tweaks
○ Tweaked DirectX threading settings
○ Implemented cockpit texture quality option
○ Per-livery config
○ Mostly fixed SELCAL/Registration (still not 100% reliable)
○ N2 goes ‘XX’ correctly on EWS
○ Added simulation rate increase up to 2x (for now, will increase it as we do more testing)
[EFB]
○ EFB general stability and load-in improvements
○ Fixed pushback issues, pushbacks should now just work
○ Fixed issue with non-reconnection of EFB with Fenix restart
○ Fixed day/night button on Navigraph app
Thanks, yes, I will need to work my way through the list!
Nice flight from Edinburgh to Madrid tonight - and actually pushback worked properly - only thing I can think that I did differently was select the gate from the drop down menu rather than clicking on the spots on the world map when I was setting departure point.
My first flight with the new patch certainly went well. I duplicated the real Frontier 785 and missed his arrival time by 1 minute. And I thought I was being sneaking getting off the stand 2 minutes early. The actual pilot of FFT785, had the same thoughts.
