Is it normal for material editor need about minimum 6sec + with 100% CPU to update/refresh preview when I change value of the material or add texture??
It’s the same pain from Corona for C4D 4.1 version till now with Daily build.
P.s. Material editor also freezes or crashes Cinema4D and I noticed the only difference sometimes if I turn OFF or ON core in task manager under Processor affinity :S
Cinema4D is R16.051
Are we the only one with this realy slow&freezing material editor since A4.1 “it was quite ok for survive” till A6 daily? 
This is tested on computer at home: i7 5930K, GTX970 (last update), 32GB, C4D R16.051
p.s. This happened after I installed the first Alpha A6…and now this is happening even when I give the old version back
Hi , same problem here… can’t work in this way, it happens even changing the material’s name!!
I can’t understand if I need a more powerful pc (hope not!! 
Yes it’s insane! The biggest problem is that, if we install back to the old version which worked like charm…the slow&freezing material editor party is still ther :S
You don’t need more powerful pc..it’s some kind of bug or i don’t know what 
Hi, tried in a “simple” mac book pro 13" with integrated graphic card , 4gb ram and i5 processor dual core, a 2012 laptop… but with cinema 4d R17… it’s work fine!! material editor super fast!!
So the bug probably is in earlier cinema 4d version??
At home I’ve got Cinema4D R16.051.
It’s weird, because at the moments it work normally.
Is there any way to completely delete CoronaforC4D from computer (register, some hidden files, etc) or is enough just to uninstall Corona from Programs and Features?
I would like to make clean install of Corona because after I’ve installed A6 was more or less ok. Now, even if I give the old version back the same thing happens :S
This 15 sec freeze of Cinema 4D is killing me…no matter what I click (add tex map, change glossiness or. name of the material,etc…)..CPU jump to 100%, C4D freeze for about 15sec +
Hi,
to completely uninstall Corona (on Windows) you should use uninstall option in Programs and features or run uninstaller directly (by default it should be located in C:\Program Files\Corona). This should remove all versions of C4D plugin installed and also all registry and files located outside C4D folder as long as there is no Max version installed - if there is, it will leave some files and registry records used by Corona for 3ds Max. Plugin for C4D does not use anything that could be left for 3ds max, so uninstalling C4D part should be enough for clean install. Apart from that, it is always good to install Windows updates as I’ve already seen some similar issues when using non-updated system (although everything required by plugin should be already installed by installer).
As of problem with materials, I know there are some issues that can slow down update of material preview but I couldn’t reproduce anything so bad, ie it can take few seconds to update but shouldn’t take so long nor freeze C4D while rendering preview. We will try to do something about this in A6 RC2…
Ales,
I have that “yeeeeeeeesssss” expression on my face!
Windows update has eliminated all the problems. Last update was done about two years + ago. Thanks for the tip and help!
I owe you a beer for this one!
Sadly the problem is back after a few days…here we go again with this pain in the … 
C4D oz. Vray materials work without problem (super fast preview update).
Copy paste from Console:
Parsing of material Mat took 0 seconds
Parsing of material Floor took 0 seconds
====RENDER STARTED====
Core build timestamp: Oct 12 2016 14:28:18
REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
CoronaCore::renderFrame before core->onFrame
Calculating displacement took 0 seconds
rtcCommit: 0ms
rtcCommit: 209ms
rtcCommit: 0ms
rtcCommit: 9194ms
EMBREE: Created 3 elements, memory usage: 708.608 bytes.
CoronaCore::renderFrame after core->onFrame
CoronaCore::renderFrame before unique materials
CoronaCore::renderFrame after unique materials
Preparing geometry took 9.424 seconds
Precomputing light distribution took 0 seconds
Rendering took 0 seconds
CoronaCore::exiting renderFrame
Rendered 0/10 passes
Unique Primitives: 9840
Primitives with instancing: 9840
Area lights: 5
Geometry groups: 2
Materials: 5
Instances: 2
Portals: 0
Area lights: 5
Avg samples per pixel: 0
Avg rays per sample: -nan(ind)
Rays/s: 0
Samples/s: 0
Parsing of material Mat took 0 seconds
Parsing of material Floor took 0 seconds
====RENDER STARTED====
Core build timestamp: Oct 12 2016 14:28:18
REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
CoronaCore::renderFrame before core->onFrame
Calculating displacement took 0 seconds
rtcCommit: 9877ms
rtcCommit: 14998ms
rtcCommit: 0ms
rtcCommit: 4999ms
EMBREE: Created 3 elements, memory usage: 704.512 bytes.
CoronaCore::renderFrame after core->onFrame
CoronaCore::renderFrame before unique materials
CoronaCore::renderFrame after unique materials
Preparing geometry took 29.92 seconds
Precomputing light distribution took 0 seconds
Rendering took 0 seconds
CoronaCore::exiting renderFrame
Rendered 0/10 passes
Unique Primitives: 9840
Primitives with instancing: 9840
Area lights: 5
Geometry groups: 2
Materials: 5
Instances: 2
Portals: 0
Area lights: 5
Avg samples per pixel: 0
Avg rays per sample: -nan(ind)
Rays/s: 0
Samples/s: 0
Parsing of material Mat took 0 seconds
Parsing of material Floor took 0 seconds
====RENDER STARTED====
Core build timestamp: Oct 12 2016 14:28:18
REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
CoronaCore::renderFrame before core->onFrame
Calculating displacement took 0 seconds
rtcCommit: 0ms
rtcCommit: 0ms
rtcCommit: 0ms
rtcCommit: 0ms
EMBREE: Created 3 elements, memory usage: 712.704 bytes.
CoronaCore::renderFrame after core->onFrame
CoronaCore::renderFrame before unique materials
CoronaCore::renderFrame after unique materials
Preparing geometry took 0.253 seconds
CoronaCore:RenderFrame: after directLight
CoronaCore::renderFrame: after GI precompute
Precomputing light distribution took 0 seconds
Pass 1/10
Last pass rendered in 0.092 seconds
Pass 6/10
------Entire previous render::run took 440ms
Rendering took 0.44 seconds
CoronaCore::exiting renderFrame
Rendered 10/10 passes
Unique Primitives: 9840
Primitives with instancing: 9840
Area lights: 5
Geometry groups: 2
Materials: 5
Instances: 2
Portals: 0
Area lights: 5
Avg samples per pixel: 9.98901
Avg rays per sample: 56.7441
Rays/s: 1.04346e+07
Samples/s: 183889
Parsing of material Mat took 0 seconds
Parsing of material Floor took 0 seconds
====RENDER STARTED====
Core build timestamp: Oct 12 2016 14:28:18
REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
CoronaCore::renderFrame before core->onFrame
Calculating displacement took 0 seconds
rtcCommit: 0ms
rtcCommit: 1ms
rtcCommit: 1ms
rtcCommit: 0ms
EMBREE: Created 3 elements, memory usage: 712.704 bytes.
CoronaCore::renderFrame after core->onFrame
CoronaCore::renderFrame before unique materials
CoronaCore::renderFrame after unique materials
Preparing geometry took 0.262 seconds
CoronaCore:RenderFrame: after directLight
CoronaCore::renderFrame: after GI precompute
Precomputing light distribution took 0 seconds
Pass 1/10
Last pass rendered in 0.093 seconds
Pass 6/10
------Entire previous render::run took 435ms
Rendering took 0.435 seconds
CoronaCore::exiting renderFrame
Rendered 10/10 passes
Unique Primitives: 9840
Primitives with instancing: 9840
Area lights: 5
Geometry groups: 2
Materials: 5
Instances: 2
Portals: 0
Area lights: 5
Avg samples per pixel: 9.9942
Avg rays per sample: 56.7737
Rays/s: 1.05655e+07
Samples/s: 186099
I would like to +1 this issue!
I’m running RC3 with R17.048 on WIN7 on a 5820k with 32gb ram.
The material editor with Corona is a real problem for me. Everything else about the package is outstanding and i really want to convert my workflow over from vray immediately. I’ve been trying to do some medium sized projects with RC2 and RC3 and the material editor lag is a disaster. It appears that every time a preview update is done, C4D is doing it twice… one for the editor, and one for the material browser, because they both seem to finish their previews in significantly different times. Normally, the material browser preview is the most laggy.
Have the devs got anything to say about this? Is the problem widespread? Has it been acknowledged as an issue?
Have any users found a suitable workaround for this?
Thanks,
Brad.
Is there any news about this bug (slow&freezing material editor)? I ask because we simply can’t/won’t use vrayfor4D anymore!
Even with the latest Corona4D-a6-rc4-windows is nothing better.
Hi, the crashing of material editor should be fixed now, please see Fatal crashing with A6 RC1 and RC2 - Corona for C4D :: Issues - Chaos Forum.
Thanks for fast reply!
My CoronaforC4D doesn’t crash. We have insane (from 30sec to 2min) slow&freezing material editor, no matter what I click (add tex map, change glossiness or. name of the material,etc…)..CPU jump to 100% and C4D freeze or it lasts 1min + to update preview. Even if I import new material or from library, the same thing happens.
It is the same with the latest version Corona for C4D Alpha 6 RC4 yesterday (https://drive.google.com/drive/folders/0B7g1HtV8lD7gWVBKVDhUUk9pYVE).
It looks like I’m not the only one with this problem :)FB link: https://www.facebook.com/photo.php?fbid=10207698267439760&set=gm.718590251623875&type=3&theater
Would it be possible to connect to your computer to find the cause of this bug?
if it is possible to do “connection” tomorrow, because today I’m flying around clients?
Please see video on link with our problem: Dropbox - Error - Simplify your life
And this is from Log in Cinema4D:
===== Error(-11) =====
An internal error occured: wxWidgets Assertion failure. Please report this problem to us.
File: ....\src\msw\textmeasure.cpp(64)
Function: wxTextMeasure::BeginMeasuring
Condition: m_hdc
Message: Must not be used with non-native wxDCs
===== Error(-11) =====
An internal error occured: wxWidgets Assertion failure. Please report this problem to us.
File: ....\src\msw\textmeasure.cpp(64)
Function: wxTextMeasure::BeginMeasuring
Condition: m_hdc
Message: Must not be used with non-native wxDCs
===== Error(-11) =====
An internal error occured: wxWidgets Assertion failure. Please report this problem to us.
File: ....\src\msw\textmeasure.cpp(64)
Function: wxTextMeasure::BeginMeasuring
Condition: m_hdc
Message: Must not be used with non-native wxDCs
===== Error(-11) =====
An internal error occured: wxWidgets Assertion failure. Please report this problem to us.
File: ....\src\msw\textmeasure.cpp(64)
Function: wxTextMeasure::BeginMeasuring
Condition: m_hdc
Message: Must not be used with non-native wxDCs
I tried to delete and there’s not any difference
hmm…it was worth a try…
maybe for others this might help…
cheerz rob