To b:
I once tried to cast rays from a camera to points in a pointcloud to determine visibility.
It was enough to have the camera connected to a raycast node and it was evaluated all the time - even if the raycast node was completely disconnected from
anything else.
This was on 2012 (without SP) - haven't tried since.
Gesendet: Mittwoch, 15. Mai 2013 um 11:33 Uhr
Von: "Sebastian Kowalski" <l...@sekow.com>
An: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com>
Betreff: heavy ice operation flaws
Von: "Sebastian Kowalski" <l...@sekow.com>
An: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com>
Betreff: heavy ice operation flaws
hey list,
i am feeling a bit bad because of complaining every time i am writing to this beloved list.
sorry, but…
a) load a heavy cache, generate a shitload of points, build up huge arrays and the ram consumption raises to max. well thats not the problem, but delete that cloud, plug off the cache reader the memory wont flush.. its stays that high.
seems to be reserving the ram, cause it wont rise higher when doing the operation again. ok i understand. but then setup a second cloud, do something similiar, and goodbye softimage.
b) having an hidden pointcloud in the scene does not say that that tree wont be evaluated when some param outside the tree is feeding it. like doing some cam frustum calculation.
c) similar to b), save a scene with an hidden object, simulated by an ice tree. its gonna evaluate, progress bar is up (and on win 7, its gonna hide itself behind the main application).
on occasions it also gonna ramp up on ram, and wont flush after saving is done. (when you got an HIDDEN pointcloud reading a cache )
thats all on 2013.
-sebastian
i am feeling a bit bad because of complaining every time i am writing to this beloved list.
sorry, but…
a) load a heavy cache, generate a shitload of points, build up huge arrays and the ram consumption raises to max. well thats not the problem, but delete that cloud, plug off the cache reader the memory wont flush.. its stays that high.
seems to be reserving the ram, cause it wont rise higher when doing the operation again. ok i understand. but then setup a second cloud, do something similiar, and goodbye softimage.
b) having an hidden pointcloud in the scene does not say that that tree wont be evaluated when some param outside the tree is feeding it. like doing some cam frustum calculation.
c) similar to b), save a scene with an hidden object, simulated by an ice tree. its gonna evaluate, progress bar is up (and on win 7, its gonna hide itself behind the main application).
on occasions it also gonna ramp up on ram, and wont flush after saving is done. (when you got an HIDDEN pointcloud reading a cache )
thats all on 2013.
-sebastian
