Loadout support #66
Loadout support #66
Conversation
| const paintConfig = createPaintConfig(player.isOrange) | ||
| body = new BodyModel(Body.DEFAULT, Decal.NONE, paintConfig, manager.config) | ||
| wheels = new WheelsModel(Wheel.DEFAULT, paintConfig, manager.config) | ||
| await Promise.all([body.load(), wheels.load()]) |
There was a problem hiding this comment.
Does your library handle caching the body and wheel loads?
There was a problem hiding this comment.
The lib itself doesn't handle caching, but I've enabled three's internal cache here:
Although since this only caches the raw downloaded assets, they do still need to be processed. If you want to speed up processing, there are also smaller textures available that have 4x less pixels.
There was a problem hiding this comment.
Three's cache is fine for handling preexisting assets being added to a scene, but this might still make the request to download these models N times over assuming the browser isn't smart about cache. On a mobile connection, another 30Mb is another 30 seconds.
There was a problem hiding this comment.
Three's FileLoader is smart enough to not load duplicate assets https://github.com/mrdoob/three.js/blob/master/src/loaders/FileLoader.js#L48
E.g. if you enable default loadouts and check the requests in the dev console, there is only one request for the octane, while normally the browser would show multiple requests but indicate that the subsequent ones are fetched from cache.
|
I am considering making some big changes to the model files. Setting this to WIP |
# Conflicts: # package-lock.json # package.json # src/loaders/scenes/GameFieldAssets.ts
Loads car models from rocket-loadout.com
Also fixes #45