Hello all,

I have mentioned this in another topic regarding the last update.

I have now spent some 5 very frustrating days since the update trying to get my Working Title G1000 to work without any semblance of success.

When I have it installed, all my G1000 equipped aircraft (default and Modded) suffer the same problem.  There is no speed indicated and the altitude and vertical speed indicator do not do anything.

To summarize the procedures and processes I have carried out so far.

1. After two days of failure to rectify, I uninstalled MSFS 2020, after moving the Community Folder to another drive. I then re-installed the sim, noting that the new download was the 79gib one.  All went well and I now had the new splash screen.

2.  Using only the stock Bonanza G36 I flew a normal flight and noted that both the airspeed and the altitude/Vertical speed worked normally.

3. Then I loaded Rob Youngs G36 Turbo and noted during the flight that the airspeed and altitude indications were normal,

4. I then loaded the Working G1000 mod and my problem was back.  I deleted the WT G1000 folder from the Community folder and the aircraft worked normally again. I then went to the WT Github site and downloaded the latest version (3.7) and reinstalled that.  The next flight in the aircraft produced the same problem.

Having installed and uninstalled the WT G1000 mod many times with exactly the same result, I believe that, logically, the problem is in the compatibility of the G1000 after the update.  However, I do appear to be the only one who is suffering from this.  I have no idea where to go from here.  The problem is not in the Community folder because the only items in there are the Rob Young mod and the Working Title G1000 and when I delete the WT G1000 the problem goes away.

I will further note that I have lost the splash screen but it has come back three times now on a one off basis and disappears for the next reload of MSFS2020.  I have absolutely no idea, how MS and Asobo have managed this inconsistency, but it has certainly added some novelty to my problems LOL

I would really appreciate any help at all with this.

Regards

Tony

You mention removing the WT mod but NOT the RY mod?  What happens when the only thing in the community folder is the WT mod(s) and nothing else with stock/base sim?

The splash screen has come and gone for me as well, so you are not alone on this.

Does the WT G1000 work in the stock C172?

Just now, Bert Pieke said:

The splash screen has come and gone for me as well, so you are not alone on this.

Does the WT G1000 work in the stock C172?

it sure does

Sir,

My error, That was done just after the first step of flying stock (no G1000) and then with G1000 installed  The problem is there with the stock aircraft and G1000.  The same process was applied and repeated with many of the G1000 aircraft (Default)

Tony

2 minutes ago, Bert Pieke said:

The splash screen has come and gone for me as well, so you are not alone on this.

Does the WT G1000 work in the stock C172?

No Bert,  none of the stock or modded aircraft work with the WT G1000 installed.

Tony

6 minutes ago, himmelhorse said:

No Bert,  none of the stock or modded aircraft work with the WT G1000 installed.

Tony

I would focus on the stock aircraft for this test... just to rule out the RY mod.

Having said that, I am not seeing what you are seeing.. flying V3.6.. have not tried V3.7.

Edited June 1, 20215 yr by Bert Pieke

Just now, Bert Pieke said:

I would focus on the stock aircraft for this test... just to rule out the RY mod.

Having said that, I am not seeing what you are seeing..

Bert,

I was pretty sure you and everybody else are not seeing what I am seeing.  I am the only one that I can see who is even talking about it, other than the people who are responding to this.

One other thing I have noticed is that since the update the DA62 (stock) has the MFD and the PFD reversed. This, like my speed and altitude problems have only occurred since the last update.

Tony

4 hours ago, himmelhorse said:

One other thing I have noticed is that since the update the DA62 (stock) has the MFD and the PFD reversed. This, like my speed and altitude problems have only occurred since the last update.

Hi Tony,

Just tried the DA62 (which I never fly..) and can see nothing amiss with either the PFD or the MFD..

Hope someone can jump in with something more helpful  😉

 

@himmelhorseThis is a  big shot in the dark. Please try this - can do no harm.

Remove the file Content.xml from this path :   C:\Users\.....\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache    [MS Store version]

The file will be recreated on next start of simulator.

It worked for me when I experienced weird things in MSFS2020 a little while ago.

I hope it helps.

SAPilot,

Many thanks for that.

I will try that in the morning .... time for a hard earned wee snorkle (medicinal Port LOL) and after that I would not trust myself to even try that. I have MY priorities right LOL

At five in the evening, I do enjoy a little loud music and  my mate Al Cohol

I will advise a little later.

Regards

Tony

13 hours ago, himmelhorse said:

One other thing I have noticed is that since the update the DA62 (stock) has the MFD and the PFD reversed.

Are you certain you are using the latest WT G1000 mod?  0.3.7.  I had this happen with the DA62 as well, however that was after a sim update and before WT responded with an updated mod.  And I believe that was back around mid-December.  The updated WT mod at that time cured the MFD and PFS reversal.

I stopped using the WT G1000 after SU4. They updated the original G1000 and seems to work great: 

 

16 hours ago, himmelhorse said:

Hello all,

I have mentioned this in another topic regarding the last update.

I have now spent some 5 very frustrating days since the update trying to get my Working Title G1000 to work without any semblance of success.

When I have it installed, all my G1000 equipped aircraft (default and Modded) suffer the same problem.  There is no speed indicated and the altitude and vertical speed indicator do not do anything.

To summarize the procedures and processes I have carried out so far.

1. After two days of failure to rectify, I uninstalled MSFS 2020, after moving the Community Folder to another drive. I then re-installed the sim, noting that the new download was the 79gib one.  All went well and I now had the new splash screen.

2.  Using only the stock Bonanza G36 I flew a normal flight and noted that both the airspeed and the altitude/Vertical speed worked normally.

3. Then I loaded Rob Youngs G36 Turbo and noted during the flight that the airspeed and altitude indications were normal,

4. I then loaded the Working G1000 mod and my problem was back.  I deleted the WT G1000 folder from the Community folder and the aircraft worked normally again. I then went to the WT Github site and downloaded the latest version (3.7) and reinstalled that.  The next flight in the aircraft produced the same problem.

Having installed and uninstalled the WT G1000 mod many times with exactly the same result, I believe that, logically, the problem is in the compatibility of the G1000 after the update.  However, I do appear to be the only one who is suffering from this.  I have no idea where to go from here.  The problem is not in the Community folder because the only items in there are the Rob Young mod and the Working Title G1000 and when I delete the WT G1000 the problem goes away.

I will further note that I have lost the splash screen but it has come back three times now on a one off basis and disappears for the next reload of MSFS2020.  I have absolutely no idea, how MS and Asobo have managed this inconsistency, but it has certainly added some novelty to my problems LOL

I would really appreciate any help at all with this.

Regards

Tony

This only seems to be a problem if you have live ai traffic turned on. I had this same problem and it was driving me crazy. 

4 hours ago, fppilot said:

Are you certain you are using the latest WT G1000 mod?  0.3.7. 

fppilot,

Very, Very, very certain.  I have downloaded it three times now, believing that I may have had a glitch in the system.

Tony