Yes, sorry. Btw. when i hide curves the speed goes up more noticable in the larger scene:
Time to regen viewport 100 times = 7.24 seconds. (13.82 FPS) (GPU Tesselation OFF)
Time to regen viewport 100 times = 1.20 seconds. (83.26 FPS) (GPU Tesselation ON)
I’m working on curves this week. You will most likely not see as drastic of an improvement at first with curves as were seen with polysurfaces and extrusions, but there should be at least another small bump in improvement on your model soon. I don’t know if I’ll have this in place by tomorrow’s WIP, but that doesn’t seem to be a problem for you
The GPU Tessellation feature should work well with AMD GPUs in the latest WIP. Previously the feature was only working well with Nvidia and Intel GPUs.
Is GPU tesselation now on by default. I just upgraded to the latest WIP, and realized that wireframe is not rendered anymore. Then I looked at the appearance settings:
Haven’t tried it yet with a newer version of the Nvidia driver (there are reasons not to install it).
This is correct. The other addition is that curves are also drawn using the tessellation shaders. I was going to make an announcement about this, but immediately found several bugs related to dynamic display (dragging of curves and array preview) that I have been focused on fixing.
Does this mean that all wires are gone from the display? I can’t tell based on the screenshot you provided.
Can you help me understand why you won’t update from the old driver?
[quote=“stevebaer, post:67, topic:43747”]
Does this mean that all wires are gone from the display? I can’t tell based on the screenshot you provided.[/quote]
Yes, all the wires are gone in the Wireframe viewports.
At the moment, my Windows installation has issues and I cannot control the brightness of my laptop’s display anymore. Until that is fixed, I was thinking about staying with the graphics driver package provided by Lenovo, which doesn’t included the latest Nvidia drivers.
One thing comes to mind. I started developing a plugin for V6 with a display conduit. The problem seems to have started, after I first loaded it. I deleted my PlugIn rhp and restarted Rhino. Still the problem persists.
Hi Silvan,
I could tell as soon as I saw your screenshots that you were running an Intel GPU. This appears to be a driver bug that appears on almost all Intel drivers that don’t support OpenGL 4.4 and above. I’m probably going to turn tessellation off by default for these drivers until I can figure out some kind of way to work around the bug. I’ve been able to repeat this on older Intel GPUs in the office and have made numerous attempts to figure out if there is some way to work around this issue always coming up empty.
Ah, funky. Rhino should be running on the dedicated Nvidia card and not on the Intel integrated graphics. This must have changed after having had the computer on sleep. I overlooked this in the info.
Edit: After restarting the computer, things are back to normal. Nvidia GPU being used, tessellation working.
I would say no. With all the different things an interactive content creation view has to do as opposed to a game it’s doubtful it would help much if at all, few users have such setups, and any good GPU renderer like Cycles in V6 or iRay or Octane can use however many compatible cards you can stuff in your machine no matter what they are and having SLI enabled may in fact slow those down.
Indeed it seems that even for gaming with the current-gen products nvidia is no longer really promoting SLI as it is neat (I used to have 2 970s) but is a constant source of game issues, especially trying to use more than 2.
Yes, that was my question. Admittedly my only experience of SLI is in games, but man it makes everything better. Anyway, I get that it’s not going to happen here, I’ve moved on.