Jump to content

  • Log In with Google      Sign In   
  • Create Account


Simple 3dModels displays, but more complex ones don't. Memory limit, buffer size, etc... ?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 babarorhum   Members   -  Reputation: 100

Like
0Likes
Like

Posted 05 February 2012 - 04:39 PM

Hello,

I have recently created an importer which loads Blender 3D generated models into my under-development iphone app.

For simple objects such as cube, cone, etc... it works perfectly fine. However, as soon as the objects reach a certain degree of complexity such as a donut shape , sphere; the engine display only a part of the objects; e.g half of it; sometimes less. I have checked the vertices and indices in the data model and they are perfectly fine.

It looks like there would be a hard limit such as a number of vertices, memory allocation etc...but i can't exactly figure it out. As i am not yet quite confident in OpenGL ES there might be quite a direct answer to this problem ; but hasn't found it yet.


Any pointer, tips are more than welcome to draw the second half of this sphere ;)

Cheers,
Stéphane
PS. some screenshots to complement this post:

The model in Blender:
Blender Initial Sphere.png

The model in the Iphone simulator; as you can see quite not the same:
Iphone Sphere.png

Sponsor:

#2 SaTANO   Members   -  Reputation: 376

Like
1Likes
Like

Posted 06 February 2012 - 09:49 AM

I made some applications for iPhone with more complex geometry 8000+ poly (just for testing) and it works correct
There should be problem with your allocations in VBO (indexes probably) which should be OK for simple objects like cube in front view
- check your index count and vertex count in VBO creation state
- also check for quads vs. triangles (index count from 4 to 6), are you exporting direct triangles?

#3 babarorhum   Members   -  Reputation: 100

Like
0Likes
Like

Posted 07 February 2012 - 04:36 PM

Problem solved: the number of the indices didn't deal with the vertex indice array but another array. Once it has fixed ; it works perfectly fine ! Big Thanks !




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS