When I try to create a new design, the program simply crashes. This is "new" behavior - I've successfully created two designs in the past (December 2018 and January 2019) - I provide that information in case an update that has happened since then is what screwed things up.

I've tried running the game as an administrator, and the effect is the same. I've also tried turning of "cloud saves" - again, I hit "OK" after entering in the parameters of the new design, and the thing just crashes to the desktop.

Can somebody tell me how to fix this, please?

How did you turn off cloud saves? Did you remove the cloud directory save mount from the dosbox configuration file, as described here? You should contact support, in any case.

Hmm ... no I didn't do it the way you describe in the link. It occurs to me that all I probably did was turn off sync between the cloud saves and local saves. I'll be sure I try out the method you posted when I next boot up the game (and will gladly mark your answer as the solution if it lets me create designs).

I did find an extremely clumsy work around: if I manually create a ########.DSN folder (where ######## is what the folder name for the design would be, and a SAVE folder in the .DSN folder), then while running FRUA will "see" the "blank" .DSN folder as an option to select when you try to change to a new design. If you select it, you can then modify the design properties normally (down to actually giving it its 'display' name), and it *seems* to save you work and let you play it correctly.

Like I said, it's clumsy (so much so that I'd not think of it as a 'real' solution), and I don't know if I'll run into problems later, but it did work.

Some info that could be of interest in solving this issue:

- Do you run FRUA with GOG Galaxy or without it? In the latter case, do you have GOG Galaxy installed? Is it active in the background?
- Do you run FRUA with UAShell or without it?
- If you use your workaround for creating a design, what happens if you try to create and save a character or save your game?

I think you should also contact the GOG support about the issue, even if the method darktjm linked to solves the problem. GOG needs to acknowledge that this is actually a serious issue and it's their responsibility to fix it, as this seems indeed related to the latest update and didn't occur before. (I told them some weeks ago, but so far nothing happened. Maybe they need to hear it from more users.)