I didn’t restart after switching cables between graphics cards - I don’t know if that has any ill-effect on the results.
ok, I would much appreciate, if you could make sure if the scores are correct. what is your “feeling” regarding the WX9100 viewport performance compared to a card like the GTX1060 or GTX1080?
With the new version and SR12 RC it runs perfectly fine on my system again without crashing, nice work, thanks!
Here is the score:
happy with my new scores now
Thanks @Holo
Here’s the score of my PNY Prevailpro P4000
Is it normal that the test runs in a small ?floating? viewport?
I think the viewport size is hardcoded at 888x500
Yes, as @jesterking suggests it’s a predefined size from back in the “fullHD is huge” days 
It is important to test the size in a controlled environment, thus the fixed size and the custom display modes.
The reason for the odd placement is just that Rhino6 closes the viewports in a different order than Rhino5.
I’ll add a note to fix that for the next build.
I get an error when trying to install the .rhi file:
Yeah, as Nathan says, it might be SR related.
Unfortunately I compiled it by using the RhinoCommon.dll from the SR12 prerelease and that might require a newer build.
Holomark 2 R6 v2,61
Total Score: 255185
Total Runtime: 1270.32 sec
GPU scores: 238640
GPU_01 - 151.50 fps - Cube 4 tests
GPU_02 - 78.70 fps - UDT Shape
GPU_03 - 416.70 fps - Wireframe
GPU_04 - 400.00 fps - Shaded
GPU_05 - 120.50 fps - Rendered
GPU_06 - 163.90 fps - Block Rendered
GPU_07 - 1056 units Nurbs @ 5 fps in Wireframe
GPU_08 - 529 units Nurbs @ 5 fps in Shaded
GPU_09 - 146 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 156.30 fps - RenderMesh Render
GPU_11 - 400.00 fps - RenderMesh RenderSpeed
GPU_12 - 500.00 fps - JoinedMesh Render
GPU_13 - 769.20 fps - JoinedMesh RenderSpeed
GPU_14 - 154 units mesh @ 15 fps in Shaded
GPU_15 - 274 units mesh @ 15 fps in Render
GPU_16 - 976 units mesh @ 15 fps in RenderSpeed
GPU_17 - 238.10 fps - mesh in Rendered Studio
GPU_18 - 53.80 fps - Nurbs in Rendered Studio
GPU_19 - 57.10 fps - Block Illustration
GPU_20 - 149.00 fps - 2D single
GPU_21 - 91.70 fps - 2D massive (20x)
CPU scores: 16545
CPU_01 - 5.98 sec - Booleans and Contours
CPU_02 - 1.22 sec - Twist and Taper (UDT)
CPU_03 - 7.22 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 11.99 sec - Reduce Mesh
CPU_07 - 0.91 sec - Calculating Technical display
CPU_08 - 2.85 sec - Making Silhouettes
System manufacturer
System Product Name
NVIDIA GeForce RTX 2070 - 4095.0 MB
DriverVersion: 25.21.14.1722
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.7 GHz
TotalPhysicalMemory: 32.0 GB
Microsoft Windows 10 Pro N
- None - 64-bit
Rhino 6 sr 12 64 bit
AA level = 4Hi out here,
I had the same issue with SR11 also. Installing SR12 solved the incompabillity but Rhino crashes after some time. Couldn’t find a rhino crash dump file but Windoof recorded something.
Unfortunately the dmp file is not allowed and the txt is to big.
Thank you for investing your time, Jorgen.
André
In the 2nd run it worked. With fantastic score…
Holomark 2 R6 v2,61
Total Score: 248508
Total Runtime: 1152.03 sec
GPU scores: 227340
GPU_01 - 588.20 fps - Cube 4 tests
GPU_02 - 81.30 fps - UDT Shape
GPU_03 - 500.00 fps - Wireframe
GPU_04 - 454.50 fps - Shaded
GPU_05 - 142.90 fps - Rendered
GPU_06 - 181.80 fps - Block Rendered
GPU_07 - 863 units Nurbs @ 5 fps in Wireframe
GPU_08 - 496 units Nurbs @ 5 fps in Shaded
GPU_09 - 156 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 204.10 fps - RenderMesh Render
GPU_11 - 454.50 fps - RenderMesh RenderSpeed
GPU_12 - 526.30 fps - JoinedMesh Render
GPU_13 - 769.20 fps - JoinedMesh RenderSpeed
GPU_14 - 118 units mesh @ 15 fps in Shaded
GPU_15 - 359 units mesh @ 15 fps in Render
GPU_16 - 1038 units mesh @ 15 fps in RenderSpeed
GPU_17 - 277.80 fps - mesh in Rendered Studio
GPU_18 - 64.50 fps - Nurbs in Rendered Studio
GPU_19 - 72.50 fps - Block Illustration
GPU_20 - 142.70 fps - 2D single
GPU_21 - 94.30 fps - 2D massive (20x)
CPU scores: 21168
CPU_01 - 5.69 sec - Booleans and Contours
CPU_02 - 1.13 sec - Twist and Taper (UDT)
CPU_03 - 2.67 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 10.69 sec - Reduce Mesh
CPU_07 - 0.87 sec - Calculating Technical display
CPU_08 - 2.52 sec - Making Silhouettes
PC Specialist LTD
OctaneV 17
NVIDIA GeForce GTX 1070 - 4095.0 MB
DriverVersion: 24.21.13.9901
Intel(R) Core™ i7-8700K CPU @ 3.70GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.7 GHz
TotalPhysicalMemory: 32.0 GB
Microsoft Windows 10 Pro
- None - 64-bit
Rhino 6 sr 12 64 bit
I noticed that video cards with 8 GB of video RAM such like GTX 1070 and RTX 2070 are shown as 4 GB in these performance tests. Is there any reason for that difference?
Create a zip archive containing both files, then upload at Rhino - Upload to Support - type up shortly what you were doing when Rhino crashed. A dev will get this on the todo list to investigate and fix.
Hello B Design Bg2,
I noticed and was wondering the same thing.
Thank you,
Andy
sorry for the delay in replying. Here is my SR report:
Rhino 6 SR10 2018-10-6 (Rhino 6, 6.10.18279.17351, Git hash:master @ dcc8b4dc1c0590dc372722e624f0f6b1407e1469)
Licence type: Commercial, build 2018-10-06
License details: Cloud Zoo. In use by: dallas
Windows 10.0 SR0.0 or greater (Physical RAM: 64Gb)
Quadro M2200/PCIe/SSE2 (OpenGL ver:4.5.0 NVIDIA 382.99)
It would be interesting to see how the same setup compares to V5
Something doesn’t seem/look right in how you’re bailing out of some of the tests… It looks like you’re bailing when FPS reaches 5 in some cases and 15 in others…However, if you sit and watch the results on the command line, as you’re approaching the bail out number, you’ll see (I do here anyways) a broad range of values occurring… For example: For GPU_07, as I approach 5fps, the value on the command line fluctuates pretty significantly… It’ll show 5.8 then 6.1, then 5.3, then 6.2, then 5.6, then 5.4, then 6.0, …and then all of a sudden it bails. Is it waiting to hit 5.0 once, and then bails? Or are you looking at averages over some number of frames?
I ran it again, and I too see better results the second time through.
True, that depends on the display modes that are tested. GPU 07- 09 has 5 fps as limit while GPU 14-16 has 15 (It even says so on the score sheet ) This was chosen as limits for Rhino5 and Holomark2_R6 is just using the same settings even though Rhino6 is much faster.
Regarding “bailing out” you are very right. I made a simple “when fps drops below, terminate” decision, with no doubleckecking to see if a background process is using the CPU. (But it always checks with three frames)
I will not us a populating test for HM3 though, there I will use fixed numbers and rather check how many frames can be drawn during x seconds.
Why your system spend 6 seconds on meshing the first time, and only 3 (!!!) seconds the second time is beyond me and surely is not Holomarks fault, so I bet Windows did some background stuff there. But obviously both the CPU 04 and 05 are silly tests since they are way too fast to give any nuanced scores.
Thanks for testing though, and if you want to test the same system with Holomark2 for Rhino5 then the scores should be as comparable as possible. The only difference is that the HM2_R6 mini is a bit cooler with some decals on it and that the display modes aren’t identical, but as close as I could make them.