You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a custom layer and inserting at any position (using insertLayer at index 0 instead of addLayer) results in a change in how other layers are rendered. I've narrowed it down to the custom layer changing what's bound at the first bind index and context.bindGlobalUniformBuffers not being called after the custom layer is done rendering.
In some situations, depending on what gets bound to index 0, the app might also crash.
To Reproduce
Modify "MBXViewController.mm:1754` to the following
Describe the bug
Using a custom layer and inserting at any position (using
insertLayer
at index 0 instead ofaddLayer
) results in a change in how other layers are rendered. I've narrowed it down to the custom layer changing what's bound at the first bind index andcontext.bindGlobalUniformBuffers
not being called after the custom layer is done rendering.In some situations, depending on what gets bound to index 0, the app might also crash.
To Reproduce
CustomStyleLayerExample
using the metal rendererAdd Custom Triangle Layer (Metal)
Expected behavior
Nothing should be different and the triangle doesn't show because it gets overdrawn by the layers above it.
Screenshots
Image of map without anything changed
Image of map after selecting the custom layer
Expected Output
Platform information (please complete the following information):
Additional context
The issue was solved by re-binding the global UBOs at the end of the custom layer tweaker in this PR.
The text was updated successfully, but these errors were encountered: