I love the sceneries but your updaters and system of upgrading leave a lot to be desired.
The upgrade system works perfectly and, in fact, it's what allowed to fix the problem with a simple run of it, which downloaded only a single updated file, which fixed the crash.
The real reason of the problems some of your were having, it's because you were all still running on P3D 4.1, since the problem happened only because we used some calls specific to 4.2 without realizing it, which caused 4.1 to crash. Nobody using 4.2 had any problem.
P3D 4.1 was so bugged with GSX, because of the missing texture problems, that we assumed most GSX users would have upgraded to 4.2 by now and, in fact, LM suggest to ALWAYS update to the very latest version, as soon as possible.
And why some users haven't updated to 4.2 ? We know why: because of compatibility issues with some other addon!
So, why we are supposed to test and guarantee that everything will always work with each and every version of the sim, when others don't even bother to support the
current one ? You cannot even download the 4.1 installer anymore: LM will only let you download the old Clients, with a suggestion NOT to use them.
If you think its just me, you should read some of the forums out there regarding them.
Users like to complain about it, ONLY because a tiny minority of what our software does, is to handle activation. This is not, of course, what is causing problems, because 99% of what our software does, is totally unrelated to activation, and any software that does such things CAN crash, because it's a .DLL, so it can bring down the sim with it, just like any other 3rd party .DLL addon module.
Interesting how nobody "on forums" said anything similar when a new FSUIPC build totally killed the sim, and this JUST happened when P3D 4.2 came out:
https://forum.simflight.com/topic/84951-issue-with-fcuip5-with-p3d-v42/And, from Pete's reply:
Seems to be a problem of multiple SimConnect clients not working well together and especially messing up menus and displays.
So, it was an issue very similar to this one: the mixup of using different versions of the SDK. And our issue was fixed on the same *NIGHT* it was reported.
And the only reaction from user were jokes about him being on vacation...and FSUIPC *is* a commercial program too, that when it fails, it will render unusable way more products that FSDT ones and in some cases (like that one), would prevent the whole sim from start. But nobody complains too much about it, just because it's not used by protect products.
