@aRtBee

 

1. then you are missing the point of SSDs... they are intended to be used anywhere where fast Read/write is helpful... just because they can't be  swap files are an example... or files which require high speed  I/O... mySSD can write at least 5 times faster than my RAID"0" C drive.... whci is why I use it for my windows swap... and why I'd like to use it for other things... but it does not seem to be much help for Poser.

2. RAM disks are fine and well as long as the computer stays powered on... lose power you lose your temp files... which under certain circumstances may be "a bad thing" for example using memory for a swap disk is  probably not a good thing... nor for storage for things you have not saved to permenant storage... nor files which are used to stop, start or cache information used by Windows or your applications.

3. Yes and the point of the temp folder is? Looking at the actual files [which includes the rendered image cache] tells me theres nothing there that could not be put on a different drive than the %user appdata%

4. Yes the renders are cached in the same location [maybe you have not tried what I have done]. I moved the whole poserpro app data temp file cache to a different location. Apparently FFRender64 is hard coded to use :AppData:Roaming:PoserPro:9:RenderCache: to store the image as it is being rendered... upon completion of the render the file is copied to the temp file location... in my case this means that the files is rendered onto my C drive then at the completion of the render it is copied to the RenderCache on my D: drive... which sort of makes the whole idea of being able to move the temp folder' moot

I'll be glad to take a look at your tutorial... but seems to me I'm barking up the wrong tree as apparently moving the temp files achieves no useful purpose... so much so that one wonders why the feature still exists... especially since the programmers hard coded where the images will be rendered.