Multiple issues: interactTouch/Mouse, opviewTOP performance and engineCOMP bugs

Bugs
1

Hi all

issues.zip (24.8 KB)
Win 10, RTX6000, 2020.27390

Found a few issue with interactTouch/Mouse, opviewTOP and engineCOMP.

When you open the demo file you interact with a panel rendered inside an engine COMP (“/project_engine”). The actual/source network is (“/project”)

Issue 1:
if you interact with toggle buttons via InteractTouch or interactMouse a toggle button behaves like a “toggle up anywhere” button. i.e. click on the button and move the mouse away before you let go >> you still toggle the button

Issue 2:
Opview cooktime seems very high. For a medium complex UI (simulated with a bunch of buttons) the opview TOP cooks 3 ms. In my production file the opview TOP even cooks 6 ms. This seems pretty high, no?

Issue 3:
inside an engine COMP the keyboard in DAT seems to only react to

  • shift and control keys
  • and those are only updated when the mouse is moved

Issue 4:
the multitouchin DAT is not working at all inside an engine COMP, which makes this whole “(multi) touch panel inside an engine COMP” more complex than needed

Issue 5:
also noticed that the mouse CHOP is not working at all inside an engine COMP

2

Thanks @Achim, all separated these out into a few issues in our database.

Re: OP Viewer, have you tried the OP Viewer COMP? I know not all workflows work with it but it is the more modernized approach to grabbing OP Viewers, but isn’t helpful if you need them in a TOP stream.

3

Hi Ben, yes i need them as a TOP stream to get the UI out of an engine COMP. I would have expected this to be super fast as the UI is already calculated in the panel and everything stays on the gpu .