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

Cinemachine & Register Height Input Weird Culling #1006

Open
HrafnkellTorri opened this issue Apr 11, 2022 · 2 comments
Open

Cinemachine & Register Height Input Weird Culling #1006

HrafnkellTorri opened this issue Apr 11, 2022 · 2 comments

Comments

@HrafnkellTorri
Copy link

Describe the bug
A clear and concise description of what the bug is.
When using Crest Register Height Input with cinemachine there is a weird culling issue when looking horizontally like is seen on the pictures.

Screenshots / video
These are very helpful to understand and diagnose issues.
unknown
unknown

Log
What is in the editor log? Clear before running and then provide any errors/warnings that appear. The log frequently provides the key hints.
Nothing.

Versions
Which render pipeline (built-in/LWRP/HDRP)? Which version of LWRP/HDRP? Which version of unity (including minor, i.e. 2019.1.0f2)?
4.15 in URP

To Reproduce
How can the developers reproduce this bug? Are you able to reproduce the issue in the example content/scenes?
Please include steps to reproduce the behaviour, with the example content ideally so we can follow the steps on our side.
Cinemachine camera looking at a height input

Platform

  • Editor or standalone?
  • Platform (win/mac/...)
    editor and standalone, win

Hardware
What hardware are you seeing the issue on? GPU model is particularly useful.
Gtx2080

Additional context
Add any other context about the problem here.
images of the bug

@HrafnkellTorri
Copy link
Author

Strangely enabling or disabling Create Clip Surface Data for example fixes this during runtime.

@daleeidd
Copy link
Collaborator

This one is puzzling. Is this still a problem?

Strangely enabling or disabling Create Clip Surface Data for example fixes this during runtime.

I think that is because the OR gets rebuilt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants