07-22-2016, 09:31 PM
Hi Kresimir,
I thought I'd start a new thread from my previous called 'retime ram usage' since this is really a new topic. I am trying to resolve the fact that I've used all ram on this node simming a WT sim to get the detail needed, and now need to slow the sim. I realize that the normal procedure is first running WT and then RT, however the RT process requires more ram than the WT sim needed and I'd need entirely new hardware to pull this off since this node is maxed at 72GB of ram.
(I'm calling 'post processing' RT since my primary focus is to retime the sim).
Is there a way to add the capability to the RT process to preserve the WT channel data so that an RT can be done first and then the WT process run after?
This would allow us to add maximum detail as our ram would allow during the WT process 'after' the RT process and and not have to keep it to approximately 60% so that there is still ram available for the RT phase. (The number could be wrong - that's what a few tests showed on this node).
I did try cheating the process by first running an RT of a default sim, preserving all channels, then loading the RT cache into the default folder and running WT on it. What I got was this strange error which didn't make sense since the WT data was definitely recorded with the default sim (arrow drawn pointing to it) and something about 'non null pointer to 12'... I'm guessing my cheat didn't work.
In the RT channels to be saved, I noticed there is TEX. I was hoping that was the WT channel, however since this didn't work, I'm guessing it's only texture coordinates.
In any case, could this feature be added? To allow for this order of simming: Default > RT > WT ?? Would help a lot of users to save on ram requirements for these huge detailed sims that need to be slowed.
I thought I'd start a new thread from my previous called 'retime ram usage' since this is really a new topic. I am trying to resolve the fact that I've used all ram on this node simming a WT sim to get the detail needed, and now need to slow the sim. I realize that the normal procedure is first running WT and then RT, however the RT process requires more ram than the WT sim needed and I'd need entirely new hardware to pull this off since this node is maxed at 72GB of ram.
(I'm calling 'post processing' RT since my primary focus is to retime the sim).
Is there a way to add the capability to the RT process to preserve the WT channel data so that an RT can be done first and then the WT process run after?
This would allow us to add maximum detail as our ram would allow during the WT process 'after' the RT process and and not have to keep it to approximately 60% so that there is still ram available for the RT phase. (The number could be wrong - that's what a few tests showed on this node).
I did try cheating the process by first running an RT of a default sim, preserving all channels, then loading the RT cache into the default folder and running WT on it. What I got was this strange error which didn't make sense since the WT data was definitely recorded with the default sim (arrow drawn pointing to it) and something about 'non null pointer to 12'... I'm guessing my cheat didn't work.
In the RT channels to be saved, I noticed there is TEX. I was hoping that was the WT channel, however since this didn't work, I'm guessing it's only texture coordinates.
In any case, could this feature be added? To allow for this order of simming: Default > RT > WT ?? Would help a lot of users to save on ram requirements for these huge detailed sims that need to be slowed.