As this fork has diverged fairly significantly from the main branch, I have gotten requests for how to use both of them. Currently, they have to completely swap out the driver every single time. I would like to request that you implement this using the vendor features found in the main driver. Those make it so that the driver has a separate name and separate settings files, which allows them to coexist. Then, users can switch between the drivers with a single click in the GUIs. The vendor functionality as implemented in the main driver results in the drivers automatically locking themselves out when both are active.
Also, if you do make a vendor driver, add a bit of code on install to check if the installed CustomHeadsetOpenVR driver has the shaders belonging to this one and uninstall it out so that it doesn't stick around for people who have only used your driver and not the main one.
As this fork has diverged fairly significantly from the main branch, I have gotten requests for how to use both of them. Currently, they have to completely swap out the driver every single time. I would like to request that you implement this using the vendor features found in the main driver. Those make it so that the driver has a separate name and separate settings files, which allows them to coexist. Then, users can switch between the drivers with a single click in the GUIs. The vendor functionality as implemented in the main driver results in the drivers automatically locking themselves out when both are active.
Also, if you do make a vendor driver, add a bit of code on install to check if the installed CustomHeadsetOpenVR driver has the shaders belonging to this one and uninstall it out so that it doesn't stick around for people who have only used your driver and not the main one.