A few issues with nightly 13610

[jensl]

Hi,

Not sure if these are fixed in the newer builds but here goes:

-The currentFrame seems to change now as I render, it always seems to move forward a frame and I'm not sure why. This is troublesome when you are trying to keep rendering the same frame and do comparisons.
-Coverage pass still has invisible lights (which means renderID/objectID and non-aliased render elements aren't usable when there's an invisible light cutting through things in coverage)
-new ObjectID pass is great and batch renders OK but interactively I get black buckets, even when only my local computer is rendering (e.g. it's not a build mismatch or DR issue).


Jens

[vlado]

-The currentFrame seems to change now as I render, it always seems to move forward a frame and I'm not sure why. This is troublesome when you are trying to keep rendering the same frame and do comparisons.

Can you explain this one a bit more?

-Coverage pass still has invisible lights (which means renderID/objectID and non-aliased render elements aren't usable when there's an invisible light cutting through things in coverage)

It is on the "to do" list.

-new ObjectID pass is great and batch renders OK but interactively I get black buckets, even when only my local computer is rendering (e.g. it's not a build mismatch or DR issue).

Do you have a scene for this? I can't reproduce it in the scenes I tried.

Best regards,
Vlado

[jensl]

Hi,

1. To explain this further, I render a frame interactively, frame 200. When the render completes, the timeline is now at 201. I render again, although I meant to render frame 200. This seems to be linked to using a velocity render element and turning on distributed rendering - when it's on, and the velocity render element is enabled, it moves forward a frame, but then doesn't move back a frame when rendering completes. When distributed rendering is off, it does move back a frame.

3. I've attached a screen grab of object ID as rendered on my computer without distributed rendering. It should be all green, but some buckets render black no matter what.

[vlado]

Ok, interesting. Can you get us a scene for this to vraymaya@chaosgroup.com?

Best regards,
Vlado

[jensl]

Hi, A few more notes from nightly 13610 unless noted:

1. Image planes don't respond to different gamma settings in the v-ray extra attributes.
2. Render elements should have an 'enabled' checkbox in the extra vray attributes, currently it's only in the less usable extra attributes tab.
3. (works in nightly 13989) V-Ray light mtl doesn't seem to work with opacity well, problems mapping a file texture and map opacity.
4. V-Ray Mtl does not have hardware texturing option to use self illumination map, which would be handy in some instances. Also, self illumination map could benefit from a compensate camera exposure checkbox like light mtl.
5. (nightly 13989) Open Maya, set V-Ray, open VFB, load image from history, save image to exr - no images saved, no errors. Works once a render is done, then the history image loaded and saved.