Clarification on Memblocks with BoneIndices and Boneweights? There doesnt seem to be enough bytes to store the data

Author

Message

Golelorn

8

Years of Service

User Offline

Joined: 20th Nov 2016

Location:

Posted: 25th Jan 2019 22:31 Edited at: 25th Jan 2019 22:31

Link

According to the shader the boneweight and boneindice attributes are 4 components each. Also according to the data I read back from the memblock confirms there are 4 components.

I have verified the following.

+ Code Snippet

    ////boneweights
	//SetMemblockByte( id, 60, 0 )        // float 
	//SetMemblockByte( id, 61, 4 )        // component count 
    //SetMemblockByte( id, 62, 0 )        // normalize 
	//SetMemblockByte( id, 63, 12 )     // string length 
    //SetMemblockString( id, 64, "boneweights" )  //12 bytes
    
    
    ////boneindices
	//SetMemblockByte( id, 76, 1  )        // float 
	//SetMemblockByte( id, 77, 4 )        // component count 
    //SetMemblockByte( id, 78, 0 )        // normalize 
	//SetMemblockByte( id, 79, 12 )     // string length 
    //SetMemblockString( id, 80, "boneindices" ) //12 bytes

However, there isn't enough bytes for 8 more float value (32 bytes). There is only 20 bytes left after the position, normal, and uv components. Its reporting back that the vertex size is only 52 bytes instead of the 64, I expected.

I would appreciate any guidance on what I am doing incorrectly. Thank you very much.

Attachments

Login to view attachments

Back to top

Profile PM

puzzler2018

User Banned

Posted: 25th Jan 2019 22:48 Edited at: 25th Jan 2019 22:55

Link

For starters - Should your normalise be 0 instead of 8

What size if your attribute size?

- 32 is texture
- 36 with color too

Maybe you need 4 for additional stuff

Havent explored that yet

SetMemblockInt(chunkmesh,12,32) // 32 no color - 36 if color data --> maybe more if bonedata

What do you have param 12 set at

Back to top

Profile

puzzler2018

User Banned

Posted: 25th Jan 2019 23:07 Edited at: 25th Jan 2019 23:12

Link

5 Attributes --- Damm. What you going on here... Textural / Color / Bonedata - thats 3 attribute Already

My apologies its the

SetMemblockInt(chunkmesh,8,3) // 3 attributes

With an amazing progress you do with your app, im sure you know more than me

Also still I talk like crap sometimes

Back to top

Profile

Golelorn

8

Years of Service

User Offline

Joined: 20th Nov 2016

Location:

Posted: 25th Jan 2019 23:19 Edited at: 25th Jan 2019 23:19

Link

There is no vertex color, and not sure what you mean by normalize is set to 8? I thought I had it set to 0.

In the end, it doesn't appear to matter, because I do not know how to put a bone in an object created from a memblock.

So the mesh looks like this lol

Attachments

Login to view attachments

Back to top

Profile PM

puzzler2018

User Banned

Posted: 25th Jan 2019 23:19

Link

You require to have bonedata too - check above

Back to top

Profile

puzzler2018

User Banned

Posted: 25th Jan 2019 23:22

Link

Could you sent all parameters to us

eg

SetMemblockInt(chunkmesh,0,VertexCount)
    SetMemblockInt(chunkmesh,4,IndexCount)
    SetMemblockInt(chunkmesh,8,3)
    SetMemblockInt(chunkmesh,12,32) // no color - 36 if color
    SetmemblockInt(chunkmesh,16,60)
    SetMemblockInt(chunkmesh,20,IndexOffset)
    SetMemblockInt(chunkmesh,24,0x0c000300)
    SetMemblockString(chunkmesh,28,"position")
    SetMemblockInt(chunkmesh,40,0x08000300)
    SetMemblockString(chunkmesh,44,"normal")
    SetMemblockInt(chunkmesh,52,0x04000200)
    SetMemblockString(chunkmesh,56,"uv")
    //SetMemblockInt(memblock,60,0x08010401) // maybe one day or year in 2019 lol
    //SetMemblockString(memblock,64,"color") // maybe one day or year in 2019 lol
        for i = 0 to m.VertexList.Length
             
        if m.VertexList[i].air = 1 // has a block there
            SetMemblockFloat(chunkmesh,60+i*32,m.VertexList[i].x)
            SetMemblockFloat(chunkmesh,64+i*32,m.VertexList[i].y)
            SetMemblockFloat(chunkmesh,68+i*32,m.VertexList[i].z)
            SetMemblockFloat(chunkmesh,72+i*32,m.VertexList[i].nx)
            SetMemblockFloat(chunkmesh,76+i*32,m.VertexList[i].ny)
            SetMemblockFloat(chunkmesh,80+i*32,m.VertexList[i].nz)
            SetMemblockFloat(chunkmesh,84+i*32,m.VertexList[i].u)
            SetMemblockFloat(chunkmesh,88+i*32,m.VertexList[i].v)
        endif
        //SetMemblockInt(memblock,104+i*36,m.VertexList[i].color) //maybe one day or year in 2019 lol
    next

