You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Projects not necessarily need access to the embedded asset lists. In our case, we only load assets via kha.Assset.loadFromPath() so everything in these lists is superfluous, but these 1500 assets increase the generated kha.js filesize from 1.2mb to 2.6mb in html5 builds, and won't even compile in windows debug builds without workarounds, see #133.
So the new option would convert assets as usual, but wouldn't add fields to the internal kha.Assets lists.
This could ideally be set for each prj.addAssets() call in khafile.js. In our case, i'd only exclude the first 2 calls from the following example.
Projects not necessarily need access to the embedded asset lists. In our case, we only load assets via kha.Assset.loadFromPath() so everything in these lists is superfluous, but these 1500 assets increase the generated
kha.js
filesize from1.2mb
to2.6mb
in html5 builds, and won't even compile in windows debug builds without workarounds, see #133.So the new option would convert assets as usual, but wouldn't add fields to the internal kha.Assets lists.
This could ideally be set for each
prj.addAssets()
call in khafile.js. In our case, i'd only exclude the first 2 calls from the following example.The text was updated successfully, but these errors were encountered: