MarkoH01: Apparently this bug is quite rare but imo it is also extremely important and annoying and therefore should be fixed asap.
So it happens only occasionally (rarely), not all the time? Do you know how to reproduce the problem?
Hopefully GOG is able to catch why it happened with that particular game, or reproduce the problem. Rarely occurring problems are the worst. Just last week at work I was troubleshooting a problem with one of our suppliers as their product showed a problem that I don't recall seeing elsewhere. They really much wanted to know how to reproduce the problem, but I had no idea, I just new it had happened at least once in one part of the system.
In the end we had to close the ticket as not reproducible, and with a workaround so that I wasn't blocked by that incident.
MarkoH01: My sincere apologies but it seems as I was wrong when saying that the bug is well known. The guy who told me about it sad that it is well known but only meant that he knows the bug quite well - he never told GOG.
"The guy" being a game developer/publisher, not GOG staff?
MarkoH01: My sincere apologies but it seems as I was wrong when saying that the bug is well known. The guy who told me about it sad that it is well known but only meant that he knows the bug quite well - he never told GOG.
ReynardFox: So why did they not tell GOG? We all know they're really good at being deaf, but surely passing the information on at all would be better than sitting on it...
Maybe they were busy that they couldn't or didn't want to use any time to troubleshoot it with a "secondary" store like GOG... Happens to the best of us, I also had to find a timeslot in my timetable to report a problem to our supplier, and later troubleshoot it with their staff on a Zoom conference...