Latest Contributions by AndreasUlmer

‎05-08-2025

Thanks for reporting. Yes this looks like a bug. Cannot promise but we hopefully are able to fix this with the next release. Until then I'd say a request interceptor is your best workaround option.

‎10-07-2024

Can be done using axis https://developers.arcgis.com/javascript/latest/api-reference/esri-renderers-visualVariables-SizeVariable.html#axis renderer.visualVariables = [ new SizeVariable({ axis: "width", field: "width" }), //or new SizeVariable({ axis: "width", valueExpression: "$feature.width*2" }), new SizeVariable({ axis: "height", valueExpression: "1" }) ];

‎08-14-2024

We identified the problem of the broken drawing shown in the screenshot (the funky colorful triangles) when applying &disableFeatures=im-shading SceneLayers (which includes Integrated Mesh Layer) are cached in the browser's indexedDB for performance reasons a slightly different version of integrated mesh data gets cached when the url parameter &disableFeatures=im-shading is set loading a non-matching version from the indexedDB cache causes the broken rendering The fix/workaround: when switching between im-shading disabled and enabled using the url parameter, the browser's indexedDB cache must manually be deleted Clear SceneLayer indexedDB in Chrome (similar in other browsers): open developer tools navigate to Application tab under Storage / IndexedDB, select esri-scenelayer-cache click Delete database Apologies for the inconvenience on this, we hope this workaround is sufficient for you for the moment. And as stated earlier, we are revisiting this behavior for the upcoming 4.31 release. ----- I marked it solved by accident. FYI, I marked it as unsolved again for now.

‎08-13-2024

Update: we can now reproduce the broken drawing as seen in the screenshot, and are looking into it.

‎08-13-2024

@Shannon Is the screenshot what you get after applying &disableFeatures=im-shading? That should not happen of course. Is there a chance you could share the problematic scene with us (the url), with an instruction how to exactly get to the problem? It's hard to say more without seeing the actual problem. In case you don't want to share the url publicly you can also DM (direct message) me. Also, confused why you marked the case as solved. Was this done by accident?

‎08-12-2024

In ArcGIS Online SceneViewer, you can add this url parameter to disable the new integrated mesh shading: &disableFeatures=im-shading This should get you back to the pre-4.30 state. Does this work for you as a workaround for the moment? And FYI, we are reconsidering this behavior for 4.31, but no decisions yet.

‎08-12-2024

@ShannonAK, @ArthurJensen: are you using SceneViewer on ArcGIS Online? Or a custom application built with ArcGIS Maps SDK for Javascript?

‎08-08-2024

With the 4.30 release, we "Added shading to IntegratedMesh3DTilesLayer and IntegratedMeshLayer" (https://developers.arcgis.com/javascript/latest/release-notes/#bug-fixes-and-enhancements). In case your imagery is an integrated mesh this likely explains the visual difference. In this context, surface normals (the local direction of the surface) on integrated mesh are used to shade (apply lighting to) the surface. This helps to improve realism under specific lighting conditions and integrate IntegratedMesh data better into the scene (since most scene elements are being shaded this way). Shading also helps to understand the shape of the integrated mesh better, but at the same time might expose issues in the data set. In the case at hand it seems that the data has incorrect normals at tile borders (normals not properly interpolated across borders), which get more visible now due to shading.

‎04-22-2024

Many thanks for looking at this Andreas and your useful advice. I'll have a go at implementing your suggestion. Great! Let us know if this works for you. Do you know when the use of the fov function with goTo will be available please ? Added issue to our roadmap, but can't give a concrete date when this will be tackled I'm afraid.

‎04-19-2024

Suggested workaround: apply new fov before view.goTo() (ℹ Camera needs to be cloned to apply modifications: https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#camera) document.getElementById("gotoVP2_53.5deg").addEventListener("click", () => { const cameraCloned = view.camera.clone(); cameraCloned.fov = 53.3; view.camera = cameraCloned; view.goTo( ... this will instantly (without animation) change camera fov to the new desired setting then the camera will transition smoothly to the new viewpoint Unfortunately there is no way atm to smoothly transition between fovs. This is something we consider to improve in a future release. Is this workaround acceptable for you?

‎03-21-2024

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.

‎03-21-2024

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)

‎11-23-2023

Identified as bug / regression in 3D SceneView (missing antialiasing). Fixed, lines are smooth again. Will be shipped with next ArcGIS Online release, Feb 2024.

‎11-17-2023

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?

‎11-06-2023

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.

Online Status	Offline
Date Last Visited	‎10-27-2025 07:53 AM

My Ideas

Latest Contributions by AndreasUlmer

Re: customParameters doesn't work for all requests on BuildingSceneLayer

Re: Set PathSymbol3dLayer width only (not height) using visualVariables

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Using fov with Camera settings

Re: Using fov with Camera settings

Re: How to change the Callout of a FeatureLayer that is already on the SceneView

Re: Features flickering in 3D view when FeatureFilter present

Re: How to smooth polygon lines?

Re: Rendering Draco Compressed GLTF models

Re: Use rgb attributes to color features in 3D

Re: customParameters doesn't work for all requests...

Re: Artifacts in scene layer

Re: Artifacts in scene layer

Re: Using fov with Camera settings

Re: How to change the Callout of a FeatureLayer th...