Author Topic: Slow material editor - C4D  (Read 17144 times)

2016-10-16, 18:28:37

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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.
« Last Edit: 2016-10-16, 18:46:27 by minimaldesign - Blaž »

2016-10-16, 18:30:08
Reply #1

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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
« Last Edit: 2016-10-16, 18:49:46 by minimaldesign - Blaž »

2016-10-25, 16:12:54
Reply #2

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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
« Last Edit: 2016-10-25, 16:19:01 by minimaldesign - Blaž »

2016-10-25, 17:53:15
Reply #3

marcuiz77

  • Active Users
  • **
  • Posts: 5
    • View Profile
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!! :))

2016-10-25, 18:30:51
Reply #4

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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 :P

2016-10-27, 09:48:57
Reply #5

marcuiz77

  • Active Users
  • **
  • Posts: 5
    • View Profile
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??

2016-10-27, 10:38:10
Reply #6

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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.
« Last Edit: 2016-10-27, 19:10:50 by minimaldesign - Blaž »

2016-10-27, 19:53:45
Reply #7

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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 +
« Last Edit: 2016-10-27, 20:00:44 by minimaldesign - Blaž »

2016-11-01, 13:15:13
Reply #8

Ales

  • Corona Team
  • Active Users
  • ****
  • Posts: 186
    • View Profile
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...

2016-11-03, 05:08:57
Reply #9

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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.

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!

2016-11-10, 16:39:31
Reply #10

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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:

[Corona4D] Parsing of material  Mat took 0 seconds
[Corona4D] Parsing of material Floor took 0 seconds
[Corona4D] ====RENDER STARTED====
[Corona4D] Core build timestamp: Oct 12 2016 14:28:18
[Corona4D] REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
[Corona4D] CoronaCore::renderFrame before core->onFrame
[Corona4D] Calculating displacement took 0 seconds
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 209ms
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 9194ms
[Corona4D] EMBREE: Created 3 elements, memory usage: 708.608 bytes.
[Corona4D] CoronaCore::renderFrame after core->onFrame
[Corona4D] CoronaCore::renderFrame before unique materials
[Corona4D] CoronaCore::renderFrame after unique materials
[Corona4D] Preparing geometry took 9.424 seconds
[Corona4D] Precomputing light distribution took 0 seconds
[Corona4D] Rendering took 0 seconds
[Corona4D] CoronaCore::exiting renderFrame
[Corona4D] Rendered 0/10 passes
[Corona4D] Unique Primitives: 9840
[Corona4D] Primitives with instancing: 9840
[Corona4D] Area lights: 5
[Corona4D] Geometry groups: 2
[Corona4D] Materials: 5
[Corona4D] Instances: 2
[Corona4D] Portals: 0
[Corona4D] Area lights: 5
[Corona4D] Avg samples per pixel: 0
[Corona4D] Avg rays per sample: -nan(ind)
[Corona4D] Rays/s: 0
[Corona4D] Samples/s: 0
[Corona4D] Parsing of material  Mat took 0 seconds
[Corona4D] Parsing of material Floor took 0 seconds
[Corona4D] ====RENDER STARTED====
[Corona4D] Core build timestamp: Oct 12 2016 14:28:18
[Corona4D] REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
[Corona4D] CoronaCore::renderFrame before core->onFrame
[Corona4D] Calculating displacement took 0 seconds
[Corona4D] rtcCommit: 9877ms
[Corona4D] rtcCommit: 14998ms
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 4999ms
[Corona4D] EMBREE: Created 3 elements, memory usage: 704.512 bytes.
[Corona4D] CoronaCore::renderFrame after core->onFrame
[Corona4D] CoronaCore::renderFrame before unique materials
[Corona4D] CoronaCore::renderFrame after unique materials
[Corona4D] Preparing geometry took 29.92 seconds
[Corona4D] Precomputing light distribution took 0 seconds
[Corona4D] Rendering took 0 seconds
[Corona4D] CoronaCore::exiting renderFrame
[Corona4D] Rendered 0/10 passes
[Corona4D] Unique Primitives: 9840
[Corona4D] Primitives with instancing: 9840
[Corona4D] Area lights: 5
[Corona4D] Geometry groups: 2
[Corona4D] Materials: 5
[Corona4D] Instances: 2
[Corona4D] Portals: 0
[Corona4D] Area lights: 5
[Corona4D] Avg samples per pixel: 0
[Corona4D] Avg rays per sample: -nan(ind)
[Corona4D] Rays/s: 0
[Corona4D] Samples/s: 0
[Corona4D] Parsing of material  Mat took 0 seconds
[Corona4D] Parsing of material Floor took 0 seconds
[Corona4D] ====RENDER STARTED====
[Corona4D] Core build timestamp: Oct 12 2016 14:28:18
[Corona4D] REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
[Corona4D] CoronaCore::renderFrame before core->onFrame
[Corona4D] Calculating displacement took 0 seconds
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 0ms
[Corona4D] EMBREE: Created 3 elements, memory usage: 712.704 bytes.
[Corona4D] CoronaCore::renderFrame after core->onFrame
[Corona4D] CoronaCore::renderFrame before unique materials
[Corona4D] CoronaCore::renderFrame after unique materials
[Corona4D] Preparing geometry took 0.253 seconds
[Corona4D] CoronaCore:RenderFrame: after directLight
[Corona4D] CoronaCore::renderFrame: after GI precompute
[Corona4D] Precomputing light distribution took 0 seconds
[Corona4D] Pass 1/10
[Corona4D] Last pass rendered in 0.092 seconds
[Corona4D] Pass 6/10
[Corona4D] ------Entire previous render::run took 440ms
[Corona4D] Rendering took 0.44 seconds
[Corona4D] CoronaCore::exiting renderFrame
[Corona4D] Rendered 10/10 passes
[Corona4D] Unique Primitives: 9840
[Corona4D] Primitives with instancing: 9840
[Corona4D] Area lights: 5
[Corona4D] Geometry groups: 2
[Corona4D] Materials: 5
[Corona4D] Instances: 2
[Corona4D] Portals: 0
[Corona4D] Area lights: 5
[Corona4D] Avg samples per pixel: 9.98901
[Corona4D] Avg rays per sample: 56.7441
[Corona4D] Rays/s: 1.04346e+07
[Corona4D] Samples/s: 183889
[Corona4D] Parsing of material  Mat took 0 seconds
[Corona4D] Parsing of material Floor took 0 seconds
[Corona4D] ====RENDER STARTED====
[Corona4D] Core build timestamp: Oct 12 2016 14:28:18
[Corona4D] REPORT: unchanged: 0, Prim: 2, Inst: 0, Mtl: 0, Env: 1
[Corona4D] CoronaCore::renderFrame before core->onFrame
[Corona4D] Calculating displacement took 0 seconds
[Corona4D] rtcCommit: 0ms
[Corona4D] rtcCommit: 1ms
[Corona4D] rtcCommit: 1ms
[Corona4D] rtcCommit: 0ms
[Corona4D] EMBREE: Created 3 elements, memory usage: 712.704 bytes.
[Corona4D] CoronaCore::renderFrame after core->onFrame
[Corona4D] CoronaCore::renderFrame before unique materials
[Corona4D] CoronaCore::renderFrame after unique materials
[Corona4D] Preparing geometry took 0.262 seconds
[Corona4D] CoronaCore:RenderFrame: after directLight
[Corona4D] CoronaCore::renderFrame: after GI precompute
[Corona4D] Precomputing light distribution took 0 seconds
[Corona4D] Pass 1/10
[Corona4D] Last pass rendered in 0.093 seconds
[Corona4D] Pass 6/10
[Corona4D] ------Entire previous render::run took 435ms
[Corona4D] Rendering took 0.435 seconds
[Corona4D] CoronaCore::exiting renderFrame
[Corona4D] Rendered 10/10 passes
[Corona4D] Unique Primitives: 9840
[Corona4D] Primitives with instancing: 9840
[Corona4D] Area lights: 5
[Corona4D] Geometry groups: 2
[Corona4D] Materials: 5
[Corona4D] Instances: 2
[Corona4D] Portals: 0
[Corona4D] Area lights: 5
[Corona4D] Avg samples per pixel: 9.9942
[Corona4D] Avg rays per sample: 56.7737
[Corona4D] Rays/s: 1.05655e+07
[Corona4D] Samples/s: 186099

