|
POST
|
Hi Roman König sorry for the confusion on this. You are right that normal usage of TileLayers should not be flooding the console with errors. However, one problem with requesting blankTiles is that if a user starts zoomed in, then you might run into a situation where no data is displayed despite there being data in a parent tile. We will be fixing the logic to properly request parent tiles when data for a tile at a given LOD is missing, and also avoid flooding the console with these errors. We're making an internal issue (#22922) to track this, not sure that this will make it in 4.13, but we can definitely address for 4.14.
... View more
09-10-2019
10:15 AM
|
0
|
1
|
2929
|
|
POST
|
One more thing Roman König, if you have a large number of tabs with the API open at the same time, that can result in rendering contexts getting lost and various WebGL errors popping up; the max number of WebGL contexts is unfortunately shared across all tabs in the browser.
... View more
09-10-2019
09:58 AM
|
0
|
2
|
4538
|
|
POST
|
Mohammad Agus Salim I talked two a couple of product engineers and and unfortunately I don't think we have a great workaround for this. For 4.x. though we will think about how we might allow more control over querying to allow apps to make their own trade-offs in terms of visual quality & network performance.
... View more
09-09-2019
04:46 PM
|
0
|
1
|
3393
|
|
POST
|
To give another update on this, we did merge a fix into our 4.13 branch that we think should significantly improve the appearance of basemap text at non-integer pixel ratios (e.g. at 80% zoom or 125% zoom)
... View more
09-09-2019
03:58 PM
|
1
|
0
|
2127
|
|
POST
|
Quick update on this - after some discussion we agreed that these types of errors should not stop rendering. We'll be taking a look at our error handling to see where we can improve. Probably we need to be wrapping more calls in catch blocks that recover and log the error.
... View more
09-06-2019
11:16 AM
|
1
|
0
|
4127
|
|
POST
|
The fix is in our 4.13 development build, I'll let you know as soon as there's something we can share.
... View more
09-06-2019
11:14 AM
|
0
|
0
|
4127
|
|
POST
|
Hmm this is a good idea, I'll discuss and see if there is something we can do on this front.
... View more
09-06-2019
10:09 AM
|
1
|
0
|
4127
|
|
POST
|
Just to let everyone know, we had a little bit of trouble getting the device, but we were finally able to get a computer with an HD 4000 and verify that the workaround we have works on that device as well. We are looking to merge the workaround into our 4.13 dev branch sometime today, and the behavior will basically be as follows: - Run a graphical test at startup that determines whether the driver suffers from this issue - If so, a warning will be logged and our lowp sampler workaround will be applied.
... View more
09-06-2019
10:06 AM
|
1
|
0
|
4392
|
|
POST
|
Hmm we did change the way the hittest works for 4.13, so it might be better next release. There may be some kind of race condition here. Do you know what hardware the affected device is using? (CPU/GPU)
... View more
09-06-2019
10:01 AM
|
0
|
0
|
4538
|
|
POST
|
Hi ntpc iland. Yes we plan on fixing this for 4.13. We added a test for the issue that will run at program start. If it fails, it will log a warning and then apply a fix we have verified on a device with an HD 3000 & on another with an HD 4000.
... View more
09-06-2019
09:29 AM
|
0
|
0
|
824
|
|
POST
|
Sorry Roman König I personally haven't seen this error, but it does look like something WebGL related. Do you know if you can still reproduce this on 4.12? Also what kind of map interaction results in this error? Do you consistently get it just from loading the map, or does it require you to zoom in/out or pan?
... View more
09-05-2019
10:01 AM
|
0
|
5
|
4538
|
|
POST
|
Sorry Mohammad, I don't have too much experience with 3X, but I'll check with someone and see if there is any workaround. I suspect however that there probably won't be one unfortunately.
... View more
09-03-2019
10:57 AM
|
0
|
0
|
3393
|
|
POST
|
Ah, I work on the labeling and fixed this issue in another context, which I think should fix this one as well. Not sure if we plan on exposing a 4.13 pre-release yet, but I'll get back to you on that.
... View more
09-03-2019
10:53 AM
|
2
|
6
|
4127
|
|
POST
|
Hi Dan Lokman! Unfortunately the fix for this didn't quite make it into 4.12, but it will be there for 4.13.
... View more
08-29-2019
09:41 AM
|
1
|
8
|
4127
|
|
POST
|
Hi Mohammad Agus Salim. Is this in the context of trying to reduce network traffic by lowering payload sizes? FeatureLayers (in 4.X) will already make reduced precision quanitized queries when used against services that supported them. We've also since added a new more compressed pbf query format that further reduces payload sizes.
... View more
08-28-2019
04:58 PM
|
0
|
4
|
3393
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-27-2026 10:39 AM | |
| 1 | 07-11-2025 09:45 AM | |
| 2 | 04-25-2025 09:43 AM | |
| 2 | 04-24-2025 03:06 PM | |
| 2 | 03-25-2024 12:13 PM |
| Online Status |
Offline
|
| Date Last Visited |
04-09-2026
09:53 AM
|