# V6 Display: Anti-alias issue and technical display mode issue

**URL:** <https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971>\
**Category:** Rhino for Windows\
**Created:** [September 15, 2018, 12:31am UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971 "2018-09-15T00:31:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Howden](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/steve_howden/32/482024_2.png) [@Steve\_Howden](https://discourse.mcneel.com/u/Steve_Howden)\
**Post date:** [September 15, 2018, 12:31am UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/1 "2018-09-15T00:31:25Z")

</div>

Hi Folks,

I’ve had V6 installed for some time but due to frantic work levels have been using V5 (since I had not got around to moving my settings and umpteen plugins and scripts over).  
Today I thought I’d start the migration and immediately ran into two show stopping problems.

Before I go any further I thought I’d better check in and see if I am doing something wrong.

Problem 1: Wire frame antialiasing. It’s horrible. I am on a Quadro M4000 with 8GB VRAM with latest drivers displaying onto very nice monitors (an Eizo Flexscan and a Wacom Cintiq 24HD). Doesn’t seem to matter what I set antialiasing to. Even at 8x it is seriously worse than V5. I’m using the “Workstation App - Dynamic Streaming” preset in the nVidia control panel.

Problem 2: I use Technical display mode and a variation of that display mode where I shade objects. In V5 I can get a clean display where the edges and silhouettes of meshes show nicely. I V6 I can’t get the mesh borders to show at all. Polysurfaces DO show the borders but it’s very choppy. Attached is a screen grab showing a model made of meshes in the two versions. I’ve also attached the V5 .ini file for that display mode

Any trouble shooting help greatly appreciated. Steve

 ![technical-shaded-v5-V6](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/6/8/683e734a56e34e67e48323cec193112966d78fbf.jpeg) [Technical Shaded.ini](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/4/b/4b4f4d9d6175f5bef377b59678e79a07a2a32cf0.ini) (10.4 KB)

---

<div class="post-metadata">

**Author:** ![Jarek](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jarek/32/511212_2.png) [@Jarek](https://discourse.mcneel.com/u/Jarek)\
**Post date:** [September 15, 2018, 12:55am UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/2 "2018-09-15T00:55:16Z")

</div>

Hi Steve,

I can only confirm that #2 in V6 doesn’t seem to work - can’t get Mesh naked edges to show in Technical mode with any settings configuration (just played with it for a while, including manually editing the ini file). Something is definitely odd.

As for #1, there was an ongoing discussion regarding this.  
See here if this is of any help on your system:

> [@Bad quality of antialiasing in Rhino 6](https://discourse.mcneel.com/t/bad-quality-of-antialiasing-in-rhino-6/66022/19):
>
> I wrote a TestLineSmoothing command over the weekend to prototype a fix for the issues you guys are seeing. I’m having trouble finding a monitor/computer combo at the office that repeats what you are seeing so I am doing a little bit of guessing while writing this code to see if makes a difference. NOTE: you need to have GPU tessellation enabled for this command to make a difference. All of the line smoothing ad “thinning” code is in the GPU tessellation shader. You may also want to reset your W…

–jarek

---

<div class="post-metadata">

**Author:** ![Jarek](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jarek/32/511212_2.png) [@Jarek](https://discourse.mcneel.com/u/Jarek)\
**Post date:** [September 15, 2018, 12:56am UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/3 "2018-09-15T00:56:41Z")

</div>

> [@Steve\_Howden](#):
>
> Today I thought I’d start the migration and immediately ran into two show stopping problems.

I did the same 2 weeks ago finally (switch production from V5 to V6) and ran into some other show-stoppers. And we are “only” at SR10 😛

-j

---

<div class="post-metadata">

**Author:** ![Steve\_Howden](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/steve_howden/32/482024_2.png) [@Steve\_Howden](https://discourse.mcneel.com/u/Steve_Howden)\
**Post date:** [September 15, 2018, 1:06am UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/4 "2018-09-15T01:06:29Z")

</div>

Thanks Jarek,

At least it’s good to know that I’m not imagining things 😉

I’ll have a bit of a fiddle with the wireframe anti-alias and see if I can get it any better.

The Mesh edge display in Technical mode is however a _total_ show stopper for me. I’ll have to go back to V5 for now. McNeelies: Any chance this could get looked at?

Cheers, Steve

---

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [September 17, 2018, 6:22pm UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/5 "2018-09-17T18:22:53Z")

</div>

> [@Steve\_Howden](#):
>
> Any chance this could get looked at?

Hi Steve,  
This is now on the list as [RH-48509](https://mcneel.myjetbrains.com/youtrack/issue/RH-48509).

---

<div class="post-metadata">

**Author:** ![Steve\_Howden](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/steve_howden/32/482024_2.png) [@Steve\_Howden](https://discourse.mcneel.com/u/Steve_Howden)\
**Post date:** [September 17, 2018, 6:44pm UTC](https://discourse.mcneel.com/t/v6-display-anti-alias-issue-and-technical-display-mode-issue/70971/6 "2018-09-17T18:44:48Z")

</div>

Thanks Wim.  
S