Hey guys,
I’m using the most recent version of Vassal (3.2-4beta?), and for some reason, instead of saving to the .vmod that I specified, it saves to something like tmprandomstringofnumbers.zip. The file structure of the .zip seems to be the same, and I’m able to open the module if I change the file extension to .vmod.
It’s a bit annoying, because I have a sort of ctrl + s tic, so I save progress every couple minutes or so. When I go back to my folder, there’s like 15 different tmp*.zip folders, and I can’t always be sure that I’ve gotten the right one.
Thanks in advance.
Not sure what happened, but apparently it’s saving properly again. Oh well!
Thus spake Greenmeep:
Hey guys,
I’m using the most recent version of Vassal (3.2-4beta?), and for some
reason, instead of saving to the .vmod that I specified, it saves to
something like tmprandomstringofnumbers.zip. The file structure of the
.zip seems to be the same, and I’m able to open the module if I change
the file extension to .vmod.
It’s a bit annoying, because I have a sort of ctrl + s tick, so I save
progress every couple minutes or so. When I go back to my folder,
there’s like 15 different tmp*.zip folders, and I can’t always be sure
that I’ve gotten the right one.
Thanks in advance.
This happens becasue the file you’re trying to write to isn’t writable,
and VASSAL is making sure you don’t lose your work by saving to a file
which is writable. Check the file you’re trying to write to in order to
determine why it’s not writable for you.
–
J.
Thanks for your reply.
I realized recently that it wasn’t that the file wasn’t writable, but rather that I was shutting off Vassal before it was finished saving.
However, I do have a question - I’m using Vassal for a card game, which has several (~600) cards as of now. I’m assuming that this was part of the reason why I was able to shut off Vassal before it was done saving properly. Every time I try to save, though, Vassal returns an error partway through, which I expect is due to running out of memory. Are there any solutions to this problem?
Thus spake Greenmeep:
Thanks for your reply.
I realized recently that it wasn’t that the file wasn’t writable, but
rather that I was shutting off Vassal before it was finished saving.
However, I do have a question - I’m using Vassal for a card game, which
has several (~600) cards as of now. I’m assuming that this was part of
the reason why I was able to shut off Vassal before it was done saving
properly. Every time I try to save, though, Vassal returns an error
partway through, which I expect is due to running out of memory. Are
there any solutions to this problem?
Why do you think you’re running out of memory? What’s the error message?
–
J.
Thus spake Greenmeep:
Thanks for your reply.
I realized recently that it wasn’t that the file wasn’t writable, but
rather that I was shutting off Vassal before it was finished saving.
How exactly are you “shutting off” VASSAL before it’s finished saving?
That shouldn’t be possible using Quit from the menu or the X in the
window decorations. If it is, it’s something we’d like to reproduce and
fix.
–
J.
Clicking the physical “save” button causes Vassal to wait until it’s done saving before it exits. Ctrl + s doesn’t seem to have the same restriction.
As for the error, I can’t be quite sure, as it resolved itself after I saved it (until the error) then manually popped in the images that it didn’t save. Subsequent saves seem to be carried out okay.