animated texture - expression looping doesnt work

[jmfowler]

octane animated texture - expression loop doesn't work IE ( octaneImageTexture1.frameExtension=frame%250 ) causes crash or doesn't work, and if i delete the expression Maya deletes the entire image node.

You can manually disconnect the expression from the image node in the graph editor ( delete link) and then manually keyframe the extension but the node -STILL- attempts to load a succesive numbered frame instead of the frame applicable from keyframing. in the image attache 1-250 load fine but then maya says it can't load .xxx despite the fact its not supposed to be loading above 250???

[JimStar]

All works OK in my case...

I just set the "Use Image Sequence" checkbox in the Octane Image Texture, then:

Code: Select all

//I have 24 frames
setAttr -type "string" expression1.expression "octaneImageTexture4.frameExtension=frame%24"

And voila - "Image Number" is set accordingly when I change the current frame...

Can you please just post here the simple sample scene where it is done your way and crashes?..

[jmfowler]

ah i found the problem - it doesn't work for Float image textures... see my image I was using float image texture sequence in bump Channel - keeps crashing but now i change it to just ( full colour) image texture and it works.

Jimstar - I entered your code in the mel script ( modified for me) and it worked - BUT if I try to edit the expression in the expression editor maya crashes???


EDIT : I've also just learn't that the expression requires the texture sequence to start with extension 0000 instead of 1 since the repeat looks for it ( for anyone reading this )

[JimStar]

ah i found the problem - it doesn't work for Float image textures... see my image I was using float image texture sequence in bump Channel - keeps crashing but now i change it to just ( full colour) image texture and it works.

Float image texture works for me OK too...

Jimstar - I entered your code in the mel script ( modified for me) and it worked - BUT if I try to edit the expression in the expression editor maya crashes???

Can you describe exact workflow you use when you get the crash?.. What you do, press, open, etc...
As I can't reproduce it so far...

EDIT : I've also just learn't that the expression requires the texture sequence to start with extension 0000 instead of 1 since the repeat looks for it ( for anyone reading this )

No, it depends on your expression. If you set something like "octaneFloatImageTexture1.frameExtension=frame%250+1" as expression - you should not have the sequence starting with "0000", but with "0001".

[jmfowler]

JImstar - here is the file, 1 mesh with 2 shaders applied, the top surface has animated bump map using octaneFloatImageTexture.

If i go to expression editor and click edit - maya crashes every time, if I use mel code it updates but then crashes when i move along the time line.
I have already rendered this scene before, but since i try to use animated water using expression it crashes. - and if I delete the link between the expression and the texture node and try manually key framing - octane appears to still look for a frame extension not related to the new information ...

https://dl.dropbox.com/u/61350979/Anima ... ureTest.mb
https://dl.dropbox.com/u/61350979/color.zip

UPDATE : hmmm... there seems to be something specifically in my main large file thats causing octane to look for the wrong extension once the expression loop kicks in. ( after frame 250 in my case - at frame 252 it look for extension 252 ....etc ) I got it working in the small file above but my main has some problem causing this.

expression editor is damaged, just noticed this - // Error: file: C:/Program Files/Autodesk/Maya2013/scripts/others/expressionEditor.mel line 2350: Object 'EEexprNameT' not found. //

UPDATE : I deleted my pool and its textures out of my main scene and imported the pool from the small file (above) with new names etc, frame extension is working properly now ( and using expressions) - weird?? alas my expression editor still crashes but at least i can edit the expression from the mel command line.

[JimStar]

Yess! Found the problem.
Will be fixed in next version.
Thank you!