Latest Contributions by mgeorge

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

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

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

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

Hmm this is a good idea, I'll discuss and see if there is something we can do on this front.  ... View more

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

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

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

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

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

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

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

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

Hi Matthew Barr‌, basically it's as Robert Scheitlin, GISP‌ has said. For more information see https://community.esri.com/thread/237519-sketch-and-measurement-graphics-not-showing-up-after-412-update. We are currently tracking this issue and working on a possible workaround for drivers that cannot be fixed. ... View more

Hi Denis Pokotylyuk‌, I can't give any promises, but we are currently working on this and want to have clustering in some form by 4.14 (I.e., at feature parity with 3x). There have been some exciting server/service advancements that we want to leverage in 4.x where we can. In fact, I just got out of a meeting on this very topic. By the way, if there's anything new you'd like to see in terms of clustering, please let us know! ... View more