A direct quote from mrtommymxr -

The 42 makes my 62 mod look bad.
The 42 gave me the chance to do everything from the ground up.

9 hours ago, JYW said:

Good to know that it is realistic to have the GFC700 in the older Centurion 2.0 -engined version too

It definitely is. A friend sent me the official aircraft manual of PH-DTM, a 2006 DA-42. The manual states it is meant for DA-42 without AP or with KAP140; it also mentions a separate manual is available for GFC700 equipped DA-42 aircraft, so it appears the GFC700 was an option from early on. But I agree when googling panel shots you come across a lot of KAP140 in the older aircraft.

7 hours ago, UrgentSiesta said:

I was wrong. From the Dev:

All of this has been made from scratch. The modelling, texturing and systems/NXi all from scratch using various sources of information.

Thanks for this exact quote from Jacob from the COWS team.

I also found this quote from kaosfere from the Working Title team on the time it took them to develop the G1000 NXi in the Working Title Discord chat:

https://discord.com/channels/750764704175226992/764259309106102293/1206263747992100954

So the G1000 NXi for Working Title took them 10,000 man hours. And 1.5 years of work full time for a single developer is 3000 man hours, according to kaosfere.  So if a single developer were to work on the Working Title G1000 NXi, that's (3000 hours)/(1.5 years) = (10000 hours)/(X years), so that's roughly 5 years  for a single developer to complete the Working Title G1000 NXi. Granted, Working Title also did the general framework, and the framework has been used on the other Working Title Garmin avionics, so if Jacob wasn't doing a general framework that could be reused on other projects, he could save some time.

But still, kaosfere above would be impressed if Jacob from Cows could do a feature parity G1000 NXi to the Working Title in a shorter time. Granted, if you read on in the Discord chat, both kaosfere and Matt Nischan assumed that Jacob was developing off the XP 12 G1000 and using it as the base (so some of the functionality was already done by reusing the XP 12 G1000), which seems to not be the case with your direct link to Jacob's quote above. Also, I think somebody else in the Working Title Discord chat mentioned that Jacob started working on the G1000 NXi back in September of 2022? I don't know how accurate that information is, but if Jacob started from scratch back in September of 2022 on the G1000 NXi, he has been working on the G1000 NXi for only 1.5 years. And of course if Jacob is the sole programmer on the Cows team, Jacob had other programming duties to do, such as developing and integrating the DA42 for MSFS, programming the flight model and ground handling, etc.

Anyways, I really am interested to see when Cows releases the DA42 for XP 12, and if the G1000 NXi Jacob has worked on is feature parity with the Working Title G1000 NXi. That would be a very impressive job from a single programmer if they can release this year, Jacob would be some kind of super programmer if he does it 👍.

Edited February 12, 20242 yr by abrams_tank

12 hours ago, regis9 said:

That’s a good question, but hopefully it’s an easy fix for them as the right engine spot is easy to use.

The clickspot for the engine start will be corrected, I have seen it on their fixes list.

Regarding their G1000 implementation, it would be nice to add to it the Checklist and perhaps also the possibility to move & scroll the charts, like the VFR maps.

8 hours ago, Vali said:

Regarding their G1000 implementation, it would be nice to add to it the Checklist and perhaps also the possibility to move & scroll the charts, like the VFR maps.

You should be able to zoom and scroll the charts using the range knob of the G1000. You have to click the knob first to activate the pan cursor. Then you should be able to pan.

1 hour ago, Malaromane said:

You should be able to zoom and scroll the charts using the range knob of the G1000. You have to click the knob first to activate the pan cursor. Then you should be able to pan.

Indeed, thanks for the hint, I have tried it again.

I sure hope they come up with better implementation for the Aileron, Elevator & Rudder AXIS for FSUIPC. The readme states using FSUIPC or SPAD you need to use their LVAR's in the folder. Unfortunately they are missing the elevator and I have no idea how to implement them in my FSUIPC which is what I use for my controllers. I can find their LVARS for the other button options but none of the AXIS items show in the list. Of course, even if they did, I have no CLUE as to how to use them this way. 😕😕😕.

What is the proper call sign on the radio, Diamond or Twin Star? Or??

I heard in some video Twin Star (at least in US), e.g. at 5:38:

 

did you guys know you can put headphones on in this plane to drop the sound to near zero

I did not know that. Leaning cool stuff everyday.

 

 

 

6 hours ago, rfelger said:

What is the proper call sign on the radio, Diamond or Twin Star? Or??

In the US, on initial callup, you can say a few things:

N12345

Diamond 12345

Twinstar 12345

As an air traffic controller, I'd recommend saying "twinstar 12345" because it clues us in that you are a twin, increasing situational awareness too so like if you have an engine failure, we would know you still have one good engine.

Edited February 14, 20242 yr by ryanbatc

Update now on Orbx Central - 

 

One of the best aircraft to drop on the sim with virtually no hype whatsoever., and one not to miss. 

2 minutes ago, Car147 said:

One of the best aircraft to drop on the sim with virtually no hype whatsoever., and one not to miss. 

Agreed. And already a few minor faults corrected just a few days after release. This one is special.