That would be great if Virtuali could help us because I don't understand why they didn't experience this issue while users does.
The question is not why I (or anybody else at FSDT) are not experiencing this. The question is why only A FEW users, of the several *thousands* that downloaded the update, are experiencing this.
Without even mentioning, is not even really sure that "this" really means. THIS post reported a very specific problem, indicated in the error log, which is a lot of "exception UNRECOGNIZED_ID" errors, which are Simconnect error reports, which very strange reference parameters we cannot relate to GSX, as if Simconnect was just acting up.
There are other posts here, saying "I Have a the same problem", because the OP referred to "unresponsive menus", but this doesn't mean in any way the problem is the SAME, because only the OP posted his log file. The unresponsive menus is just the effect, not the cause of the problem itself.
Instead, ALL the other posts about unresponsive menus, where users took the time to post their Couatl.LOG file, seemed to confirm THEIR problem (which is BY FAR, the more common one), is instead related to something blocking the cache regeneration process. Some users have confirmed THIS (different) issue was fixed by excluding all the sim folder from the antivirus realtime scanning.
Since we haven't been able to replicate any of these problems, the only way to test it would be on the user's system, with a Teamviewer session. If users don't want to cooperate, after all our repeated invitations, they simply cannot expect or demand we would be able to fix a problem that doesn't happen to us or to the vast majority of users that downloaded the update.
To those that said "I have the same problem", please verify this is the case, and compare YOUR Couatl.LOG file the one the OP posted here. If you don't have the long list of "exception UNRECOGNIZED_ID" error messages in your Couatl.LOG file, then you DO NOT have the same problem, so it's very likely it's instead related to the problem with the cache regeneration, that is being discussed on a separate thread, so you better post it there.
And again, to ANYONE with this problem, I'll repeat again my availability for a direct check on your system with Teamviewer, which is the only chance you'll have to have this fixed (for you AND for your fellow users with the same issue), because we haven't been able to replicate it in ANY WAY.
Perhaps it's caused by a conflict with some other product all of you with this issue are using, that we are not aware of, but it doesn't really make any sense to ask to each one "which other addon you have installed ?" and have it test multiple configurations, when I could check it way easily and much faster with Teamviewer.
Please PM me to arrange a Teamviewer session, because there are no other ways I can see right now to have it fixed it. A bug which can be reproduced (and being able to reproduce it on an user's system on a Teamviewer session IS enough), can probably be fixed VERY quickly. A bug that cannot be reproduced, cannot be fixed, it's simple as that.
So, again, please offer your cooperation, for your own's ( and the other FEW users with similar issue) sake.
