I think there are some more things I would like to add at some point, as I said before, specifying the tea key for publishing and loading would be nice. Also, I'm not entirely sure I've done this, but I might: It might be a good idea at some point to check whether multiple packages do actually work. They're not needed in some games, but if you have a couple of smaller packages, you could more easily provide updates without having to replace _all_ the data either by layering packages on top, or just replacing older packages for newer ones.

The packing system is normally finished ! It just need some testing, specially on Linux.

cheers

I had a look at what you did to add the mesh files and yes, I think that's much cleaner

I unfortunately can't do anything at lunch as some recruiter is going to call, and then I want to quickly try to export, import, load etc stuff, maybe give you some pretty things for the showcase courtesy of my friend Umar Using some more of his existing work to make sure I have an art pipeline I understand

I finished the bin mesh publishing, I tested on mac and windows only,
and now the mac version put everything in the app.

There was some problem with the bin mesh :
- The anim data ref was not put to NULL when calling mesh->clean() so as we was re-using it, the mesh bin export was accessing removed refs.
- I forgot something in the anim mesh bin loader, when reading the animation keys (I forgot to init the key type... oups...).

... I spend some hours yesterday to find out

I removed writing to package, I don't think it is necessary, and it was a bit confusing. It's better to just create temp files manually and add the file to the package, I added an entityName argument to it.

Normally it is working, but we should check on linux to be sure.
Only thing remaining are the level files... I'll try this week if I can...

And yeah, I think I made it about 10MB, which is far too big, but I'm not entirely sure what the best idea for a dynamic size buffer would be when we are expecting to keep writing to it.

I'm starting checking tonight, I'll try to give a review tomorrow or late in the night,
good evening,

Anaël.

Turns out, for whatever reason, I didn't put a null pointer check on the sound loader... oooops! Fix incoming shortly!

Also, is there any reason why libsndfile might not be able to read a .wav? :S

Errm, the has functions that I linked to are similar to md5sums, although for a smaller scale. They are usually a trade off between speed and potential clashes. The main use for them is comparing and storing strings, which are large and slow to work with. Most hash functions can hash arbitrary length strings into 32 bits with few clashes. Makes them useful for creating keys for std::maps

EDIT: the code is submitted. I hope I haven't broken anything

about the hash function, i never dealed with that, what is it for ? to encrypt a pass ?
will it be compatible with potentially another pack system ?
for the where to put it, it could be a new file in MCore I guess, like MHashTools.h / cpp

The problem is now, I still can't reliably export bin files, and I also can't reliably load them. I guess I will tidy up what I can, then comment out the section which doesn't work, or wrap it in #ifdef, so you can have a look to see if I'm doing anything silly.

Also, what do you think about the method for calculating a teakey by hashing a passphrase? If it's acceptable, where would you like the hash function kept, and do you have a preference as to which hash function? There are a load here with downloads here. Originally I just chose one of those to test it.

Is there anything else you would like to be added this weekend that comes to mind? I'm going quickly add functionality to change the package extension, if it's desired. Then I think I'm done with it

EDIT: It seems that for some reason, the published executable is still referencing the original project location, so yes, it was still picking up the original files. I have no idea how this happened, but shouldn't be too hard to fix.

MMaterialsAnim * materialsAnim = MMaterialsAnim::getNew();
...
if(engine->getMaterialsAnimLoader()->loadData(filename, materialsAnim))
        exportMaterialsAnimBin(filenameDest, materialsAnim);

If the loading of your model is 9s for both, it means it's still loading the xml, it cannot be the same time for the bin...
If it's compiling you can still commit it, I can have a look when I have time (today and this week-end is the Angoulême comics festival so I'm not sure when).

cheers,
Anaël.

Also, I stuck the 50.8MB model through the exporter, I'm sorry to say that MaratisPlayer opened both binary version and xml version in ~9s. Interestingly, though, the bin is 979KB