22 minutes ago, JYW said:

Wow!

That's crazy.   Explains a lot of the problems people are having.

Agreed. And today on their discord they are asking for customers to help them get a copy of the SDK because they are having issues obtaining it themselves.  “help us by sending link to download latest SDK for SU 14 😄” 

 

Edited December 5, 20232 yr by btacon

25 minutes ago, btacon said:

Agreed. And today on their discord they are asking for customers to help them get a copy of the SDK because they are having issues obtaining it themselves.  “help us by sending link to download latest SDK for SU 14 😄” 

 

The height of professionalism in a developer, for sure! 😆

Next it'll be, "Could someone buy a MSFS Premium Deluxe licence for us, as we think the issue is because we're using Standard".

They're certainly quite a special bunch, our Swiss friends at FSS.

 

Edited December 5, 20232 yr by JYW

"FlightSim Studio AG is a highly skilled development team" 🤣

have they in the meantime fixed the easy bugs or do we need to also help them with the correct link to their own online manual?

Edited December 6, 20232 yr by turbomax

3 hours ago, btacon said:

The reality is they never figured out the how, indeed they were making up their own variables naming because WT had not published them yet.

I think this is a bit unjustly harsh to FSS here. They built their GCU support on top of the G1000 at a time when the GCU support in the sim hadn't even been launched. Knowing how long dev takes, they probably built it long before we even announced that it was coming on SU14. But it would have been impossible for them to do it in SU13 because that support simply didn't exist; there were no variables at all.

So FSS actually did something noteworthy and beat us to the punch of implementing the GCU, but it was just a case of unfortunate timing as I'm sure our implementation broke the internals they were hacking around to make the whole thing work.

Now, it is true that we were not contacted about this implementation, as I mentioned, and dev teams do tend to raise us on the bat phone in the support channels available in those scenarios, and we probably would have suggested to just hold off for a month or two, but there are also good potential business reasons not to do something like that; and it can also get prickly from a customer standpoint to leave a big feature out but not yet be able to tell anyone why. So I do cut them some slack here. Just bad timing through no particular fault of anyone in particular.

That being said, the events have been available on the devsupport site since they landed in the SU14 beta, so hopefully all developers are able to get their implementations fixed up in short order.

35 minutes ago, turbomax said:

"FlightSim Studio AG is a highly skilled development team" 🤣

have they in the meantime fixed the easy bugs or do we need to also help them with the correct link to their own online manual?

Not sure what is fuss about . Here is a correct link

https://docs.flightsim-studio.com/v/tecnam-p2006t/introduction/welcome

The Contrail app now says:
"We are currently uploading a new version of this installer. Please check back in a few minutes!"

It's been there for a while now.

5 minutes ago, sd_flyer said:

Not sure what is fuss about . Here is a correct link

I posted the correct link myself 2 weeks ago after the aircraft itself pointed to that missing link, after I had to go searching their website for a manual. the question was: have they fixed that after 2 weeks? (no access to my pc right now)

1 hour ago, MattNischan said:

I think this is a bit unjustly harsh to FSS here.

Hi Matt. Hope you are well and congrats to the entire Asobo and WT Team for SU14.  Quite impressive.

Now about my comments. A bit harsh?  Sure, if that’s how you see them I can go along with your POV.  My five years in Change and Release Management were in the Payment Card Industry, not the gaming industry, but the mechanics, deliverables and outcomes are similar. You have a broader and more context rich perspective in this case so I will defer to you

Unjust?  Can't go there.  There is nothing unjust about me calling out FSS’s self inflicted pain.  I have been working with FSS on this issue for over 10 days I estimate.  What started out as a wonky and failing AP (remember our convo Matt) evolved into this pile of manure that it now is.  None of it by my hands and  I have been warning them for at least four days of the impending code failure when SU14 goes from BETA to PROD.  FSS has had line of sight for many, many days so…

Harsh?  Maybe.  Unjust?  Nope.

Peace,

-B

 

There's definitely a lack of quality control at FSS.   You have the online manual still being a dead link, but also, the loading screen for the P2012 still makes reference to the P2006 in error.   The loading screen also refers to the user choosing "easy or realistic mode", which is again a feature of the P2006.. but the P2012 doesn't have that option in the EFB.   I told them about these during my efforts to try to get my P2012 activated.  If I were the dev, I'd cringe at things like these and get them patched up at the first opportunity (along with the link to the online manual). 

I think they're lacking a good, methodical, qualified project manager. 🙃

1 hour ago, JYW said:

There's definitely a lack of quality control at FSS.   You have the online manual still being a dead link, but also, the loading screen for the P2012 still makes reference to the P2006 in error.   The loading screen also refers to the user choosing "easy or realistic mode", which is again a feature of the P2006.. but the P2012 doesn't have that option in the EFB.   I told them about these during my efforts to try to get my P2012 activated.  If I were the dev, I'd cringe at things like these and get them patched up at the first opportunity (along with the link to the online manual). 

I think they're lacking a good, methodical, qualified project manager. 🙃

The typical" lets get this product to market to generate a bunch of cash(that can't be refunded), we'll fix it later" scenario? This is tarnishing a pretty good developers name and reputation. I'm pretty sure that if they waited for this plane to be ready before they released it it would have done wonders for the FSS name brand because this plane has so much potential, it really is a great looking plane, it just needs to work now. I now know I'll be waiting for extensive reviews for any of their future products before I buy them. This is not a cheap, low cost plane and they have had my money now for almost a month, got me this time. And. They are still selling it even though it doesn't work.......

I am impressed by their 2006, although I had similar problems updating through Contrail (other products on there are alright).  It is just that this saga is sending their reputation backwards a bit.  A pity! 

I want the 2012, but I won't purchase it until things are resolved.

5 minutes ago, bobcat999 said:

I am impressed by their 2006, although I had similar problems updating through Contrail (other products on there are alright).  It is just that this saga is sending their reputation backwards a bit.  A pity! 

I want the 2012, but I won't purchase it until things are resolved.

I think that when they do get the problems worked out they will have a really nice plane. I too have the P2006 and I can say it's one of my favorite planes, it's just too slow (no fault of FSS). I just think this plane was a little rushed to get to market, eventually it will be as good as the P2006 (we hope). I'd wait to purchase too....

15 hours ago, MattNischan said:

I think this is a bit unjustly harsh to FSS here...

Matt, I think you could make the Wall Street Crash sound not so bad.  I bet people like working with you and your propensity to not stress too much or place blame around too easily.  

Maybe we should all take a leaf out of your book a bit more often.

PS. It's a pity about the SR22 doors though!  

Edited December 6, 20232 yr by bobcat999

6 hours ago, Daytona125 said:

I too have the P2006 and I can say it's one of my favorite planes, it's just too slow

One of my favourites too... but yes, with a cruise speed of 135 KTAS, it must be the slowest twin in the world (excepting the Cri-Cri).   Still, mostly intended for training, where speed is less important and 12 GPH from a twin is extremely desirable.

We need Tecnam to offer the P2006 with 2 x Rotax 915 turbo-charged 141hp engines, IRL.  Then a mod could be created to up the power in the FSS P2006.   It would be a blast then!

Edited December 6, 20232 yr by JYW

Now been updated, to v1.0.3 - trying a quick flight and all seems ok so far.

Here's the change log from FSS's Discord channel:

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

Also, they say:

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

 

Edited December 7, 20232 yr by MorrisMinor