*** Update Quick Save Maps v0.6 released ***
Quick Save Maps v0.6 has just been released. I also made a little video about the new feature set:
[ame="
http://www.youtube.com/watch?v=ZVh6glcUTOI"]Quick Save Maps v0.6 - New features[/ame]
To sum up the best new features and improvements:
- Easy installation through Adobe Extension Manager!
- Added compound RGBA maps (ability to replace each individual RGB channel with a layerset)
- Added DDS support
- Added CryTIF support
- Added ability to choose different resampling method per texture (So normal maps can be scaled with Nearest neighbour for example).
- Allow fixed-size rescaling
- UI: Duplicate maps
- UI: Adjust number of maps per page
- UI: Reorder maps
- UI: "Jump to" interface for easier navigation
****
Replies
http://home.insightbb.com/~jamestaylor/
At least, last time I checked which was last month.
so Yeah if your working with CS5 it might be a good idea to look at Felix' script=)
I understand your concerns, but to make it a bit clearer, here are the advantages of Quick Save Maps over the other 2 tools discussed:
- No need to shuffle layers around before saving them, you can virtually hit the "save" button at any time: The tool will detect what map you are working on all by itself, then hide the rest of the document and save the image the way you want it. After it is finished, all original layer visibilities are restored and it will seem like the script never touched the document.
- No need to toggle anything invisible yourself: The tool will hide all other layers but the current layer set
- Very easy interface where you can visually add any amount of new maps with custom naming conventions
- You have a handy tool to export / import your settings in order to share them among team members. Also the configuration file is an easy-to-read XML document if you want to tweak it manually.
- More file formats: PNG, TGA, TIFF, JPEG and even BMP just for the lols
- To batch save all maps no further configuration needs to be done - you can place one hotkey to save your current map and another one to batch save all maps.
- No assumptpions: No need to name the toplayer "uv" or something to hide it because everything but the current texture map / layerset will be hidden anyway.
I carefully designed this tool to be very user friendly, easily understandable and of course very very quick.
Thanks,
Felix
a whole lot of them on the wiki. I personally like d1vSave, dunno why
But yeah you can pretty much do all this with qSave and some fairly simple Photoshop scripting (which is what I've already done personally), mostly using lots of isolate groups etc., the advantage being that you can do some more advanced stuff like moving a map to the alpha channel and such.
Some questions / suggestions about your script :
- You don't talk about paths, can you save files to different paths? Often times in production the PSD files aren't stored in the same folder as the maps. You should be able to define paths relative to the original path (this is something qSave doesn't do very well).
- No mention at all of alpha channels, can you chose if they're saved or not?
- You seem to be missing the DDS format, which is pretty standard in games, even if most companies use an intermediary like TGA or such most of the time.
I deliberately chose not to include alpha channel support for this release since we were using separate transparency maps during our last production. I am, however, actively working on implementing that. Subsequent releases will of course be free of any charge.
For the next release I plan to essentially allow the user to choose a file format and configure it with all the options that the file format comes with. The biggest challenge here is to keep the user interface as clean as it is now.
As for the DDS: I would need to look into the possibilities here, since the DDS exporter itself is just a plugin to Photoshop. Again, in our last production we would save our maps out separately which was super quick and easy with this tool and then run it through a converter.
As for the paths: I would love to hear your recommendations and usage examples. It should not at all be hard to add that, but first I need to know how this could be useful in a production environment.
Wesley:
If you are free to do so and interested, you could pass me a copy of that file for benchmarking. The PSD testing-files that I have been working with had little to no overhead using this tool. It would be very interesting to benchmark it against that 1GB monster file of yours.
In danger of repeating myself, I would like to let you guys know that I will in no circumstances charge for this tool twice. All releases from here on are included by buying it once. I will update the information on my website to communicate that more clearly.
Thank you for your interest,
Felix
I decided to post an interface snapshot of the upcoming v0.5 release, just to give you guys a teaser of what QSM v0.5 will be capable of and to give you a chance to give your opinion on it.
Screenshot here
I think the snapshot should speak for itself but I will list the best new features here:
Near-completion Features for v0.5:
- Custom Path
- Resampling techniques
- Customizeable File Formats (JPG, TGA and PNG have been completed so far)
- Any amount of maps, 3 per page to fit any screen.
- Save the alpha channel (when background is checkered in PS)
- Save another map instead as the alpha channel
- Convert to grayscale
- Invert Red / Green (to flip normal maps)
- Save settings to PSD
- Every texture map will store settings for each configured format, even if it is not used. This means you can change between them without loss of data.
- Extended XML configuration possibilities, here is what a texture map looks like in the back-end: QSM xml configuration
Of course all of those options are coupled with the one-key-saving-a-map-sweetness. It only means more options to configure what happens when you hit that special key.
Cheers,
Felix
Just letting you guys know - especially the sceptics - that Quick Save Maps version 0.5 has been released. It is a complete overhaul of v0.4 and incorporates all requested features plus more. For the folks who already bought v0.4, there should be a download link in your inbox for your free copy.
If you are interested, check these locations for more info:
Video overview: http://www.youtube.com/watch?v=ja4bPjBX5PY&feature=youtu.be
You can also check the docs and the Quick Save Maps website.
Cheers,
Felix
Good luck with all yer hard work.
@FelixSchl
got a feature you missed that should be there, post export commands with wildcards, would be especially useful when working with a engine like source, since you could export out hte maps, than run a tool on the output to convert to tga to vtf.
or even basic commands like copying the file to a preset location would be nice too.
Sorry I can't pass that on.
But the new updates look awesome. Especially like having the gloss in the alpha of the spec.
That feature is already there - it is the "post processing" feature I talked about. You have a large number of wildcards available that should mostly cover any situation. I talk about that in part 3 of the intro tour. you can also find a list of available wildcards there (I name them "Tokens").
However, most of my textures don't have alpha channels, but the hair diffuse, would always contain the transparency in the alpha. Can the tool be configured to work in such instances? If I didn't want an alpha channel on half my open textures, but did on the other half, does the tool see that there is no layer set named "alpha" or whatever, and just not save an alpha for that texture?
I'm currently using the QSave script which is great, but doesn't cope witht this sort of funcitonality. If this tool does, Im going to have to grab a copy to test tomorrow I think.
The configurations you make, including those for the alpha channels, are either stored externally in a central configuration file or directly with the PSD itself. This way you can configure the PSD that contains the diffuse map + alpha separately from the ones without the alpha channel.
If both of the textures you are talking about reside in the same document it becomes as easy as adding a new map to your configurations.
I hope that helped,
Felix
What you are describing is currently not possible but could surely be implemented. In fact, I will make it an official 0.6 target. I was thinking about it before, when I was adding the alpha channel support.
I am always open for suggestions
I will need to look into the DDS story first since admittedly I have not been working with this format myself yet. However, if the converter has a command line interface, you could definitely use the post-processing tool for that for now. It would probably be easiest to call a custom batch file though to handle the actual argument passing and file referencing. If you need help with that please let me know and I will try to assist where possible
http://developer.nvidia.com/content/dds-utilities-83111271645
Just letting you guys know that I just released Quick Save Maps v0.6. I also made a little video about the new feature set:
[ame="http://www.youtube.com/watch?v=ZVh6glcUTOI"]Quick Save Maps v0.6 - New features[/ame]
To sum up the best new features and improvements:
Big thanks to felipefrango for testing and ideas!
PS.: I'm not getting paid to say this, I just like this tool a lot.
I've thought about just this, saving out different layers into specific channels, and with different sizes of the files. And now especially on top of that with dds support.
For example, atm i'm doing an arttest for an company with there own engine. The diffuse is straightforward DX5 2^ map, the specular should be a DX1 scaled down to 1^ with the specular in the red channel and the gloss in the green. This script would speed up that process tremendously. Just saying, and no, i'm not paid either.
I say it trumph the other two pretty badly. Except that it's 10$, and that's a bummer. I'm a student and 10$ for a script is not really justifiable for me personally. Not right now anyway. This one is actually a script do consider paying for, for once.
I can understand you mate, I am still a student too. And yes, the scenario you described is absolutely possible. I am using this tool in our 5 month student production at school right now for much the same purpose.
That is, I am doing this:
Color (RGB) + Opacity (A) - DXT1/3/5 depending on alpha method
Normal (RGB) + Parallax (A) - DXT3
Specular Color (RGB) + Specular Power (A) - DXT5
Btw, I am using DDS for the first time, if the above is an incorrect approach please let me know. Point is though, that I can do all this with a bit of QSM configuration, then hand the config of to the team and then iterate on my maps like nothing.
Edit: Good luck with your arttest by the way!!
Going way off topic here but interesting none the less.
http://wiki.polycount.com/PhotoshopTools#Export_Tools
I love QuickSaveMaps and I use it constantly. The speed I can iterate at now without having to do stupid things like saving is awesome!! File dialogues are annoying.
Thanks for your hard work.
One thing I'm having issues with is the CryTif format saving out. CryTif is installed and set up correctly ( i use it every day) however QSM gives me errors saying it's not installed. Not sure if it's a bug or I'm doing something incorrectly. Thank you again for the awesome tool!
Long story short, it might be related to either a change in the Photoshop version of cryTIF version that breaks this method. I can look into it tomorrow morning.
Edit:
Where can I grab a copy of the relevant plugin files? Was not planning on downloading the whole sdk if I don't have to.
http://csprance.com/wp-content/uploads/2014/01/cryTiff.7z
There is the CryTiff plugin not sure if there is a difference between the 3.4 and 3.5 versions so I included them both.
Any update on this plugin?
However, csprance already helped me a good bit diagnosing the issue. I just started downloading the massive crySDK - so I will have it fixed by the weekend I hope, given csprance or another volunteer with access to both cs5 and cs6 and maybe cc is willing to help out - I need someone to run tests because I only have access to cs6 at this present moment and am unlikely to get my hands on other versions.
It's definitely will speed things up! Again, thank you.
But so far it didn't give any error whatsoever, maybe we can safely ignored it? Or can we make it auto delete that particular temp .dds file?