Writing a save over the current file every preview would not be helpful to me, unless a @Socks noted it saves under a new filename. I preview endless things I'd not want saved. Would be better than nothing, but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad. Maybe impossible.
@Armelline said:
Writing a save over the current file every preview would not be helpful to me, unless a Socks noted it saves under a new filename. I preview endless things I'd not want saved. Would be better than nothing, but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad. Maybe impossible.
@JSproject said:
Considering that I've had projects become corrupted on several occasions and considering it has happened during saving . . . any form of "auto save" is a pretty terrible thought.
Agreed, the majority of corrupt files tend to happen as they are being written to disk - generally speaking, a file that corrupts in RAM doesn't effect the file on disk - that's why incremental saving is so useful as you are constantly writing to a new part of the disk.
@Armelline said:
Writing a save over the current file every preview would not be helpful to me,
Agreed, writing a save over the current file would be a disaster to me, as I spend 99% of the time experimenting and trying things out, it's only ever the final 1% at the end of this process that gets used - I might even strip all the rules out of a actor, except for just one rule, to try and track down an issue, if that file were to be written over the current file at the preview stage I would have essentially lost that actor's rules.
So, you change a value in a dozen actors, hit preview, only to realise the result looks even worse than before - and given that GameSalad lacks a Cmd+z / Undo at this stage your best option is to simply revert to your saved file . . . except that now the changes you don't want have been written to disk, so you'd need to manaully enter them once again.
Like the issue with importing and deleting image assets (a problem compounded by what is essentially a form of autosave with regard to images only), I can see people having to first do a Save-As every time they want to preview if the system wrote over the current file.
So, yeah, if the system were to overwrite the current working file it would be a real step backwards, we would essentially be loosing GameSalad's only viable alternative to Undo / Cmd+Z - or we'd now need to Save-As every time we preview (I preview hundreds of times a day!)
So that route would be a big step backwards.
@Armelline said:
unless a Socks noted it saves under a new filename.
If the autosave were to increment the file name (producing a list of working files XX022, XX0023, XX0024 etc) with the most recent being the file in RAM (the file you are working on) then we'd very likely end up with a long list of pointless tangents to our development history.
Ideally the development history (a list of GS files in a folder) would look something like this . . .
walk animation glitch fixed >
walk animation better speed >
transition from walk to jump looking better >
transition from walk to jump finished >
landing animation speed sorted >
. . . . etc etc
With an automated save that saved on every preview and generated an incremental list the development history would look more like this:
walk animation looking a bit better >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit better >
walk animation looking a bit better >
walk animation too slow >
walk animation still too slow >
walk animation still too slow >
walk animation too fast >
walk animation speed ok >
walk animation finished >
. . . etc etc
Every little cul-de-sac we tend to wonder down - and then reverse out of - during the process of making a game would, in theory, become part of this list ?
@Armelline said:
I preview endless things I'd not want saved.
Same here, it's the majority of my working method.
@Armelline said:
Would be better than nothing . . .
I'd say it could be worse ! If you have the responsibility to save your own work, it encourages people to adopt a robust saving system - simple incremental Saving As works perfectly here.
@Armelline said:
but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad.
Honestly if it's an optional autosave feature I believe it can be beneficial. On the otherhand, if the autosave feature is required I can see multiple reasons for this to be an issue.
There have been times when I completely mess up a project because I decided I was going to adjust my logic. Because there was no autosave feature I was able to close the program and reopen it to the most recently saved version. If autosave was enabled I would have been in a rather sticky situation.
As an option (you can check or uncheck it in preferences) a warning pops up on screen if you have gone more than X minutes without saving your file (you can set the X value in preferences) it is then up to you to dismiss the warning or save your file through the normal process.
As an option (you can check or uncheck it in preferences) a warning pops up on screen if you have gone more than X minutes without saving your file (you can set the X value in preferences) it is then up to you to dismiss the warning or save your file through the normal process.
Would it still be considered autosave if a user's input is required?
@RabidParrot said:
Would it still be considered autosave if a user's input is required?
Not, not at all, I'm not describing an autosave system, I'm describing an alert system which would remind the user to save if a certain amount of time had elapsed since the last save.
The problem primarily seems to be with people who forget to save.
Well you seem to basically want a versioning system, @Socks, which we're not going to get. Perhaps have the option to auto-save with incremented filenames, but using a slightly different format when you trigger the save.
@Armelline said:
Well you seem to basically want a versioning system, Socks, which we're not going to get. Perhaps have the option to auto-save with incremented filenames, but using a slightly different format when you trigger the save.
That would be fine and all, but can you imagine working on a 100mb+ project. 10 auto saves and you're using 1gb. Depending on save frequency, that would obliterate HDD space. So an option to turn off would be mandatory.
Right now I just use a paid Dropbox which has some versioning support (version history with the ability to restore). It's saved me from at least 2 corrupt projects and commited code mistakes that should have never been.
Sounds like a good compromise, so Project 1, Project 2 and Project 3 are the projects you actually save, whereas Project 1.1, Project 1.2, Project 1.3 (etc) are what the autosave generates ? If it worked like that it would be fine, although if it was triggered by preview I'd have thousands of files after a week of fiddling with a project !
I think Preview is the wrong action to trigger a save, I think the trigger should be a keyboard command, I'd personally go for Cmd+S
I'd go for a user defined interval for autosaves, definitely not preview. But preview would be great for some.
Save options would be:
☐ Save on Preview?
☐ Autosave every xx minutes?
☐ Use different filename for manual saves?
☐ Prompt to discard auto-saves on quit?
(Last option would offer you a popup when quitting that would let you discard all the auto-saves that session. It would not discard the final save if it was an autosave. Options 3 and 4 would only be available if option 2 was checked.)
That would suit me okay.
@AlchimiaStudios said:
So an option to turn off would be mandatory.
☐ Save on Preview?
☐ Autosave every xx minutes?
☐ Use different filename for manual saves?
☐ Prompt to discard auto-saves on quit?
Shouldn't that be 'Use different filename for auto-saves?' ?
@Armelline said:
(Last option would offer you a popup when quitting that would let you discard all the auto-saves that session. It would not discard the final save if it was an autosave. Options 3 and 4 would only be available if option 2 was checked.)
Sounds pretty comprehensive, but I do think a simple alert would solve the issue of people forgetting to save.
@AlchimiaStudios said:
That would be fine and all, but can you imagine working on a 100mb+ project. 10 auto saves and you're using 1gb. Depending on save frequency, that would obliterate HDD space. So an option to turn off would be mandatory.
10 previews !? I think a lot of people do 10 previews every few minutes ! Definitely agree with the option to switch it off.
@WebWarrior said:
One feature we've discussed internally a bit is to have Creator automatically save whenever you preview. I'd be curious to hear your thoughts on that!
That sounds great...however previewing and finding the 10 changes you made were wrong...for us noobs who might not know where the problem is then have to remove everything.
If this was to happen I would want a revert to saved just like you have a revert to protocol...then I'm a go one that.
Also there's no way I would want a new file names every save. No way. I have enough duplicates I create myself let alone 20 a night to sift through.
For me anymore...I make 2 small changes....preview...if it works I save.
If I have something I'm going to test but know it may screw things up I save as 1.1 or 1.2 and so on. Once my new idea works I delete the older ones. But say for every 10 save as...I keep one last save. Then in steps I will delete as needed.
In a month I may end up with 20 save as files....I have to keep them in a separate place..at the beginning of each month I end up with "last best save" and "current build"...dated
In terms of doing radical changes, I always do an internal backup of the old methods in the actor and disable them. Only if the new method works do I delete the old.
In terms of autosave, how about having versioning, but you decide how many 'backups' you have, before it starts overwriting old ones? Even if there was just one 'backup' slot, you would have a version saved, say a couple minutes before the crash, but it wouldn't be overwriting your primary project file.
@Armelline said:
Socks - An alert would annoy the crap out of me. I'd hate having to dismiss it all the time.
Are you saying you'd decide to use an option (to have a timed alert) that annoyed the crap out of you, why on earth would anyone do that !? Even if you'd chosen to use it, saving your file fairly regularly would mean you'd never see it, the only time you'd rarely see it is when you'd forgotten to save for a prolonged period.
Also ideally you wouldn't have to dismiss it if you didn't want to, you could just carry on working.
@Socks, if it was an option I could disable, that would be fine. But if it was a popup that you couldn't disable... ouch The flashing alert you demonstrate would drive me nuts too Sometimes I'll go 10+ minutes without a save, deliberately, and seeing that flash for 10 minutes would be irritating to say the least
@Armelline said:
if it was an option I could disable, that would be fine. But if it was a popup that you couldn't disable... ouch
I'm pretty sure everyone has agreed, and more than once, on the idea that any and all of these systems should be optional, AlchimiaStudios has said the system should be optional, FINNBOGG says the we should have the option to choose, Lovejoy thinks the option of an auto save would be nice, you've said you want the system to be optional, abuabed84 has suggested any feature should be . . . you guessed it . . . optional, and I've said the system really needs to be optional . . . I described the idea of a simple alert as "an option" that you can "check or uncheck in preferences" . . . . so with all that in mind, what makes you think I am now suggesting 'a popup that you couldn't disable' !!? Lol !!
Lol. Yes it would be optional, my post suggesting an alert states it clearly as optional, it's an option, no it wouldn't be a a popup that you couldn't disable !!
Although, there is something I'm curious about, your suggestion of an autosave system, where we have file1.1, file 1.2, file 1.3, file1.4 (etc) saved off between our actual manually saved files (file1 and file2 . . . etc) - would this system be optional, it's not clear it would be optional, I know you've said it all these things should be optional, but this will be terrible if this thing you've said would be optional was not optional, I really don't like the idea of it not being optional . . . . ouch
lol
@Armelline said:
The flashing alert you demonstrate would drive me nuts too Sometimes I'll go 10+ minutes without a save, deliberately
Then set the interval to 12 minutes, or 20, or whatever you like.
@Armelline said:
and seeing that flash for 10 minutes would be irritating to say the least
Why then let it flash for ten minutes ? Surely you'd just dismiss the warning (something like clicking on it maybe) ?
@BlackCloakGS said:
Or would you rather we turn on auto save that is built in to the Mac OS X?
How does it work ?
Does it generate a separate file/s to your actual working file ? By that I mean if you start a new file, you call it XX01 and save it, will this file be altered by auto save ?
@WebWarrior said:
One feature we've discussed internally a bit is to have Creator automatically save whenever you preview. I'd be curious to hear your thoughts on that!
I think that would be the worst time to save, since the preview is the place where most crashes happen. The optimal solution is to figure out the crash locations and causes by receiving reports from users and fixing them for a more stable software
PhilipCCEncounter Bay, South AustraliaMemberPosts: 1,390
edited June 2015
@Armelline said:
Writing a save over the current file every preview would not be helpful to me, unless a Socks noted it saves under a new filename. I preview endless things I'd not want saved. Would be better than nothing, but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad. Maybe impossible.
I agree with Armelline
@Socks said:
Every little cul-de-sac we tend to wonder down - and then reverse out of - during the process of making a game would, in theory, become part of this list ?
@Armelline said:
I preview endless things I'd not want saved.
@Socks said:
Same here, it's the majority of my working method.
Me too.
@Armelline said:
Would be better than nothing . . .
@Socks said:
I'd say it could be worse ! If you have the responsibility to save your own work, it encourages people to adopt a robust saving system - simple incremental Saving As works perfectly here.
I agree with both of you.
@Armelline said:
...but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad.
I agree once more.
@BlackCloakGS said:
Or would you rather we turn on auto save that is built in to the Mac OS X?
No, no, no thank you. I'd rather choose when I save, and how I name and increment the file.
One of Apple's biggest mistakes of recent years was eliminating "Save As" in their Apps just to placate the crossover x-Windows users!
I also think that "Undo" in GS would be a fantastic feature to add. I'll put it on the Features Request List.
Most Autodesk products like 3dsMax and Maya have used an AutoSave system for years, that autosaves discreetly and without affecting the users flow of working with the software... just copy something like that, thats been proven to work usefully for years...
So... you'd have an option to do autosaves. Under that option, you have the option of how long between autosaves, and how many autosave files to cycle through. Basically it would save to the next autosave file in a seperate directory, and cycle through the backup files.
So you wouldn't have huge folders of saves, just maybe 10 files (autosave1,autosave2, etc)... as the point of the autosave is not to manage your project save files, or to dictate how often you save... the auto files are so that you can go back to a relatively close saved file if a crash occurs.
You'd still do your own saves, to your own project directories... you'd just also have a folder that you can go to when things have gone wrong, that should give you a salvageable file....
Im not sure the argument of fixing all crash bugs negates the need for an AutoSave function, as to be honest, theres always going to be new crash bug implemented down the road when new features or code are added... so adding an AutoSave function just makes more sense really...
It is also a strategy question to implement autosave. Wants GameSalad be a tool for everyone or only for an elite?
AutoSave is a standard in many well-known software products such as Microsoft Office ... Products which knows everyone around the world. It is a de facto standard. I wouldn't make autosave to complex, just save in the same file.
I have some multiple Gbyte software python-projects in JetBrains Pycharm and Eclipse. I had never corrupt files from a autosave. The UIs aren't slowing down during autosave.
Comments
Writing a save over the current file every preview would not be helpful to me, unless a @Socks noted it saves under a new filename. I preview endless things I'd not want saved. Would be better than nothing, but only if it was an option. Make it compulsory and I'd find it extremely difficult to use GameSalad. Maybe impossible.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
Agreed.
Follow us: Twitter - Website
Agreed, the majority of corrupt files tend to happen as they are being written to disk - generally speaking, a file that corrupts in RAM doesn't effect the file on disk - that's why incremental saving is so useful as you are constantly writing to a new part of the disk.
Agreed, writing a save over the current file would be a disaster to me, as I spend 99% of the time experimenting and trying things out, it's only ever the final 1% at the end of this process that gets used - I might even strip all the rules out of a actor, except for just one rule, to try and track down an issue, if that file were to be written over the current file at the preview stage I would have essentially lost that actor's rules.
So, you change a value in a dozen actors, hit preview, only to realise the result looks even worse than before - and given that GameSalad lacks a Cmd+z / Undo at this stage your best option is to simply revert to your saved file . . . except that now the changes you don't want have been written to disk, so you'd need to manaully enter them once again.
Like the issue with importing and deleting image assets (a problem compounded by what is essentially a form of autosave with regard to images only), I can see people having to first do a Save-As every time they want to preview if the system wrote over the current file.
So, yeah, if the system were to overwrite the current working file it would be a real step backwards, we would essentially be loosing GameSalad's only viable alternative to Undo / Cmd+Z - or we'd now need to Save-As every time we preview (I preview hundreds of times a day!)
So that route would be a big step backwards.
If the autosave were to increment the file name (producing a list of working files XX022, XX0023, XX0024 etc) with the most recent being the file in RAM (the file you are working on) then we'd very likely end up with a long list of pointless tangents to our development history.
Ideally the development history (a list of GS files in a folder) would look something like this . . .
walk animation glitch fixed >
walk animation better speed >
transition from walk to jump looking better >
transition from walk to jump finished >
landing animation speed sorted >
. . . . etc etc
With an automated save that saved on every preview and generated an incremental list the development history would look more like this:
walk animation looking a bit better >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit worse >
walk animation looking a bit better >
walk animation looking a bit better >
walk animation looking a bit better >
walk animation too slow >
walk animation still too slow >
walk animation still too slow >
walk animation too fast >
walk animation speed ok >
walk animation finished >
. . . etc etc
Every little cul-de-sac we tend to wonder down - and then reverse out of - during the process of making a game would, in theory, become part of this list ?
Same here, it's the majority of my working method.
I'd say it could be worse !
If you have the responsibility to save your own work, it encourages people to adopt a robust saving system - simple incremental Saving As works perfectly here.
Agreed !
Honestly if it's an optional autosave feature I believe it can be beneficial. On the otherhand, if the autosave feature is required I can see multiple reasons for this to be an issue.
There have been times when I completely mess up a project because I decided I was going to adjust my logic. Because there was no autosave feature I was able to close the program and reopen it to the most recently saved version. If autosave was enabled I would have been in a rather sticky situation.
My preferred choice . . . .
As an option (you can check or uncheck it in preferences) a warning pops up on screen if you have gone more than X minutes without saving your file (you can set the X value in preferences) it is then up to you to dismiss the warning or save your file through the normal process.
Would it still be considered autosave if a user's input is required?
Not, not at all, I'm not describing an autosave system, I'm describing an alert system which would remind the user to save if a certain amount of time had elapsed since the last save.
The problem primarily seems to be with people who forget to save.
Well you seem to basically want a versioning system, @Socks, which we're not going to get. Perhaps have the option to auto-save with incremented filenames, but using a slightly different format when you trigger the save.
Project 1.1
Project 1.2
Project 1.3
Project 2
Project 2.1
Project 2.2
Project 2.3
Project 2.4
Project 3
etc.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
That would be fine and all, but can you imagine working on a 100mb+ project. 10 auto saves and you're using 1gb. Depending on save frequency, that would obliterate HDD space. So an option to turn off would be mandatory.
Right now I just use a paid Dropbox which has some versioning support (version history with the ability to restore). It's saved me from at least 2 corrupt projects and commited code mistakes that should have never been.
Follow us: Twitter - Website
Sounds like a good compromise, so Project 1, Project 2 and Project 3 are the projects you actually save, whereas Project 1.1, Project 1.2, Project 1.3 (etc) are what the autosave generates ? If it worked like that it would be fine, although if it was triggered by preview I'd have thousands of files after a week of fiddling with a project !
I think Preview is the wrong action to trigger a save, I think the trigger should be a keyboard command, I'd personally go for Cmd+S
I'd go for a user defined interval for autosaves, definitely not preview. But preview would be great for some.
Save options would be:
☐ Save on Preview?
☐ Autosave every xx minutes?
☐ Use different filename for manual saves?
☐ Prompt to discard auto-saves on quit?
(Last option would offer you a popup when quitting that would let you discard all the auto-saves that session. It would not discard the final save if it was an autosave. Options 3 and 4 would only be available if option 2 was checked.)
That would suit me okay.
Absolutely.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
Yep, a user defined interval rather than preview.
Shouldn't that be 'Use different filename for auto-saves?' ?
Sounds pretty comprehensive, but I do think a simple alert would solve the issue of people forgetting to save.
10 previews !? I think a lot of people do 10 previews every few minutes ! Definitely agree with the option to switch it off.
@Socks - An alert would annoy the crap out of me. I'd hate having to dismiss it all the time. Perhaps as another option though!
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
That sounds great...however previewing and finding the 10 changes you made were wrong...for us noobs who might not know where the problem is then have to remove everything.
If this was to happen I would want a revert to saved just like you have a revert to protocol...then I'm a go one that.
Also there's no way I would want a new file names every save. No way. I have enough duplicates I create myself let alone 20 a night to sift through.
Complete Guide to iOS Publishing {} Complete Guide to Mac Publishing
For me anymore...I make 2 small changes....preview...if it works I save.
If I have something I'm going to test but know it may screw things up I save as 1.1 or 1.2 and so on. Once my new idea works I delete the older ones. But say for every 10 save as...I keep one last save. Then in steps I will delete as needed.
In a month I may end up with 20 save as files....I have to keep them in a separate place..at the beginning of each month I end up with "last best save" and "current build"...dated
Complete Guide to iOS Publishing {} Complete Guide to Mac Publishing
In terms of doing radical changes, I always do an internal backup of the old methods in the actor and disable them. Only if the new method works do I delete the old.
In terms of autosave, how about having versioning, but you decide how many 'backups' you have, before it starts overwriting old ones? Even if there was just one 'backup' slot, you would have a version saved, say a couple minutes before the crash, but it wouldn't be overwriting your primary project file.
Are you saying you'd decide to use an option (to have a timed alert) that annoyed the crap out of you, why on earth would anyone do that !?
Even if you'd chosen to use it, saving your file fairly regularly would mean you'd never see it, the only time you'd rarely see it is when you'd forgotten to save for a prolonged period.
Also ideally you wouldn't have to dismiss it if you didn't want to, you could just carry on working.
Like this:
@Socks, if it was an option I could disable, that would be fine. But if it was a popup that you couldn't disable... ouch
The flashing alert you demonstrate would drive me nuts too 
Sometimes I'll go 10+ minutes without a save, deliberately, and seeing that flash for 10 minutes would be irritating to say the least 
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
I'm pretty sure everyone has agreed, and more than once, on the idea that any and all of these systems should be optional, AlchimiaStudios has said the system should be optional, FINNBOGG says the we should have the option to choose, Lovejoy thinks the option of an auto save would be nice, you've said you want the system to be optional, abuabed84 has suggested any feature should be . . . you guessed it . . . optional, and I've said the system really needs to be optional . . . I described the idea of a simple alert as "an option" that you can "check or uncheck in preferences" . . . . so with all that in mind, what makes you think I am now suggesting 'a popup that you couldn't disable' !!? Lol !!
Although, there is something I'm curious about, your suggestion of an autosave system, where we have file1.1, file 1.2, file 1.3, file1.4 (etc) saved off between our actual manually saved files (file1 and file2 . . . etc) - would this system be optional, it's not clear it would be optional, I know you've said it all these things should be optional, but this will be terrible if this thing you've said would be optional was not optional, I really don't like the idea of it not being optional . . . . ouch
Then set the interval to 12 minutes, or 20, or whatever you like.
Why then let it flash for ten minutes ? Surely you'd just dismiss the warning (something like clicking on it maybe) ?
Or would you rather we turn on auto save that is built in to the Mac OS X?
How does it work ?
Does it generate a separate file/s to your actual working file ? By that I mean if you start a new file, you call it XX01 and save it, will this file be altered by auto save ?
I like the idea of having the project save as a backup every time your preview, this way it doesn't override your project file.
Fortuna Infortuna Forti Una
@Socks All of Apples apps support it. Try it out in pages.
I think that would be the worst time to save, since the preview is the place where most crashes happen. The optimal solution is to figure out the crash locations and causes by receiving reports from users and fixing them for a more stable software
I agree with Armelline
Me too.
I agree with both of you.
I agree once more.
No, no, no thank you. I'd rather choose when I save, and how I name and increment the file.
One of Apple's biggest mistakes of recent years was eliminating "Save As" in their Apps just to placate the crossover x-Windows users!
I also think that "Undo" in GS would be a fantastic feature to add. I'll put it on the Features Request List.
Most Autodesk products like 3dsMax and Maya have used an AutoSave system for years, that autosaves discreetly and without affecting the users flow of working with the software... just copy something like that, thats been proven to work usefully for years...
So... you'd have an option to do autosaves. Under that option, you have the option of how long between autosaves, and how many autosave files to cycle through. Basically it would save to the next autosave file in a seperate directory, and cycle through the backup files.
So you wouldn't have huge folders of saves, just maybe 10 files (autosave1,autosave2, etc)... as the point of the autosave is not to manage your project save files, or to dictate how often you save... the auto files are so that you can go back to a relatively close saved file if a crash occurs.
You'd still do your own saves, to your own project directories... you'd just also have a folder that you can go to when things have gone wrong, that should give you a salvageable file....
Im not sure the argument of fixing all crash bugs negates the need for an AutoSave function, as to be honest, theres always going to be new crash bug implemented down the road when new features or code are added... so adding an AutoSave function just makes more sense really...
@abuabed84 Have you checked out @Armelline SaveSalad? Only works on the mac, but here's a link:
http://forums.gamesalad.com/discussion/70000/armellines-free-stuff-for-everyone-check-first-post-for-the-latest-update/p1
It is also a strategy question to implement autosave. Wants GameSalad be a tool for everyone or only for an elite?
AutoSave is a standard in many well-known software products such as Microsoft Office ... Products which knows everyone around the world. It is a de facto standard. I wouldn't make autosave to complex, just save in the same file.
I have some multiple Gbyte software python-projects in JetBrains Pycharm and Eclipse. I had never corrupt files from a autosave. The UIs aren't slowing down during autosave.