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

Picking + colorize can break when 3DTilesInspector overlay is in the way #9352

Open
ptrgags opened this issue Jan 29, 2021 · 0 comments
Open

Comments

@ptrgags
Copy link
Contributor

ptrgags commented Jan 29, 2021

Sandcastle example: Any sandcastle with 3D tiles picking + 3D Tiles Inspector. For example, [https://sandcastle.cesium.com/?src=3D%20Tiles%20Formats.html](this built-in-one)

Browser: Google Chrome

Operating System: Kubuntu 18.04

Steps to reproduce:

  1. Zoom in on one of the buildings so that it's partially under the inspector
  2. pick the building, but then move the cursor off the building onto the inspector. Like this:
    image
  3. now while never letting the mouse leave the inspector, turn on colorize
  4. now move the mouse back onto the picked building. It loses its color (in the second screenshot, the building should be colorized purple but here it stays the default orange)
    image (9)

I presume there's some mouse handler that isn't firing because the inspector is in the way, and this leads to an incorrect order of object creation/destruction.

Also in some rare cases the renderer can crash with an error about using an object that has been destroy()ed. Though I can't consistently reproduce this part.

I'm wondering if this applies to other debug settings like wireframes or bounding volumes. I'll check this now.

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