Octane preventing C4D from closing.

[TonyBoy]

All my Scenes hang now (404 OK-2018 hangs), The c4doctanelog contains and finishes with a boatload of <markMaterials>.

[TonyBoy]

[quote][2019-05-26 13:29:42][1] Register OctaneLive
[2019-05-26 13:29:42][0] Loaded Octane DLL:OctaneRender Enterprise 2018.1.3 version:5000013 SDK:2018.1.3
[2019-05-26 13:29:42][0] Octane Render VR for Cinema 4D 2018.1.3 built for:190 C4D vers:19068
[2019-05-26 13:29:42][0] C4D:19068 comp:[LICENSEDUSER-PC] OS:[WINDOWS 64 BIT] Windows 7, 64 Bit, Professional Edition Service Pack 1 (build 7601) opengl:460 sysInfo:32 versType:2
[2019-05-26 13:29:42][0] CPU:[GenuineIntel, stepping 6, model 7, instruction family 6] speed:2.5 GHz numOfCpu:8
[2019-05-26 13:29:42][0] Plugins:[browser io_obj mkmodeler xtensions addons advanced render alembic archigrass bitmapfilter bpexchange ca ca2 cineman clothilde collada14 collada15 colorchoosergui compositing dwg dwgobjects dynamics exchanges expressiontag fbx gpurenderer hair houdiniconfig houdiniengine iges i_skp licenseserver metrics mocca model mograph motioncam motiontracker newman objects okino onlinehelp onlineupdater python relaxuv sculpt sculptbrushes shader sketch sky sla spacemouse substance teamrender texturemanager thinking particles tpoperators walkthrough xpressocore Cagedeformer CDAlignToCam CDConstraints CDHPBView CDIKTools CDJointSkin CDMorph CDPSTracksX CDSelectParent CDSpringyKeys CDSymmetry CDTransfer 3dquakersMatR18 Forester1ExpansionPack1R18 Forester1ExpansionPack2R18 3dquakersR16 ForesterR16 IvyGrower c4dOctane-R19 3dquakersR18 ForesterR18 ]
[2019-05-26 13:29:43][1] LoadOslScripts()
[2019-05-26 13:29:43][1] LoadCustomLuts()
[2019-05-26 13:30:04][1] <markMaterials>
[2019-05-26 13:30:06][1] <markMaterials>
[2019-05-26 13:30:40][1] <markMaterials>
[2019-05-26 13:31:05][1] <markMaterials>
[2019-05-26 13:32:03][1] <markMaterials>
[2019-05-26 13:33:03][1] <markMaterials>
[2019-05-26 13:33:13][1] <markMaterials>
[2019-05-26 13:33:13][1] <markMaterials>
[2019-05-26 13:33:14][1] <markMaterials>
[2019-05-26 13:33:17][1] <markMaterials>
[2019-05-26 13:33:19][1] <markMaterials>
[2019-05-26 13:33:19][1] <markMaterials>
[2019-05-26 13:33:19][1] <markMaterials>
[2019-05-26 13:33:20][1] <markMaterials>
[2019-05-26 13:33:20][1] <markMaterials>
[2019-05-26 13:33:21][1] <markMaterials>
[2019-05-26 13:33:21][1] <markMaterials>
[2019-05-26 13:33:22][1] <markMaterials>
[2019-05-26 13:33:22][1] <markMaterials>
[2019-05-26 13:33:23][1] <markMaterials>
[2019-05-26 13:33:25][1] <markMaterials>
[2019-05-26 13:33:26][1] <markMaterials>
[2019-05-26 13:33:26][1] <markMaterials>
[2019-05-26 13:33:27][1] <markMaterials>
[2019-05-26 13:33:27][1] <markMaterials>
[2019-05-26 13:33:28][1] <markMaterials>
[2019-05-26 13:33:30][1] <markMaterials>
[2019-05-26 13:33:30][1] <markMaterials>
[2019-05-26 13:33:31][1] <markMaterials>
[2019-05-26 13:33:31][1] <markMaterials>
[2019-05-26 13:33:39][1] <markMaterials>
[2019-05-26 13:33:40][1] <markMaterials>
[2019-05-26 13:33:40][1] <markMaterials>
[2019-05-26 13:33:41][1] <markMaterials>
[2019-05-26 13:33:41][1] <markMaterials>
[2019-05-26 13:33:42][1] <markMaterials>
[2019-05-26 13:33:46][1] <markMaterials>
[2019-05-26 13:33:55][1] <markMaterials>
/quote]

[aoktar]

Tonyboy,
It's hard to track when many people sent messages in to same topic. Send me a PM if you wish me check it by a remote connect.

[GSMATTAnimation]

I am having problem with a fresh installed copy of Cinema 4D R20.059 and Octane Render 4.04-R2. No matter what layout causes the crash!
I do have R18 installed and with Octane Render 4.04 installed with custom layouts and do not have the same issue.

[Iceman9]

I have a theory about what might be causing these crash-on-quit or hang-on-quit problems. I can't yet comfirm, but I have a bit of evidence.

I use two different workstations for my 3d work. Which makes machine A is the slave sometimes, and other times machine B is the slave.

But by default both machines boot with the Octane render slave app active.

Yesterday I was crashing repeatedly when exiting. I noticed that I had the slave daemon active. I quit the slave daemon app and in a dozen open/save operations since then....it has not crashed on quit.

So perhaps having both c4d open with the Octane plugin active and the slave daemon on the same machine at the same time is what is causing the crashes.

[thewhiteleaf]

I still suffer from this issue. Any insight or updates?

Thank you!

[SimonKn]

Been having the exact same problem and have solved it on my side by going 'edit - preferences' 'Open Preferences Folder' (in Cinema) and then deleting the Octane folder that was in the plugins folder there.
I think the plugin should only exist in 'C:\Program Files\MAXON\Cinema 4D R20\plugins'

[thewhiteleaf]

Been having the exact same problem and have solved it on my side by going 'edit - preferences' 'Open Preferences Folder' (in Cinema) and then deleting the Octane folder that was in the plugins folder there.
I think the plugin should only exist in 'C:\Program Files\MAXON\Cinema 4D R20\plugins'

You're not going to believe this but I just so happen to figure this out yesterday. I was going to post an update when I saw your response. I had an older version of Octane installed in the Preferences plugins folder and the current version in the MAXON plugin folder.

[Iceman9]

If someone comes to this thread and is having c4d hang or crash upon quitting the program...if you review this thread you'll find that most (or all) of the time the problem was having either the Octane slave active on the same machine...or having two copies of the plugin installed (in different plugin folders). It is probably not a software bug at all. Review your configuration.

[Aleksei]

Been having the exact same problem and have solved it on my side by going 'edit - preferences' 'Open Preferences Folder' (in Cinema) and then deleting the Octane folder that was in the plugins folder there.
I think the plugin should only exist in 'C:\Program Files\MAXON\Cinema 4D R20\plugins'

If someone comes to this thread and is having c4d hang or crash upon quitting the program...if you review this thread you'll find that most (or all) of the time the problem was having either the Octane slave active on the same machine...or having two copies of the plugin installed (in different plugin folders). It is probably not a software bug at all. Review your configuration.

None of these helped...