Tweet
Hi there,
My team and I are currently working on a project where we are loading image sequences into a mesh light, my query works for loading/managing image sequences into Maya. We are currently finding that when sending to Vray Cloud, it's very hit and miss whether or not it'll actually show in render. The first problem we had was Maya seems to internally change the file name, eg: Image.0001.png > With 'image sequence' ticked, changes it to Image.1.png and then when sending to the cloud we got missing texture errors due to the renaming. We got around this by removing the padding, which is okay.
We could use the <frameNum> tag, but we are finding that whilst Vray knows what this is, Maya's File Path Editor throws a warning and then when sending to the cloud, it on occasions doesn't render Also we cannot offset using <frameNum> which isn't very flexible. I've also found this to be the same for sequenced caches through the proxy object, using <frameN>, renders locally fine > send to the cloud NOPE. No warning of missing file etc, just doesn't appear.
Just wondering how people have handled this? Whilst I think it's mostly an issue because we are sending to the cloud, I feel the way that maya handles sequenced assets and in some cases it just cannot by default.
Cheers,
Danny
My team and I are currently working on a project where we are loading image sequences into a mesh light, my query works for loading/managing image sequences into Maya. We are currently finding that when sending to Vray Cloud, it's very hit and miss whether or not it'll actually show in render. The first problem we had was Maya seems to internally change the file name, eg: Image.0001.png > With 'image sequence' ticked, changes it to Image.1.png and then when sending to the cloud we got missing texture errors due to the renaming. We got around this by removing the padding, which is okay.
We could use the <frameNum> tag, but we are finding that whilst Vray knows what this is, Maya's File Path Editor throws a warning and then when sending to the cloud, it on occasions doesn't render Also we cannot offset using <frameNum> which isn't very flexible. I've also found this to be the same for sequenced caches through the proxy object, using <frameN>, renders locally fine > send to the cloud NOPE. No warning of missing file etc, just doesn't appear.
Just wondering how people have handled this? Whilst I think it's mostly an issue because we are sending to the cloud, I feel the way that maya handles sequenced assets and in some cases it just cannot by default.
Cheers,
Danny
Comment