Latest Contributions by AndyGup

Based on the troubleshooting so far, this appears more likely to be related to a regression in Chrome on this specific hardware platform than to the SDK itself. We haven’t been able to reproduce it internally because we don't currently have access to your exact hardware, so we can’t fully validate the behavior on our side. Since WebGL2 issues can be browser/GPU/platform-specific, it may be worthwhile to open a Chromium issue as a next step (https://issues.chromium.org/). If you do, feel free to share the link here and we’ll continue to help where we can. ... View more

Thanks, the hardware info helps. Can you update your Mesa driver and try again? You are currently running Mesa 24.2.8 and the latest is 26.0.5. Sometimes even minor updates can fix rendering issues on V3D. ... View more

You're right, after double checking it's not a grid issue. It's also not a bug in the JS SDK. You will just need to set the areaOfInterestExtent in ProjectOptions*, or you can also set geographicTransformation. Once you do that you should get a result that is much more accurate. My test app is showing a difference of 0.0035 meters between your expected result and the projectOperator, as well as geometryService.project(): projectOperator result 31255 => 3857 1556587.0407006142 6132161.568937744 projectOperator result distance to expected EPSG:3857 point (meters) 0.0035446469419314845 const targetSR = new SpatialReference({ "wkid": 3857 }); const point = new Point({ "x": 48402, "y": 335041, "spatialReference": { "wkid": 31255 } }); // Austria const testExtent = new Extent({ "xmin": -292428.21, "ymin": 140068.94, "xmax": 295094.41, "ymax": 438461.34, "spatialReference": { "wkid": 31255 } }); let projected = projectOperator.execute(point, targetSR, { areaOfInterestExtent: testExtent, // be sure to set this });   ... View more

> Is ArcGIS JS missing the correct transformation grid for this CRS? @QuentinDLV this is likely because the JS SDK projectOperator currently doesn't have any support for grid transforms, so you are only getting a best-effort result through equation-based geographic transformations. See the known limitations section in the doc, here. Have you tried testing with geometryService? ... View more

@Alamos can you check to see if the issue is reproducible in another browser like Firefox? If it's not reproducible then this is likely to be an internal bug in Chrome since the ArcGIS JS SDK version stayed the same and simply upgrading browser versions causes the error. In that case, you'll need to file an issue on new.crbug.com. Make sure you have the latest OS and firmware drivers installed. You can also try comparison testing with hardware acceleration disabled: Settings > System > Use graphics acceleration when available. ... View more

@Alamos  with Chrome 146, can you see the graphics in this sample? https://developers.arcgis.com/javascript/latest/sample-code/intro-graphics/.  ... View more

@ChristopheSutergotcha. How are your non-new instance geometries being created when they have the z-problem? If converting them to JSON is correcting the problem then it's possible there is some sort of issue with the non-JSON geometry instances. If you continue to have issues, or run into convert/revert performance issues, then I'd encourage you to open a support ticket so we can take a deeper look. ... View more

@ChristopheSuter can you provide a repro sample?  ... View more

It's hard to tell without a repro example. These errors can often show up when using local assets that haven't been configured. Take a look at this doc and see if any of the info helps: https://developers.arcgis.com/javascript/latest/working-with-assets/#copy-and-point-to-local-assets, for example be sure to configure the assets path. For more info on minimal repro apps: https://developers.arcgis.com/javascript/latest/troubleshooting/#minimal-reproducible-application.  ... View more

@LefterisKoumis good catch on the documentation bug in the tutorial. We'll get it changed from unit(s) to unit, which is the correct parameter. It's documented in both the geodeticAreaOperator and geodeticLengthOperator under options.. ... View more

Hi @AFackler_NAPSG since you are getting a native firmware error message directly from the AMD driver, this is most likely a hardware problem, and not an issue with the ArcGIS JavaScript SDK which powers Experience Builder, Dashboards, Map Viewer, etc. You mentioned thinking the same thing in your comment here. Based on your descriptions in this particular case, the browser's WebGL2 support error message is being caused by the underlying laptop hardware failure. ... View more

@JoelBennett the 4.33 downloads have been updated. ... View more

@NiklasKöhn  thanks for the feedback. Correct, there's currently no replacement for pointFromDistance(). We are looking into options for that. ... View more