OTOY Forums

used2bgordy wrote:Hiya,

Version 2.01 and v 2.02
I don't know if it was already discussed but We're having problems with MatID and ObjectID channel.
We have a scene with a package and some cloners flying around. Mat ID changes once the cloners appear in the render (I believe they should stay the same).
Object ID keeps the same color for all cloners (each cloner has ~ 5 different objects)
I'd be nice to have a color option to set as MatID in the material and a color option to set as ObjectID in the Octane Object TAG.

Version 2.02
Randomly objects in cloners do not update while rendering sequence.
Also, MB (Motion Blur) Behaves strangely in LV, meaning it has rotation keys and deformation keys but it translates in Y.

Artur

Hi,
we have to change the logic for matID and objectID to be able assing user defined colors. I suppose that can be done in next versions.
I'm very interesting to see how couldn't get succes for unupdating the objects in animation rendering. Is it possible to send me a scene to check it?
Also LV and motion blur has tricky usage. Because LV cannot access the all data as Picture Viewer does. You should go frame by frame to see better results. Anyway this cannot guarantee to produce exact results.
When you should see correct results? If you send a render to Live Viewer or Picture Viewer.

here's link to the scene:

https://www.dropbox.com/s/mjde15y6ltsvl ... _scene.c4d

used2bgordy wrote:here's link to the scene:

https://www.dropbox.com/s/mjde15y6ltsvl ... _scene.c4d

Yes, matID colors are changing after first frame. But cannot see the problem about unupdated objects on rendering

About updating. It seems to come and go.
We switched machine and went back to 2.01 because of the time restriction. We couldn't test it more. It happened a couple of times though.


Artur

used2bgordy wrote:About updating. It seems to come and go.
We switched machine and went back to 2.01 because of the time restriction. We couldn't test it more. It happened a couple of times though.
Artur

please keep me informed any problems. I'm still working on update system on objects, for making it faster on viewport.

Yeah thanks.

Appreciate your help.

Artur

It is possible, scenes that were created with Vue xtream are, with the octane render to render?

Hi Ahmet-

A couple of issues have come up here in my studio. The Live Viewer suddenly restarts itself for no reason sometimes. Like you're testing a render in the LV and maybe letting it render for a few minutes and without even touching the computer it starts over. It's pretty annoying. It's happening on pretty much all our machines. Started with 2.01 I believe and continues with 2.02.

Another thing happening on one of my employee's computer is after he uses the focus picker the LV goes into a loop of one sample restarts. So it only renders one sample and then resets and renders on sample and resets and on and on. If he tries the focus picker again sometimes that fixes it and it'll render as usual, but not always.

Thoughts?

alec

ASyme1 wrote:Hi Ahmet-

A couple of issues have come up here in my studio. The Live Viewer suddenly restarts itself for no reason sometimes. Like you're testing a render in the LV and maybe letting it render for a few minutes and without even touching the computer it starts over. It's pretty annoying. It's happening on pretty much all our machines. Started with 2.01 I believe and continues with 2.02.

Another thing happening on one of my employee's computer is after he uses the focus picker the LV goes into a loop of one sample restarts. So it only renders one sample and then resets and renders on sample and resets and on and on. If he tries the focus picker again sometimes that fixes it and it'll render as usual, but not always.

Thoughts?

alec

ok not helpfull to find it. it's so common report. please check motion blur is on cameratag and any c4d cameratag. try to give me some scene which can produce this

I realize it's hard to diagnose from a description but that's all I've got right now. I'll see if we can make a movie of the problem. It's big problem though. I've got two guys that effectively can't work in Octane right now. We're going to step back to 2.0.22 as see if that fixes things, but it's pretty messed up right now.

I'll let you know what I find out.

Thanks
alec