generated from vrchat-community/template-package
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Changing preview objects causes flickering selection outlines #453
Comments
bdunderscore
added a commit
that referenced
this issue
Oct 14, 2024
Previously, we swapped between two proxy renderers in order to minimize the cost of building new game objects all the time, and to allow a new pipeline to build in parallel with rendering the prior pipeline. This worked, but caused flickering effects, due to the unity selection system being stateful and remembering the previously selected/highlighted instance ID. Here, we instead have a single primary proxy used for all rendering, and use alternate objects while setting up a shadow proxy pipeline. Closes: #453
bdunderscore
added a commit
that referenced
this issue
Oct 14, 2024
Previously, we swapped between two proxy renderers in order to minimize the cost of building new game objects all the time, and to allow a new pipeline to build in parallel with rendering the prior pipeline. This worked, but caused flickering effects, due to the unity selection system being stateful and remembering the previously selected/highlighted instance ID. Here, we instead have a single primary proxy used for all rendering, and use alternate objects while setting up a shadow proxy pipeline. Closes: #453
bdunderscore
added a commit
that referenced
this issue
Oct 15, 2024
Previously, we swapped between two proxy renderers in order to minimize the cost of building new game objects all the time, and to allow a new pipeline to build in parallel with rendering the prior pipeline. This worked, but caused flickering effects, due to the unity selection system being stateful and remembering the previously selected/highlighted instance ID. Here, we instead have a single primary proxy used for all rendering, and use alternate objects while setting up a shadow proxy pipeline. Closes: #453
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: