It is very well modeled and programmed. Sound is good. 5 configs available. EFB is great. Provides Navigraph link. And so on …
I personally enjoy the P2012 a lot because I can use it in many different ways. I like to fly in remote areas and take off and land at smaller airports. the P2012 is really great as a feeder plane.
It has replaced my beloved old Twinotter and that means a lot.
I’d wait just a bit to see if they fix a few things. The plane doesn’t work at all for me, I can’t(like others) turn the fuel on. MSFS is out of SU14 beta now and a lot of people were waiting patiently to see if this plane will work. It eventually will be a wonderful plane, but I’d wait…
I hate to say I told you so, but, we who have been on SU14 BETA have said the plane is a no go for about 4 days - and no response from the devs.
Now SU14 is released and the plane is still in the hanger.
Others seem to have the problem that they cannot turn the fuel on with SU14. Same for me, when I try to use the mouse in the virtual cockpit. Using hardware binds works for me though.
EDIT:
Sorry for any confusion, I must not have been on SU14 for my first flight.
Yep, fully broke for me as well, throttle not reacting (the axis does something, but the levers seem to have a fit), empty battery and no fuel flow.
for me when i select start from runway…black screens and no engine…in parking the same but i can turn on the glass cockpit via ground power but the engines don’t start…fully bugged
never had problems with any aircraft in fs2020 (may be a few but never black screen)
In the real world federal aviation authorities sometimes ground aircraft because of technical issues. Today Asobo was kind of like this authority because the release of SU14 messed up the communications API causing issues transfering data from wasm to javascript and back. It was working well before and we have no idea why and how they changed it but we will deal with it.
A workaround has been proven to work already but we need to check every single system to make sure it is running correctly because otherwise you guys won’t be able to enjoy it and we will be flooded with bug reports. We do our best to ship that update asap and will let you know once it’s available.
We are glad to hear that you would like to fly the Traveller 24/7 and soon you will be able to do so again. Until then it would be a good opportunity to fly the E-Jets or the P2006T, both are already working again in SU14.
Update v1.0.3 available
Grounding canceled! You can enjoy the aircraft in the latest MSFS version again.
One thing is left that we were not able to fix within this timeframe: The fuel consumption is still not correct. It is significantly higher than the tables at the moment. Additionally the EECS Pre-Flight-Test is not activating. We plan to fix that early next week. Stay tuned! Available now in Contrail and Aerosoft One.
Changelog
Fixed Comm bus issues to enable FMS keypad to be used
Fixed DRM issue causing users not able to start the aircraft
Fixed propeller and general sounds issues
Fixed Pilot side G1000 keyboard input enabler
Fixed altitude reading on Standby Altimeter behavior if the BARO value updated
Fixed TKS mode lights not lit up
Fixed Checklist description tooltips
Update several camera settings
Improved Fuel Pumps logic at Auto
Improved VR to be able to focus / zoom in
Enabled Pilot side PFD to pop up instead of First Officer side
Enabled EFB charging when battery ON to prevent EFB battery drained
Enabled Emergency Procedures Checklist animation
Please note: Because we deleted our own FMS plugin controlling the keypad and instead linked the new default key events from Asobo the keypad lost some of its previous features:
There’s no FMS mode (key set to inop), only COM, NAV and XPDR. Input will be switched automatically to MFD if MFD is not in map mode.
You can’t swap frequencies anymore (key set to inop).
You can’t switch between COM1 and COM2 by pressing COM key while in COM mode
You can’t switch between NAV1 and NAV2 by pressing NAV key while in NAV mode
You should be able to set something up. I was doing something non standard to toggle the modes before the mode events were published so if there is a non control pad event that will do the toggle you can use that on an external control.All the G1000 normal events still work so if it’s possible with those then something can be done.
Yeah I use the Air Manager G1000 bezel, the default frequency change command works. If you have the swap com1/2 event bound (cannot remember from the top of my head what the name is) you will be fine