Game Development Community

Bug I think in ShapeImage.cpp

by Vince Gee · in Torque 3D Professional · 04/16/2013 (5:21 am) · 4 replies

Is it me, or having two definitions of correctMuzzleVector in the init persists is bad?

Around line 689
addField( "correctMuzzleVector", TypeBool,  Offset(correctMuzzleVector, ShapeBaseImageData),
      "@brief Flag to adjust the aiming vector to the eye's LOS point.\n\n"
      "@see ShapeBase::getMuzzleVector()" );

   addField( "correctMuzzleVector", TypeBool,  Offset(correctMuzzleVector, ShapeBaseImageData),
      "@brief Flag to adjust the aiming vector to the eye's LOS point when in 1st person view.\n\n"
      "@see ShapeBase::getMuzzleVector()" );

I'm assuming one of the definitions should go? Or am I wrong?

#1
04/16/2013 (7:46 am)
Maybe this is why I always have issues setting correctMuzzleVector?
#2
04/16/2013 (8:04 am)
Definitely looks like a bug.
#3
04/16/2013 (8:12 am)
Looks like a great candidate for a Pull Request!

- Dave
#4
04/16/2013 (8:32 am)
Seen this before: www.garagegames.com/community/forums/viewthread/131893

And so has Richard. lol