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
Shader overwrites on alembic files and issues with MB
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
-
cph_visuals
- Posts: 9
- Joined: Wed Jun 19, 2019 4:05 pm
- Attachments
-
- ABC_test.zip
- (8.46 MiB) Downloaded 42 times
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.
You can stay with 2023.1.3-R2 until that's fixed or make a work around.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
-
cph_visuals
- Posts: 9
- Joined: Wed Jun 19, 2019 4:05 pm
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?
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!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?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
-
cph_visuals
- Posts: 9
- Joined: Wed Jun 19, 2019 4:05 pm
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.
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.
It will work fine if you pull out your source object from the group. Assume that's a quick work-around.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw