Pack / Serialize the Environment (.env) During Export to BabylonJS .babylon File

Feature requests
, , ,
1

Please make it possible to pack / serialize the Skybox environment with all properties within .babylon files during export.

2

it should be the case if you use an environmentTexture. Can you share a repro where it is not ?

3

Just noticed the Pack textures within .babylon files - #22 by staub

For clarity, env should be embedded and not referenced in the .babylon file.

1 Like
4

Heya @sebavan

Thanks for looking into this!

Correct. I’d like to have the environment embedded into the .babylon file upon export so no external sources have to be used. I love the richness it gives the scene, but with the unique use case I have, I can’t reference the .env externally… and I’ve tried a million things to try to trick it.

Here’s an example

https://raw.githubusercontent.com/invertedNormal81/serve/main/envExample.babylon

If I export to .babylon with the URL refs, open it up and remove the refs, the environment disappears… suggesting it is not packed.

If I export to .babylon with the .env loaded from a local file on my laptop, move the .env file to another folder to test and open the babylon file the scene doesn’t load at all… suggesting the .env data was not packed and is hopelessly looking for the file.

I’m hoping it’s not too much effort to get this implemented.

Thanks again!