Cesium Ion locations not saving

Hi, I have tried adding various 3d tiles today to cesium ion and there seems to be an issue with saving the location, as you refresh the page after saving and it reverts to the original position?

1 Like

me too

Hi, could we please get assistance. We can’t continue any projects until this is fixed?

Also, there is now an offset from the pivot point?

Hi Clint, TaeHo01, I apologize that you are having trouble with locating the tilesets.

I tried to reproduce issue using some sample data and was not able to.

Are you able to provide an asset id, and any error messages so that Cesium can investigate this issue further?

Hi Mark,

No worries.

This is an ID as an example that won’t save. It was uploading via the 3ds max cesium ion uploader.

2283711

There isn’t an error, it’s just if you go back after locating, it doesn’t save.

Kind Regards,

Clint Motley

Co-Founder / Managing Director

p 0431 461 763

e clint@immersiv.com.au

w www.immersiv.com.au

Title: instagram - Description: instagram iconTitle: linkedin - Description: linkedin icon

Thank you for providing that information. We are still having trouble reproducing this, so I have some more questions for you:

  • What browser and operating system are you using?
  • Are you able to open the developer console and check for any errors in the console?
  • What location are you trying to set? Are you able to post a screenshot or video of the UI before pressing save?

Regards

Hi,

There isn’t an error, it’s just if you go back after locating, it doesn’t save.

I have also been experiencing the same issue lately.

Here are the steps I followed:

  1. Save the obj file as “3D Model (tile as 3D Tiles)”
  2. Press “Adjust Tileset Location”
  3. Enter latitude and longitude
  4. Press “Save”
  5. Reload the page

The latitude and longitude have not been updated while I pressed the “Save” button and “{{object-name}} location saved” was displayed in the upper right corner of the screen as seen in the image below.

What browser and operating system are you using?

Browser: Chrome (version: 117.0.5938.92)
OS: macOS Monterey (version: 12.6.5)

Are you able to open the developer console and check for any errors in the console?

At step 4 (Press “Save”), there are no errors displayed in the console log.
When checking the network tab, I can see the following request, but the status code is 204 No Content.

Request URL: https://api.cesium.com/assets/{{object-id}}/transform
Request Method: PUT

What location are you trying to set?

Longitude: 139.7671
Latitude: 35.6812

Are you able to post a screenshot or video of the UI before pressing save?

I wanted to post a video, but it seems impossible to do so in this forum (My apology if I misunderstand this). Instead, here is the screenshot.

I hope this information helps a bit.

Best regards,

Thank you for that additional information @km1995 . I have added this information and hope this will help our team be able to determine the cause and fix the bug.

Our team has investigated this issue and deployed a fix to production. Please try updating the location again and let us know if you have any issues. Thank you again for reporting this problem.

Hi, I can’t save the location after tiling a point cloud (.las file ) because the request gives a cors error,
“Access to XMLHttpRequest at ‘https://api.cesium.com/assets/2538535/transform’ from origin ‘https://ion.cesium.com’ has been blocked by CORS policy: Method PUT is not allowed by Access-Control-Allow-Methods in preflight response”


Thank you for your help

Hi MattiaTiburzi, welcome to the Cesium community.

It looks like there is some security settings problems when you are trying to the asset location.

If you can provide some additional information that will help us troubleshoot the issue.

  • Can you let us know what browser and OS version you are using you are using?
  • Are you able to successfully locate the asset in another browser?

Thank you very much, I was using Google Chrome on windows 11, I’ve switched to firefox and it works

Glad to hear that it worked in Firefox.

Can you let us know what version of Chrome you are using? We were not able to reproduce this in our initial testing of this issue. Thanks