-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
using reactmap layers still generates 2 canvases and fails to render properly #2432
Comments
Can you confirm that you're using |
my package.json has: my whole package.json:
|
What is your |
It is a styled-component div. Additionally, all the stuff that is the children of StaticMap has no effect on the result. |
Nothing immediately jumps out at me. Do you see any console errors? Can you check if |
I get no console errors and it definitely calls |
This one I actually know why. Mapbox's custom layer implementation does not support anti-aliasing: mapbox/mapbox-gl-js#7543 Looks like you're not rendering anything 3d. You can try this trick:
|
Hmm, that doesn't seem to help. still jagged and no transparency. The iconAtlas is a png with transparency.
|
I agree. I'd suggest you chime in on the Mapbox issue, it may help them prioritize a fix. |
I am attempting to use the new reactmap integration. I am passing the
gl
context object to the StaticMap but the rendering appears to be messed up. What seems to happening is that Deck.GL is still rendering to its own context and theStaticMap
, I assume is rendering to the react-map context. However, I can only see the StaticMap while panning. When I stop panning it starts rendering the Deck.GL layers, except it does not render alpha.Here are a couple of screen shots:
This is what the Deck.gl layers output:
The background is a png, the white jagged stuff markers are the layers.
When I start panning I get the actual map that seems intact.
These things should be overlayed and have alpha.
Here are the relevant parts of the code:
This works fine if I don't try to mix the contexts, but this is some weird behavior.
The text was updated successfully, but these errors were encountered: