Natively Implement WT GNS 430/530 in All Asobo & Microsoft Aircraft

Discussion Hub Aircraft
, , , , ,
1

I know I’ve made a fuss of this all over this forum:

…and elsewhere.

I’ve had an offline private message conversation with mods over whether or not these should be tagged as bugs or wishlist items.

The thing is, the Working Title Garmin G1000NXi & G3X (minus the Pipistrel due to its portrait vs landscape display format) avionics are natively implemented across the board for these Asobo & Microsoft (40th Anniversary, LL, FF as applicable) aircraft. Why, then, hasn’t the same been done for the GNS-equipped aircraft?

The V35B, for example, is still sold on the Marketplace and it is still equipped with the Asobo GNS, why?

Perhaps this thread is a moot point as far as 2024 is concerned (I certainly hope so), but 2020 is still going to exist for a number of years.

Microsoft, could you please clean up these inconsistencies amongst your own aircraft?

I really do not understand why this continues to not get handled. I know these fixes are really not that time intensive.

9 Likes
Beech 18 using old GNS530
Which WT Add-ons To Install
2

that is a question for Carenado. they havent updated ANY of thier aircraft. Got tired of waiting so did it myself.

3

Personal Comments and Observations

This doesn’t help anyone on Console, but I immediately eschewed the GNS in favor of the GTN750, it made flying the V-tail so much more enjoyable.

I agree, the GNS units do need to be updated. The way I understand the backside of commissioned support goes - the subcontractor studio (i.e., Carenado, Inibuilds, etc) would do the work, but only if MS budgets it. So really, the buck stops at Redmond first to authorize and fund the work before the subcontractor can do anything, even if they wanted to in the first place.

1 Like
4

Could you explain how you did that? And would that be applicable to other aircraft as well, or just the V35?

5

Let’s take that question to this thread:

So this one can stay on track. If you read through it, it’s pretty easy to do.

1 Like
6

I’m not clear on who is responsible for Asobo-branded aircraft (local legends, famous flyers, etc) once they’ve been released to them by the 3rd party devs.

7

They aren’t Asobo branded

They are Microsoft branded.

8

Ok, fair point, but the intention remains the same - are the 3rd party devs responsible for updating them down the line?

9

In the case of the Pipistrel, that is an Asobo in-house aircraft if the aircraft’s OneStore directory name is anything to go by. It still has the Asobo GNS.

10

Apparently, it looks like a complete mystery.

I mean even getting bugs fixed is a complete crapshoot when it comes to these aircraft.

11

Yep. In that case, it’s the Asobo backlog (and however many teams it needs - i.e., WT to integrate - maybe, Art Team to redo any artwork) that’s likely driving that schedule.

12

Without getting off-topic it just seems there is a massive need for a “clean up” team to come through and address so many of these small fixes that just go left unaddressed for years.

1 Like
13

It took me 6 minutes to update 5 carenado panels. The gns Asobo and wt use the same artwork on the bezel. So at $110.00 an hour, carenado owes me $10.99 hahaha

3 Likes
14

The problem, in the case of the V35B, editing the panel.cfg to implement the WT GNS (or by using the add-on), it bugs the autopilot.

It needs to be properly coded to ensure that the AP remains operationally correct.

15

Slightly off topic but many freeware aircraft have had their G3X quicker than those we’ve paid for.

I’m not even including delays due to marketplace releases. Their own stores haven’t been updated (ORBX Blackwing as one example).

Why is it so hard?

16

Come to think of it, i havent even checked the milviz 310. Hmmm

17

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.