It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
This problem is on WL3:DLR for me. Keep getting this message during startup and it says it might affect gameplay. I'm assuming that leads to the issue I am having where I play a few trunes and then the game crashes. Tried installing to my C: drive insteadd of D:. Next thing is to intsall it outside of the GOG Galaxy environment. Any help/thiongs to try appreciated. At least WL2 Deluxe is working fine for me.

Red
Post edited January 03, 2020 by Redhanded67
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
Redhanded67: This problem is on WL3:DLR for me. Keep getting this message during startup and it says it might affect gameplay. I'm assuming that leads to the issue I am having where I play a few trunes and then the game crashes. Tried installing to my C: drive insteadd of D:. Next thing is to intsall it outside of the GOG Galaxy environment. Any help/thiongs to try appreciated. At least WL2 Deluxe is working fine for me.

Red
I get the same error message and have a great PC also. The game also crashes on me, probably 9 times in 10. Then I will get that one game that allows to play the game. But I save constantly, so if it does crash, I haven't lost much progress.
This error always existed. I have a disc version and I would get that error even on Windows Vista. Nevertheless, it never affected my gameplay.

I played Gog version extensively on my Windows 10 machine and I still get that error, yet the game does not crash. And I bet that everyone who plays that game on modern machine gets this error.
I have both disk & GOG versions and I get that message also. It has never affected my gameplay and never had the game crush at any time.
Have you tried installing it to a disk with LIMITED space?
E.g. create a new drive (or maybe even use a USB thumb drive) with only 1 (one) single GB of diskspace.

My guess would be that the detection algorithm can't stand too large numbers of free bytes and rolls over, giving a negative number.