i was hoping someone would be able to tell me what controls targeting of a creature model in-game (i.e. when the pointer changes to a sword or mouth as it targets the creature). i ask because i’m diddling around with creature models, i changed the scale in one, and now although the creature appears just as i’d like it to, it’s become more difficult to target in-game. is there a node for this in the model? is it a .2da entry?
Scaling isn’t perfect.Imo it doesn’t make much of a difference if you scale with the toolset or within the model file itself. Negative effects can only be avoided if you “scale” the vertices itself.
From your description I take you made it much larger, but the hit range is still in size of the smaller original. So which one is it and how much do you scale it? (Hopefully it’s something available in public …)
actually i shrank it to 60% of its original size. sorry about that, i should’ve put that info in the original post… ‘setanimationscale 0.6’ in the header and ‘scale 0.6’ in the top-level dummy node.
i tried fiddling around with the various entries in appearance.2da that manage a creature object’s active area [CREPERSPACE etc.], which made absolutely no difference.
don’t worry if nothing comes to you, this isn’t a show-stopper and i can manage without shrinking it. i just thought i’d post in the hope that someone who’s more experienced with modeling than i might’ve already run into this situation before.
appearance.2da controls distance, including whether one creature can reach another in combat, as explained in the wiki.
However, I understood the OP to be asking about initial targetting with the cursor.
IIRC the selection box size is determined from the model geometry. I recall fixing some placeables that had huge selection boxes when some dummy node had huge dimensions for no good reason. Not sure what would make selection harder.
thanks for the help, guys, i fixed it.
[well, tbh i didn’t really fix it, credit actually goes to OldMansBeard…]
a bit less cryptically, i stumbled across this article, and downloaded OMB’s cleanmodels and resized it as recommended in the article. voilà, problem sorted [apparently in 0.015 seconds… ].