10-10-2018 04:59 PM
10-11-2018 07:41 AM
10-11-2018 03:00 PM
10-11-2018 03:47 PM
Thank you for the response. If you could clarify on a couple of points: What is it that you mean by "disabling vr" before switching instances in the first paragraph? Is the disabling something I do in Unity code? Or from the Oculus app or something? Also, do I need to make a separate Oculus account to connect the two instances? Or can I connect from my OculusID to itself to test the SDK? The two instance constraint should be fine, so that's good.
MikeF said:
so prior to the home 1.31 update it was quite easy, you could just build and run multiple instances on the same machine. You would only be able to see one instance at a time of course but you could still easily swap between instances by disabling vr, focus on other instance and enabling.
But now as of 1.31 you can at the most test two instances, one has to be in the unity editor and the other has to be a build. Any more instances and you'l get nothing in the headset and no input response. This is due to a change in home that only allows input focus on a single instance of an application (most likely due to dash)
I would like to hear if anyone has another suggestion though
10-11-2018 04:48 PM
10-11-2018 05:26 PM