PR is the most critical thing they can do for now, because without PR they will never get the required support which is needed for "preservation".
However, not even that one was done "right"... there is
no link to the media on the first post... somehow awesome how hard someone can fail, excuse me.
Nonetheless, we have to understand... they are probably very short on personnel, while on some bigger platforms where tons of cash can be salvaged... those companies might have troubles "turning down new applications from potential employees"... nonetheless... as soon as those big companies are not anymore happy with the profits, they may instantly wipe up to 10% of the "weakest" employees... and thats it for them. Similar stuff was happening at CDPR already... as soon as they has been bloated up way to much. So... becoming big is always a 2 edged sword.
I think more important is to become sustainable and rather "keep it slow but steady" instead of "fast yet unstable".
SilentMRG: Do you know DxWrapper?
https://github.com/elishacloud/dxwrapper Maybe this wrapper can help you. It has two configuration lines (WinVersionLie and WinVersionLieSP) that start the game without having to use compatibility modes via ".exe/shortcut". The GC 2 error is an exception error, from what I saw in your other post, so I think using the "HandleExceptions" line of DxWrapper is a possible solution.
No, Ground Control
2 (two) does not work with this "trick". You can be sure, if it would work by just adding a few files... it would be revealed to the gamers already. It simply did not work... and the reason why there are like 100 different "always inferior" solutions is because this game is simply UNSTABLE on a modern OS. I can not say what it does exactly... for this to know we would need the source code or a very demanding "reverse engineering" (which is usually a gray area if not officially allowed... which is almost never the case). So, the solutions the users was handing out was simply in some way able to improve the lack of stability a bit... and the main reason for the lack of stability is because it does look out for devices on the OS and in general it is making way to much "bootup checks" and because a new OS... especially with up to 10 USB devices attached... is that complicated... this "outdated game code" will simply lose its "sanity"... finally get unstable.
The original devs simply was pretty progressive and had in mind "we will make a top notch engine able to automatically detect and deal with any stuff... " while this was top notch those "old days".... today it is totally outdated and even creating unnecessary issues as it does more checks than absolutely necessary. Reason why the "more simple" engine of the first title still works fine... but not the "advanced engine". Sometimes it is better to be simplistic in nature if future compatibility can not be given. From a philosophical perspective i do understand the stuff pretty well but not sure what can be done in a purely technical manner.
Best solution is probably simply to create a new engine that is based on the old engine but sufficiently updated to a modern OS.
This issue can happen to a lot of games in the future... so i would see it as a "warning"... which is very relevant to the current topic.
