Flat
05-25-2003, 02:33 AM
Last night my machine hanged while rendering some surface HVs. Not a big deal, even though it was a bad surprise.
The bad news came when I resumed the render : firstly there was a gradient for particle size that "forgot" which camera to track. Okay, easy to fix (but the scene file contains garbage where the camera reference should be).
Next, and this is the real problem, there is a distinct shift in texture position between the first render and the resumed one.
Same scene, same machine, different results. :(
I guess I'm not the first one to be bitten by this one (ouch !). Anybody found a solution ?
Note : this is not the texture motion bug where you have to use world-coords and the object itself as reference. Though it may come from a bad rounding when reloading the scene.
Phil, who doesn't want to restart a 15-hours render each time.
Edit : upon further inspection it's the hypertexture that got nudged a little. That's weird as this one is using local coords and no ref object.
The bad news came when I resumed the render : firstly there was a gradient for particle size that "forgot" which camera to track. Okay, easy to fix (but the scene file contains garbage where the camera reference should be).
Next, and this is the real problem, there is a distinct shift in texture position between the first render and the resumed one.
Same scene, same machine, different results. :(
I guess I'm not the first one to be bitten by this one (ouch !). Anybody found a solution ?
Note : this is not the texture motion bug where you have to use world-coords and the object itself as reference. Though it may come from a bad rounding when reloading the scene.
Phil, who doesn't want to restart a 15-hours render each time.
Edit : upon further inspection it's the hypertexture that got nudged a little. That's weird as this one is using local coords and no ref object.