2016-11-28, 00:28:40
Reply #11

bgolds99

  • Active Users
  • **
  • Posts: 21
    • View Profile
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.

2016-12-05, 05:50:03
Reply #12

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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.
« Last Edit: 2016-12-05, 05:55:17 by minimaldesign - Blaž »

2016-12-05, 09:00:06
Reply #13

Nikola

  • Corona Team
  • Active Users
  • ****
  • Posts: 478
    • View Profile
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 https://forum.corona-renderer.com/index.php/topic,14009.msg90874.html#msg90874.

2016-12-05, 10:47:15
Reply #14

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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 https://forum.corona-renderer.com/index.php/topic,14009.msg90874.html#msg90874.

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
« Last Edit: 2016-12-05, 10:54:18 by minimaldesign - Blaž »

2016-12-05, 11:09:01
Reply #15

Nikola

  • Corona Team
  • Active Users
  • ****
  • Posts: 478
    • View Profile
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 https://forum.corona-renderer.com/index.php/topic,14009.msg90874.html#msg90874.

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?

2016-12-05, 11:37:40
Reply #16

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
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 https://forum.corona-renderer.com/index.php/topic,14009.msg90874.html#msg90874.

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: https://www.dropbox.com/s/2o342juhvrsmyhq/Corona%20bug%201.mp4?dl=0

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



2016-12-05, 12:25:10
Reply #17

machmirdenlukas

  • Active Users
  • **
  • Posts: 32
    • View Profile
i had same Problem years ago with vray for c4d...
the Problem was too many texturesearch-paths in Preference...

i could reproduce this lag with corona now... if i delete the paths...everything´s smooth...
hope this helps...
cheerz rob

2016-12-05, 12:34:18
Reply #18

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
i had same Problem years ago with vray for c4d...
the Problem was too many texturesearch-paths in Preference...

i could reproduce this lag with corona now... if i delete the paths...everything´s smooth...
hope this helps...
cheerz rob

I tried to delete and there's not any difference :(

2016-12-05, 12:40:06
Reply #19

machmirdenlukas

  • Active Users
  • **
  • Posts: 32
    • View Profile
hmm...it was worth a try....;)
maybe for others this might help...
cheerz rob

2016-12-05, 17:14:18
Reply #20

burnin

  • Active Users
  • **
  • Posts: 1536
    • View Profile
Confirming same behavior. 
A6 rc 4 (core 1.5 (hotfix 2)) with C4D R17.055 (win7)

+ another one spotted: Material Manager Preview does wrong with gamma: Preview Icons are darker!

EDIT:
got informed, there's no such bug/behavior on R18.028
Anyone can confirm or refute?
« Last Edit: 2016-12-05, 21:30:24 by burnin »

2016-12-06, 09:29:08
Reply #21

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
Confirming same behavior. 
A6 rc 4 (core 1.5 (hotfix 2)) with C4D R17.055 (win7)

+ another one spotted: Material Manager Preview does wrong with gamma: Preview Icons are darker!

EDIT:
got informed, there's no such bug/behavior on R18.028
Anyone can confirm or refute?

No, it's also on R18...it seems we are cursed, at least I'm :)
So I have to move to office, if I want to work....it seems the problem is only on a home computer.

