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
We are using IconLayer to represent live data with auto packing atlas (we generate a hundred different icons depending on the data we receive). Everytime we receive an event with updated data, we set props with an updated layer and we get the changes represented in the map.
We have noticed that sometimes icons stop rendering properly and instead of showing an icon, it shows nothing (completely transparent). However, if I click where the icon is suposed to be I get the event. (we haven't found a reproducible pattern, but it happens frequently).
We don't get any error on the console, even if we set log level to 3 or higher.
It happened something similar with black squares instead of disapering icons in the past: #3875. I was told it happened because I exceded the texture size, and indeed that was the problem. For this reason I reduced the size of the icons, so they fit into the texture and everything was working with version 7.3.6. However, since I upgraded to 8.0.6. I'm getting this disapering icons problem. I don't know if it is related with my previous issue, but it seems a regression from version 7 to 8.
Repro Steps
It is reproducible in any browser and OS.
First time data is drawn properly, but after navigating through the map zooming in and out or changing bounds (which causes generating new icons), it eventually stops drawing icons without leaving any crash log.
Notice that when zoom is changed or bounds are changed, data is updated.
We update the layer info, using set props like this:
The amount of data entries may change depending on the bounds of the map in the screen and the events we receive, so we don't always have the same length of data (pointing this out, just in case it is relevant).
Environment (please complete the following information):
Framework Version: deck.gl 8.0.6
Browser Version: could reproduce it in Safari, Chrome and Firefox
OS: could reproduce it on MacOS and Windows
Logs
No error logs are generated
The text was updated successfully, but these errors were encountered:
@xintongxia I think this is related to the y-flipping in image loader. When you copy the old texture to a new one it might not be positioned correctly.
Description
We are using IconLayer to represent live data with auto packing atlas (we generate a hundred different icons depending on the data we receive). Everytime we receive an event with updated data, we set props with an updated layer and we get the changes represented in the map.
We have noticed that sometimes icons stop rendering properly and instead of showing an icon, it shows nothing (completely transparent). However, if I click where the icon is suposed to be I get the event. (we haven't found a reproducible pattern, but it happens frequently).
We don't get any error on the console, even if we set log level to 3 or higher.
It happened something similar with black squares instead of disapering icons in the past: #3875. I was told it happened because I exceded the texture size, and indeed that was the problem. For this reason I reduced the size of the icons, so they fit into the texture and everything was working with version 7.3.6. However, since I upgraded to 8.0.6. I'm getting this disapering icons problem. I don't know if it is related with my previous issue, but it seems a regression from version 7 to 8.
Repro Steps
It is reproducible in any browser and OS.
First time data is drawn properly, but after navigating through the map zooming in and out or changing bounds (which causes generating new icons), it eventually stops drawing icons without leaving any crash log.
Notice that when zoom is changed or bounds are changed, data is updated.
We update the layer info, using set props like this:
this.overlay.setProps({ layers: [ clustersLayer.clone({ data: clustersData }) ]});
This is how we generated the IconLayer:
The amount of data entries may change depending on the bounds of the map in the screen and the events we receive, so we don't always have the same length of data (pointing this out, just in case it is relevant).
Environment (please complete the following information):
Logs
No error logs are generated
The text was updated successfully, but these errors were encountered: