What is the roadmap for standard UI element support like sliders, buttons, input, toggles, dropdown, etc.
Why aren’t the SpatialUI scene example components included as prefabs or Create > Components? Should we use these? Are these intermediary UI components that will no longer work in future Polyspatial versions?
Going forward - Will Unity UI be supported on Polyspatial?
just a note that I sanity checked with an empty project, starting from the 1.0.3 VisionOSTemplate, and the included SampleScene. I cannot seem to select the input field on device. I’ve tried gaze selection and also poking.
The top is Unity UI Input Field
The bottom is TMP UI Input Field
@kapolka I followed the same steps as @ina and I am seeing the same result. The input field becomes active and the carat turns on, but the soft keyboard doesn’t appear, and it doesn’t accept input from bluetooth keyboard. The repro is easy – open the 1.0.3 VisionOSTemplate project and add an InputField (TMP) object to the canvas. I’ll also open a bug report on this.
I’ve found that the soft-keyboard doesn’t appear when you are using a Mac Virtual Display. This seems like an OS-wide issue though (the connected keyboard will still allow you to input text) so worth sanity checking your input fields without a virtual display enabled. Other than that, we are seeing no issues
Thanks for the report! I can reproduce the issue, and while I’m not sure what’s causing it, it does seem to be project-specific. If I export SampleScene into a custom package along with all its dependencies and import it in another project (created from scratch from the 3D (URP) template, then switching to visionOS target, configuring XR Plug-in Management, etc.), the TextField/keyboard works as expected.
I’ll keep investigating to see if I can figure out what’s different about the visionOS template project.