Unable to load save files when relaunching the game

[Former user]

Every time I restart the game, all of my saves become unusable, with an Error 005.

Steps I've used to reproduce :

1. Download a fresh copy of 0.4.2
2. Create any character (with the default settings)
3. Save the game
4. Close the game
5. Start the game again
6. Try to load the save --> Error 005.

I've provided the save file I am unable to load as an attachment. Loading the file without restarting the game worked fine.

[Houdini111]

I still can't replicate this, even with this save.
Perhaps it's being denied read access to the file?

[TAAG]

Is there any way to check on how it could be denied read access? I do not believe it's a permission issue, as the file has all permissions set for all users.

I don't believe it's a filestream issue either, as if I open the game, try to load to file, keep it hanging at the error message, then open the save file in an editor, edit it and attempt to save it, my editor provides me a read-only error. But if I close the game, I can edit it and save it fine.

[Houdini111]

That screenshot brought something to my attention that I didn't think about. It could be that the different file system is causing issues. I don't know if anyone else has tested on anything other than an english version/locale of Windows. I don't know yet if that's actually the problem

Try using the exe I've attached and tell me what message boxes you get when trying to load (after saving and quitting).

[TAAG]

I see a BEFORE OPEN, an AFTER OPEN, and then it loads just fine.

[TAAG]

I switched back to an English locale and still have the same issue with the 0.4.2 release.

Could this somehow have been solved on the branch you've provided the exe from, but not on 0.4.2 release, or did the few changes you've applied to your build fix the issue?

[Houdini111]

I'm pretty sure I didn't make any changes on my branch that would affect the loading (except for those message boxes).
I've attached a different version, this time compiled straight from the current version of master (no message boxes either).
I'm not sure about after what commit v4.2 was compiled, so I'm not sure if this is exactly the same as what you had.

[V H. U]

I've also tried it in the uncompressed version of v4.2 that was posted and I was unable to replicate it with the provided save.

[TAAG]

I also have the issue with the version you just gave me.

Which is really odd since the version with the before+after messages works for me

[Houdini111]

Alright. One more test. It's back to my branch, but without the "BEFORE" and "AFTER" message boxes (but keeping the try/catch block and the MessageBox in the catch).

[TAAG]

Somehow it gets me back to the Error 005 as well.

Which makes it feel like a disk race condition or something where, for some reason, the messages delays something on my disk and make it work?

[TAAG]

This is odd, as I am able to somehow reproduce the issue on my laptop as well

[Houdini111]

That's a good theory. What happens if you try this version? It's just master, but with a 0.5 second wait where the "BEFORE" message was.

[TAAG]

Seems like that is not the solution as well .

I'm out of ideas and to be fair, this just reminds me of the beginner JavaScript class I had a few years back. I had to do a Rock-Paper-Scissors game, and my display wouldn't update correctly unless I had an alert pop up before updating the display for some reason. I don't recall ever figuring out why.

[Houdini111]

Let's try a more extreme test to be certain. A five second delay should definitely prove one way or the other.

[TAAG]

It felt more like 10 seconds before hitting the same error message But yeah, it proves that's not the issue.

[V H. U]

[link broken] https://bitbucket.org/VowelHeavyUsername/dungeon_depths/downloads/D_Dv0.4.3.zip

Give this one a try. I think the problem might be caused by the board not being completely initialized before it is needed.

[TAAG]

Doesn't work out either, still an error 005.

I've been able to figure out a way to load past saves, but it's really gimmicky. If I open the game, create a new character, save the new character in a different slot (in slot 2), then load the old save(that's in slot 1), it's able to open the old save for some reason.

[TAAG]

Note about that workaround, I need to save the new character before loading, otherwise it still doesn't work.

[V H. U]

This confirms to me that something isn't being initialized before it is needed.

[V H. U]

I've modified the load method a little.

[TAAG]

This version works with a small graphical glitch.

The game loads, says game successfully loaded, then the map goes black for ~2s until it says game successfully loaded again and works fine.

[V H. U]

Alright, good. We've got progress, at least.

I'll have to see what I can do about the graphical glitch.

[V H. U]

I think I've got this resolved as of Pull Request #29, though as I can't repeat it on my device I can't really confirm as so.

Therefore, I'm changing its priority to trivial until I can confirm one way or the other.

[TAAG]

I've downloaded 0.4.3.1 and this seems to be fixed on my machine (without the graphical glitch).

[Houdini111]

That's great to hear.

[V H. U]

Awesome

[V H. U]

Removing version: v0.4.2 (automated comment)