_{Hello all,}

_{With their usual remarkable efficiency and absolute consistency, MSFS have posted yet another flawed update.}

_{Yesterday I had some lovely flights in the G37 Turbo and both the DA62 and the DA62x.}

_{This morning I was greeted with an update which I downloaded and installed.}

_{My first flight G36 Turbo out of YBCS and my MFD/PFD is black.}

_{I tried the da62x ... it has no disappeared from my list of aircraft. Thanks guys.}

_{I tried the DA62 and got the same black MFD and PFD. I reinstalled the DA62x and got the same black MFD and PFD.}

_{I thought that the common denominator for this problem was the WT G1000 so I removed that. No difference with any of the aircraft.}

_{Next step was to delete the DA62x and the G36 (both modded and with the G1000) and go back to the stock aircraft.}

_{No change at all.}

_{I then went through my aircraft and the following aircraft are all the same.}

_{1. Bonanza G36}

_{2. Diamond DA62}

_{3. Baron B58}

4. Cessna 172 G1000

5. KingAir 350

I have deduced that the WT G1000 mod is not the problem

I do not believe the modded aircraft are either but after spending at least 6 hours trying to sort this mess out, I have hit the brick wall.

I understand the need for updates but why do I have to go through this unholy word not allowed after every update?

Any possible solutions are, as usual, appreciated.

Tony

@himmelhorse

In case you’re wondering where your topic when, I moved it from Hangar chat to the MSFS forum. Not sure why it was posted in Hangar.

9 minutes ago, cmpbellsjc said:

@himmelhorse

In case you’re wondering where your topic when, I moved it from Hangar chat to the MSFS forum. Not sure why it was posted in Hangar.

A senior moment I think.  I am not sure why either LOL

Thanks mate

Tony

sofar i dont see any problem, but then i dont use modded aircraft.

as always try unmodded first.

wim123,

If you have a quick look at my post you will see that only two of the aircraft mentioned are modded and that the modded aircraft were removed for testing. Going back to the stock aircraft did not alter anything either. Please note that WT G1000 was also removed. None of this made a difference.

Tony

15 minutes ago, himmelhorse said:

wim123,

If you have a quick look at my post you will see that only two of the aircraft mentioned are modded and that the modded aircraft were removed for testing. Going back to the stock aircraft did not alter anything either. Please note that WT G1000 was also removed. None of this made a difference.

Tony

ok , i will try 172 and g36 laters.

6 hours ago, himmelhorse said:

Any possible solutions are, as usual, appreciated.

Smth is wrong with liveries.

7 hours ago, himmelhorse said:

_{Hello all,}

_{With their usual remarkable efficiency and absolute consistency, MSFS have posted yet another flawed update.}

_{Yesterday I had some lovely flights in the G37 Turbo and both the DA62 and the DA62x.}

_{This morning I was greeted with an update which I downloaded and installed.}

_{My first flight G36 Turbo out of YBCS and my MFD/PFD is black.}

_{I tried the da62x ... it has no disappeared from my list of aircraft. Thanks guys.}

_{I tried the DA62 and got the same black MFD and PFD. I reinstalled the DA62x and got the same black MFD and PFD.}

_{I thought that the common denominator for this problem was the WT G1000 so I removed that. No difference with any of the aircraft.}

_{Next step was to delete the DA62x and the G36 (both modded and with the G1000) and go back to the stock aircraft.}

_{No change at all.}

_{I then went through my aircraft and the following aircraft are all the same.}

_{1. Bonanza G36}

_{2. Diamond DA62}

_{3. Baron B58}

4. Cessna 172 G1000

5. KingAir 350

I have deduced that the WT G1000 mod is not the problem

I do not believe the modded aircraft are either but after spending at least 6 hours trying to sort this mess out, I have hit the brick wall.

I understand the need for updates but why do I have to go through this unholy word not allowed after every update?

Any possible solutions are, as usual, appreciated.

Tony

It's obvious it's something with your mods. No one else is reporting this problem 

1 hour ago, TENPATROL said:

Smth is wrong with liveries.

With ALL the aircraft mentioned and even when deleted???

 

59 minutes ago, devgrp said:

It's obvious it's something with your mods. No one else is reporting this problem 

See the above.  I have deleted the DA62X and the G36 mods and this happens with those deleted and with the default da62 and G36.

I appreciate that I appear to be the only one going through this but it happens with every update. I may wait for the next update to fix this problem and break something else for me.

Tony

tried several aircraft np, all screens turn on when i turn avionics on, c172, g36, caravan, all ok.

i dont know why it doesnt work with you, but did you really clear the comm folder..something else not connected to these 

aircraft can bork things. 

 

 

40 minutes ago, himmelhorse said:

With ALL the aircraft mentioned and even when deleted???

 

See the above.  I have deleted the DA62X and the G36 mods and this happens with those deleted and with the default da62 and G36.

I appreciate that I appear to be the only one going through this but it happens with every update. I may wait for the next update to fix this problem and break something else for me.

Tony

Make sure you using the latest updated wt and plane mods. 

Anything unusual in content manager?

7 minutes ago, rka said:

Anything unusual in content manager?

I had a simconnect failure this morning that kept the sim from starting, a day after the update.  It was fine immediately after the update yesterday.  I was not expecting yesterday's update so had not emptied my Community folder (via the Addon Linker).  So immediately after this morning's failure I launched Addon Linker to remove all Community folder items hoping that would cure the failure.  Upon launch it was immediately apparent that two necessary links in the Addon Linker had been broken. Addon linker started with its options window and those two selections were blank.   I had to reestablish the link to my Community folder location (Windows Store version of MSFS), and the link for My Addons Folders.

And then....

I was able to launch MSFS successfully and found that the update had reinstalled the Asobo Aviators Club liveries that I had uninstalled and found a new set of Asobo Kenmore liveries that I had not noticed before.  I have summarily uninstalled both. 

My G1000, GNS, and G3000 avionics, all with mods, are working fine in the aircraft I checked after all of the above.

2 hours ago, himmelhorse said:

With ALL the aircraft mentioned and even when deleted???

ALL liveries - also go to content manager and delete aviators club, test pilot liveries, kenmore etc.

 

 

Edited June 25, 20214 yr by TENPATROL

Well guys,

What a pleasant surprise I got this morning.  

Logged into MSFS and went to Profile/Content Manager to find a load of effin garbage in the form of unwanted liveries and other content that I had previously deleted. some of them were duplicated up to three times.  I went through the lot and deleted previously deleted stuff and all the liveries that I did not want. 

These guys have more nerve than a toothache to do that.

I do, however, want to thank those who suggested that I check the Profile/Content Manager. After further checking, I have noted, in another thread, that this stupidity will not be repeated in the next update. I think they are probably working on something just as silly though and one which is inevitably destined to break someones Sim.   

However, I still have black MFD and PFDs in the aircraft previously mentioned.

Tony