After a huge amount of frustration, time and effort, I eventually got a message from FSS about the above problem.  Uninstalling, reinstalling, starting as administrator did not work, but simply deleting one file is their temporary fix for the problem - it worked, but it apparently affects the use of the keypad, which is not regarded as a big deal!  So if there is anyone else out there struggling with the same issues in this newly released aircraft here is the fix:  1. REMOVE the file fss-aircraft-tecnam-p2012\SimObjects\Airplanes\FSS_Tecnam_P2012\panel\FMSPlugin.js   2. YOU MAY ALSO NEED TO edit the layout.json file in the root folder to delete the entry for the FMSPlugin.js file.  3. WAIT FOR FSS - you will find the avionics work after doing 1 and 2, and FSS said they are working on permanent a fix.  

Edited November 27, 20232 yr by ozzieblr
Hit return before completing the message!

Do you have an active Navigraph subscription?

Hey. I am facing the same issue, even after installing the patch 1.01. With the FMSplugin.js file in the panel folder, the MFD is being cracked.

I having an active Navigraph subscription. No problems with other addons like the FSR500.

I contacted the FSS support again. They said that the update 1.01. was supposed to resolve this FMSplugin.js issue. For me this did not work...unfortunately

Update 1.0.2 live on Contrail now

-B

 

3 minutes ago, turbomax said:

 

I haven't tried it yet but looks like new update fixes autopilot bug

didn't work earlier today. they fixed it finally this afternoon with v1.0.2. in the ChangeLog no word about fixing their "custom" WorkingTitle G1000 that was messed up, that they had turned into a non-WorkingTitle G1000. now it's a fun plane. just in time for SU14 next week.😁

 

the link to their online manual still ends up in nirvana. after 2 weeks?

 

Edited November 28, 20232 yr by turbomax

35 minutes ago, sd_flyer said:

I haven't tried it yet but looks like new update fixes autopilot bug

I have. For me it was still broke if I use my key bindings to activate AP. Only the VC button works for me, still

7 minutes ago, btacon said:

I have. For me it was still broke if I use my key bindings to activate AP. Only the VC button works for me, still

for me in pervious version AP was all messed up even when I don't use binding in my honeycomb bravo. Oh well 😞

Version 1.02 hasn´t been available via Aerosoft ONE yet. Will check this later again. 

I also bought the P2006t and still struggling to get it working with my honeycomb Bravo.

The autopilot is completely messed up when I use the HC Bravo. Hopefully it is not the same nightmare

with the P2012. Tried MSFS bindings only and also spad.next. Both are not working 100% correctly.

Edited November 29, 20232 yr by EDHE27

1 hour ago, EDHE27 said:

when I use the HC Bravo

autopilot ON/OFF and VS does work as of v1.0.2 with Honeycomb Bravo.

Even after updating to 1.02. the MFD is messed up with the FMSplugin.js in the panel folder. Very disappointing...

Could it be a common problem with the javascript within my system? I am on Windows 11, no MSFS beta

 

Edited November 29, 20232 yr by EDHE27

Anyone else having this MFD issue ? The screen remains almost black. No functionality at all... Thank you for any support...

Installed 1.02 from Contrail 2 days ago. No problem at all spotted yet.

Combo with Honeycomb Alpha and Bravo. I only use basic Bravo AP functions: setting HDG directions, ALT, VS

HELP !

I bought this today as I thought the problems were solved for SU14 beta users.

So far:-

* It's dead when I turn on the batteries (ext power is only way of getting elec.)

* Fuel levers won't move

* Fuel pump switches won't move

* It won't start, and they didn't include a panel state with ready to go.

I thought the SU14 beta problems were only to do with the avionics?   My G1000 seems ok. Everything else is completely unusable.

Any clues?   Do I still need to do the 'temp fix' ??

Thanks