I have recently upgraded to V5 and seem to be having a few graphics problems with the interface.
The most noticeable is a trial, or echo, around viewports and toolbars when dragging (see attached screenshot).
The second is an intermittent bug where the viewport seems to stick in some areas when rotating and zooming. Again, I've added a screen capture.
Here are some system specs:
OS - Win7 64-bit
GPU - Nvidia Quadro 600
CPU - i7-2600k
RAM - 16GB
Has anyone got any idea what could be causing these bugs? I had no problems with Rhino v4!
Thanks in advance,
As in my previous post, I have exactly the same problem with Rhino 5 and this Nvidia Quadro FX 5600 card, but your description of the problem is better.
Graphics Card : 1.5GB PCIe x16 nVidia Quadro FX 5600 (SHEGA2), Dual Monitor DVI or VGA Graphics Card
No nearer to finding a solution, then…(?)
I'm afraid not, and it's driving me a little crazy. I’m guessing it’s something to do with the graphics cards and related settings!?
Seems a little odd when we both have legit ‘workstation’ GPUs. I’d expect cards like this to have the least problems, being OpenGL specific. Weird.
Hi Philip- we are a aware of this and we are working on it. Actually, I take that back, partly- the viewport drag problem has not been reported... it may very well be related as both are screen redraw problems. I"ll let the developer know- thanks.
Please view my new reply for some added spec.
Looking forward to hearing about the fix.
This looks more system wide than viewports not updating. Your entire UI isn't refreshing, not just the viewports.
I also notice you mention using Win7 64bit, however, your UI looks like XP... Have you installed the XP theme (or something)... That might be part of the problem. If so, please explain exactly what you've done and have configured in Windows 7 that's not the "standard" install.
Hey Jeff & Pascal -
I have the same problem but as an extra detail - I see this problem the worst in a 3 window view when I move a tool panel over the "inactive" (back) windows. The echo trails rolls across the 2 back windows, but NOT in the front, active view.
But do the trails finally go away, or do you have to do something extra to get them to disappear? If they're not going away, then there's a problem somewhere, if they do eventually go away, then the trails are simply a result of your system trying to keep up with all of the drawing and refreshing that's going on.
Hey Jeff, Shouldn't be much to refresh on this wireframe page. The panel in the pic has been moved upwards and the trails show up behind it on the 2 inactive windows. Using a professional tower workstation with 2 Xeons (2.5 GHz x 2), 16 Gb of RAM, 1.5 Gb of VRAM. 64 bit, but Vista Ultimate, not Win7. The trails go away, but this doesn't happen in any other program or on the desktop.
I agree...but I'm just not seeing this behavior here at all, on any of my machines, including a laptop. Setting my viewport configuration exactly like yours, enabling the "Classic XP" theme, positioning the layers panel exactly like you have... Dragging the panel around, up and down, left and right, all my viewports update instantly...in fact, I just knock stuff off my desk trying to move the mouse fast enough to produce trails :) ...but still, smooth refreshes and updates.
Can you get a screenshot of Rhino's OpenGL settings page and post it here.
Comparing to other programs doesn't really mean much...unless they're programs that use multiple OpenGL contexts in multiple child windows, that all update simultaneously.
What happens if you UNCHECK that second option:
"Redraw scene when viewports are exposed" ???
That option was needed in XP, but it's not really needed in Win7... however, it might make matters worse in your case, but let's try it and see what happens. Even though it looks like XP, the Windows 7 Desktop Windows Manager (DWM) is still in use here, so theoretically, you shouldn't need that option checked.
Might well be something really simple like that, but unchecking the option (and restarting Rhino with it unchecked - you get the idea) doesn't change anything. I take it you're not managing to reproduce the problem ? In a previous thread there was a 3rd person reporting the same glitch but he simply hadn't checked the "use acclerated hardware modes" box…which isn't my case, unless something's corrupt…?
Update : Just checked the other thread and it's not the same thing at all. A little off topic, sorry.
The other thread