@Evak
I wonder what efficient binary data you exactly mean. The only case i see were this really is an issue is when you're dealing with online 3d content (no webplugin for blitzmax) or really big models data (like for cad visualisation for instance) and due to this want the smallest possible filesizes but in case 1) the whole webplayer content is compressed (also streamed media) and in case 2) this is a totally different area were you won't find any engines like a Max3D, so in both cases no issues.
The much bigger problem you're facing quite often is having a format which is spported by modellers you or the people you're working together can use and not if your final meshsize is 12kb or maybe 14kb. And if you're really caring about such things then you better use some generative algorithms for your meshes instead.
I wonder what efficient binary data you exactly mean. The only case i see were this really is an issue is when you're dealing with online 3d content (no webplugin for blitzmax) or really big models data (like for cad visualisation for instance) and due to this want the smallest possible filesizes but in case 1) the whole webplayer content is compressed (also streamed media) and in case 2) this is a totally different area were you won't find any engines like a Max3D, so in both cases no issues.
The much bigger problem you're facing quite often is having a format which is spported by modellers you or the people you're working together can use and not if your final meshsize is 12kb or maybe 14kb. And if you're really caring about such things then you better use some generative algorithms for your meshes instead.