Azure is down so *.babylonjs.com is too

Please watch this post. I will comment here when Azure is back online

Really sorry for the inconvenience.

4 Likes

A good reminder to use local lib files :smiling_face_with_sunglasses:

4 Likes

Can’t agree more!

1 Like

I thought I had everything locally but it seems something is pulling https://cdn.babylonjs.com/glslang/glslang.js in my codebase for some reason :headstone: :scream:

Good way to test :smiley:

Yeah this could be a weekly event!

2 Likes
scene.createDefaultEnvironment() 

createDefaultEnvironment() also wont work :sweat_smile: guess I should not be using it as much as I do.

For anyone blocked right now, this section from the docs might be useful :smiley:

Here’s the quickest method:


1. Downloading the resources and deploy them on your own CDN

This option is the best for you, as you are in full control of the resources. To get the resources in the CDN structure you can download a Github release at Github Babylon.js releases.

After downloading the cdn snapshot zip file and deploying it on your server, change the base URL to the base URL of the resources deployed.

2. Changing base URL for external resources

To change the base URL for all resources loaded by Babylon, use the static member of tools:

BABYLON.Tools.CDNBaseUrl = "https://my.wonderfull.server";

Any resources loaded in our core library will be loaded from this URL instead of https://cdn.babylonjs.com (or https://assets.babylonjs.com). The structure needs to remain the structure of our CDN.

2 Likes

Going online this one is better https://www.jsdelivr.com/ than BabylonJS

No thank you lol :smiley:

1 Like

this could help: Asset missing from BabylonJS CDN breaks scene.createDefaultEnvironment() - #5 by Deltakosh

Ok folks it seems to start to get back online! Please report :slight_smile:

I’ve got a notification for cdn.babylonjs.com/babylon.ktx2Decoder.js not being available. I’ve asked previously, but have never managed to actually get it to deploy locally, don’t remember the reason. Does anyone know whether this has become more straightforward in the meantime?

@alexchuber any reason why it will not work from a local reference? Maybe CORS ?

@rassie It could help if you have a repro somewhere

It’s hardcoded somewhere to use CDN by default. Replacing that is somewhat elaborate.

I don’t think it is hardcoded as mentioned on that thread:

BABYLON.KhronosTextureContainer2.URLConfig is what you want to update

Well, yes and no. We are firmly in ES6 land, so it’s not as easy. I’ve got my best AI working on it as we speak :slight_smile:

Lol! Let me ping @ryantrem to see if he can help as he is our ES6 mastermind

AFAIK, the only way to avoid fetching the URLConfig.jsDecoderModule (which defaults to babylonjs.ktx2decoder.js) is to use a worker. But that doesn’t sound right either :confused:
Let’s see what others say, and I’ll look into this in the meantime.

1 Like