QuickSave Update Plugin Button Set for ZB3 (replaces QuickSave)

[Svengali]

quicksave update splash.jpg

QuickSave Update plugin for ZBrush3 replaces the first QuickSave plugin which replaced the old PSnap button set.

Unzip and install new QuickSave.zsc in the ZStartup\ZPlugs folder. Next time you startup ZBrush3 you will find NINE buttons in the ZPlugins menu under the Svengali subgroup.

Image and I+ buttons


:b1: First, the Image button lets you save the canvas image as a .psd or .bmp file.


:b1: After that, the I+ button will save new versions of canvas image incrementing the original filename. Tree002.psd, Tree003.psd and so on.

Model and M+ buttons


:b1: First, the Model button lets you save the current model (tool) in the directory of your choosing. Models are automatically saved at the lowest SubD level. If more than one SubTool is present, the top SubTool is selected and given the file's name, after which the original SubTool is reselected.


:b1: Any subsequent saves with the M+ button will increment the root filename, assigning that new filename to the top SubTool.

Docum and D+ buttons


:b1: Here, you save the current Document (.zbr) to the directory of your choosing. Note that if a model is active, it WILL NOT appear in the document file, but will be restored afterwards, same location and size, in edit mode.


:b1: The D+ button will incrementally save subsequent document files.


NEW: Video and V+ buttons

Nothing fancy here, just two new buttons which work pretty much like the others in QuickSave.

Video button


:b1: If you Press Video button when no Movie is in progress., you get a warning popup message that tells you so... and aborts.


:b1: If Movie IS in progress, the Pause button is automatically pressed and the Save As Movie dialog box opens up - you enter a new name, press Enter, and the Movie (from beginning to its current pause point) is saved in the directory you choose, a momentary popup confirmation message is displayed, then the Movie resumes recording.


:b1: If you have already saved a movie before, all you need do when the Save As Movie dialog box opens up, is to press Enter, and the Movie (again, from beginning to its current pause point) is saved OVER the previous save using the same filename and path. A momentary popup confirmation message is displayed, then the Movie resumes recording.


:b1: Note for the Video button to work you must have already MANUALLY STARTED the Movie (after setting your custom parameters). The Video button merely automates saving to the current point then, continuing the capture. When done, you must also MANUALLY STOP it.

V+ button


:b1: If you Press Video button when no Movie is in progress., you get a warning popup message that tells you so... and aborts.


:b1: If Movie IS in progress, the Pause button is automatically pressed and a NEW COPY WITH INCREMENTED NAME is automatically created (from beginning to its current pause point) and saved in the same directory as the original, a momentary popup confirmation message is displayed, disappears, then recording of the Movie resumes recording.


One warning about using V+

:b1: If you press the V+ Button after beginning a Movie, but without having already saved it with a UNIQUE NAME for that RECORDING session, you will save a NEW COPY OF THE MOVIE IN PROGRESS WITH INCREMENTED NAME using the Movie Name assigned from a previous session. This may or may not be what you want, but QuickSave can't know.


The ninth button, QS-Help?, elaborates on this info about each button and how it works.

To use QuickSave, I drag all buttons (except for QS-Help?) to my User Interface (as shown).

*** A CAUTION! ***
I strongly recommend that you TEST THESE BUTTON-SAVE OPERATIONS WITH NON-CRITICAL FILES UNTIL YOU ARE CONFIDENT THEY WORK AS EXPECTED. And please, if you find any problems report them here.

Finally, at the suggestion of Marcus_Civis, I’ve added some code that keeps better track of previously used folders. Thanks to Marcus and to Aminuts for extensive testing and various feedback... and to Scott for suggesting the Video addition. appreciate it guys!


Sven

[Bimm the Stone]

OK, this is pure Candy....saves so much work..Thank YOU!


Bimm

[panstar]

Just what the good Dr, ordered. Thanks this is great.

[Sebcesoir]

Very cool... !!!thx dude!

[vlad74]

This is great. Thanks a lot.

[Wordsmith]

Sven, thank you so much. We all really appreciate the work you and others do in our behalf.

It always amazes me the things people can do, and are willing to share on this forum.

Again, thanks

Word.

[feureau]

