Thanks for your messages, may be it’s not the key point.
For example, I create a program which is running on Vive named OpenApp, and I create a function which can open another VRGame, such as ZenBlade.
When I run the program, first the ZenBlade can’t be controlled by Vive, there is no input, the Vive doesn’t connect with the game. Second my program OpenApp is auto closed, it obviously isn’t what I want.
So I try some ways to deal with it, the most effective way is I run under code.
UGameplayStatics::GetPlayerController(inWorld, 0)->ConsoleCommand("quit");
procHandler = FPlatformProcess::CreateProc(*AppPath, nullptr, true, false, false, nullptr, 0, nullptr, nullptr);
It will make OpenApp release the connection with Vive, and close itself. But the ZenBlade can correctly get the connection with Vive and be played with VR.
Is there any way can prevent my OpenApp do not quit, and I can also open and play the ZenBlade with Vive, and when I quit the ZenBlade, I can return to the OpenApp. It seems not a big issue, but it really doesn’t work at all.
I search the steamVR plugins, it seems doesn’t have any way to deal with it.
May be what I say is a little confused, it is really a simple question.
Thanks for your answer again, my English is really pool. I wish my expression doesn’t confuse you:)