Sorry your browser is not supported!

Hello there!

I ran into some troubles while converting objects, loaded into the sObject struct, toan irrXML readable version.

First of all my code to get the data from the memblock:



I used the memblock because I couldn't figure out how the sObject stores the vertex data, there is a pointer (BYTE*) pointing to the original vertex data (pOriginalVertexData), but can't copy the memory to an array.

But maybe a better question is: am I reading the memblock the right way?

The FVF is: XYZ | NORMAL | DIFFUSE | TEX0

That's that, but how about the Indices, how do I extract it's ids corresponding with the vertices. Can I just give them id's, 0 1 2 3 4 5 6 7 ... etc?

This is the first 4 iterations of couting the data i got from the memblock:



The XYZ seems alright, if 100 stands for 1 (thus, devided by 100 it looks normal), same for normals?

I couted the diffuse color as:

file << hex << dwColor;

With this I am attempting to convert it to and irrXML file format.
And because this http://www.irrlicht3d.org/download/example.irrmesh example works, I used it as a template. All goes well till the real meat, vertices & indices. It crashes upon loading without errors.

Thank you,

Leo

PS: I am wondering where the memblock get's all the data from the mesh. sObject->sObjectData->ppMeshList->sMeshDraw->pVertexData and pIndexData are all blank, I am wondering how it does it magic when it converts the normal object to an memblock (which i guess lies in the pBlock), but that's an exact copy of the sObject...

I'm at that point myself so I'll keep an eye on this thread. I've managed to create a blank object with a set amount of verts and indices ready for me to copy my mesh data directly into it. As far as I know you have to 'lock vertex data' before you can access it.

If I come up with anything in the meantime I will post it here.

Try calling dbSync() at least once and see if they are still empty.

Matty H, I understand it now! For sMeshDraw to get it filled in, it has to be rendered once, because the sMeshDraw struct is used when rendering the scene. To retrieve those values darkgdk uses we have to call dbSync() at least once, indeed. The vertex commands now work too, thus they use the same struct to get it's data from then. Is this correct?

Thank you sir! Very cool to see this working.

PS: Now I see how amazing alot of garbage the first version was spitting out.

Here is a codesnippet of the first 4 iterations:


Seems legit.

Gonna try to figure out the rest. And see if 2Texture Coords are available. I believe dbGetVertexDataU/V() accepts an extra parameter to tell the coordinates of all textures, I am not certain on this one, gonna test it out.