Issues with Rhino 6

So, i have bought myself a new computer which is still rather old but has 2 gb of dedicated video memory, its blazingly fast at least in Rhino 5. So i made a few test rounds with Rhino 6 nothing extensive but a few findings, which might not help to solve anything but better talking about it than ignoring it.


performance
setting both versions to Antialiasing of 4, Rhino 6 seems a bit slower by feeling, it does not feel so snappy as in Version 5. it feels a bit like using a 512 mb video card which i had before compared to the 2 gb i would have now.

also i had some strange issue, in the beginning swiveling around and navigating in general, also opening and proceeding commands seemed all snappier. the last times i opened it its just super slow, even a simple box or nothing at all paning zooming in wire mode in any viewport like a chewing gum, like something is working in the background not giving me full performance. quitting rhino 6 several times and opening rhino 5 i see that the issue was definitely in version 6. maybe its a coincidence, but just now switching around the Antialiasing in the open gl settings there and back seems to have resolved it for now, anybody else experiencing that?

losing focus
sometimes i lose focus on accidentally called up commands, meaning i cant escape them from anywhere, only hovering the mouse onto the open command panel gives me the focus back which allows me to use escape. i cant repeat how that happens but when it happens it seems sticky till i restart Rhino.

floating command bar
something far less important but noticeable, that the new bar is quite a bit bigger, it just feels clunky and waists a bit visual space. also useless round buttons partially greyed out from general Mac OS theme are now in that bar. looked definitely better in the old version.

56

54

GUI in general
i am not sure i like the white boarders around everywhere, maybe i can switch that off in the advanced settings? i dont know it just looked so brutal to scroll through that mess there that i left it for now…

also most of the icons seem far too glowy in mojave dark mode, i assume that these were simply batch inverted with no extra love for the detail. that this does not work out on several icons making them almost unrecognizable has hopefully been considered already.

placing panels like Boxedit into the sidebar is a fancy thing, i believe the idea is good, but i am not fully sure i would like that at all instances. maybe having the option for a floating panel would be good i could not find any at least, as the dashed version for example instead of toggling the visibility in the sidebar there which makes no sense to me.

hope its not too much crap i wrote up here, i will add things as a go along testing it.

in version 5 when i wanted to copy a command with cmd a then cmd c, it marked the entire command, now cmd a does not work in the command panel anymore, i have to mark it with the mouse entirely to copy it.

using floating command dialog. did not test command dialog in the sidebar.

nobody interested in commenting on these hick ups?

the meshes work well now in the new version, congrats, larger amount of meshes are now workable, where rhino 5 put my computer to the knees, but the rest seems slower (shaded mode very slightly slower) to a lot slower (technical display mode, pen etc.), under these conditions i dont feel very invited to transfer to version 6 soon…

i downloaded the evaluation version recently to see if some of these issues have been quietly resolved but it does not seem so. not being able to escape still occurs suddenly.

also something which i really hoped would be resolved in the next version -> navigating with tab through commands to change numbers is still painful like in version 5. why would it jump to the arrows instead of to the next field, does not seem logic to me.

I would recommend testing with the 6.17 release candidate by subscribing the the release candidate stream

There have been several bug fixes and performance improvements in this release candidate

thanks Steve will check it out, but regarding the hick up with the escape or improving the tab navigation in commands with numbers there are no news i assume?

Hi - so far I haven’t been able to reproduce that here. Does this happen with specific commands? Any further details would help.
-wim

hi @wim thanks for checking in, the hick up occurs with the move and copy command, i have not seen other commands effected the same way yet.

the last time it happened after loading a python script through RunPythonScript, not sure if it happened right after it but very shortly after it since i only messed around for 1-2 minutes in total. but i had this happening without python either before, not using anything special but testing rhino on its mere surface.

Thanks for the additional information. I’ll keep poking at it and keeping an eye out for other reports of this behavior. If you see any pattern, please let us know!
-wim

1 Like

hi @stevebaer , so i downloaded the release candidate and had a go. i must resume version 5 is still faster in several points.

basically all viewport manipulations are a bit slower than in version 5.
especially zooming feels really noticeably heavier, it feels like the difference between my old 2009 macbook pro to my newer computer now in version 5. that is particularly bothersome for me personally because i was longing for that snappy feeling, which i now only have with version 5. anything you are still going to change? its not that i used an enormous amount of objects, basically just 448 copied and moved cubes.

dragging objects is now also slower. it seems to wait for that pop up (which for drag one would not need and cant access anyway i think) and this pop up now takes a little longer, delaying the movement and making the entire experience working in rhino laggier. its not a lot but its definitely enough to become distractive.

technial view seem now a bit faster, but compared to rhino 5 its still a little slower.

What kind of results are you getting with TestMaxSpeed on this model?

@stevebaer

Rhino 5 in average
Time to regen viewport 100 times = 0.61 seconds.

Rhino 6
Time to regen viewport 100 times = 1.48 seconds. (67.75 FPS)
Command: '_Paste
Command: TestMaxSpeed
Time to regen viewport 100 times = 0.99 seconds. (100.81 FPS)
Command: '_Paste
Command: TestMaxSpeed
Time to regen viewport 100 times = 1.02 seconds. (98.23 FPS)
Command: '_Paste
Command: TestMaxSpeed
Time to regen viewport 100 times = 1.45 seconds. (69.01 FPS)

oh and by the way the results of commands are not shown anymore, only after clicking on the symbol.

Hmm… you’re getting well over 60 FPS. If view manipulation feels heavier, there must be something else going on. I don’t know what this is as at the moment and am not entirely sure what would be a good way to test things. I’ll have to think about it.

hey Wim:

it might be important to add that i am using a standard mouse with incremental scroll wheel. its as i pointed out particularly noticeable with zooming. the steps of the mousewheel feel like they need longer to complete. the difference is not huge but enough to make it feel slightly chewier. rotating the viewport seems very similar as in 5 if i dont want make up the difference but it feels just a little bit faster in 5. to be fair the more often i change between 5 and 6 the more often i am beginning to believe that i am getting crazy, time for a good night sleep.

3 more things which i collected:

1
the viewport has some odd behaviour, after working a bit and changing the viewports i suddenly end up with this, which not only happened a few times but also transmitted itself into rhino 5. once even so persistently that 4View command only helped after using it multiple times from each viewport individually. and it seems to move the viewports every time the exact same way. since i rarely shift them around i cant even remember if i ever moved them that way once at least not in rhino 6.

2
switching between 5 and 6 messes up my inspectors in rhino 5.

3
that may concern @nathanletwory
everytime i switch to raytraced i get a beachball forever, i cant do anything anymore besides force quitting. artic works though. i even get an instant shut down trying to switch from a mixed viewport style in one viewport to ray-traced. could not get it going once. it shows the viewport with ambient occlusion which looks ready but then it beachballs. i read that it might need a few minutes to compile something, (why its supposed to be doing that is also a bit strange to me) but i left it even for something like 10 minutes once and it never stopped.

Seeing the GPU configuration in your first post:

  • no CUDA support on the Mac for Raytraced.
  • you don’t have a supported AMD card for OpenCL - nothing is being compiled
  • you’ll be using Raytraced on the CPU
  • if you’re doing a complex scene in a large viewport it will take a long time for anything to appear. Things to fiddle with in advanced settings:
    • RhinoCycles.DpiScale - higher number means less work to do. Blocky in viewport, but _-ViewCaptureToFile will always render at value 1. On my MPB I use 3 or 4 for even the slightest hint of ‘interactivity’
    • RhinoCycles.UseStartResolution (set to true)
    • RhinoCycles.StartResolution (set to some power of 2, say 32 or 64)
    • RhinoCycles.UseFastDraw (set to true)

thanks for the imput, thats a pitty, since the computer is not very old and still pretty powerful, rendering on cpu is a real bummer… any plans here or do i have to throw my computer away and run with the newest?

i tried all your settings and have RhinoCycles.StartResolution set to 64, better more or less what does that mean anyway? but the issue remains, as soon as i switch to raytraced i get an infinity beach ball. forcing me to force quit rhino. i wonder why arctic works, does it not also use raytraced?

edit: by the way when i switch to raytraced i get this in the bottom of the viewport, its not readable, maybe due to the dpi settings? i enhanced the colors here and scaled it to a “readable” size.

@nathanletwory

is there anything at all i can do to get ray-traced working? as written above arctic works already and i found that i can change the settings in the display mode that it shows the rendering material. so why does it not work with raytraced? i also set the same lightning system to ambient occlusion, everything else seems the same but as soon as i switch to ray-traced Rhino goes to the beach not coming back…

here another request or idea, would it be possible to deactivate the ambient occlusion or the virtual ground plane while rotating the viewport to speed it up? it seems to slow it down significantly. or is this maybe just on my machine noticeable?

Just to answer this question - no:
Arctic:
image

Raytraced:
image

1 Like

@encephalon I’m not sure that running 10.14 with this card is a good idea, my girlfriend has the same laptop, and as there are no official drivers from NVIDIA, it is much less snappier than on High Sierra.

@nathanletwory what do you mean there is no support for CUDA on macOS?

https://www.nvidia.com/en-us/drivers/cuda/418_163/macosx-cuda-418_163-driver/

It just requires 10.13, and it seems you are stuck on that forever, upgrading to Mojave is not a wise decision, rollback was a nightmare to me, when I naively did it on my desktop.

1 Like

Copy/paste does not working