[SDK] Force ICE-Tree refresh

[Vincent Ullmann]

Hey List,

Iam looking for a way to reset/reEvaluate a ICE-Tree.
There are currently two examples were i need this.

1.)
I have a Render-Scene with some Point-Clouds reading a single icecache-file.
When i change the icecache-file on the Disk, my PointCloud wont update, 
until i reOpen the Scene or change the Frame-Input on the Cache-on-File-Node


2.)
I startet to write a Custom-Tool, wich uses the nice new Feature in 2014 
to directly write ICE-Attributes. Everything is working write now. So i 
can change a Attribute via a Python_Script or Cpp-Tool, but the Changes 
are only visible if i somehow force an Update (eg. Change something else 
in my ICETree)


I think this should be possible, but had no succes so far.

Re: [SDK] Force ICE-Tree refresh

[Sandy Sutherland]

Have you tried using a Mixer input rather than cache node?

S.

On 2013/07/15 9:54 PM, Vincent Ullmann wrote:

Hey List,

Iam looking for a way to reset/reEvaluate a ICE-Tree.
There are currently two examples were i need this.

1.)
I have a Render-Scene with some Point-Clouds reading a single 
icecache-file.
When i change the icecache-file on the Disk, my PointCloud wont 
update, until i reOpen the Scene or change the Frame-Input on the 
Cache-on-File-Node


2.)
I startet to write a Custom-Tool, wich uses the nice new Feature in 
2014 to directly write ICE-Attributes. Everything is working write 
now. So i can change a Attribute via a Python_Script or Cpp-Tool, but 
the Changes are only visible if i somehow force an Update (eg. Change 
something else in my ICETree)


I think this should be possible, but had no succes so far.

Re: [SDK] Force ICE-Tree refresh

[Alan Fregtman]

Putting in an If node and toggling the condition value couldn't force a
refresh?



On Mon, Jul 15, 2013 at 4:54 PM, Vincent Ullmann <
vincent.ullm...@googlemail.com> wrote:

> Hey List,
>
> Iam looking for a way to reset/reEvaluate a ICE-Tree.
> There are currently two examples were i need this.
>
> 1.)
> I have a Render-Scene with some Point-Clouds reading a single
> icecache-file.
> When i change the icecache-file on the Disk, my PointCloud wont update,
> until i reOpen the Scene or change the Frame-Input on the Cache-on-File-Node
>
> 2.)
> I startet to write a Custom-Tool, wich uses the nice new Feature in 2014
> to directly write ICE-Attributes. Everything is working write now. So i can
> change a Attribute via a Python_Script or Cpp-Tool, but the Changes are
> only visible if i somehow force an Update (eg. Change something else in my
> ICETree)
>
> I think this should be possible, but had no succes so far.
>

Re: [SDK] Force ICE-Tree refresh

[Vincent Ullmann]

@Sandy:
Hmm... i kind a dont like the Mixer...  ;-)
But i will give him a try tomorrow, for the caching

@Alan:
Yes, i tried a if-node and that worked, but it doesnt seemed like the 
best Solution. :-)

Becouse i had to modify the tree.


Image, you have a Brush-like-Custom-Tool, to modify Particle-Colors. In 
that Case you need interactive Feedback, and dont want to change to much.

I tried commands like the "ResetObject()", but i didnt worked





Am 15.07.2013 23:14, schrieb Alan Fregtman:
Putting in an If node and toggling the condition value couldn't force 
a refresh?




On Mon, Jul 15, 2013 at 4:54 PM, Vincent Ullmann 
> wrote:


Hey List,

Iam looking for a way to reset/reEvaluate a ICE-Tree.
There are currently two examples were i need this.

1.)
I have a Render-Scene with some Point-Clouds reading a single
icecache-file.
When i change the icecache-file on the Disk, my PointCloud wont
update, until i reOpen the Scene or change the Frame-Input on the
Cache-on-File-Node

2.)
I startet to write a Custom-Tool, wich uses the nice new Feature
in 2014 to directly write ICE-Attributes. Everything is working
write now. So i can change a Attribute via a Python_Script or
Cpp-Tool, but the Changes are only visible if i somehow force an
Update (eg. Change something else in my ICETree)

I think this should be possible, but had no succes so far.

Re: [SDK] Force ICE-Tree refresh

[Raffaele Fragapane]

