search

microsoft / MixedRealityToolkit-Unity

This repository is for the legacy Mixed Reality Toolkit (MRTK) v2. For the latest version of the MRTK please visit https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity
https://aka.ms/mrtkdocs
MIT License
6k stars 2.12k forks source link

'SpatialInteractionController' does not contain a definition for 'TryGetRenderableModelAsync' #1172

Closed linojon closed 6 years ago

linojon commented 6 years ago

Hi, trying to build example scene (MotionControllerTest). It runs in editor. Get this error when try to build:

Assets\HoloToolkit\Input\Scripts\Utilities\Extensions\InteractionSourceExtensions.cs(97,39): error CS1929: 'SpatialInteractionController' does not contain a definition for 'TryGetRenderableModelAsync' and the best extension method overload 'InteractionSourceExtensions.TryGetRenderableModelAsync(InteractionSource)' requires a receiver of type 'InteractionSource'

Using Unity 2017.2.0f3-MRTP Windows 10 Pro build 16299.19 MRTK Dev_Unity_2017.2.0 branch

StephenHodgson commented 6 years ago

Do you have the latest SDK installed? 10.0.16299.0?

linojon commented 6 years ago

Thanks, that was it. Got it to build. (Yay) and run via VS. But the controller models dont show up (the data is updated like when Play in editor). I'm running the example scene with no modifications.

linojon commented 6 years ago

Is there a forum or slack to ask questions? i'd really like to figure out the controller models question. Thanks.

HattMarris1 commented 6 years ago

There is -> https://holodevelopersslack.azurewebsites.net/

linojon commented 6 years ago

oh, MixedRealityCameraParent/MotionControllers was disabled in the scene by default. Thank you guys for being so responsive.

keveleigh commented 6 years ago

The models not showing is likely timing with the driver. The first time you use the controllers in an app, the driver attempts to download the actual models. If they download during app usage, the models should pop in. Making sure you have the latest drivers wouldn't hurt either.

Edit: nevermind, looks like you figured it out!

StephenHodgson commented 6 years ago

Huh strange. I'm pretty sure we enabled those on the prefab again. Did you get the latest release?

monsdar commented 6 years ago

Had the same issue too, turned out I had the new (10.0.16299.0) and the old SDK installed (10.0.15063.0). I needed to switch the SDK to the new version in the Unity Build settings.

Not sure if this needs to be done manually or if my project is just a bit messed up. Wanted to let you know in case someone has the same issue.

andijakl commented 6 years ago

This issue also affects the main branch, so it also appears when building for HoloLens and using the default 15063 SDK for that. Not sure if switching to the 16299 SDK is the best solution for HoloLens?