Author Topic: What does the "compiled objects"actually mean?  (Read 1042 times)

Offline kiffa

  • long
  • ***
  • Posts: 199
    • View Profile
What does the "compiled objects"actually mean?
« on: January 26, 2013, 04:00:25 pm »
I want to know the difference between "uncompiled objects" and "compiled objects".

I have read the wiki, which describe  the advantages and disadvantages of compiled objects. But i want to know more details.

For example, the compiling process 、 the structures of compiled objects 、 why does it have the advantages/disadvantages... and so on.

Thanks.

Offline Raswr

  • byte
  • *
  • Posts: 13
    • View Profile
Re: What does the "compiled objects"actually mean?
« Reply #1 on: January 26, 2013, 05:55:02 pm »
As far as I know, jpct-ae uses compiled objects only. For what I read on the wiki it sounds as a relationship between compiling and using VBO's, as it's something that makes rendering of high poly stuff faster and i guess strip is removing from memory the original vertex data you read from the model file, but you would also need that data for animation purposes.

I might be completely wrong here so just wait for an official answer  ;)

Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11970
    • View Profile
    • http://www.jpct.net
Re: What does the "compiled objects"actually mean?
« Reply #2 on: January 26, 2013, 08:10:03 pm »
I might be completely wrong here so just wait for an official answer  ;)
No, that's basically how it is. The desktop version offers the option to use compiled or uncompiled objects. Compiled ones are faster, uncompiled are more flexible. jPCT-AE uses compiled objects only. Anything else would be much too slow on a mobile device.