Hey, the new one's out! w000t!! Thanks svengali! This plugin has saved countless hours of zbrushing. ;)

[Svengali]

Thanks guys... I hope to have a few others posted this week, both updates and one or two new ones.

Sven

[Buckie]

I remember having this very useful plugin for ZB2, great to see it for ZB3 now, Thanks Sven... :D

[Atwooki]

Works a treat Sven (just as before :) ) Thanks for all your ingenuity and hard work :tu:

Chris

[RAMWolff]

Awesome set of tools. Thanks so much!! :)

[JUPITER]

Thanks for the .zsc ;) very useful

[NathanLedet]

Loving it...however, it keeps saving in the ZScripts folder. Is there a way to make it save in the ZTools folder?

[Svengali]

I'm surprised you are having this problem. The script specifically allows you to pick the folder path in the standard file save dialog window. And Quicksave remembers this path between saves, even between ZBrush sessions.

After the model is saved there is a popup note that tells you the path where your file was saved (above the name of the file saved). The path you choose when you do a save should match the path when you later do an incremental save...



quicksave confirm window.jpg

Sven

[NathanLedet]

well oddly enough after you post it seems to be working.... :lol:

newb error.

[Chi_D]

Needed a quick save like this. Thanks

[jaystein777]

Svengali, I think you just saved ZBrush 3.1 for me. I no longer seem to be getting the save crashes. So far so good. :)

[Flyer]

Svengali, Thank you.

Quicksave is a truely impressive solution to the ever so common issue of zbrush crashing during saving. I couldn't begin to tell you how many times I have lost my creativity on models. But still being human, from time to time I tend to get so envolved and focused on my project that I forget to reach for the "M" key to save and my workstation crashes.

Now, not being a programer or scripter I have no idea of the time or envolvement it takes to create scripts like these, but I was wondering if additions to the script would be possible? The addition I had in mind was a timed autosave. With a timed auto save, the artist would be able to set the time interval whether it was 15 seconds or 15 minutes and would not have to worry that his work was saved just prior to a system crash. I know that this is not a new idea and that programs such as 3ds max come standard with this type of save programming. I was just wondering if this could be added to the quicksave scripting?

Again, thank you for "saving" us. :)

[MichaelMaehring]

Hi,

thanks for the autosave script - as Zbrush keeps crashing constantly I hope this will help me moving forward with my work

One question: your script does not save my models at their lowest level (which I know is also a reason for broken models)

any idea why?

kind regards Michael

[MichaelMaehring]

Loving it...however, it keeps saving in the ZScripts folder. Is there a way to make it save in the ZTools folder?
use the "model" button to determine path - then use M+ button

m :tu:

[Svengali]

Ohlda,

QuickSave was originally written before subtools (pre ZB3). The first version didn't save the model at lowest subD level, but I changed that in the second (pre ZB3) version (to reduce the saved file-size). This also seemed to resolve crash-on-save problems.

With the release of ZB3/3.1, I updated QuickSave to guarantee it would work in the new environment, then also added another save mode (video).

* The current QuickSave still only reduces the current selected subtool to lowest subD... but it does not set any of the other subtools to lowest subD. Perhaps it should, but to do so, I'd have to add a subroutine to specifically set each and all subtools to lowest subD before saving.

I don't know if this would help further reduce crash-on-save problems, or for that matter, further reduce the size of saved files. It's something I'll have to investigate. Based on test results I might consider a future refinement to QuickSave.

Sven

* Correction: The current QuickSave selects the TOP SUBTOOL, then sets that to the lowest subD before saving... finally resets TOP SUBTOOL to previous subD level and returns to subtool that was active before the save. Note also that the top subtool is also renamed to match the most recently saved file name.

[Hardtwist]

Thanks Sven:cool: This will come in very handy.



Jim

[Svengali]

I've briefly tested a modified version of QuickSave which reduces all subtools to lowest subD levels before saving the model - surprisingly, the new saved files turned out slightly LARGER than the same files previously saved with just the first subtool reduced to lowest subD level.

Consequently, I've decided to let the current release of QuickSave stay as is.

Sven

[Wozrush]

I got the idea from this thread to manually save my tools with their lowest subdivision levels to save HD space and your right, they do come out as slightly bigger files?

I don't know anything about .ztl .obj files but I thought that was odd?

PS: Thanks for the plugin :)

[DanRoberts]

Thanks much Sven.

I was just tthinking today I needed an update to this plug as I have just upgraded my system and there it was. Will save lots of time.

Thanks again,

Dan

[Gen-an]

thanks very much! M+ is awesome :tu:

[rasdasa]

fabulous, thank you x37!

[Freerunner]

Thanks Sven looks like a crackingly good little plugin I will be testing it in about 20 secs :D

[walfisch]

Fantastic. Thanks for coding mate :-)

[caustic02]

Is there a trick to drag the buttons to the UI? I seem not to be able to do so.
Thanks for your help, and thanks for the wonderful plugin.

[Gen-an]

1. Preferences>Custom UI>Enable Customize
2. hold down CTRL and drag the button where you want it
3. disable Preferences>Custom UI>Enable Customize
4. finally to save the settings Preferences>Config>Store config

[caustic02]

Thanks a lot!

[VERADV]

Much Thx! :cool:

[PSTCHOART]

great plugin ,

how to determine the number of files that save.. ?

i mean: i can't stop the count ..start form - 001,002,003 .... to 999..

for example ..

i want to save only 6-7 versions of the file, then they must begin to be replaced by 1, 2, 3 ... to 6-7


hope you can understand me :) my English is bad

thanks

[Svengali]

PST,
Yes, I understand.

Having a limited number of saves has been requested before.

When I update QuickSave for ZBrush 4.0 I will make that the default save method... (unless Pixologic offers the autosave, which everyone wants!)

I will make it so a click on QuickSave + button starts by saving with 01, incrementing up through 09, thereafter saving by overwriting... 01, then 02, etc.

Any other suggestions are welcomed, but be aware that currently, timed autosave using ZScript is not possible.

Thanks for using QuickSave, Svengali

[PSTCHOART]

great thanks Svengali (member.php?u=3419)


i can't wait for update ..

thanks

Ceco

[DigitalDreamer]

After loosing 3 ztools, due to crashes, though thankfully I did save an earlier version, I came across this thread and downloaded your plugin. Thank you so much! I performed the same operation, which caused my crashes, namely saving at highest poly divisions, and this time no crash! Whoopie! I know your script saves out at the lowest sub d and an incremental version (not over write) so makes it easier. Also I think a cause of my earlier crashes has been unwittenly saving a model whith hidden polys a definate no no!
So thankyou again, great plugin!:tu::D:tu:

[japanNuke]

i love this plugin! xD
the idea of having 999 copies of my model is just great :cool:
i dont know why ppl complain about no overwriting option
imo overwriting can be dangerous, its better to manualy delete older versions
thanks again, the fun of using zbrush is back :D

[Lynxed]

Does this amazing plug-in works with Z3.5R2?

[akaDARK]

The plug-in still working for me on 3.5R2

[Kenmasters]

This is a real time-saver! Thanks :) (http://www.electronickitchenscales.org/salter-kitchen-scales-cheap-salter-electronic-kitchen-scales.html)

[biggerjohn]

Is this safe for 3.5R3?

[akaDARK]

Is this safe for 3.5R3?I am using the save model function for R3 and look safe for now.

[tennet]

Hi! Just installed Quicksave and I've experienced some problems saving over network.

I'm running Zbrush 3.2 on a Mac and I get this message "WARNING: File not saved" when trying to save my model over the network (using (Apple) AFP-network protocol)? The file IS still saved at the destination, but the script doesn't seem to understand that.. Trying to save incrementals after this will save the model to last "working" destination and not to the chosen network path.

I can connect to the server using some other protocol called CIFS (SMB) and then the script works, but it's very slow. AFP-access is much faster, it's more like saving to the internal drive.

Running the script and saving to the internal harddrive works perfect, but I have my projects stored on a network server. Hope you can help. Thanks!

// tennet

[Svengali]

I'm a bit in the dark as to how this might be resolved... 1) I developed QuickSave on the PC - I'm not Mac savvy at all. 2) Also, I haven't actually tested the PC version on a network - I'm not really sure ZScript is meant to deal with network file operations and would have to defer to other ZScripters who might have some informed input here about that.

