Yeah... xDDD I used serialialized loading since weeks is faster... and uses less memory because no importation process must be executed.
But above those advantages I believe the serialized format has one severe problem: it is very very big: by example for one of the animations I work:
I suspect that the matter is that serialized data include not only the geometry data, also include all the other properties so the objects do not need to be initialized again. Very very fast, but very very big. Probably there exists a better solution which picks advantages from both alternatives, but for the moment I guess the serialized form is the best available, as long as you can zip the data inside jars or apks, so the size lowers.
Anyway maybe something is possible in this way
But above those advantages I believe the serialized format has one severe problem: it is very very big: by example for one of the animations I work:
- source data: 60 .objs, animated: around 1'5 mb (.obj maybe are one of the bigger formats, very very redundant).
- import with a java application and exported to serialized form. I discard redundant geometry with strip, and I apply some other optimizations (I do not remember now, but I readed everything weeks ago).
- the result is that the serialized data: animated 60 frame object: around 4 mb.
I suspect that the matter is that serialized data include not only the geometry data, also include all the other properties so the objects do not need to be initialized again. Very very fast, but very very big. Probably there exists a better solution which picks advantages from both alternatives, but for the moment I guess the serialized form is the best available, as long as you can zip the data inside jars or apks, so the size lowers.
Anyway maybe something is possible in this way