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

Ground polygon regression in 1.67 #8664

Closed
lilleyse opened this issue Mar 5, 2020 · 4 comments · Fixed by #8694
Closed

Ground polygon regression in 1.67 #8664

lilleyse opened this issue Mar 5, 2020 · 4 comments · Fixed by #8694

Comments

@lilleyse
Copy link
Contributor

lilleyse commented Mar 5, 2020

Ground polygons are getting clipped strangely in 1.67. It happens with viewer.scene.logarithmicDepthBuffer = false or true

Git bisect points to #8630. @mramato any ideas?

Sandcastle - zoom towards the triangles and look at them from a horizon view.

1.66

2

1.67

1

@lilleyse lilleyse changed the title Polygon regression in 1.67 Ground polygon regression in 1.67 Mar 5, 2020
@mramato
Copy link
Contributor

mramato commented Mar 5, 2020

Thanks for catching this. I'll look into it ASAP. Step one is figuring out if it's all ground primitives or just entity ground primitives, that should narrow down the issue pretty quick.

@mramato
Copy link
Contributor

mramato commented Mar 5, 2020

I can reproduce this, but I have no idea why it's happening yet. It only occurs with the PerInstanceColorAppearance not MaterialAppearance.

@mramato
Copy link
Contributor

mramato commented Mar 5, 2020

@lilleyse as far as I can tell, this is a bug in using PerInstanceColors with GroundPrimitive, but I need to port your example to the Primitive API directly to be sure.

My guess is that it's always been a problem and my change just exposes it because we are attempting to use the feature now instead of batching colors into separate primitives

Any thoughts of where we should be looking?

@lilleyse
Copy link
Contributor Author

lilleyse commented Mar 5, 2020

My guess is that it's always been a problem and my change just exposes it because we are attempting to use the feature now instead of batching colors into separate primitives

Hm that is possible...

@likangning93 has a better grasp of the system than me. Thoughts @likangning93?

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

Successfully merging a pull request may close this issue.

2 participants