The error message is generated by a routine that follows each save operation using a simple "fileexists" test - displaying the warning you are seeing if it cannot confirm that the file was actually written on the path used for the save.

Sorry I couldn't be more help. :confused:

Sven

[Toymaker_71]

Svengali,

I took a class from Scott Spencer last fall and he taught us many amazing things. Showing us your tool was one that was simple but truely invaluable. Thank you!


Cheers

[Svengali]

Toymaker_71:

A big thanks back at you for YOUR gracious note. It sounds like that class of Scott's is one I'd like to sit in on if he ever takes it on the road.

Sven

[kilik128]

hi sVen your's work on this plugin is very amazing

i have maybie suggestions but i'am not sure is possible to do it
is about rendering by compositing you know like
spécular bump color shadow etc...
and one render .zbc on mass can be usefull
but i hope is implemented in zb4 so just wait and see:)

thank's again !

[j.fernwright]

any chance a option could be added to have the image files automatically generated with the name of the selected subtool?(including iteration as usual)

[TuSo]

Just using it for images works fine in 4.0. Tell lemo his bcast works as well.
Thanks to both of you.

[sasquatchpoacher]

I LOVE the quick save Model and incremental save [+] for saving ztools. Is there any chance we could get a Project save button and incremental [+] Project save for the new file types?

[precisionart]

I second that. perhaps also a timed, auto, incremental project save:)

[Svengali]

Could someone explain to me what the big advantage is saving the Project over Saving the Model (Tool)?



The Project feature allows you to save nearly every aspect of what you're working on, with a single click.

The Project file contains the most important elements loaded in ZBrush:

Document size and colors
Loaded Tools and their SubTools
Current Tool position
Camera position
All maps assigned to a Tool or SubTool
Floor Visibility
Perspective value

The Project file doesn't contain:

Textures residing in the Alpha or Texture palettes
Position of the elements in the User Interface like opened menus
Brush settings if they have been changed, or brush inventory


When saving the Tools and their subtools, they ALREADY INCLUDE ALL maps assigned to a Tool or SubTool(s).

It seems to me saving a project really only saves additional trivial information that normally doesn't change or information that is momentary or transient.

So, I really don't see what value there would be in saving iterations of the Project file over iterations of the Model (Tool) file?

Sven

EDIT: check that, I think I see... Saving a project saves ALL existing tools in one shot, right?

Then, it would seem to me a practical way to design such a Project QuickSave option would be if it saved only a limited number of versions, for example five, where as once the fifth incremental version had been saved, the next save would overwrite the first. Then the next would overwrite the second and so on. Open to opinions and suggestions here. :)

[kilik128]

just one suggestions about BPR render save all pass (shadow occ ...) in one click

about saving project i love can save light tool material at same time
and keep my render setting it's save lot of time
the desadvantage of ZPR is take lot of memory if you forget clean your project before save and i don't know how do it i just read that's somewhere

[Svengali]

New button for QuickSave4 = Project and P+

Right now I've setup the incrementing Project button's save option so that it only saves the FIVE most recent versions of a Project: for example (after the first version is saved with the Project button) each press of the P+ button will generate, MyProject002.zpr on through MyProject005.zpr.

Then, after pressing P+ once more, MyProject001.zpr is OVERWRITTEN with the latest Project data. Next time P+ is pressed, MyProject002.zpr is OVERWRITTEN, and so on.

So, you see there will only be five backups in a given Project series. I'd appreciate any feedback on this before finalizing and posting the ZB4 version of QuickSave, especially for those who create complex Projects in a production environment.

- Does this make sense?
- Is five recent backups enough?
- What is the average size of a production-scale Project file? (one heavy with subtools, materials and textures.)

- I'm thinking of a similar option (9 most recent versions) for the Model M+ buttons. Any votes for that?

Feedback appreciated, thanks. When the new QuickSave4 is finalized I'll post this week or next.


Sven

[precisionart]

I would prefer more as i like to keep a history of my work. What i do with your previous version is save incremental until I get many dozens then i go back and delete all but #1, #10, #20, #30, #40 etc.

Five would not be enough. Is it necessary to have it start over? could you have a toggle or user set value?

[tennet]

I also prefer to be able to save an "unlimited" number of model versions and then delete most of them when the project is finished.

[Scott Spencer]

Just popping in because I'm updating the second edition of my book and I wanted to see what Sven had updated on the script. I wanted to say this script is the single greatest ZBrush utility in my opinion. How anyone works without it!

Svengali rocks :)

Scott

[guilemo]

Any news about this? Seems like such a great script!

[Svengali]

Here is an unofficial updated version - named QuickSave4 - in which I've made several modifications AND added Project save buttons.

Before officially posting this new version I would ask a few people who already use QuickSave to test its functionality and reliability on NON-CRITICAL projects and models to verify that it is properly working.

REPEAT: This is an unofficial version for TESTING PURPOSES ONLY.

When I'm sure it's been tested and working I will post an announcement with the final version of QuickSave4 in the ZBrush ZScript Utilities Forum. (target date: December 26th) at which time I will edit this post and remove this unofficial test version posted here.

What has changed?

1. Some routines have been simplified (internal code).
2. The M+ Subtools polygon readout problem reported by rv_el and CastorPT in another thread should now be resolved (Thanks to marcus_civis for pointing out an obscure ZScript quirk - and it's work-around)
3. Added buttons for Project and P+ which work similar to all the other QuickSave button pairs.

NOTE: I had considered a mode for saving a limited number of versions (where updates would begin saving over older versions after a maximum of ten had been saved) but based on feedback from users I've left things the way they were. This means that YOU must police the accumulation of incremental versions and delete the excess copies yourself - manually thinning the herd so to speak.


Thanks ahead of time to anyone who tests QuickSave4, then posts feedback here.

Svengali

<edit: Please load the updated test version of QuickSave4 below...>

[CastorPT]

Hi Svengali,

So far I found some issues when trying to use the M button to save the model, I get the following error:

Zscript Note: Specified routine could not be found
[RoutineCall,SaveModeInfo9]

if I use the M+ button then it works ok but I cannot choose the folder for the increments.

And good call on not having looped saving but forcing the user to manage, its really useful to have the history of the work being done!,

[Svengali]

CastorPT,

Thanks very much for the feedback. I've updated the script and wonder if you could test this new version to see if the problem has been resolved?

Svengali

[kilik128]

:D :D :D Nice !!!!!!!!!!!!!!!!!!! amazing tHankx !! always and again !
you get my forever respect ! :tu: :tu: :tu:

[rv_el]

Sorry man but it still has the same error. I hit M+, it saves a new file and tells me its saved it. Then from there on out until I reset Zbrush and all that I cannot get a popup on a subtool.

[Svengali]

Sorry man but it still has the same error. I hit M+, it saves a new file and tells me its saved it. Then from there on out until I reset Zbrush and all that I cannot get a popup on a subtool.

OK, I'll have another look at the M+ save function this weekend and see if I can reproduce the error... and fix it.

Sven

[Svengali]

OK, I'll have another look at the M+ save function this weekend and see if I can reproduce the error... and fix it.

Sven

rev_el,

I just ran a test with the the demosoldier model, saved it... saved it again incrementally... hid some of the subtools and saved it incrementally a third time and still the subtool popups were functional - displaying poly and point counts, etc.

Could you try the demosoldier model in your ZBrush setup and see of you still have the problem? If you can't see the subtool popups with that model, I'd guess the problem isn't with QuickSave4.

Sven

p.s. To anyone else using QuickSave4 who reads this... would you take a minute to test the demosoldier model with QuickSave incremental save(M+) and report back if you find a problem with the subtool popups? Thanks.

[rv_el]

That worked. So I do not know whats going on with my files.

The only thing i can guess right now is how big the file is. number of subtools, how cranked up the subtools may be, and the end result file size. I work with very very large zbrush files.

*shrug*

I don't know.

[tennet]

Hi! I've been using the old version of the Quicksave plugin until now (with ZB4), but I have ran into some problems now. I was doing retopo work and saved 6 increments, all files were saved "correctly" (~91mb each), but suddenly Zbrush crashed. When trying to load my tools again, then ZBrush just crashes again. And it keeps crashing every time I try to load any of the tools saved during that session using Quicksave?!

Does this have anything to do with the old plugin or is it something with Zbrush 4? Is it possible to load/restore these saved tools in some way (I managed to do quite a lot of topo work before the crash...)?

Hope someone can help. Thanks!

/ Tennet

[jawa64]

as it is quicker to load models when they are in their lower subdiv. Would it be possible to add another button to Svengali's quicksave plugin that has tool:SubTool:AllLow adding lowering subd to the action of saving?

[TarBeeBee]

Isn't Quicksave already saving it @ it's lowest subdiv level for each subtool?



This plugin is absolutely indispensable, thank you Svengali for making it! :)

