I’ve been trying to load a .babylon file which is approximately 300mb file and it loads and downloads everytime rather than coming from browser cache. What should I do to achieve it?
Each browser handles the individual file cache differently, 300MB is way too big to consider. I would bring the maximum file size to 80MB, or 50MB may be better. It’s not just an upper limit, there are other conditions. You may be able to improve the age by sever/content type configuration but I wouldn’t worry too much about this.
You will make better use of browser cache and asynchronous loading of assets, if you separate the assets into multiple files. You can use AssetManager and AssetContainer to your advantage.
The way to go is service workers here
How do I use the AssetManager you are talking about? Say suppose i have an environment, the buildings surrounding it and a main building inside which i perform few actions etc. all as one file, i need to seperate these individually so as to load them from cache ?
This can help Babylon.js docs
When I use the asset manager, i need to position the loaded assets in place right? Only then it will look same as the combined model!
Basically i have built an environment along with its surroundings using blender! and when i export them as glb/babylon it does not look similar to how it was in the blender. Do i need to enble any option for it to render properly?
This is a really broad question and can have tons of reasons. A repro would be great.
Are you speaking position, lighting, material, animations… ???
Yes everything is packed into one model as a .babylon file created in blender
@sebavan was asking what doesn’t match. What are the differences between the model on babylon.js scene and the model displayed in Blender?
Oops sorry, my bad! Yes the lightings mainly doesn’t match properly with the model created. It looks good in blender but thats not the case when rendering using babylon in web
Without a repro, it will be tough to help you:(
you can save the 3d model into indexed DB, and load from indexed DB.
for chrome and safi, indexDB record size support greater than 300M.
for firefox, less than 267M.