Hi,
weird, this is not common.
Please remove the installed c4doctane version and upgrade to 2022.1.2-R4:
https://render.otoy.com/customerdownloa ... R4_win.rarPlease use 7zip to uncompress the .RAR archive, it is free:
https://www.7-zip.org/Then, it is possible to generate a log from the daemon, and run it in a more verbose mode.
Please, copy paste the attached `octane_daemon_log.txt` file in the Render-Node directory:
Then please perform a rendering session with Network rendering active, and the Render-Node connected until slowdown.
Then navigate to `C:\Users\UserName\AppData\Local|temp`, or write %TEMP% in the Explore path field.
Locate the octane_damon_log.txt file and share it, thanks.
It would be nice to have also the corresponding c4doctanelog.txt file from the Workstation.
So before starting to render in Network, please, open a scene that is giving you issues, then go to c4doctane Settings/Log Output tab, and enable all the Log option checkboxes.
Then, load the scene in Live View with Network rendering active, then in Picture Viewer until slowdown, then go to c4doctane Settings/Log Output tab, press the "Generate log report" button, and share the octanelog_report.zip file, thanks.
ciao,
Beppe