We think so too!

Yup, it's covered in our Widgets 101 course on the HQ PRO :) But one of my goals when talking about a topic is to try not to collude it too much with techniques that aren't related to the topic (within reason). That way when newer folks are watching a video like this about Engine COMP or similar, they won't all of a sudden have to stop the video and say "wait...what just happened?!" to something unrelated to the topic I'm trying to focus on. Always happy to hear more tricks though, please keep 'em coming!

Learned from the best my friend (you!) :)

It is integrated behind the scenes I believe (it mentions GPU affinity in the documentation) so it will probably be exposed as a parameter soon or at least the workflow will become more obvious.

I mentioned GUI workflows although I didn't elaborate more on them :) Previously when you offloaded GUI's you would usually have the GUI in another app or on another machine, and then you'd send data back from it. If you needed to include it in the window setup you have on the main machine, you'd often use something like the Remote Panel tools in the Palette, which allow you to do an interesting workflow where the UI is rendered somewhere else, the texture is sent back to the main app, then from the main app you skin a container with the texture and collect the panel click states, then you send that panel click data back to the system/app running the UI and use Python to re-simulate the clicks on that. It creates this interesting loop signal path that essentially offloads your main system from the UI rendering but still allows your main system to catch the UI input. With Engine COMP you could re-build this pretty quickly by sending panel values in via a CHOP to the Engine COMP, and get the rendered UI back out from it to display. Hopefully that makes sense and sorry for the length of comment!

@@TheInteractiveImmersiveHQ super helpful comment, cheers