Thanks again.. I will check that..
In mean time I got an old version of jpct (1.23) which i used to create a serialized file and it is working like a charm... thanks for your pointer ..
I have one more query. I have evaluated Rajawali 3D engine also. Compared to it the loading time is blazing fast. (4 sec vs 30 sec). However, I noticed one thing. The file size of serialized object is very high. I will give a comparison below:
File Type: obj
File Size: 8.48 MB
Serialized file Size:
JPCT - 12.12 MB
JPCT (Zip) - 2.2 MB
Rajawali - 2.45 MB
Rajawali (Zip) - 1.8 MB
There is not much difference in the Zipped files(0.4 MB) but the difference in serialized formats is very high(~10 MB). Also I was of the assumption that Serialization will reduce the file size (compared to obj). Can you give me some pointers or details on the serialization?
In my case the models will be streamed from server. Typically the models will be of ~10 to 15 MB (obj). I am very much worried about the streaming time because of file size. Can you give any suggestion as to which will be the best way to handle such cases?
p.s: One more interesting thing I noticed was on reopening of the app(after closing the app), Rajawali again takes ~20 sec, but JPCT renders immediately
... It would be very helpful if you an put some light on how JPCT is achieving this....
Thanking you once again ...