SDK – Retrieve information about the POD exporter

This topic contains 18 replies, has 4 voices, and was last updated by  dgu 4 years, 3 months ago.

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #31335

    rraallvv
    Member

    In the POD file there is a string of characters that indicates information about the exporter

    For instance the string:

    ‘PVRGeoPOD x64 2.14.2 | Blender v2.67 (sub 0) | Python v3.3.0 | 3.1’

    Can’t be retrieved from ReadFromFile, nor apeears to be in the user data nor description.

    Is it posible to retrieve this information through SDK?

    This information is useful to convert some parameters that vary with each exporter.

    #37621

    Sean
    Moderator

    Moving topic to PowerVR Insider – Meta Insider is for Meta SoC questions.

    #37622

    dgu
    Member

    Hello

    allow me to believe that only the Pod Version that is really important ,the one specified in POD File Format Specification associated to the sdk and PVRSHaman, it s clearly independent of any authoring tools as well witch is a very good things.It s a beautifull container

    regards
    david

    #37623

    rraallvv
    Member

    Hi,

    In PVRSHaman spot light cutoff angles in POD files exported by Blender are in radians converted from radians, wich is a very small angle. While Maya exported POD files shows the cutoff angle ok, i.e. degrees converted to radians.

    This is an issue of the Blender POD exporter, wich happens to be included in the SDK, it export the cutoff angle in radians while PVRSHaman expets degrees.

    #37624

    dgu
    Member

    i see , it this case and for now it look better to export it as a Collada DAE.This work fine;)

    #37625

    rraallvv
    Member

    I’ll try it, thanks for the advice

    #37626

    dgu
    Member

    is it easy to do a render to texture using blender ?
    i mean how it is flexible to manage UV?

    #37627

    Scott
    Moderator

    In the POD file there is a string of characters that indicates information about the exporter

    For instance the string:

    ‘PVRGeoPOD x64 2.14.2 | Blender v2.67 (sub 0) | Python v3.3.0 | 3.1’

    Can’t be retrieved from ReadFromFile, nor apeears to be in the user data nor description.

    Is it posible to retrieve this information through SDK?

    Hi,

    You should be able to retrieve the info by

    char history[256];
    m_Scene.ReadFromFile(c_szSceneFile, NULL, 0, history, 256);

    history will contain the information. The POD file in this situation won’t be loaded into m_Scene and you should ignore the return value.

    Cheers,

    Scott

    #37628

    dgu
    Member

    didnt know that good to learn from the Pod Father !! 🙂

    #37629

    rraallvv
    Member

    is it easy to do a render to texture using blender ?
    i mean how it is flexible to manage UV?

    I’m quite new to blender, switched from maya because the lack of a good Bullet Physics exporter.

    Im not sure if blender can do the same things with UV that maya does, sorry.

    #37630

    dgu
    Member

    i didnt know that blender can export serialized object for bullet ?

    #37631

    rraallvv
    Member

    i didnt know that blender can export serialized object for bullet ?

    Yes, this is how bulletphysics.org/Bullet/phpBB3/viewtopic.php?f=9&t=6683&p=23315#p23315

    #37632

    dgu
    Member

    that is really good , do you use Filewrap after ? or you store the serialized file on disc ?

    #37633

    rraallvv
    Member

    that is really good , do you use Filewrap after ? or you store the serialized file on disc ?

    It stores a .bullet file that can be previewed with code.google.com/p/3d-editor-toolkit/

    …and loaded at run time with the bullet class btBulletWorldImporter

    #37634

    dgu
    Member

    i mean bool loadFileFromMemory(char *memoryBuffer, int len);

    can be use using FileWrap tools from the sdk then that is cool.

Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic.