Page MenuHomeFeedback Tracker

tank_f skeleton from sample does not make sense
Closed, ResolvedPublic

Description

Take a look at the following part of the sample model.cfg:

class Tank_F: Tank {

		skeletonInherit = "Tank";
		skeletonBones[] = {
			"zasleh","otocHlaven",
			"recoilHlaven",	"otocHlaven",
			"hatch_gunner","OtocVez",
			"hatch_commander","OtocVez",
			"commander_turret","OtocVez",
			"commander_gun","commander_turret",
			"gunnerview","otocVez"
		};

};

"hatch_commander" is a child bone of OtocVez (main turret), but should be a child of commander_turret.

Additionally, "gunnerview" is also a child of OtocVec (main turret), but should clearly be a child of OtocHlaven (main gun)

Details

Legacy ID
788291764
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Tools

Event Timeline

Varanon set Category to Tools.Sep 1 2015, 12:17 AM
Varanon set Reproducibility to Always.
Varanon set Severity to None.
Varanon set Resolution to Fixed.
Varanon set Legacy ID to 788291764.May 8 2016, 12:37 PM
pettka added a comment.Sep 3 2015, 5:00 PM

Thank You for good points. I would dare differ on the hatch part as hatches are usually part of the main tank turret. Which means their movement should be dependent on it rather than on rotation of commanders MMG, but feel free to correct me if I'm wrong.
As for the gunnerView memory point, You are perfectly correct. It should be out with next update of samples, thank You once more. Could You, please, give it a try afterwards and close this issue if it is as it should be?