![]() ![]() So you're disregarding my entire post because you don't believe that a file that doesn't sync correctly to a cloud save doesn't count as "disaster recovery?" Even though I suggested an alternate solution for the feature that addresses your concern about people mistaking MyPaint for being laggy?Īgain, my situation, despite you not believing it to be "disaster recovery" was a file that I was working on for a client, using a STABLE release build of the software so I wouldn't have to make a report like this.Īnd I see the discussion of this feature being implemented is in #90, with saying what I just did: have various options in the settings in response to the concern you address: autosave slowing down someone's computer.Īnd again, to address my original issue: MyPaint had an error message popup before I closed the software. Because I just said that I tried to do a normal save and it didn't.Īnd I did not save the file in a different location because I am used to getting MyPaint error messages when I'm trying to save a file, and the file is in tact after the error message (whether I quit MyPaint or I ignore the error manually.) So no, I am not using autosave as substitute for regular saving obviously. If you want to change the image format, select the image format before saving your file. If the inactivity autosave works for people, that's fine but it doesn't work for me, and I don't want other users to get blindsided by In my original post: just said that I did press "CTRL+S" to attempt to save my file (And again, I tried to save the file MANUALLY to the location I have it stored at multiple times!) And does the situation I JUST described in this post was a situation where I DID attempt to save the file normally but it didn't. ![]() Again, autosave should give peace of mind for artists, and the inactivity basis of this autosave does the complete opposite. This style of autosaving is not efficient or good for artists, and counterintuitive. I tried checking the autosave cache, but nothing.Īnd before anyone tells me that I shouldn't have been testing mypaint to use this file: again, it was a stable release. I thought it would be fine because I have autosave turned on.Įxcept that I checked my preferences, when I tried to re-open the file, and because the autosave is based on inactivity rather than just as set quantity of time, I lost all my progress because I was working on the file non-stop. (probably because my file was saving to Google Drive and couldn't sync yet, so this part isn't the MyPaint bug.) ![]() ![]() Text, layer and resolution information will not deteriorate, but still retain itself. These are the formats supported by FireAlpaca. Autosave function has been equipped since the version 1.7.0. Turns out that the error was that the file wouldn't save. File formats supported by FireAlpaca If you want to change the image format, select the image format before saving your file. There was about 49-52 layers and the canvas was around the 4000 x 4000's.I was in the middle of working on an important file, and when I tried to save it, MyPaint had an error. Automatic save is enabled by default for every 10 minutes. The layers are still available (though you cant see any drawings on them) though do not appear visible when set to be visible (///u/everythingfirealpaca/s1/:everythingfirealpaca:8ZgT:).įor context: I was drawing individual tiny white lines and dots on a black background for texture. Automatic save filescommonly referred to as 'autosave' filesare backup files created automatically by the Autosave feature. Just trying to see if i can retrieve my two days worth of work in anyway would rather try to get them back instead of admitting immediate defeat.Īnd I have filled a bug form on firealpaca's website (though they have yet to respond) currently the only layers that work are the 2 reference layers and the white dot. The computer im using is a windows 10, firealpaca + computer is on the newest update, and the tablet is a ex-pen 12(?) if that helps with anything. Temporary_11345267 Thu, 19:18:11 GMT Heyo, ive run into a devastating error with firealpaca(image 1) regarding my layers and I was wondering anyone knew what caused this or if there is a small change of getting them back? I know there's a slim chance that ill get them back but im just trying to see what I can do from starting from scratch completely. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |