Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect UI raycast hits #6

Open
Spiess opened this issue Feb 7, 2022 · 1 comment
Open

Incorrect UI raycast hits #6

Spiess opened this issue Feb 7, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@Spiess
Copy link
Member

Spiess commented Feb 7, 2022

UI raycast hit order appears to be determined by order in hierarchy instead of z distance to the UI pointer since switching away from Unity VR Interaction Toolkit.

This problem does not appear to occur when UI elements share the same canvas, so a possible fix should be using a single world-space canvas for all conventional Unity UI.

@Spiess Spiess added the bug Something isn't working label Feb 7, 2022
Spiess added a commit that referenced this issue May 31, 2022
Workaround for #6.
Added additional layer UI Interaction Blocker and changed tracked device raycast settings for all canvases to check 3D occlusion and add the new layer to the blocking mask.
Spiess added a commit that referenced this issue Jun 1, 2022
* Advanced query infrastructure.

Implemented infrastructure to support staged and temporal queries in the
form of the QueryTermManager.

* Updated Cineast API.

Updated the Unity Cineast API package to the newest development version.

* Query controller staged query support.

Implemented staged query support in query controller.
Queries are already stored in the query response object each query
display contains, therefore the redundant query variable has been
removed from the query display list.

* Implemented query term order representation.

- Restructured prefabs directories.
- Refactored interactor to allow interactions with both interactables
  attached to the entity containing the collider as well as the entity
  containing the rigidbody, although the collider interactable has
  priority in edge cases where both are available.
- Implemented Query Term Provider Representation to visually represent
  query term providers and their order in the query.

* Implemented query term provider reorganization.

- Fixed query list view for staged queries.
- Implemented query term provider reorganization into new stages, new
  temporal contexts and existing stages through grabbing and dragging.

* Implemented basic temporal query support.

Implemented basic support for temporal queries with some parts still
work in progress.
- Temporal query results are not logged.
- Only the first segment of each temporal result is presented.

* Updated DRES integration version.

* Implemented query term representation connection lines.

Implemented connection line to connect query term representations with
their respective query term providers.

* Implemented a workaround for incorrect UI raycast hits.

Workaround for #6.
Added additional layer UI Interaction Blocker and changed tracked device raycast settings for all canvases to check 3D occlusion and add the new layer to the blocking mask.

* Implemented quick submit for controllers without touchpad pressed action.

* Implemented first version of temporal media item display.

* Implemented better term provider representation naming.

* Updated connection indication for pose term provider.

* Updated pose projection to use a 90 degree FOV.

* Added drawer functionality to temporal media item display.
@Spiess
Copy link
Member Author

Spiess commented Nov 8, 2023

A discussion about this bug can be found in this Unity forum thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant