Forum Discussion
Meta XR Core SDK update to 68.0.0 is preventing unity to build
I just updated the xr core sdk to 68 and unity prevents me from launching my game since there are issues with MetaXRSimulator:
Library\PackageCache\com.meta.xr.simulator@66.0.1\Editor\MetaXRSimulatorEnabler.cs(100,42): error CS0029: Cannot implicitly convert type '(Meta.XR.Editor.UserInterface.TextureContent CheckIcon, UnityEngine.Color Meta)' to '(Meta.XR.Editor.UserInterface.TextureContent, UnityEngine.Color?, bool)'
Library\PackageCache\com.meta.xr.simulator@66.0.1\Editor\MetaXRSimulatorEnabler.cs(100,150): error CS8135: Tuple with 2 elements cannot be converted to type '(TextureContent, Color?, bool)'.
Library\PackageCache\com.meta.xr.simulator@66.0.1\Editor\MetaXRSimulatorEnabler.cs(100,30): error CS1662: Cannot convert lambda expression to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type
Thanks.
3 Replies
Replies have been turned off for this discussion
shocking update. I just saw a Unity update for the Meta XR Core SDK, so i thought great........updated, broke my project, everything is now not compiling with these errors about.
yep, tried to persist as I thought it was my ability. But nope, broken scripts from Meta, nothing now works, not passthrough. Beyond frustrating, I now lost a days pay today and I will still have to roll back on Tuesday morning to prove to my contractor I know what I am doing..........Im a few weeks in, so Im taking a long weekend and quite likely walk away from the project. I only updated as I couldnt get the OVRINPUT on the SecondaryThumbstick to work..........completely broken, and looking on the Unity asset store, same for many others.
Just shocking work. Thanks Meta. I ventured into MR with faith as VR was good progress. I think I'll be back tracking Open XR and full VR, NOT the Meta SDK.
Hello,
Just so you know, there was a bunch of updates that followed yesterday including the meta xr simulator that was causing the issue, that fixed it for me to re-update everything to 68...
Now, if you are on simultaneous concurent hand and controller tracking just know that pinching with your hands is now activating the Trigger and the A button ........ so they basically took 4 buttons out of us. It's nutts. (it's only an issue in the Build itself, unity ignores all of that nonesense.
(so I stayed on 67)
