I will be working on improving the general performance of display during the development of V6. @jeff will also be helping with this, but his focus is generally on improved stability and new display features. My plan is to continue to contribute to this post over time with updates of what I am worki…

Hi Brian, here is the scene. I just show one sphere as the rendermesh because after showing and hiding the RenderMesh, the tesselation is saved in the Rhino file and it gets more than 100mb big. However, the Rendertesselation for the other spheres is of course the same. Ballfield.3dm (2.0 MB)

Thanks for the file. Turning off AA here doesn’t help the display speed when the render mesh is displayed. The PolygonCount reports 11.7 million polys but it’s fast in shaded mode if the render mesh wires are off. @stevebaer are mesh wires yet to optimized or is this slowdown to be expected? When z…

There are plenty of optimizations to continue to look into. We are currently in a phase of updating code to use a newer version of OpenGL which in itself won’t make anything faster, but probably more stable across a large set of graphics drivers.

I first thought the slow wireframe display is due to the fact that the view is drawn antialiased, but now that I deactivated it like Brian pointed out, it is still slow, so antialiasing does not seem to be the culprit. I compared the same scene in V5: After displaying the RenderMesh I can still nav…

[image] ruediger: antialiasing does not seem to be the culprit. Simply put (and not meant as a rant) Rhino’s delivery speed is the bottleneck and not the hardware. The card is so fast so it still has plenty of time to AA all the data from Rhino without affecting the redraw speed before the da…

@Holo , What are you seeing for times in V6 on your TextDot test from Aug 2014 now in Feb. 2017? I am using a 4K display running at full resolution of 3840x2160. For 30x30 I am getting 0.36 sec with no redraw, 5.08 sec with redraw on. For 100x100 I am getting 2.95 sec with no redraw, 5.84 sec wit…

A bug I see quite often is that “Reflection Polish” stops working in rendered mode. So I have to close WIP and open it again. Also SubD objects sometimes flicker dark or appears as dark after an object is unhidden. I have to navigate the view (pan, zoom) for the real color to show again.

@micha , please see my post on GPU tessellation at. We were running tests on your bike model and saw pretty massive performance improvements for wireframe drawing. Results will most likely vary from GPU to GPU. [image] New V6 Display Faster: GPU Tessellation Serengeti (Rhino 8 BETA) …

[image] Holo: Simply put (and not meant as a rant) Rhino’s delivery speed is the bottleneck and not the hardware. This should not be the case anymore for polysurface and extrusion wires with the GPU tessellation option. See: [image] New V6 Display Faster: GPU Tessellation Ser…

Wow, that’s a really big step forward. I’m very impressed!!! Also my current heavy production models can be easy manipulated now. It’s like Christmas and birthday at the same day. :slight_smile: @stevebaer , thank you for the note to me.

V6 Goal: Display Performance

Serengeti (Rhino BETA)

Topic		Replies	Views
Rhino WIP: New V6 Display Engine Serengeti (Rhino BETA)	56	8042	April 4, 2017
Very slow display, not usable Serengeti (Rhino BETA)	56	6930	November 2, 2017
Slow Display Serengeti (Rhino BETA)	32	3548	June 21, 2017
Rhino 6 still unusable Rhino for Windows	91	6958	March 20, 2019
Rhino WIP 8-Nov-2016 Display Serengeti (Rhino BETA)	48	4703	April 11, 2017

V6 Goal: Display Performance

Related topics