An odd problem has arisen with the Milviz 310 and TDS gtn combination on my system, seemingly since applying the recent MSFS updates. The Milviz aircraft accepts and displays two copies of the Garmin GTN 750, and the TDS software settings allow one to configure both a Unit 1 and Unit 2 of the Garmin devices. Recently, when running the Milviz 310, I have found the Unit 2 device to be fully functional, but not so for Unit 1.  With Unit 1, the Garmin opening splash screen shows as usual, but clicking the continue button has no effect.  It’s essentially a dummy unit. Is anyone else having this issue? Is this related to the MSFS updates? Any known workaround? I have applied all  urgently available updates to both the Milviz and the TDS software, have tried reinstalling both, but no luck. 
Thanks for any tips,

Rich
 

13 minutes ago, rlashier said:

An odd problem has arisen with the Milviz 310 and TDS gtn combination on my system, seemingly since applying the recent MSFS updates. The Milviz aircraft accepts and displays two copies of the Garmin GTN 750, and the TDS software settings allow one to configure both a Unit 1 and Unit 2 of the Garmin devices. Recently, when running the Milviz 310, I have found the Unit 2 device to be fully functional, but not so for Unit 1.  With Unit 1, the Garmin opening splash screen shows as usual, but clicking the continue button has no effect.  It’s essentially a dummy unit. Is anyone else having this issue? Is this related to the MSFS updates? Any known workaround? I have applied all  urgently available updates to both the Milviz and the TDS software, have tried reinstalling both, but no luck. 
Thanks for any tips,

Rich
 

Do you use the PMS GTN at all?  If so disable it.

I remember something like this. Do you have the headwind 787 installed? It's either that or what Ryan said. I remember them saying that Milviz needed to fix it in a patch, but who knows.

Edited December 2, 20223 yr by G550flyer
correct

One more consideration.. If the above does not work.. disable the WT GNS mod In Content Manager, it can interfere with the GTN.  (Even if you did not install it, it may have been forced upon you as an MSFS update..!)

Or, what I have done.. edit the panel.cfg file to prevent the GNS from loading:

[VCockpit04]
size_mm                = 320,234
pixel_size            = 320,234
texture                = $GNS530_Screen
//htmlgauge00=NavSystems/GPS/AS530/AS530.html,         0, 0, 322,236

[VCockpit05]
size_mm                = 350,190
pixel_size            = 350,190
texture                = $GNS430_Screen
//htmlgauge00=NavSystems/GPS/AS430/AS430.html, 0, 0, 350, 190

Edited December 2, 20223 yr by Bert Pieke

8 minutes ago, Bert Pieke said:

disable the WT GNS mod, it can interfere with the GTN.

Had the same problem (and the autopilot did not work either) and this solved it for me.

Thanks gents for your quick responses. I have not used either the PMS gtn nor the Headwind 787. I’ll give Bert’s solution a shot when I next fire up the sim. 
You guys are great for all the support you provide here. MSFS would leave me totally frazzled we’re it not for this forum. 
Kind regards,

Rich

Quick question Bert. Did you in any way edit the gns references in the panel.cfg file or did you just delete them altogether from the panel.cfg file?

I see right now there is a new update in the Content Manager for the WT GNS430/530. Hopefully it might fix this incompatibility….

As great as their GNS430/530 is, it breaks the TDS GTN750 and I might as a result uninstall the WT option from the Content Manager and go back the the PMS version as then I at least get to use the TDS GTN.

Bert’s option is good but then you need to do the edit on every aircraft that uses the TDS.

Edited December 2, 20223 yr by RaptyrOne

1 hour ago, rlashier said:

Quick question Bert. Did you in any way edit the gns references in the panel.cfg file or did you just delete them altogether from the panel.cfg file?

Dont delete the text, just use the // to have the lines of code ignored as in Bert’s example above.

Then it is just as easy to undo.

Thanks.  That should take care of it. 

1 hour ago, RaptyrOne said:

I see right now there is a new update in the Content Manager for the WT GNS430/530. Hopefully it might fix this incompatibility….

As great as their GNS430/530 is, it breaks the TDS GTN750 and I might as a result uninstall the WT option from the Content Manager and go back the the PMS version as then I at least get to use the TDS GTN.

Bert’s option is good but then you need to do the edit on every aircraft that uses the TDS.

I don't think it will directly fix it.  Looks like a dev (or Bert LOL) would have to edit something.  WT mentioned use of LVARs to deactivate the WT from loading in an aircraft.

Just to close the loop, Bert’s fix to the panel.cfg file did the trick. Both gtn units are now operable in the C310.  Thanks again for the help. 
Rich

1 hour ago, ryanbatc said:

WT mentioned use of LVARs to deactivate the WT from loading in an aircraft.

That is yet one more way to prevent the GNS units from loading in the aircraft.. whichever way you find easier..

Good news about the LVARS is that Milviz can code this into the aircraft, so that no user edits are required... next update?

2 hours ago, RaptyrOne said:

Bert’s option is good but then you need to do the edit on every aircraft that uses the TDS.

For now, that is the case.. If the various addon vendors (Carenado?) get familiar with this, they can do this as part of the design.

Possibly, TDS could force this variable in the GTN code... 😉

Edited December 3, 20223 yr by Bert Pieke

7 hours ago, rlashier said:

An odd problem has arisen with the Milviz 310 and TDS gtn combination on my system, seemingly since applying the recent MSFS updates.

Out of curiosity, Rich, did you update the 310 to its latest version?