Am I the only one think it's ridiculous that they marked OpenGL viewport as "deprecated" when Vulkan one is this bad? Does anyone really use Vulkan viewport at all? Is there any other DCC where you need to fight to see which faces are selected? Is there another professional software that is self-claimed to support win/mac/linux but has such great discrepancy between platforms?

But anyway you'd better delete this post. Because "forum is not a place to report bugs" and you don't want to get banned, right.

Not sure what display settings you've changed from the default, but it's pretty easy to see edges with the factory settings.

malexander
Not sure what display settings you've changed from the default, but it's pretty easy to see edges with the factory settings.

Default settings. macOS

Mac unfortunately does not support wide lines, so edges are a bit tougher to see there.

malexander
Mac unfortunately does not support wide lines, so edges are a bit tougher to see there.

everything is displayed correctly in deprecated OpenGL

It is OSX thing. Apple does not support OpenGl nor Vulkan anymore, so this is probably going through MoltenVK. On Linux, for me, Vulkan is way more performant and looks better than OpenGl.

alexeyvanzhula1984

malexander
Mac unfortunately does not support wide lines, so edges are a bit tougher to see there.

everything is displayed correctly in deprecated OpenGL

The OpenGL renderer uses a geometry shader to turn lines into quads. Vulkan made that feature optional, and MoltenVK didn't implement it. It'd need to be re-implemented as a tessellation shader (which isn't natively supported either, but at least is emulated correctly), which we can probably do. Features often take a little bit longer to implement on Mac due to the hardware and API choices Apple has made, but we get there.

SreckoM
It is OSX thing

No. Windows users also complain about display issues. With MoltenVK it’s understandable, but I thought the viewport rendering was supposed to produce identical images on Windows and Linux.

alexeyvanzhula1984

Image Not Found

Flickery, as in they turned off VSync for Houdini? Hard to say what the problem is without more context. Ironically, the faster the frame refresh, the worse tearing gets with VSync off -- and Vulkan is quite a bit faster than GL, on average.

There weren't any reports of this during the beta or internally, so I'd recommend they check their driver against what's recommended, and submit a bug with their system specs if it persists.