Problem with .dae > .pod > PowerVR engine workflow

Tagged: 

This topic contains 2 replies, has 2 voices, and was last updated by  Dan 5 years ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #31055

    Dan
    Member

    I am evaluating the PowerVR Insider SDK for developing a 3D engine.

    I have gotten a brief overview of the SDK by working through the demo projects and taking a look at sources / documentation.
    Now I have problems with the dae > pod import workflow. 
    This is what I want to archive:
    – load one of my scene.dae files with a project built upon the PowerVR SDK.
    This is what I do:
    – I have created a demo scene – a simple cube – which I export with Cheetah3D (or Cinema4D or SketchUp) to a cube.dae file.
    – I am converting the cube.dae to cube.pod using PVRGeoPOD Gui 2.12 (I have tried lots of different export settings…).
    – I verify the cube.pod with PVRShaman – it opens up and looks fine.
    – I am copying cube.pod to the “IntroducingPOD” Example (SDK 3.0), set all references in the Xcode project
    > When I try to run the Application, it instantly crashes with a EXC_BAD_ACCESS in OGLES2IntroducingPOD.cpp:573: 

    glVertexAttribPointer(TEXCOORD_ARRAY, 2, GL_FLOAT, GL_FALSE, pMesh->psUVW[0].nStride, pMesh->psUVW[0].pData);

    I would expect:
    – I was hoping to find a demo project (“POD Viewer” or so) which just loads any kind of .pod file (like PVRShaman does) to get started with the sdk.

    My questions:
    1. Which is the right project to get started with loading my custom scene files?
    2. Which export settings do I have to apply in PVRGeoPOD so the .pod works with that project?
    3. Which properties are obligatory for my .dae file (Do I need textures in every material? Do I need to include a camera / a light?)
    I am really stuck here – the SDK looks really great but it’s quite frustrating to get stuck right at the beginning with basic stuff.
    Thanks in advance for any help. 
    #36361

    Scott
    Moderator

    Hi,

    1. Which is the right project to get started with loading my custom scene files?
     
    This depends on what your scene files contain and what you want to achieve. The examples aren’t designed to be generic POD viewers and are often tailored to work solely with their own POD file so the code is as simple as possible for learning the API/technique that they’re demonstrating. For simple scenes that contain texturing, lights, cameras and animation then IntroducingPOD is the place to start. If you want an example that demonstrates Skinning then Skinning is the one to use as a reference. As you’ve seen, they may require altering to suit your scenes.
     
    2. Which export settings do I have to apply in PVRGeoPOD so the .pod works with that project?
     
    The answer to this is simply, the same settings used originally. These are stored in the POD files themselves. The best way to use the original settings is to import the POD file as an options profile (right-click in the profiles window on the exporter). Then set the new profile as the current export options.
     
    3. Which properties are obligatory for my .dae file (Do I need textures in every material? Do I need to include a camera / a light?)
     
    This can vary from example to example but for IntroducingPOD it expects a light, camera, vertex position, normals and texture co-ordinates. It also expects that the latter 3 are using the data type float.

    FYI, looking at your error I’d guess that your simple cube is either missing texture co-ordinates or when you exported it the “Export mapping channels” option wasn’t enabled.

    Thanks,

    Scott

     

    #36362

    Dan
    Member

    Thanks Scott, 

    the hint with the POD file options profile was especially helpful.

    In this context I have a suggestion from my user-perspective: it would also be very helpful if the original .dae files were included in the demo projects instead of the (proprietary) .max files. That would have permitted me to mimic the respective dae’s structure when trying to get my own models to work.
    Do you happen to have a suggestion where to find a more generic pod loader project? 
    That would really facilitate getting started with the SDK. 
    Kind regards, Dan
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.