Latest Contributions by RomanKönig

‎11-08-2019

Hi Matt, thanks for your reply - i posted the DxDiag result of the affected machine

‎11-07-2019

Kimberly McCarty Happens on one (only this one) of our development machines too when using either our own developed application or the attached sample - see attached screenshot. It does not occur when using the JS API 4.12

‎11-07-2019

The parcel in the two screenshots is of different size, so the scale of the two displayed layers is different. I assume the blurry one is displayed in a scale that is not an exact match to a LOD. Therefore it is resized and a bit blurry.

‎10-24-2019

The mentioned application uses the 4.11 API In a newer application (v 4.13) i found "esri/views/support/WebGLRequirements" performing a check and displaying a different message on another machine. Is this a new check performed since 4.12 or 4.13 ?

‎10-24-2019

We are having issues with a single customer machine (until now) when initializing a MapView. The constructor new MapView() throws an error displaying "WebGL not supported. Now we asked the customer to run https://webglreport.com https://webglreport.com/?v=1 displays green whereas https://webglreport.com/?v=2 displays not supported The customer machine has a Nvidia Quadro NVS 440 graphic card and we asked them to install the newest available drivers installed, but this card does not meet the requirements stated at https://developers.arcgis.com/javascript/latest/guide/system-requirements/index.html My question is - is there any possibility to check if the system/graphic card is sufficient prior to initializing and running into errors on initializing or using API objects - something like a Javascript API runSupportTest() method or anything like that?

‎10-11-2019

I can't find any documentation about using WMTS layer with different dimension configurations. And after debugging through the JS API (4.11 in my case) it seems as if dimensions are not supported. WMTSLayer.js and especially wmtsUtils.js parses the capabilitites response and always uses the first <dimension> found if any. So my questions are: Am i right that the dimensions property of WMTS layer capabilities are not supported at the moment? If so, are there any plans on adding support in future releases aof the JS API 4?

‎09-12-2019

Hi Matt, the hardware specs of the affected system are: - OS: MS Windows 10 Pro - CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, 3601 MHz, 4 Kern(e), 8 logische(r) Prozessor(en) - RAM: 16.0 GB - GPU: Intel(R) HD Graphics 630, 1.00 GB Multiple browser tabs opened should not be the case. There's only one browser tab opened with the application using the js api.

‎09-06-2019

Thanks for your reply, Matt. At the Moment we are working with the 4.11 API, so i cannot tell if it also happens on 4.12. The problem occurs on a daily basis, say once whilst developing 7 hours with the API. Until now we couldn't pin it down to any specific action that triggers the problem.We are adding/removing, setting visibility of Layers in a MapView and it happens not only on interacting with the view but e.g. when adding a layer. We'll keep trying to figure out if there is a pattern in occuring this error, just wanted to ask if it is a known problem and anyone else has also seen this.

‎09-05-2019

We are sporadically experiencing WebGL rendering issues on one of our development computers in Google Chrome. The whole screen switches to black for a few seconds and after that the Google Chrome (newest version 76) displays an emtpy map. We are using a 2D MapView, layer types are MapImageLayer, FeatureLayer and VectorTileLayer. We are using JS API 4.11. Until now we couldn't find any relation between the displayed layers and the error occuring. I just wanted to ask if anyone else has experienced something like this and maybe has hints for pinning down the issue. Google Chrome dev tools shows an error: requestAnimationFrame (async) f @ dojo.js:formatted:11387 h @ dojo.js:formatted:11359 l @ dojo.js:formatted:11354 requestAnimationFrame (async) f @ dojo.js:formatted:11387 h @ dojo.js:formatted:11359 l @ dojo.js:formatted:11354 VM1907:103 Uncaught TypeError: Failed to execute 'shaderSource' on 'WebGLRenderingContext': parameter 1 is not of type 'WebGLShader'. at a._loadShader (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:103:238) at a.initialize (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:93:457) at a.bindProgram (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:647:240) at q._drawFill (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:133:20) at q.render (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:127:371) at p._renderFill (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:105:215) at p.renderBucket (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:99:20) at h.doRender (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:73:163) at p.hitTest (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:103:301) at h._hitTest (eval at <anonymous> (eval at <anonymous> (dojo.js:6)), <anonymous>:87:191) a._loadShader @ VM1907:103 a.initialize @ VM1907:93 a.bindProgram @ VM1907:647 q._drawFill @ VM2007:133 q.render @ VM2007:127 p._renderFill @ VM2007:105 p.renderBucket @ VM2007:99 h.doRender @ VM2007:73 p.hitTest @ VM2007:103 h._hitTest @ VM2007:87 After restarting the browser everything works fine again using the same code and layers, so the problem seems not to be directly related to our application.

‎08-28-2019

No. Unfortunately the blankTile parameter is not supported by the API. I filed an ehancement request, but it was closed and stated as "not in product plan".

‎07-30-2019

Yes, Featurelayer samples are working fine, e.g. https://developers.arcgis.com/javascript/latest/sample-code/layers-featurelayer/live/index.html or https://developers.arcgis.com/javascript/latest/sample-code/featurelayerview-query/live/index.html

‎07-29-2019

In our company we have the same problem. 2D Graphics are not displaying on 40% of our machines - all these machines have an Intel 4000 graphic card. However on a 3D Sceneview the same graphics are displayed.

‎07-11-2019

Is there any way to influence the blankTile=true|false URL parameter sent by a TileLayer object requesting map tiles? I could not find anything related in the documentation and i see that all our TileLayer objects are sending false. Want to set this to blankTile=true to avoid 404 errors logged into the browser console and webserver logfiles.

‎06-06-2019

Thanks for your reply - i'll email you a sample with a single feature layer endpoint. And i know that querying all features at once is usually not a goiod idea, but in cases where we know that the layer does not hold thousands of features it would be good to be ably to have influence on how the data is queried.

‎06-05-2019

Is there a way to influence the way a FeatureLayer is queried by the JS API (4.11)? For example we use arcgis online hosted feature layers with only a handful or up to < 100 features. Now when we add this FeatureLayer to a MapView there are numerous (in our sample 6) query requests sent to each FeatureLayer on every scale change. I know this was introduced, as in early versions of the js api 4 all features were queried at once, but it would be nice to have an option to force such a behavior. Am i missing something here?

Online Status	Offline
Date Last Visited	‎11-11-2020 02:25 AM

My Ideas

Latest Contributions by RomanKönig

Re: Basemap Flickering/Flashing 4.13

Re: Basemap Flickering/Flashing 4.13

Re: 4.x javascript api blurry background images

Re: MapView initialization error

MapView initialization error

JS API 4.x - WMTS Layer Dimensions

Re: WebGL rendering errors in Google Chrome

Re: WebGL rendering errors in Google Chrome

WebGL rendering errors in Google Chrome

Re: TileLayer url-parameter blankTile

Re: Sketch and measurement graphics not showing up after 4.12 update

Re: Sketch and measurement graphics not showing up after 4.12 update

TileLayer url-parameter blankTile

Re: FeatureLayer query options

FeatureLayer query options

Re: Detect change in zoom when complete

Disable navigation "roll"-effect

Re: TileLayer url-parameter blankTile

Re: Disable navigation "roll"-effect

Re: Sketch and measurement graphics not showing up...