INSYDIUM plugins causing "incorrect" error reporting, c4d

6 views
Skip to first unread message

Tom Durrant

unread,
Feb 18, 2026, 2:36:49 PM (2 days ago) Feb 18
to Royal Render Knights Tavern
We have some machines that have got INSYDIUM plugins installed for some projects in cinema 4d (x particles etc). 

INSYDIUM distribute these plugins for every version of c4d inside the plugins folder, this causes c4d to report an error, but still render the frame correctly. The rrCheckexitcode then checks the exit code and of course it reports wrong, and royal render then reports the render as having errored. 


I'm not sure if there's much that royal render can do in this case, is there? Potentially ignoring those errors, but that feels a bit wrong too. 


Here's some logs, and i've uploaded a sample project 7z to the upload too


```

285| Current time:Feb 18. 19:20.54

R286| Total processing time: 00:00.28 h:m.s

R287| Max memory usage: 5.2GB (of 255GB installed, total system usage at same time: 27.0GB. Feb 18. 19:20.42)

R288| Max CPU usage: 1% 0.9 of 64 cores (total system usage at same time: 0.0. Feb 18. 19:20.38)

R289| .

R290| Max GPU usage:5% 0.1 GPUs (of 2 GPUs assigned to this thread. Max system GPU usage at same time: 0.1/2. Feb 18. 19:20.46)

R291| Max GPU memory usage: 32.1GB (of 63GB installed. Feb 18. 19:20.50)

R292| TCP data: IN: 19MiB OUT: 1MiB. Max TCP speed: IN: 2MiB/s (Feb 18. 19:20.50) OUT: 0MiB/s (-.-)

R293|

R294| ************************* LOCAL RENDER INFORMATION *************************

R295| Total render files found: 2

R296| Files successful copied: 2

R297| Files broken/not copied: 0

R298| Total render files (main pass only): 2

R299| FrNr mCXRFV: FSize CopySpeed Filename ('mCXRFV' legend: m=main C=copied R=successfully read X=Exr reencoded F=image verify fail V=rrViewer cache created)

R300| 0 mC R V: 0.4 MB \rr_test\test_project\Under0000.tif

R301| 19 mC R V: 0.4 MB 23.8MB/s \rr_test\test_project\Under0019.tif

R302| ************************* CLIENT REPORTS DURING THIS RENDER *************************

R303|

R304| Possible issue found in this log file (line 278): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM.xdl64: symbol 'g_maxon' is missing. [win_dll.cpp(545)] [general.cpp(746)]

R305| Possible issue found in this log file (line 279): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_21.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_21.xdl64 has wrong binary version 21014, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R306| Possible issue found in this log file (line 280): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_23.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_23.xdl64 has wrong binary version 23004, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R307| Possible issue found in this log file (line 281): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_25.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_25.xdl64 has wrong binary version 25004, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R308| Possible issue found in this log file (line 282): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2023.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2023.xdl64 has wrong binary version 2022901, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R309| Possible issue found in this log file (line 283): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2024.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2024.xdl64 has wrong binary version 2023904, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R310| Possible issue found in this log file (line 284): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2025.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/INSYDIUM_2025.xdl64 has wrong binary version 2025000, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R311| Possible issue found in this log file (line 318): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_20.xdl64: symbol 'g_maxon' is missing. [win_dll.cpp(545)] [general.cpp(746)]

R312| Possible issue found in this log file (line 319): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_21.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_21.xdl64 has wrong binary version 21014, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R313| Possible issue found in this log file (line 320): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_23.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_23.xdl64 has wrong binary version 23004, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R314| Possible issue found in this log file (line 321): WARNING: Error loading file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_25.xdl64: file:///C:/Program Files/Maxon Cinema 4D 2026/plugins/INSYDIUM/libraries/TerraformFX/terraformfx_25.xdl64 has wrong binary version 25004, expected 2026000. [module_dll.cpp(235)] [general.cpp(746)]

R315| Possible issue found in sep(arate) log file (line 208): <div class="DETAILED line"><div>19:20:36 3205MB DETAILED: </div><div> error: The specified module could not be found.

R316|

R317| Job task completed successfully.

R318|

R319| _______________________________________________________________________________________________________________________________

R320| _______________________________________________________________________________________________________________________________

R321| ' 19:20.57 rrC4D : rrKSO NextCommand ______________________________________________________________________________________________

R322| ' 19:20.57 rrC4D : rrKSO NextCommand 'ksoQuit()

R323| '

R324| ' 19:20.57 rrC4D : rrKSO NextCommand ______________________________________________________________________________________________

R325| ' 19:20.57 rrC4D : Closing TCP

R326| ' 19:20.57 rrC4D : rrKSO closed

R327| ' 19:20.57 rrC4D : KSO Session Ended, Exiting

R328|

R329|

R330| >"C:\Program Files\RoyalRender\lc64\rrCheckexitcode.exe" -1073740791 0 0 0

R331| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

0| ++ Feb 18. 19:20.59 Render executable closed ++++++++++++++++++++++++++++++++++++++++++++++++++++

1| ++ Royal Render checks the return code of the executable or the OS +++++++++++++++++++++++++++++++

2| ++ Executable returned -1073740791 (0xc0000409) as exit code for frame 0 (jobthread 0, instance 0).

3| ++ Error COULD be: The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

4| ++ => Executable crashed +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

5| ++ Sending message 0 1 23219 0 T0 I0

6| ++ 9.1.18a ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

7| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

8| >"\\192.168.47.1\LHS_projects\zz_technical\rr_test\RoyalRender\bin\win64\rrKillWait" 1 QTGUIAGENT -this -withoutParent

9| ||rrKillWait|| waiting 0.0s for QTGUIAGENT.EXE ... thisProcessGroup. withoutParent.

10| ||rrKillWait|| INFO: this process group was started by ... (ID 9768 CMD.EXE)

11| ||rrKillWait|| INFO: parent of our process group starter ... (ID 27204 RRCLIENTCONSOLE.EXE)

12|

13| +++++++++++++++++++++++++ All commandlines executed +++++++++++++++++++++++++++++++++++

14| +++++ Astrotrain rrClient 9.1.22

15| +++++ 19:20:59.85

16| +++++ Job ID: {0S4Va}

17| +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 

```

Don Culwell

unread,
Feb 18, 2026, 3:59:19 PM (2 days ago) Feb 18
to rrKn...@googlegroups.com
We haven't seen errors from XPart but are using the entire Fused suite (which includes xpart) so maybe that makes a difference. 

Our setup sources C4D plugins from a shared location using the env var  "g_additionalModulePath".   Our env vars are pushed out via Group Policy to systems but you could add it in the RR configs as well or add it manually.   Maybe that approach would help in your case. 

Cheers

-Don

--
If you reply, the message is send to the user group which is sufficient and desired.
("Reply All" might send the message twice to the last author which is not required.
Replying "in private" prevents other users to see the answers and might not be seen by the single receiver if he has email rules in place.
If you want to talk to us in private, please use support (at) RoyalRender instead)
---
You received this message because you are subscribed to the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rrKnights+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rrKnights/f141a7ad-e77d-4ee2-a151-ce2971f6eb4en%40googlegroups.com.

RR, Schoenberger

unread,
Feb 18, 2026, 4:27:03 PM (2 days ago) Feb 18
to rrKn...@googlegroups.com

Hi

I have seen those plugin messages many times with C4D over the years.
Some installers just install all plugin files for all C4D versions.

But: In all these cases it was just a warning.
C4D did not crash because of plugins that it did not load at all.


In your case C4D crashed.
rrCheckexitcode does not read any log, it just takes what the executable returns.

Side-note: Yes, the rrClient (and not rrCheckexitcode) has a function to find error messages in the log, but not in this case.  
The rrClient would add some info about it at the end.

 

 

 

There are two ways to go:
1) Ignore crashes for the job.
Not ideal, but if you have to render now….
Just remember to take a look at those jobs more often.


2) Find out what’s causing the crash.
It may be C4D or a plugin that crashes during unload.
It may happen if a scene actually uses some feature or it crashes always.


  • Start to test with a new scene that contains a cube only.
    Send it to one client only.
  • Remove plugins from C4D until it does not crash any more
  • I personally prefer “B) a) Crash Dump files – Windows”.
    https://www.royalrender.de/help/CrashLocation.html
    Then you should see which library was responsible for the crash.
    And the developers should be able to find the crash location with your dump file.

 

 

regards,
Holger Schönberger

Craftsman and Keeper of the Royal Render Flame

Please use the rrKnights Tavern
or our support system for new questions.

Reply all
Reply to author
Forward
0 new messages