Unable to export custom dungeons
Posted: Tue Dec 18, 2012 9:53 pm
I seem no longer able to export dungeons from the editor. I first tried with the big dungeon I've been working on, then tried making new dungeons from scratch and found the same issues.
It's been some weeks at least since I last used the export feature, so I'm not sure exactly at what point it stopped working.
What happens is I go into the export menu where you can enter title, auther and description on the dungeon. When I click the Export button in this dialogue, the cursor switches to the Windows loading cursor. If I move the cursor it goes back to the regular cursor arrow. Instead of coming up with an "Export succesful" message nothing appears to happen. I tried leaving it like this for close to half an hour with no result. I also tried running a custom dungeon to see if anything was exported, but there's nothing new here.
I'm running Grimrock via Steam on a Windows 7 machine. I also tried reinstalling the game, which didn't help.
Any ideas?
EDIT: Noticed I had beta settings on. Will try to reinstall without these.
UPDATE: Removing the beta opt-in fixed the problem. It must be the new beta stuff causing the issue.
It's been some weeks at least since I last used the export feature, so I'm not sure exactly at what point it stopped working.
What happens is I go into the export menu where you can enter title, auther and description on the dungeon. When I click the Export button in this dialogue, the cursor switches to the Windows loading cursor. If I move the cursor it goes back to the regular cursor arrow. Instead of coming up with an "Export succesful" message nothing appears to happen. I tried leaving it like this for close to half an hour with no result. I also tried running a custom dungeon to see if anything was exported, but there's nothing new here.
I'm running Grimrock via Steam on a Windows 7 machine. I also tried reinstalling the game, which didn't help.
Any ideas?
EDIT: Noticed I had beta settings on. Will try to reinstall without these.
UPDATE: Removing the beta opt-in fixed the problem. It must be the new beta stuff causing the issue.