Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CESIUM_BASE_URL ignored in 1.42

See original GitHub issue

Setting the CESIUM_BASE_URL like below breaks Cesium (v1.42). It seems to be completely ignored as the console errors show (see picture).

In v1.41 everything works correctly.

window['CESIUM_BASE_URL'] = './path/to/somewhere';

Issue Analytics

State:
Created 6 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

hpinkoscommented, Apr 5, 2018

@mark-lassche there’s a new issue for this open here: #6411 We should have it fixed again for the 1.45 release

0reactions

mark-lasschecommented, Apr 5, 2018

For what it’s worth we’re running into the same issue. Adding trailing slash did not fix the problem, downgrading to 1.43 did resolve the issue for us.

Top Results From Across the Web

CESIUM_BASE_URL ignored in 1.42 · Issue #6225 - GitHub

Setting the CESIUM_BASE_URL like below breaks Cesium (v1.42). It seems to be completely ignored as the console errors show (see picture).

Unable to determine Cesium base URL automatically ...

But the error stating DeveloperError: Unable to determine Cesium base URL automatically, try defining a global variable called CESIUM_BASE_URL ...

Unable to determinecesium base url in React js - CesiumJS

DeveloperError: Unable to determine Cesium base URL automatically, try defining a global variable called CESIUM_BASE_URL.

cesium/CHANGES.md - UNPKG

- `Cesium3DTileset.url` has been deprecated and will be removed in Cesium 1.79. Instead, use `Cesium3DTileset.resource.url` to retrieve the url value.

angular-cesium - npm

Duplication of Cesium base url setting method is caused by a Cesium bug that was introduced in Cesium version 1.42 and should be...