In fact, I have posted in the past some glitches regarding viewport realtime rendering with an AMD Radeon Pro card. I have been asked to post the second glitch it in a different post so here it is.
It seems that the clipping plane does not clip the outlines of the objects unless they are fully clipped.
However, I have recently downloaded the latest versions of Rhino 6.0 (6.25.20105.13371) and Rhino WIP 7.0 (7.0.20105.12495) and I was surprised to see that for Rhino 7.0 doesn’t appear to have this issue anymore.
For quite some time now, fixes are mainly implemented in Rhino 7 and only in rare and specific cases should you expect changes in Rhino 6.
That said, In a recent reply, @Holo mentioned that updating the drivers for his AMD GPU fixed the clipping issue on his system. Have you updated your drivers lately?
Also, what does it look like when you draw NURBS boxes and not extrusion objects?
-wim
I hope the new drivers help for you, but I see that AMD still has opengl curve drawing uglyness in Rhino, and that is such a shame.
Nobody expects new features to be added to SR’s but fixing bread and butter tools for dedicated hardware should be prioritized on the official build IMO. Especially when it’s well known that Beta versions can not / should not be used for production by the majority of the users. So please see if you can implement some v7 fixes in v6.
Nurb boxes look the same. Even Isocurves don’t clip.
Updating drivers didn’t fix the issue.
I understand your point but then why do you make updates for Rhino 6.0? And does this mean previous versions of Rhino are obsolete after the new version comes out? I wasn’t aware of that. I am really surprised!
Fixing existing issues seems to be really important. Not to mention that you can already perform a comparison between the codes. I agree with @Holo…
Couldn’t agree more with this. These are things that should work in V6, and by not adding fixes like these ones to V6, we are being forced to upgrade to V7 as soon as it comes out, which I’m sure it’s not your intention but it’s the reality.
This doesn’t look like a fix that was intentionally made in V7 and kept out of V6. Driver bugs are finicky and very difficult to reproduce. My guess is that this was an unintentional fix that happened as a side effect from making other changes in the code.
Maybe I’m mistaken though; @wim do you know of a YT issue that specifically fixed this in V7?
@stevebaer - No, I don’t know of a V7 fix that specifically targeted behavior like this.
As far as I know, we only ever saw something that looked a bit like this but that was for very specific hardware on the Mac and was fixed in Rhino 6.
-wim
Thanks, that’s what I figured as well. @andreasor81 this looks like a machine specific driver bug. Try turning off GPU tessellation in Rhino’s OpenGL options page. There’s a chance that drawing wires using an alternate technique will remedy the situation.
i had a similar problem like the OP when i updated my AMD driver in April. It started after i upgraded to SR24. Since i could not work like this i rolled back to my old driver (using a system restore point) which fixed the issue for breps and extrusions. However, with meshes i still have a problem with clipping and my old driver, the mesh wireframe is not clipped:
@stevebaer, I have tried what you proposed. I have tried even forcing several 3D options from the AMD driver @stevebaer, I am not sure what kind of Graphics card you have. I have a mobile Radeon Pro WX3200.
@wim, by the way, you have already contributed to correcting a glitch in the graphics in my other post.
Rhino 7 had this glitch as well and it was corrected, together with the problem of the edges after my post. Rhino 6 had the glitch corrected, but not the problem of the edges.
Anyway, it seems I will have to get a Workbook with an Nvidia Graphics Card next time.