Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actuallucky6969b

Posted 11 February 2013 - 05:21 AM

It has been confirmed about the leaks, it was because of the material and texture vectors.

Sorry again,

alnite, it still doesn't work.

But I am in doubt, while in the destroyMeshContainer method, the pMeshContainerBase is downcasted to BoneMesh.

That means that extra components in BoneMesh need to be taken care of.

Another thing is the original book has a texture attached with the sample. It was correctly loaded everytime the program runs.

Now I am using a mesh that doesn't have a texture....

 

 

Update:

I also find a 8-bytes-short memory allocation....

tried to delete the skinned mesh first, then the device to no avail

 

 

 

Thanks

 

Jack


#2lucky6969b

Posted 11 February 2013 - 05:06 AM

It has been confirmed about the leaks, it was because of the material and texture vectors.

Sorry again,

alnite, it still doesn't work.

But I am in doubt, while in the destroyMeshContainer method, the pMeshContainerBase is downcasted to BoneMesh.

That means that extra components in BoneMesh need to be taken care of.

Another thing is the original book has a texture attached with the sample. It was correctly loaded everytime the program runs.

Now I am using a mesh that doesn't have a texture....

 

 

Update:

I also find a 8-bytes-short memory allocation....

 

 

 

Thanks

 

Jack


#1lucky6969b

Posted 11 February 2013 - 03:17 AM

It has been confirmed about the leaks, it was because of the material and texture vectors.

Sorry again,

alnite, it still doesn't work.

But I am in doubt, while in the destroyMeshContainer method, the pMeshContainerBase is downcasted to BoneMesh.

That means that extra components in BoneMesh need to be taken care of.

Another thing is the original book has a texture attached with the sample. It was correctly loaded everytime the program runs.

Now I am using a mesh that doesn't have a texture....

Thanks

Jack


PARTNERS