JoeLudwig
commented
3 years ago The UI piece of this should be straightforward, but we'll probably need some Aardvark plumbing for the actual macro actions.
Open Adil3tr opened 3 years ago
JoeLudwig
commented
3 years ago The UI piece of this should be straightforward, but we'll probably need some Aardvark plumbing for the actual macro actions.
What would this gadget do?
This gadget creates a 3D UI object that serves as a macropad, allowing a user to perform various actions to streamline workflow. Integration into programs like Photoshop, OBS, standard keyboard shortcuts, twitch, allows the gadget to supplement or replace dedicated macro hardware and makes it more accessible to more people. The code would be built to be easy to tweak the layout, add buttons and knobs, and change their function (press, hold, twisting, etc). In VR novel functions not possible in real life would make it an attractive use case like tooltips when hovering over a button, pulling buttons out to use frequently in a session, and so on.
Who would use this gadget?
Macrodecks are expensive and only partly customizable. In VR the configuration, shape, scope, and size of macrodecks can be far more flexible and cost little to nothing. While this could be used while standing by a streamer, the ideal use case would be breaking new ground by making seated work in VR much more flexible in excel, creative software, and more. This could pair well with hand tracking or passthrough AR, and any desktop mirror like Desktop+. This would make work in VR on PCVR much more capable and less constricting than any competitors, and novel functionality could make it an actually viable option.
Assuming that you're on the team, what other skillsets would you need to make this project happen over a couple days of hacking?
I am not experienced with coding, I’m just trying to provide the concept for consideration.
What will be the toughest part of building this gadget?
To use real macros, it would need to interface with existing APIs. Making the UI in such a way that accidental inputs aren’t possible without slowing down function significantly is essential, as well as making the layout easily customizable in both the number of buttons/knobs/switches and the shape of the tool.
Future versions of this would need to be more complicated on the back end to incorporate things like autohotkey to gain much more functionality.