Hi Octane development team,
I have encountered two serious issues with OctaneRender 2026.6 / C4D Plugin 2.0.3 in Cinema 4D 2027.
Both issues do not occur in Cinema 4D 2025 using the same Octane plugin version.
Issue 1: Crash when rendering large Alembic (ABC) geometry
When rendering a scene containing large Alembic (ABC) geometry in Cinema 4D 2027, Cinema 4D crashes.
The scene contains no assigned materials or camera objects, and motion blur is disabled.
Test results:
C4D 2025 + Octane 2.0.3: Works correctly.
C4D 2027 + Standard Renderer: Works correctly.
C4D 2027 + Octane 2.0.3: Crashes.
I also checked the Cinema 4D crash report.
The exception is ACCESS_VIOLATION (0xC0000005) in c4d_base.xdl64.
The crashing thread contains the following call stack:
c4d_base.xdl64
c4d_base.xdl64
io_alembic.xdl64
io_alembic.xdl64
io_alembic.xdl64
io_alembic.xdl64
c4d_base.xdl64
This suggests a possible compatibility issue involving Octane's geometry extraction process and Cinema 4D 2027's Alembic evaluation.
Issue 2: Cinema 4D becomes unresponsive when scrubbing the timeline with Live Viewer active
When Octane Live Viewer is actively rendering in Cinema 4D 2027, dragging the timeline playhead causes Cinema 4D to freeze and become unresponsive.
The same operation works normally in Cinema 4D 2025 using Octane 2.0.3.
Steps to reproduce:
1. Open an animated scene in Cinema 4D 2027.
2. Open Octane Live Viewer and start interactive rendering.
3. Drag the timeline playhead to change the current frame.
4. Cinema 4D becomes unresponsive.
Expected behavior:
Cinema 4D should remain responsive while the Live Viewer updates the rendered scene as the timeline changes.
Actual behavior:
Cinema 4D freezes and stops responding.
I am not sure whether these two issues share the same underlying cause, but both appear to be related to the C4D 2027 integration.
System information:
Cinema 4D 2027.000
OctaneRender 2026.6 / C4D Plugin 2.0.3
Windows 10, Build 19045
Intel Core i7-13700KF
NVIDIA GeForce RTX 5070 Ti
NVIDIA Driver 580.97
Attachments:
1. Cinema 4D project file and the required Alembic cache.
2. Cinema 4D crash report (_BugReport.txt).
I have attached the project and crash report to help reproduce and investigate the issues.
Could you please investigate these problems?
Thank you for your help.
[BUG] C4D 2027 – Alembic rendering crash and Live Viewer timeline freezing (Octane 2.0.3)
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.
-
lhy2495724656
- Posts: 12
- Joined: Tue Feb 02, 2021 2:47 am
- Attachments
-
- abc-bug.7z
- (37.07 MiB) Downloaded 4 times
-
- _BugReport.txt
- (851.39 KiB) Downloaded 3 times
Windows 10
i7-13700KF
RTX 5070 Ti
Memory 32GB
NVIDIA Studio 610.62
i7-13700KF
RTX 5070 Ti
Memory 32GB
NVIDIA Studio 610.62
Hi,
Thanks for the report and the scene, they made it easy to reproduce.
Good news: it isn't Octane. The crash is a Cinema 4D 2027 bug in its Alembic module. Your ABC changes topology between frame 0 and frame 1, and C4D 2027 crashes when it evaluates across that change. The same scenes render fine in C4D 2025.3.3 and 2026.4 with the same Octane plugin.
To see it yourself, open the attached copy of your scene (abc-bug_noOctane.c4d, with all Octane data removed), put it next to abc1.abc and render frames 0–5 with the Standard Renderer. It crashes there too. The timeline freeze is very likely the same issue.
Until Maxon fixes it, you can work around it by starting your render from frame 2, or by re-exporting the ABC with constant topology.
ciao,
Beppe
Thanks for the report and the scene, they made it easy to reproduce.
Good news: it isn't Octane. The crash is a Cinema 4D 2027 bug in its Alembic module. Your ABC changes topology between frame 0 and frame 1, and C4D 2027 crashes when it evaluates across that change. The same scenes render fine in C4D 2025.3.3 and 2026.4 with the same Octane plugin.
To see it yourself, open the attached copy of your scene (abc-bug_noOctane.c4d, with all Octane data removed), put it next to abc1.abc and render frames 0–5 with the Standard Renderer. It crashes there too. The timeline freeze is very likely the same issue.
Until Maxon fixes it, you can work around it by starting your render from frame 2, or by re-exporting the ABC with constant topology.
ciao,
Beppe