However the nvtt command line tools sound like they work in x64, so you could probably use James Taylor's vSavePSDTGA to invoke it as a CMD whenever you save.
The script can call a command line function when run - allowing post processing of images through proprietary tools or droplets.
Microsoft offers a DDS editing tool (DirectX Texture Editor) in the DirectX SDK. It's annoying to have to install the SDK just for that app, but if it's needed......
I tried but id didnt work.
So I found a forum thread which refers to an Adobe Installer error and a CrapCleaner (CCleaner) registry scan would sort it out.
And it worked!
A lot of file extensions were refered as corrupt, CCleaner deleted them and I was able to re-associate them within windows.
We had to go with the photoshop 32bit as well to get .dds saving abilities, I think I started a thread about this a while ago. Pretty lame but I guess nvidia assumes game teams will have custom texture pipes that convert images as part of the build step.
In response to the issue of 64-bit incompatibility, I wrote a simple javascript-based tool (really just a front end for Nvidia's Texture Tools 2 command-line functionality) for exporting DDS files from 64-bit versions of Photoshop. Although the tool works with 32-bit and 64-bit flavors of Photoshop, it's not as feature rich as Nvidia's plugin. As such, Nvidia's plugin probably makes more sense for 32-bit Photoshop installs. Please check out the tool, and let me know what you think. : )
Replies
However the nvtt command line tools sound like they work in x64, so you could probably use James Taylor's vSavePSDTGA to invoke it as a CMD whenever you save.
On the other hand I think using 32bis is ok because Im not a photographer who uses 24MP pictures and even a multilayered 32k pixel file was ok to use.
But I will try this script stuff with texture tools 2.
I renamed photoshop.exe to photoshop.exe_0000 but still not able to re-associate the files with windows tools.
Its so annoying.
So I found a forum thread which refers to an Adobe Installer error and a CrapCleaner (CCleaner) registry scan would sort it out.
And it worked!
A lot of file extensions were refered as corrupt, CCleaner deleted them and I was able to re-associate them within windows.
http://docs.kaneva.com/mediawiki/index.php/Photoshop_DDS_Exporter