Page 1 of 1
Shader overwrites on alembic files and issues with MB
Posted: Thu Jun 13, 2024 2:53 pm
by cph_visuals
Hi,
Latest release of plugin Cinema4D version 2023.1.3-R3 seems to have a bug where applying shaders to alembic files no longer works.
Additionally motion blur for the first frame of render is not correct when using render instances. This bug has been around for a while.
See attached file.
Tested on two machines.
A. Operating System: Win 11
B. Graphics Card: 4080 machine A & 4090 machine B
C. RAM Capacity; 64GB both machines
D. Nvidia driver version: 546.33 both machines
E: Cinema version 2023.2.2 both machines
F. OctaneRender plugin version 2023.1.3-R3
Re: Shader overwrites on alembic files and issues with MB
Posted: Thu Jun 13, 2024 6:23 pm
by aoktar
Thanks to you for reporting, it looks like related to R3 updates for bringing the extra UVWs sets. Now it does ignore the UVW creation if you don't have any UVW tags. I'm gonna fix it!
You can stay with 2023.1.3-R2 until that's fixed or make a work around.
Re: Shader overwrites on alembic files and issues with MB
Posted: Fri Jun 14, 2024 12:04 am
by cph_visuals
Sounds great, thanks! Seems like it's a pretty workaround!
Any progress on the pesky motion blur bug when render instanced geo is loaded on the first frame?
Re: Shader overwrites on alembic files and issues with MB
Posted: Fri Jun 14, 2024 12:14 am
by aoktar
cph_visuals wrote:Sounds great, thanks! Seems like it's a pretty workaround!
Any progress on the pesky motion blur bug when render instanced geo is loaded on the first frame?
It's not a common thing so give your example to let me see, you'll see the fix in R4 build for first problem btw!
Re: Shader overwrites on alembic files and issues with MB
Posted: Fri Jun 14, 2024 10:09 am
by cph_visuals
Sounds great, thanks!
Regarding the odd render instance issue, you can also see it in my provided example with the alembic file. Seems like the live viewer works correctly most of the time, but try and render to picture viewer and you can see the first frame the transforms for the render instances are shifted and snap into place by the second frame.
It's a real headache when rendering on a renderfarm because rerendering those frames always gives the offset result even when rerendered. As a workaround for the past months, we generally open the file and switch back to instance and rerender single frames, but it's a pain, since we usually have more than 50 million polys in a scene when we don't do render instances.
Re: Shader overwrites on alembic files and issues with MB
Posted: Fri Jun 14, 2024 10:34 am
by aoktar
It will work fine if you pull out your source object from the group. Assume that's a quick work-around.