Hi All.
I didn’t want to hijack the holomark2 thread with this so I’ve made a new thread in the hope that someone has solved this issue.
It seems that some people are affected by a severely long calculation time for technical mode.
I thought it was normal, but I can see from other people’s results from the Holomark2 test that a scene that takes other PC’s about 1.5 seconds to compute Technical Display Mode, takes my PC about 145 seconds.
There is another thread here from about 6months back with someone with similar problems and his only resolve came from reformatting his system.
In that thread @jeff suggested that OpenCl is involved in the calculation stage for Technical view.
For me all 8x Threads run at 100% for more than 2min for the holomark2 test, so something is definitely being calculated.
I’ve checked my system and for CPU it is using OpenCL 1.2, and the Nvidia Driver uses OpenCL 1.1.
As far as I could find out there is no 1.2 driver for Nvidia.
I also could not find a download for Intel OpenCL 1.1 to perhaps “rollback” to the previous version if that is the case.
Point cloud deformation also seems to be about 40x slower than other peoples systems.
Other tests and rendering in Vray seem to use the CPU to it’s full extent.
I have avoided using Technical Mode in my workflow because of the long calculation times, but if I can figure out a fix then this mode would be useful.
Any info in this regard would be appreciated. Michael VS (Q6000+i7-3770)
Hi @Holo , In my other post i mentioned that disabling Hyperthreading in Bios reduced the Technical View Mode test from 150sec to 85 sec.
I have done some further tests with my own simpler rhino scene and have found that mesh quality also plays quite a difference. Oddly enough The JAGGED option for mesh took 26x seconds in my own test scene and the SMOOTH AND SLOWER meshing option actually converted to Technical View faster in 17x Seconds. Still on the hunt for the main problem though…Michael VS
Could you check how many polygons there are in the scene with both jagged and smooth settings? Theoretically speaking, jagged can produce more polygons for certain models. (cmd: PolygonCount).