2016-12-06, 11:48:19
Reply #22

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
We solved the problem! The best Bday ever :))
Nikolat Corona dev team thank you afor your time!

Problem that cause problems with freezing and slow material preview was some Lavasoft software for Google Chrome.

2016-12-06, 11:57:24
Reply #23

minimaldesign - Blaž

  • Active Users
  • **
  • Posts: 158
    • View Profile
    • minimaldesign
We solved the problem! The best Bday ever :))
Nikolat Corona dev team thank you for your time!

Problem that cause problems with freezing and slow material preview was some Lavasoft software for Google Chrome.

2016-12-06, 14:52:55
Reply #24

Nikola

  • Corona Team
  • Active Users
  • ****
  • Posts: 478
    • View Profile
Today we fixed the problem on minimaldesign - Blaž's computer simply by uninstalling LavaSoft Web Companion tool. This tool injected remote thread to Corona and this "alien" thread caused the freezes of the material preview. So everyone who has the problem with slow/freezing material preview, do you use some security/anti-virus software? Because these anti-spywer tools behave like spyware sometimes ...

2016-12-10, 23:33:20
Reply #25

burnin

  • Active Users
  • **
  • Posts: 1536
    • View Profile
Thanks for the info... but have no such tools installed.

So, since RC5 was released into the wilderness, i took the time & went hunting.

"What kind of beast is there and where could it hide?"

To my surprise it was pretty effortless & obvious, once i peeked into the running services and processes.
It turned out to be Windows Update service (wuauserv) ran by svchost.exe.
Found it almost instantly by looking at the CPU usage in Task Manager, while poking Hue on the Material Editor.
Then it flashed me. Had same problems, but even worse slowdowns while using Maxwell 3 (there, by now is a well known issue :).
So i stopped the service... ... ... ... been clicking on Hue values for the last 5minutes... ... all material previews are refreshing smoothly (~1s).

Happy & off to wipe the dance floor :D

PS
Also "wrong gamma bug" was my bad. Am not involved with cinema anymore, only once in a while as i help out, otherwise my head is in a blender with nodes and occasionally pulling strings in houdini... so it's easy to oversee some of the spices in between.

Wish you all well, good drinks, food & lots of celebrations!
« Last Edit: 2016-12-10, 23:39:35 by burnin »

2016-12-19, 09:20:58
Reply #26

Yaseck

  • Active Users
  • **
  • Posts: 5
    • View Profile
Windows update helped my material editor a bit. For now it works faster. We'll see for how long.

2016-12-20, 17:55:26
Reply #27

Nikola

  • Corona Team
  • Active Users
  • ****
  • Posts: 478
    • View Profile
Thanks for the info... but have no such tools installed.

So, since RC5 was released into the wilderness, i took the time & went hunting.

"What kind of beast is there and where could it hide?"

To my surprise it was pretty effortless & obvious, once i peeked into the running services and processes.
It turned out to be Windows Update service (wuauserv) ran by svchost.exe.
Found it almost instantly by looking at the CPU usage in Task Manager, while poking Hue on the Material Editor.
Then it flashed me. Had same problems, but even worse slowdowns while using Maxwell 3 (there, by now is a well known issue :).
So i stopped the service... ... ... ... been clicking on Hue values for the last 5minutes... ... all material previews are refreshing smoothly (~1s).

Happy & off to wipe the dance floor :D

PS
Also "wrong gamma bug" was my bad. Am not involved with cinema anymore, only once in a while as i help out, otherwise my head is in a blender with nodes and occasionally pulling strings in houdini... so it's easy to oversee some of the spices in between.

Wish you all well, good drinks, food & lots of celebrations!
Hi, thank you for testing the Corona. Good observation, what version of Windows do you use?

2016-12-20, 19:50:20
Reply #28

burnin

  • Active Users
  • **
  • Posts: 1536
    • View Profile
^w7 x64 pro