Help Grab the middle of a rope?

[darkcser]

Are you trying to use the new SDKManager_Constructor Scene, or setting up VRTK manually by making a gameobject and adding SDKmanager.cs to it, ect?

I just tried to repeat the steps and going from scratch this time, I see VRTK added this new scene to handle the SDKManager. The problem with using this extra scene is the SDKManager.instance is null for some reason, so nothing gets set up to interact with the rope. I'm trying to figure out how to access it with the new way but haven't got it yet. There are instructions on how to setup VRTK manually, after that it should work. I'll look into it a little more but as you may see on line 70 of the InteractableSolver.cs the instance of the VRTK_SDKManager is null.

https://github.com/thestonefox/VRTK/blob...STARTED.md

Thanks for the reply!

I will set it up manually this time, and give it a whirl. 

VRTK is still kind of mystifying for me at times in the way that it behaves. For some reason with the github version of 3.3.0a it always has the controllers invisible for me. The updateposes issue was supposed to have been fixed but they still don't show up. I spent hours messing with it until it suddenly just showed up by itself -I thought it was because I opened the custom controller scene. Of course I then tried it on another clean copy from github but of course it didn't work, and the controllers were still invisible. Some odd combination of events or changes fixed it. Now I just branch off of the mysteriously working version... 

There's this section from Github:

(https://github.com/thestonefox/VRTK)

Important Note

The example scenes no longer contain the VRTK_SDKManager as this is loaded in at runtime via the VRTK_SDKManager_Constructor scene. As the VRTK_SDKManager script is responsible for setting up the required Unity Scripting Define Symbols for installed SDKs it is required that the VRTK_SDKManager_Constructor scene is opened in the Unity Editor when first using the project or when installing a new supported SDK so it can set up the scripting define symbols. The example scenes will not work until the scripting define symbols have been set up correctly so please ensure that the VRTK_SDKManager_Constructor scene is loaded into the Unity Editor first.

I'm not quite sure what "ensure that VRTK_SDKManager_Constructor scene is loaded into the Unity Editor first." I tried loading that scene and another example scene at the same time but it didn't seem to do anything different.

Hopefully with version 4, things will be a bit more transparent. I was a bit disappointed that it was Oculus that sponsored them instead of HTC. I hope the SteamVR support continues to be good.