Posted December 01, 2018
Hi!
I recently bought the Zeus + Poseidon game on GOG, and since the November 29 update, I get a "Unable to save!" message whenever I start a scenario. (I'm on Windows 10 1809)
I also replaced my old hard drive for an SSD since my last game, so maybe this is the cause of the problem, but seeing that the November 29 update brings changes to the security of GOG folders and certificates, I feel like the GOG Galaxy client update is probably responsible for the new save bug I experience, rather than my upgrading to an SSD.
The popup "Unable to save!" appears as soon as I launch as scenario, but also appears if I try to save manually.
I tried giving the write permissions to every users and groups listed in my Security tab of the Zeus and Save folders, without success.
You can find screen captures of the message (in JPEG due to the file size limit) attached to this post.
Do you also experience this problem? Could you fix it?
Thanks in advance!
I recently bought the Zeus + Poseidon game on GOG, and since the November 29 update, I get a "Unable to save!" message whenever I start a scenario. (I'm on Windows 10 1809)
I also replaced my old hard drive for an SSD since my last game, so maybe this is the cause of the problem, but seeing that the November 29 update brings changes to the security of GOG folders and certificates, I feel like the GOG Galaxy client update is probably responsible for the new save bug I experience, rather than my upgrading to an SSD.
The popup "Unable to save!" appears as soon as I launch as scenario, but also appears if I try to save manually.
I tried giving the write permissions to every users and groups listed in my Security tab of the Zeus and Save folders, without success.
You can find screen captures of the message (in JPEG due to the file size limit) attached to this post.
Do you also experience this problem? Could you fix it?
Thanks in advance!
Post edited December 01, 2018 by pascallaprade
No posts in this topic were marked as the solution yet. If you can help, add your reply