Whenever I enter the design page and set up the module I'm trying to create, when I hit the 'OK' button to start working on it the game crashes and logs itself out. It used to work but now Ican't use it. Any suggestions? I've already reloaded it.

Hey, I just downloaded the newest installer from GOG and tried it out myself, on my Win 8.1 64-bit desktop PC as well as my Win 10 64-bit laptop. On both rigs, I had the same issue as you. However, I still had FRUA installed on my desktop, from a previous GOG installer, and in that version creating a new module worked fine, so the issue must be related to the new installer and therefor something on GOG's end, and it probably affects everyone who's using the newest version (I see the installer was updated in March 2019, for cloud save functionality, although I'm not sure if that could be a cause). This should definitely be brought to the attention of Support in any case.

Could you or anyone else open a support ticket and keep others here up-to-date about what they have to say about it? I'd do it myself, but I'm not sure if I will have the time to tinker with FRUA next week, in case they ask to try different things on our end .... :/

So, did someone contact support about this yet?

Did you try turning off the cloud saves overlay (i.e., change the mount command to just mount c ..)? Or copying the conf file from the old, working version?

I don't have the same problem, but I use Linux (and gog doesn't support Galaxy anything, including "cloud saves" on Linux) and do things my own way (but not much differently from gog).

So far, I didn't do anything yet, I didn't have time to look into it last week. Those seem like good suggestions, but pardon my ignorance, where would I find the mount command? Do you mean the line in the "Launch Unlimited Adventures" shortcut ("C:\...\Unlimited Adventures\DOSBOX\DOSBox.exe" -conf "..\dosbox_ua.conf" -conf "..\dosbox_ua_single.conf" -noconsole -c "exit")?

Copying the conf file from the old, working version - for today I've already shut down the desktop PC where the old files are stored but I can try that tomorrow, thanks!

In the file dosbox_ua_single.conf in the game directory. Open it with notepad or whatever plain text editor. Find the line that says "mount c "..\cloud_saves" -t overlay" and remove it or prefix it with a # to comment it out. I guess the "mount C .." is probably already there. If not, aadd that line instead.

I'm also not sure if you have user write permission on by default in the non-"cloud_saves" part of the directory. Sorry I can't be of much help there, since, as I said, I don't use Windows.

In fact, that might be the issue in the first place: check if the "cloud_saves" directory has write permission for normal users. Again, I don't know how to do that or how to fix it in Windows.

Spot on, that line is causing the issue and commenting it out resolves it. Thanks a lot! :)

This should be brought to GOG's attention. Maybe I'll write a support ticket tomorrow.

I told Support about our findings and they said they'd forward the issue to the Product Team.

What I'd be interested in - has anyone experienced this behaviour through Galaxy as well, or do you all just use the offline installers like me?

I know, I'm interested in whether it actually works on the Galaxy side of things.

I installed and play Unlimited Adventures through Galaxy and had the exact same issue.

The game is completely un-modded and it would crash when creating a new design.

As above commenting out the line "mount c "..\cloud_saves" -t overlay" in dosbox_ua_single.conf fixed the issue.

Thank you so much this fix worked for me ;)

I reported this issue another time, a month ago, and the support staff member apologized that it hadn't been fixed yet and said they'd pass it on, but so far no changes, apparently. :/

Today I had an update for the title. I presume It is the fix for that glitch.

Yes, support told me they decided to remove cloudsave functionality for the game as it wasn't working. I assume you'Re using Galaxy? Because I'm still waiting for an update on the offline installer.

EDIT: Never mind, its up now. I just tested it and it's working again.