I think this is absolutely a fair point. At the end of the day, that decision comes down to Jorg deciding that something like the G1000 is part of the platform, and that a great version of that should be available to all aircraft designers, as it is so ubiquitous. I wouldn’t say our access to the sim code is an enormous advantage here: we’re still building what we plan on building totally within the sandbox. And if APIs get added that enable us, that means they enable everyone. And, it’s hard to argue that a faithful recreation that does all the things the original does is a bad deal for simmers, too. After all, the core reason to enable developers is because it’s good for simmers, not just developers for their own sake. If it turns out our instruments suck, then I’m sure there will be a plenty vibrant market for enhanced versions, either in paid or mod form.
But not only that, there are a ton of other instrument stacks out there, and nobody is saying WT has to build them all. There’s plenty of space for other folks to come in and help build out the platform, should the team decide that some other stacks should also be elevated to the platform level for the good of other aircraft designers and simmers.
On this, you and I strongly, strongly disagree, and if that statement still holds true in a year or two, I haven’t done my job. I’ve been saying this since before we joined the team: I don’t think folks understand what is already possible and what little is left to enable true 1:1. It’s a list I can probably count on just one hand.
-Matt | Working Title