animation exposure doesn't match

[Elele]

I send a PM Paul.

[Elele]

So I downloaded the new version, how can i export the scene?

Check the

OcDS: System Tab - Export scene

For now a link to an old post that shows a screen shot with the export settings and some other information:

viewtopic.php?f=44&t=44402#p219089

- - -
If you are not yet familiar with OctaneRender standalone the online manual has been updated with a lot of information:

https://docs.otoy.com/#51Interface%20Overview

There are also links to video tutorials on the landing page:

https://docs.otoy.com/#rOctaneRender%20Universe

- - -

Thanks for the info. So far I can export as alambic, but then there are no materials or as a scene, but then there is no animation. Much to my surprise the scene render looks exactly the same as the DS render though which is pretty cool. I'll look into it some more.

[linvanchene]

Thanks for the info. So far I can export as alambic, but then there are no materials or as a scene, but then there is no animation. Much to my surprise the scene render looks exactly the same as the DS render though which is pretty cool. I'll look into it some more.

Jup. It is either or at the moment. (did not retest with 2.24.3 but its not mentioned in release notes so I guess that is still accurate)

BUT

You as a workaround you can:

- export the scene as ORBX

- export just the camera as alembic.

- load ORBX first in standalone

- load the camera abc file

- unpin the static camera from the ORBX and make a new pin connection with the imported abc camera.

compare screenshot posted here:

viewtopic.php?f=44&t=51398&start=50#p256544

- - -

[face_off]

Thanks for the info. So far I can export as alambic, but then there are no materials or as a scene, but then there is no animation. Much to my surprise the scene render looks exactly the same as the DS render though which is pretty cool. I'll look into it some more.

At some point I'll change the export process so it wraps the ABC in an ORBX and does all the camera and materials reconnections for you. But it's a lower priority task, so it might be a few releases before it's done.

Paul

[Elele]

Jup. It is either or at the moment. (did not retest with 2.24.3 but its not mentioned in release notes so I guess that is still accurate)

BUT


- - -

I use a static background scene and camera, and only rotate a specific mesh for the turntable. So I don't think that way will work for me. I guess I could export the specific mesh as alembic and combine it with the static scene in the standalone. Though the material names also dissappear with the alembic and I'm left guessing which material goes where.

[linvanchene]

Jup. It is either or at the moment. (did not retest with 2.24.3 but its not mentioned in release notes so I guess that is still accurate)

BUT


- - -

I use a static background scene and camera, and only rotate a specific mesh for the turntable. So I don't think that way will work for me. I guess I could export the specific mesh as alembic and combine it with the static scene in the standalone. Though the material names also dissappear with the alembic and I'm left guessing which material goes where.

Seems the situation with ORBX animation export is worse than I was aware off. I was under the wrong impression that objects animated in the DAZ Studio timeline that are captured as keyframe in the DAZ Studio timeline and its plugins (like Keymate) are exported. This does not seem to be the case.

Scenes exported as .ORBX do not include key frames for objects animated in the DAZ Studio time line

I just did a test scene with a sphere moving from the front to the back and when importing the .ORBX in standalone there is no time line at all.

Workflow to replicate:

- add plane to scene
- add sphere to scene
- manually place a keyframe for the translation value in the DAZ Studio Keymate plugin
- move slider to 15 frames
- translate the sphere to the background
- make a test render of the animation in OcDS

- export the scene as ORBX from the OcDS system tab
- open scene in OR standalone

If animation data would be included in the scene there would be a timeline below the viewport.

- - -

I attached the test scene in .duf and .ORBX format as a .zip file.

[face_off]

Yes. It appears the fixing of the Shadow Visibility has caused a problem with non-Final rendering. I am investigating now. The original issue where the exposure doesn't match is because the Animation has a different environment assigned compared with when a single frame is rendered.

Paul

[Elele]

Yes. It appears the fixing of the Shadow Visibility has caused a problem with non-Final rendering. I am investigating now. The original issue where the exposure doesn't match is because the Animation has a different environment assigned compared with when a single frame is rendered.

Paul

is that a problem with the software or just with my settings? How do i get the correct environment in the animation?

[face_off]

is that a problem with the software or just with my settings? How do i get the correct environment in the animation?

There is a lot going on with this issue....

1) When you click Final, all the geometry gets loaded into a single Octane Mesh node - which means the emitter brightness changes. The "Surface Brightness" pin in theory corrects this. I believe rendering an animation uses Final - so in theory, your Final render emitter brightness should match your animation emitter brightness.

2) You scene has a different Environment selected in the Environment tab to the Animation tab. In the Animation tab click the "Fill in current setup" to match the two.

3) There is a plugin bug where a single frame render that is NOT Final is excluding some geometry in your scene. The problem was introduced in 2.24.2.3, and I am working on a fix ASAP.

Paul

[Elele]

I tried loading the environment settings for the animation (and some other things like linvanchene advised earlier in this thread), but that doesn't change anything. I also added the exported environment settings the the file i sent you earlier.

Pressing the final render button for a single render does indeed cause the issue too. So I guess I'll have to recalibrate the lighting for the animation.
For some reason some of the lights have the "surface brightness" on while others have not.

Thanks for the help!