My render instances don't seem to be working at render time. When I send my scene to the live viewer I get 50 mil polys and a frame renders in about 3 minutes. No problem there. But when I send to the picture viewer my polys go up to 99 mil and the render times skyrockets to over an hour.
Any ideas? Attaching the scene here.
C4D 2024.1, Octane 2023.1 Beta3 R4 (issue persists with 2023.1 R3 and post fog is rendering different)
Cinema4D version 2023.1-[R7] (Obsolete stable) 25.11.2023
Moderators: ChrisHekman, aoktar
- Attachments
-
- PIT_v20.zip
- (3.47 MiB) Downloaded 72 times
No. This is caused by Take system and its own render setting per take. And not saving is problem but rendering using custom Ocio from Take. Many times it ignore Ocio. There is need to manually set it even if it is already set.aoktar wrote: Saving problem must be related with your side, not us.
EDIT : It looks like the same interface issue as Custom AOV - different thing is displayed but something different is internally executed.
Last edited by SSmolak on Fri Oct 27, 2023 11:20 am, edited 2 times in total.
Architectural Visualizations http://www.archviz-4d.studio
- nycjunglist
- Posts: 25
- Joined: Tue Dec 22, 2015 6:20 am
At the moment in C4D 2024.1.0, it looks like adding an Octane Object tag to an Octane Scatter source/surface object set to Surface distribution—not Vertex—results in a crash. See attached gif.
This issue does not occur in C4D 2023.2.
This issue does not occur in C4D 2023.2.
Ryzen 9 3950x | 128 GB RAM | 2x 3080Ti
- DetNyeSort
- Posts: 4
- Joined: Tue Nov 17, 2020 11:47 am
This scenefile (See attached file) instant-crashes the moment I start the render, if camera motion blur is on.
I've tested it in both C4D V2023 and C4D V2024 using Octane 2023.1-[R1], Octane 2023.1-[R2] and the older Octane 2022.1.1-[R4] - it's all the same thing.
I'm using X-particles in the scene as well, but completely removing this makes no difference. It still crashes instantly, taking C4D down with it.
Link to file: https://we.tl/t-IlUHReYpWA
Also, on a side note, for this same project but in a different project file I've noticed that camera motion blur if the camera is following a spline using the "align to spline" tag is completely messed up, I really can't explain what is happening other than everything becomes one big blurry mess. EDIT: This seems to only happen if the spline being used for the "align to spline" tag is generated using the tracer object.
I've tested it in both C4D V2023 and C4D V2024 using Octane 2023.1-[R1], Octane 2023.1-[R2] and the older Octane 2022.1.1-[R4] - it's all the same thing.
I'm using X-particles in the scene as well, but completely removing this makes no difference. It still crashes instantly, taking C4D down with it.
Link to file: https://we.tl/t-IlUHReYpWA
Also, on a side note, for this same project but in a different project file I've noticed that camera motion blur if the camera is following a spline using the "align to spline" tag is completely messed up, I really can't explain what is happening other than everything becomes one big blurry mess. EDIT: This seems to only happen if the spline being used for the "align to spline" tag is generated using the tracer object.
Last edited by DetNyeSort on Fri Oct 27, 2023 12:43 pm, edited 1 time in total.
I'm checking it, source object having zero triangles when a tag droped over for a moment. I think it's related to performance changes of C4D 2024.nycjunglist wrote:At the moment in C4D 2024.1.0, it looks like adding an Octane Object tag to an Octane Scatter source/surface object set to Surface distribution—not Vertex—results in a crash. See attached gif.
This issue does not occur in C4D 2023.2.
Last edited by aoktar on Fri Oct 27, 2023 12:05 pm, edited 1 time in total.
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
I've a bit reduced the clones for spikes for testing. As you can see here we have same amount of triangles in LV and PV. Be sure the option is checked in Octane Settings window. And having less triangles on spikes that would make your life easier.gohmn wrote:My render instances don't seem to be working at render time. When I send my scene to the live viewer I get 50 mil polys and a frame renders in about 3 minutes. No problem there. But when I send to the picture viewer my polys go up to 99 mil and the render times skyrockets to over an hour.
Any ideas? Attaching the scene here.
C4D 2024.1, Octane 2023.1 Beta3 R4 (issue persists with 2023.1 R3 and post fog is rendering different)
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
Never noticed this option "Shared mesh for render instances"
Should be on by default? What it does exactly?
Thanks
Should be on by default? What it does exactly?
Thanks
Yes ON by default. One shared mesh for original and copies. Otherwise we create two meshes in totalthanulee wrote:Never noticed this option "Shared mesh for render instances"
Should be on by default? What it does exactly?
Thanks
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
Thanks Aoktar,aoktar wrote:I've a bit reduced the clones for spikes for testing. As you can see here we have same amount of triangles in LV and PV. Be sure the option is checked in Octane Settings window. And having less triangles on spikes that would make your life easier.gohmn wrote:My render instances don't seem to be working at render time. When I send my scene to the live viewer I get 50 mil polys and a frame renders in about 3 minutes. No problem there. But when I send to the picture viewer my polys go up to 99 mil and the render times skyrockets to over an hour.
Any ideas? Attaching the scene here.
C4D 2024.1, Octane 2023.1 Beta3 R4 (issue persists with 2023.1 R3 and post fog is rendering different)
I did toggle that off and then back on again. Not sure if it helped but I did manage to start a render with the proper amount of polys. It seemed to be an intermittent issue without a discernable cause.