There's a lot of weird confusing stuff behind this, but basically this allows the named pipes to connect if SlimeVR is run as an admin. I don't know any use-case where people would want to run SlimeVR as an admin, but for some reason a good number of people do. This would just make it work regardless. Alternatively we could just warn the user if it's run as an admin and tell them not to.
I have no idea how this security attribute stuff works, but I know at a minimum that this configuration works. Please suggest anything that can be changed about it as I'm certain this can be done better.
There's a lot of weird confusing stuff behind this, but basically this allows the named pipes to connect if SlimeVR is run as an admin. I don't know any use-case where people would want to run SlimeVR as an admin, but for some reason a good number of people do. This would just make it work regardless. Alternatively we could just warn the user if it's run as an admin and tell them not to.
I have no idea how this security attribute stuff works, but I know at a minimum that this configuration works. Please suggest anything that can be changed about it as I'm certain this can be done better.
Relevant resources: