I have a problem about skeleton animation.
I use the new visual studio release -- vs2008 beta2, in the debug version,the programme performed well,but in the release version , there is no animation, does anyone know why,does the new vs release support directX well? thx
skeleton animation problem
Started by ts200701, Aug 01 2007 03:40 AM
5 replies to this topic
#1
Posted 01 August 2007 - 03:40 AM
#2
Posted 01 August 2007 - 08:35 AM
Some errors don't show up in the debug version. I believe the compiler will add some padding to arrays, so make sure your array reading/writing don't go out of bound.
#3
Posted 01 August 2007 - 05:13 PM
I think that is the problem indeed, I once experienced something similar. A bit odd though; I thought that the debug version added some code to check bounds (the famous 0xCD bytes, iirc), but sometimes it isn't perfect.
#4
Posted 02 August 2007 - 02:42 AM
In vs2005 , there has no problem ,only in vs2008 .So i think the problem is from the compiler. has any idea?
#5
Posted 02 August 2007 - 05:28 PM
I don't mean to be mean, but it's much more likely that the problem is in your code than in the compiler.
Like geon said, if there's problems with memory corruption, like out of bounds array access, it may or may not cause a visible effect depending on the memory layout of your program, which can change from one compiler to another or between debug and release versions.
Like geon said, if there's problems with memory corruption, like out of bounds array access, it may or may not cause a visible effect depending on the memory layout of your program, which can change from one compiler to another or between debug and release versions.
reedbeta.com - developer blog, OpenGL demos, and other projects
#6
Posted 03 August 2007 - 12:54 AM
Reedbeta said:
I don't mean to be mean, but it's much more likely that the problem is in your code than in the compiler.
Like geon said, if there's problems with memory corruption, like out of bounds array access, it may or may not cause a visible effect depending on the memory layout of your program, which can change from one compiler to another or between debug and release versions.
Like geon said, if there's problems with memory corruption, like out of bounds array access, it may or may not cause a visible effect depending on the memory layout of your program, which can change from one compiler to another or between debug and release versions.
Thanks.
i have found the problem.
the converted project from vs2005 has the problem, but the original vs2008 project works well.And i do not know why this happened, is there some parameters wrong?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