[Daniel Biggers]

Is this issue of crashing when you save supposed to be fixed in zb4?

Svengali do you know when the final version will be realeased after you have finished the beta testing?

Also I want to thank you in advance for creating a script to help us out here that are pulling our hair out. :) I found this thread looking for info about the crash so I am excited to use your plugin and I love the incermantal save feature!!!

Zbrush 4
When I go to save a Zbrush project I click save as and then I get a beep and the program freezes. Even when all subtools
are at their lowest level.
It does it for any model...incl zbrush stock ztools
I cant even save a ztool.

Had to uninstall and reinstall to fix issue.
Note if yo do have zbrush set up to do an auto recovery and you open that auto recovery then go to pick a new project
and it says project had been changed do you want to save say YES!!!

Items used from new install to crashing issues increased mem to 512
undo tool to 20
did optimization check on multithreading.
turned on auto recovery
note: I noticed when I used the interactive light plugin it kinda froze for a bit and then went back to normal.

BTW I havent used the shortcut to save I always just go to the menu.

I am crossing my fingers that this plugin will save me because like everyone else after I have lost several hours, repeatedly due to me selecting save and then it crashing its really messing with my creative juice flow.

[kilik128]

quick obj can be fun:cool:

[Daniel Biggers]

Still having the issue but at least with this plugin it has been able to save 90% of the time, so thank you very much! I put in a tcket to helpdesk to find out what the issue is but even if zbrush didnt crash this is a great plugin. I love the incremental save feature!!!

[tennet]

I am using Quicksave 4 with ZB4R2 on Mac and I just noticed that when saving incremental copies (using M+) then my Polygroups are messed up (they are changed randomly). This plugin works perfect in ZB4R2 otherwise, but I haven't noticed this until tonight. Anyone else having the same problems? Maybe something to do with ZBrush 4R2?

[marcus_civis]

tennet,

If you are creating polygroups at higher subdivision levels then this is likely to be what is causing the issue. Switching to the lowest level can degrade the polygroup (and tools are saved at lowest level). Creating polygroups at the lowest level will avoid the problem.

[tennet]

Thanks Marcus! That seemed to be the problem. I deleted lower SDiv's and now it works!:)

[Svengali]

tennet,

If you are creating polygroups at higher subdivision levels then this is likely to be what is causing the issue. Switching to the lowest level can degrade the polygroup (and tools are saved at lowest level). Creating polygroups at the lowest level will avoid the problem.


marcus,

thank you for this heads up on consistent creation of lowest level polygroups... Good to know.

I've been concentrating on other software (2D) and my ZBrush has been shelved for a while - consequently I've grown a little rusty with scripting, especially with Z4 and up. I'm getting back up to speed with this latest release and will try to solidify QuickSave and some other old scripts too. I also bring back with me a few new ideas I want to work on.

For the moment, judging from other responses here, I'd surmise the version of QuickSave posted here IS working under Z4 but perhaps there still may be some room for improvement. I'll know more after I get back to it.

Anyway, Happy New Year and a personal thanks for all the work you do, on going, for the entire ZBrush community.

Sven

[spaceboy412]

Sven, i've always loved this plugin, i use the image saving feature the most, it would be cool if you could update it to include .jpg now that zbrush supports it.

[marcus_civis]

Sven, i've always loved this plugin, i use the image saving feature the most, it would be cool if you could update it to include .jpg now that zbrush supports it.

Spaceboy - excuse me butting in, Sven - I think that including JPG will not be possible as this option has its own interface (giving a preview and adjustments) which is not scriptable.