Latest Contributions by AndreasUlmer

Thanks for reporting, this seems to be a bug. Sent to dev team for further investigation. I did a few tests but at the moment I can't provide a good workaround. Use "on-the-ground" of course if that's an option. Or clone/recreate the whole layer (with new callout config in constructor), but clearly not great either depending on your use case. Will keep you posted if more intel comes up. ... View more

Hmm, really hard to say what causes this without an actual reproduction case. Could you still share the codepen (even if it doesn't reproduce the problem), so we have a starter what to look? (We specifically need to know what data and renderer / symbology is used, and how featureFilter is applied) Also, can you check the following: Can you check if it also happens with 4.29? Can you confirm the flicker does not happen when FeatureFilter is not applied?    As said, hard to say but from the current recording I would say: it's not z-fighting (happens only with coplanar faces) FeatureLayer, GeoJSON, OGCFeature should not make a difference (the internal rendering is the same on those)   ... View more

Draco compression is currently not supported for 3D Symbol resources. This is in our backlog but not yet planned for a release. Basis Universal compressed textures are supported though. If the models contain large textures, maybe this could be worthwhile to reduce size? ... View more

First answer from the linked post also applies here: Use Color VisualVariables. This concept works for both CIMSymbols and non-CIM 3D symbols. See samples: * https://developers.arcgis.com/javascript/latest/sample-code/visualization-multivariate-3d/ * https://developers.arcgis.com/javascript/latest/sample-code/layers-scenelayer-edges/ Hope this helps. ... View more

> We've seen performance benefits from using 512x512 tile sizes over 256x256 on high-res or large screens. Oh that's interesting! Would it be possible to share some more specific details (either here or DM if you prefer)? What particular improvements? Improved FPS? Faster loading of data? Definitely something we'd like to hear more about. I assume a 512 tile cover the same area as 4 256 tiles (and not the same area at 4x resolution)? AFAICT this reduces the number of network requests to 1/4, which could indeed help with certain aspects of performance. The whole terrain is then split less granular (again 1/4 tiles), I wonder if this comes with any downsides. > If supporting mixed tile sizes (even limited to 256 and 512) in 3D is complex Mixing arbitrary tiling schemes is tough: Tiling is at the core of the terrain logic and controls a lot of both internal and user-facing behavior. Mixing 256 and 512 would definitely be less tricky but still not a freebie. ... View more

Assumption confirmed: Data is the same in older versions (e.g. 10.6.1): The same "steps" can be seen on the grid when basemap is disabled. In older versions those steps were not or barely noticeable due to the flat shading where surface normals were ignored. With the new terrain shading (think dynamic relief) these terrain details become visible. So the problem lies in the data / the DEM, or the way it was created. I'm not an expert on DEMs, I would say though that the data resolution is lower than the resolution of the DEM, and that could create these step-like artefacts. I'm also not clear if there are additional interpolation options which allow to control this behavior. I would try to create the DEM with a lower resolution, which matches the resolution of the source data. For more detailed help I recommend to ask again in the ArcGIS Pro section, or whichever product is used to create the DEM. ... View more

Thanks Maxime We were able to read the service and reproduce the reported behavior. We'll do some more investigations and get back to you. ... View more

Thanks for the service link. Unfortunately it is not working for me. https://cartes.ville.sherbrooke.qc.ca/arcgis/rest/services/DEM_3857/ImageServer Browser reports "connection has timed out" / "took too long to respond". * Can you doublecheck the url, and check if it still works for you? * Confirm that it is indeed publicly available, not limited to your intranet, and no credentials are needed to access it?   ... View more

ArcGIS Online enabled terrain shading in a recent release: https://developers.arcgis.com/javascript/latest/4.26/#improved-terrain 10.6.1 did not have terrain shading yet. Our assumption is that the terrain data is actually the same, i.e. already not smooth 10.6.1, but the steps are not visible without terrain shading. To doublecheck this assumption we'd need some more info: * is this a custom DEM? Or the default world elevation service provided by Esri? * if custom, is it possible to share a url to the layer / the service? * if not custom: please share the exact location where the problem occurs so we can investigate further. You can do this in SceneViewer Share Dialog, Share link, which will include viewpoint in the url. ... View more

Hi Despite the (impressive) analysis we unfortunately can't see an obvious culprit. We would need to have access to the service in question to do deeper performance investigations. Hence the question: is it possible to share the service with us? If so please DM me for details. ... View more

Did a test of this scenario now, and can confirm it works for me. * If elevation comes from z-values: use Arcade expression Geometry($feature).z * factor * if elevation comes from attributes: use Arcade expression $feature.attributename * factor In my test in both cases the published webscene has the correct expression set, and point features display on the expected exaggerated elevation in Scene Viewer (same elevation as in Pro). See also: https://developers.arcgis.com/javascript/latest/arcade/#z-values ---- In case this still does not work for you we'd need to see the problematic webscene, and the version of Pro used to track this down further.   ... View more