H20 question - to what degree is Vulkan viewport usable?

   8400   23   6
User Avatar
Member
255 posts
Joined: Aug. 2018
Online
malexander
While there will probably be some image enhancements...

I just wanted to post to say 'thanks' for all the very useful and interesting info you've posted in this thread!

...and while I'm here I'm going to take the opportunity to bring up 'the gnomon issue' again. See: https://www.sidefx.com/forum/topic/87788/ [www.sidefx.com] and https://www.sidefx.com/forum/topic/92736/. [www.sidefx.com] I really wish that Sidefx could put more attention and resources to improving these sort of UI matters. While they may seem 'minor matters' they become 'major irritants' when you need to use them many times each day...
Edited by Mike_A - Nov. 5, 2023 18:08:24
User Avatar
Member
68 posts
Joined: May 2023
Offline
Any chance the vulkan updates will include better viewport displacement?
A few versions ago, (maybe 14) viewport displacement worked quite well but in later releases I
get this strange subdivision when turning on viewport displacement.

(This image is from the open gl viewport, vulkan doesnt show displacement for me.)

Attachments:
ub3F7HBqHf.png (809.5 KB)

User Avatar
Member
1 posts
Joined: April 2024
Offline
Is this still the case with Houdini 20.5? It seems to be the default and unknowingly and I was trying to some flipbook rendering and noticed a change to lighting.
User Avatar
Member
112 posts
Joined: Oct. 2018
Offline
malexander
Andr
Is Vulkan viewport more performant in visualizing string attributes?
The current GL viewport is exceptionally slow.

Unique strings are simply a bad case for display. We build a buffer containing all the string information and a point attribute to lookup the offset and size of the string. Usually there's a few dozen strings shared by multiple elements, so the text buffer is small. The other bad case is long strings, which because we generate 2 triangles per character times the number of elements, can also lead to sluggishness. Unfortunately there's very little the API can do here, because it's already done in a single shader.

I definitely think there should be other ways of visualizing strings - such as using solid colors and a legend for the few-string-many-elements case, highlighting/zooming to a given string, or being able to more easily inspect strings on primitives. Throwing up thousands of overlapping blue text strings seems very brute force and often not terribly useful.


It would make more sense to upgrade geospreadsheet so that when you select the string there the elements are highlighted in the viewport and vice versa? Anyway just a thought...
  • Quick Links