Project Tiny & VR

Does Project Tiny support VR? If not, is it on the roadmap?

 

Hi Ted, I just got Unity.Physics to run within Tiny Runtime, wanted to know if i'm probably missing something since I didn't get to test it fully (just a physics ball falling on a plane, with some restitution).
All I had to do was change the TinyExportDriver class and add another BlobAssetStore argument to the constructor, and populate the BlobAssetStore member of the parent GameObjectConversionSettings, so the collision conversion could add the collision data to the build. Seems to work in standalone windows and in wasm builds.

Is there other stuff that needs to be done to get Unity.Physics functional in Tiny, or is this all that is needed? I was afraid maybe i'll discover later that it's still not fully functional, and more work would need to get done, finding myself in a rabbit hole.

com.unity.dots.runtime@0.1.0-preview.5\Unity.Entities.Runtime.Build\TinyExportDriver.cs line 27

Code (CSharp):

1. public TinyExportDriver(BuildContext context, DirectoryInfo exportDataRoot, BlobAssetStore blobStore)
2.         {
3.             BlobAssetStore = blobStore;
4.             BuildSettings = BuildContextInternals.GetBuildSettings(context);
5.             m_ExportDataRoot = exportDataRoot;
6.         }

Of course I had to make the BlobAssetStore member public in the com.unity.entitites package / GameOBjectConversionSettings class, but since that class also has virtual members, I'd argue BlobAssetStore should be modifyable from derived classes anyway, since it seems the base class is intended for extension.

 

Interesting. I saw the fixedFrameRateEnabled public member in TinyEnvironment.cs, would I have to set that to true, and if so, how? Accessing the TinyEnvironment system directly from one of my systems and then setting it, or some other way?
It didn't seem to be referenced from anywhere else in the code.

Later edit: Seems to work. It's framerate-dependent, with just this change, of course, but just doing this avoids instability in physics I suppose. Now if only I could figure out how to step the physics manually.

Would alternating the fixedFrameDeltaTime between 0 and 1/60 depending on how far behind physics time is from realtime be correct?

I know there was a solution a while ago to update the physics groups from within the FixedUpdate of a MonoBehaviour, but that's not an option in Tiny

 

Thanks, that's great news!

 

Is 2D also include UI?

 

Hey Ted just curious where VR support landed for tiny. As always totally understand things change but with tiny being a potential life saver for VR quest I have to ask