Very old indeed! I've not launched softimage for years (sad). I remember this was finicky when it comes to the WAV, but if you used the embedded sin.wav, and the xsiaddon, not sure what is wrong. I'll try to see if this week end I can resurrect XSI for a few minutes and see if it works 'on my machin...

You have the latest binary DLL and add on on the github:https://github.com/claudevervoort-perso ... o-spectrum

Let me know if that works for you!

Claude

edit by owei: PLEASE USE URL TAGS..! THANKS ;)

Oh I see, if I understand well, all your particles are spawned at the same time so have the same age. If so, one way to address it would be at spawn time to bind a random value of when the explosion should start, and create a new attribute to drive the animation which would be: age duration - random...

Have you look at the timesource on the clip? You could use the particle age, or any other ICE attribute to drive which frame from the animation is displayed.

Claude

Yep I know it works when using shape instantiation, and I thought neither the doc nor Softimage itself (since it actually proposes those attributes that cannot work in the time source drop down) were clear on that limitation, and why I thought it might even be a bug. But I have beaten that one to de...

Nice setup! Definitely going to be more cumbersome than just playing with textures on my object, and so i'm torn between that and using the multi switch. Anyway thanks for taking the time to build it!

Claude

Actually I re-read the doc and I would tend to think it works on any object with ICE attributes, including ICE particles but not solely: The list includes ICE attributes only from objects used by this image clip (either directly on the object or indirectly if it's used via shape instancing). If it's...

Thanks TS for looking at it so closely! Obviously not the answer I hoped, it's a bit confusing that it does show the attribute in time source, that it works when you use the attribute on the shader tree directly (switch), but doesn't when you use it in the clip itself when looking directly on the ob...

I recreated a simple scene to illustrate the problem. You might have to point the image clip to the right location (i've included the images in the zip). In the image clip, I use time source the value of the attribute digit10 which is set by the ICE tree. It's a global object attribute and the displ...

The multi switch works! Sure a lot less convenient than using time source on the texture itself, but at least it's a work around. Sucks it's only up to 7, I think I'll need 2 switches to handle my 10 digits, and 2 attributes for each counter: one boolean for 0-1, and another one for 0-4 so that I ca...

olivier: I am not using shaped instances, just a plain mesh with an ICE tree on it to drive the counter texture on it. In the OGL view (high quality) it is showing the same number...

dave: color_switch, that sounds like a great alternative. Going to try that and let you know.

Thanks!

Claude

Thanks Olivier, it is now cycling through... time :( So did not change really, still picking up the value from global scene time and ignoring my ICE attribute. Again I think my main difference here is that I am not using it to drive particle instances, but rather a plain shader attached the polymesh...

Thanks for chiming in!

Unfortunately that does not solve it. The attributes do get updated (I have them to show in the viewport and they show they expected value). Maybe that is just a plain old bug, and i'll have to use scripting rather than ICE

Claude

Hi! I've been looking at that for a little while now and since I still can't it figure out, I'd thought it was time to ask for help :) So it is rather simple: I have a counter texture (10 pix, digit_00 to digit_09) which makes a sequence. I use that in my shader, but I want the value to come from an...

Oh thanks a ton Hirazi! I thought distributing a debug version was just a bit slower but otherwise OK. As soon as I am back on my PC i'll try to get a release build out, and update the add on accordingly.

Couple of weeks I'm afraid...

Sorry for the confusion,

Claude

I was scared of something just like that... Obvious first: it was compiled for 64 bits, just in case you use SI32. Is there any message outside of the Red flag? All libs (outside of VC++ runtime) are statically linked, so there should be no DLL to install. Unfortunately I'm on a trip away from my ma...