Weren't we supposed to be able to distribute only the serialized meshes?

[NovaSilisko]

Because I certainly can\'t. If I get rid of the .DAE files, the game won\'t load because it\'s still trying to FIND the .DAE files... Dunno if there\'s a way around this.

Is there?

[Omnivore]

You could try creating a 1 byte text file, renaming it to xxx.dae, and making sure it is older than the dae file you use to create the meshes. Then just replace the actual dae with the fake dae in distribution with meshes.

[Killerhurtz]

Not quite sure it works that way - the dae still will contain data considered different than the serialized meshes (I think) and cause more trouble.

I could be wrong though.

[NovaSilisko]

If it detects changes in the DAE, it will try to generate a new serialized mesh, from my understanding.

[Omnivore]

It checks the date-time stamp of the dae file, it *does not* load the dae file unless it fails the check.

[Tosh]

AFAIK Harv did not set the problem this way when working on v0.13. He was more concerned about loading times than mesh distribution issues.

But perhaps he may be persuaded to make v0.14 contented with serialized mesh only , i.e. to check mesh creation times only if .DAE file is present.

[Technical Ben]

AFAIK Harv did not set the problem this way when working on v0.13. He was more concerned about loading times than mesh distribution issues.

But perhaps he may be persuaded to make v0.14 contented with serialized mesh only , i.e. to check mesh creation times only if .DAE file is present.

This. Although distributing a sterilised mesh would help, I think Harv implemented it first off just to load up in game quicker.

We do have a python based steriliser at the moment. It\'s not as fully featured as the games version though.

[Tiberion]

I remember he said that being able to distribute only the binary files is a potential side benefit of the new system, but I don\'t believe he implemented it yet