V6 Goal: Display Performance


(Jeff Lasor) #121

@Holo As Steve suggested, a simple model will help immensely so that we’re not having to try to “model the problem”…

Also, something you (All of you) need to do when you come across a problem now is this:

  1. Note the problem
  2. Turn off the vbo caching via TestVBOCache command (disable it)
  3. See if the problem still exists.
  4. Report the situation

We still want to hear about the problem regardless of the results above…but this just helps us better understand whether or not this is a new problem introduced by the caching mechanism, or an already existing problem.


Rhino 6 WIP Fuzzy Geometry Display

@jeff and @stevebaer,

while attempting to create you some motivating screencaptures made with the new wip, i´ve run into an old bug which happens when capturing larger viewport resolutions using _-ViewCaptureToClipboard. If the _Scale option is used, the background (in below case it was a 2 color gradient) is repeated by the scale factor entered. I´ve tried to capture using _Scale=4 which caused below funky effect i could not withhold :wink:

btw. i really like the transparent shadow option for the groundplane without using a material. Thanks!


(Jeff Lasor) #123

Ok thanks @clement, we’ll check it out. Pretty sure this used to work in the new engine, so something worked its way into (or out of) the code.


(Steve Baer) #124

I’ve almost got this fixed Jeff. We never properly supported gradient backgrounds through tiles.

(Jeff Lasor) #125

Ya, I guess not… I was just thinking of tiled rendering in general…gradient seems to have slipped through the cracks.

(Steve Baer) #126

The gradient background tiling bug will be fixed in the next WIP.


Thanks for the instant fix !


(Steve Baer) #128

Back on to the topic of display performance, I believe I have all of the issues fixed for the next WIP that @Holo and @clement reported (thanks guys) with the exception of the “viewport colors” showing through in rendered mode. Jorgen if you have a model that illustrates this bug, I would love to see it.


Sure, I have just been caught up with making a Unity VR demo for an upcoming BIM day
(not with this model)
This model is just a wip of our old house, the model has gone from V4->V5->V6, I would not be surprised if you find some bad objects in there either, this is for my own use so “good enough” is “good enough” :wink: ), but the issue doesn’t appear all the time, so I saved it in a state that consistently shows the bug on my Quadro 4000 machine, I’ll test it on the GeForce 970 machine in an hour.

Open the file and click on wall 1 and then on wall 2. That triggers the issue here at least. Sometimes the floor disappears, other times wall 1 disappears, and then reappears. It almost seems to be related to some background calculations of some sort, but I don’t know.

Here’s the file:
HolosHouse V6 hide shade bug.zip (706.3 KB)

Also, OT, but since it is related to the file:
Can you add a “remove missing image file” option to this outdated pop-up?
And add a propper icon to each file instead of the grayed out “A swap B” icon, that appears inactive, until one clicks on the missing file name.

(Steve Baer) #130

3 posts were split to a new topic: Selection Not Updating

Selection Not Updating

Yup, about the same issues here, but this system didin’t have the custom white background so it shows that the surface has some lighting information on it when it is “hidden”.

(Steve Baer) #133

@jeff does this sound related to the rendered mode bug you were working on yesterday?

(Jeff Lasor) #134

@stevebaer Sounds very similar…only I’m only seeing/working it in Technical modes…sometimes a surface draws, sometimes it doesn’t…but so far, no rhyme or reason. …except that I don’t see it happen when caching is disable.

Also, I’m seeing certain materials display/map incorrectly in Rendered mode on certain models… I’ll update you on this later today with an example.


Hi all,

the globall performance is verry amaizing more 300% than rhino 5 (I have us the fraps software to calculate the fps number).

on rhino 5 my modele have 2 fps. On rhino 6 => 6 FPS Good jobs :slightly_smiling:

I use Windows 7 pro x64 with 32 Go ram
Quadro K2200 2Go Go ram
xeon 3.5Ghz

Rhino 6 post to errors message

this error message appears at the moment of opening file

  1. this error message appears a moment after opening files



Bike model and test max speed:

Rhino 5 17s
Rhino 6 20s

Also I tried to open my current complex project models. Rhino 6 fails to open the files.

So, from my side, no improvement, not usable.

(Brian Gillespie) #137

We knew your bike model wasn’t going to be very impressive. In fact, it was one of the first things we tested. Unfortunately, your bike model makes heavy use of wires. Wire drawing in Rhino 6 is actually a little bit slower than Rhino 5. So for shaded/rendered viewports with lots of wires, Rhino 6 isn’t going to look much faster. We have a couple ideas for speeding up wires, but they’re very complicated and probably won’t make it into Rhino 6.

Can you please upload a copy of models that Rhino WIP won’t open to https://www.rhino3d.com/upload and we’ll get them on the bug list to be fixed? Please mention my name in the comments.


My project models are slow often and the GPU is used at low load only. The bike model is a good example for where speed is needed - if the model is slow. Some users forget that a test with 20fps before and 60fps now isn’t so interesting for real projects and speed problems. I hope the bike test will be faster if v6 is finalized. If not it sounds like a capitulation of development after all the months/years of speed problems and is a bad sign for the future of the Rhino display. Most users have a lot of GPU power … . I’m frustrated that there is no progress at v6.

Could be now a good time to speak about alternative ways to get speed for scene manipulation? For example automatic temporary switch to render-mesh-only-mode. It would help viz designer and architects to get complex scenes handled.

Sorry, the project files are under NDA, so I can’t upload.


These comments kind of baffle me…
Can you elaborate on why the display of a newer version will be slower?



New versions getting slower? Sounds like you are adopting some of the AutoCAD development habits…
I agree with @Micha, most real-life projects depend on complexity and wires/edges display. Making it slower will definitely hurt us.


(Gustavo Fontana) #141

all my modeling is done with wires (isoparms at 1 on the surfaces/parts I’m working on, zero on the rest of the model). Viewmodes are usually shaded/ghosted/rendered with wires on. I only show curves when they are input to surfaces, otherwise they are hidden, on an off layer of curves, or toggled off n the view tab.

Will that way of working be slower in 6 than in 5? or are we talking about heavy wire display being slower?