+ Code Snippet

    SetMemblockInt(chunkmesh,0,VertexCount)
    SetMemblockInt(chunkmesh,4,IndexCount)
    SetMemblockInt(chunkmesh,8,3)
    SetMemblockInt(chunkmesh,12,32) // no color - 36 if color
    SetmemblockInt(chunkmesh,16,60)
    SetMemblockInt(chunkmesh,20,IndexOffset)
    SetMemblockInt(chunkmesh,24,0x0c000300)
    SetMemblockString(chunkmesh,28,"position")
    SetMemblockInt(chunkmesh,40,0x08000300)
    SetMemblockString(chunkmesh,44,"normal")
    SetMemblockInt(chunkmesh,52,0x04000200)
    SetMemblockString(chunkmesh,56,"uv")
    //SetMemblockInt(memblock,60,0x08010401) // maybe one day or year in 2019 lol
    //SetMemblockString(memblock,64,"color") // maybe one day or year in 2019 lol
        for i = 0 to m.VertexList.Length
             
        if m.VertexList[i].air = 1 // has a block there
            SetMemblockFloat(chunkmesh,60+i*32,m.VertexList[i].x)
            SetMemblockFloat(chunkmesh,64+i*32,m.VertexList[i].y)
            SetMemblockFloat(chunkmesh,68+i*32,m.VertexList[i].z)
            SetMemblockFloat(chunkmesh,72+i*32,m.VertexList[i].nx)
            SetMemblockFloat(chunkmesh,76+i*32,m.VertexList[i].ny)
            SetMemblockFloat(chunkmesh,80+i*32,m.VertexList[i].nz)
            SetMemblockFloat(chunkmesh,84+i*32,m.VertexList[i].u)
            SetMemblockFloat(chunkmesh,88+i*32,m.VertexList[i].v)
        endif
        //SetMemblockInt(memblock,104+i*36,m.VertexList[i].color) //maybe one day or year in 2019 lol
    next

Back to top

Profile

puzzler2018

User Banned

Posted: 25th Jan 2019 23:24

Link

What should it look like - Bone Data - I persume that all those lettice leaves are bones

Back to top

Profile

Golelorn

8

Years of Service

User Offline

Joined: 20th Nov 2016

Location:

Posted: 25th Jan 2019 23:51 Edited at: 26th Jan 2019 00:00

Link

I got the object to animate after turning it into a memblock and combining 56 trees to one object.

The bad part is there is only 1 bone being shared amongst all vertices. So the mesh is a "little" distorted to say the least.

The "trick" was having to use SetObjectMeshFromMemblock over the bone. But, I want to be able to combine meshes and bones. One bone, ain't gonna cut it.

I am guessing we aren't able to insert bones. So, gonna try something else.

Attachments

Login to view attachments

Back to top

Profile PM

puzzler2018

User Banned

Posted: 26th Jan 2019 00:11 Edited at: 26th Jan 2019 00:11

Link

each tree is a bone then - correct?

As long as you have the correct number of attributes on the mesh you can all you want.

I wont explain how memblocks work cause you fully know -plus my brain is knackered

Back to top

Profile

Sorry your browser is not supported!

AppGameKit Classic Chat / Clarification on Memblocks with BoneIndices and Boneweights? There doesnt seem to be enough bytes to store the data

Attachments

Attachments

Attachments