2 hours ago, vgbaron said:

This is the main issue with all these mods. It is fantastic that talented people are spending their time coming up with them but I fear that only a few are3 concerned about compatibility with other mods.

vgbaron,

I tend to somewhat disagree with this statement.  There is no doubt that this is a factor but I feel it is very few who adopt this attitude, and, in fact, most of the modders are, indeed, concerned about the impact their mods have on the community who adopt them. I very firmly believe that most of the modders have their hearts in the right place and a real asset to the simming community. Long may this remain so too. I also admit that I have probably taken this out of context and the rest of your advice is extremely relevant, as I am in the process of finding out. Please do not take this as a criticism.

I also feel that this is somewhat irrelevant, given the fact that there was no problem whatsoever with what I had in my community folder prior to the update. Also, given that fact alone, combined with the fact that I appear to be the only one afflicted with this problem, does not, in my opinion give rise to any suspicion regarding an addon developer. 

I am now suspecting a computer corruption of one of the files in the community folder during transfer/copy after the update.  

I am now in the middle of testing (a long process given loading times etc.) I have tested with the G36 mod only and that is ok. I have put in all my working title mods and the g36 is ok, Next is the Salty747, Longtitude, DA62 co pilots etc (one at a time) so I have a long way to go. I am getting there though and I wish to thank everyone who has offered a solution so far. 

Update to follow as testing continues.

Regards

Tony

OK guys,

Update.

Found the culprit ... Bonanza visible co-pilot.  I have deleted this from the Community folder and then reinstalled it from my mod folder. With that reinstallation everything is still OK.

So again, it looks like a computer glitch as I previously stated in my last post. 

I want to thank again everyone for their input., with particular reference to the advice leading to the process I have just completed. I have to admit, that until this advice was forthcoming, I was going round and round in circles and achieving absolutely nothing.

Guess who is a happy little Vegemite again?

Regards with absolute gratitude

Tony 

Just another example that underscores how mods can conflict with each other.

53 minutes ago, jabloomf1230 said:

Just another example that underscores how mods can conflict with each other.

If you read the post jabloom1230, you will/should have, noticed that this is entirely incorrect. 

The problem was a computer corruption after the update.  it was not a problem before the update and a full reinstallation of the problematic software (once found) fully corrected the problem.

It was definitely NOT a conflict in this case.

Tony

6 hours ago, marsman2020 said:

Highly recommend using the MSFS Addon Linker (https://flightsim.to/file/1572/msfs-addons-linker) to enable/disable mods and only enable exactly what you need on a given flight.

+1, absolutely +1.

I also found the "copilots" mod caused CTD for me.

Dave Hinson

14 hours ago, DaveH said:

I also found the "copilots" mod caused CTD for me.

Dave,

It is working fine for me now. Whilst I acknowledge it was the cause of my problems, it was not the problem. That was actually a corruption in the copying of the Community folder either to a new drive or back from that drive to the original drive.

May well be worth a delete and reinstall for you.

Regards 

Tony