An if node at the bottom of the stream is actually A GREAT solution, and we
have many standard graphs built procedurally that always feature one in a
name coded compound.
Not only it allows you to force a bottom-most pull reliably at your
convenience, it also makes sure you can always reliably disable/enable
graphs procedurally at a whim without having to deal with the often
finnicky operator stack.

A compound with two ports, an if evaluated one and a pass through, costs
nothing in performance and is a great way of comforming graphs and gaining
control over their eval without going insane trying to script within the
domain of an ICE tree (which is by its nature tricky at the best of times).


On Tue, Jul 16, 2013 at 8:54 AM, Vincent Ullmann <
vincent.ullm...@googlemail.com> wrote:

>  @Sandy:
> Hmm... i kind a dont like the Mixer...  ;-)
> But i will give him a try tomorrow, for the caching
>
> @Alan:
> Yes, i tried a if-node and that worked, but it doesnt seemed like the best
> Solution. :-)
> Becouse i had to modify the tree.
>
>
> Image, you have a Brush-like-Custom-Tool, to modify Particle-Colors. In
> that Case you need interactive Feedback, and dont want to change to much.
> I tried commands like the "ResetObject()", but i didnt worked
>
>
>
>
>
> Am 15.07.2013 23:14, schrieb Alan Fregtman:
>
> Putting in an If node and toggling the condition value couldn't force a
> refresh?
>
>
>
> On Mon, Jul 15, 2013 at 4:54 PM, Vincent Ullmann <
> vincent.ullm...@googlemail.com> wrote:
>
>> Hey List,
>>
>> Iam looking for a way to reset/reEvaluate a ICE-Tree.
>> There are currently two examples were i need this.
>>
>> 1.)
>> I have a Render-Scene with some Point-Clouds reading a single
>> icecache-file.
>> When i change the icecache-file on the Disk, my PointCloud wont update,
>> until i reOpen the Scene or change the Frame-Input on the Cache-on-File-Node
>>
>> 2.)
>> I startet to write a Custom-Tool, wich uses the nice new Feature in 2014
>> to directly write ICE-Attributes. Everything is working write now. So i can
>> change a Attribute via a Python_Script or Cpp-Tool, but the Changes are
>> only visible if i somehow force an Update (eg. Change something else in my
>> ICETree)
>>
>> I think this should be possible, but had no succes so far.
>>
>
>
>


-- 
Our users will know fear and cower before our software! Ship it! Ship it
and let them flee like the dogs they are!

Re: [SDK] Force ICE-Tree refresh

[Ciaran Moloney]

Did you try Desktop.RedrawUI() ?  Will probably want to have a OGL window
open somewhere...


Ciaran

On Mon, Jul 15, 2013 at 11:54 PM, Vincent Ullmann <
vincent.ullm...@googlemail.com> wrote:

>  @Sandy:
> Hmm... i kind a dont like the Mixer...  ;-)
> But i will give him a try tomorrow, for the caching
>
> @Alan:
> Yes, i tried a if-node and that worked, but it doesnt seemed like the best
> Solution. :-)
> Becouse i had to modify the tree.
>
>
> Image, you have a Brush-like-Custom-Tool, to modify Particle-Colors. In
> that Case you need interactive Feedback, and dont want to change to much.
> I tried commands like the "ResetObject()", but i didnt worked
>
>
>
>
>
> Am 15.07.2013 23:14, schrieb Alan Fregtman:
>
> Putting in an If node and toggling the condition value couldn't force a
> refresh?
>
>
>
> On Mon, Jul 15, 2013 at 4:54 PM, Vincent Ullmann <
> vincent.ullm...@googlemail.com> wrote:
>
>> Hey List,
>>
>> Iam looking for a way to reset/reEvaluate a ICE-Tree.
>> There are currently two examples were i need this.
>>
>> 1.)
>> I have a Render-Scene with some Point-Clouds reading a single
>> icecache-file.
>> When i change the icecache-file on the Disk, my PointCloud wont update,
>> until i reOpen the Scene or change the Frame-Input on the Cache-on-File-Node
>>
>> 2.)
>> I startet to write a Custom-Tool, wich uses the nice new Feature in 2014
>> to directly write ICE-Attributes. Everything is working write now. So i can
>> change a Attribute via a Python_Script or Cpp-Tool, but the Changes are
>> only visible if i somehow force an Update (eg. Change something else in my
>> ICETree)
>>
>> I think this should be possible, but had no succes so far.
>>
>
>
>