The values for these memory points are static (and misplaced, below the rendered position of the character), but the assumption would be that they are moving, as they are part of the animated selections on the character.
Description
Description
Details
Details
- Legacy ID
- 3765410865
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Scripting
Steps To Reproduce
Use debug console to observe values using selectionPosition of "lfemur" or "rfemur" or any other leg memory point and notice that their value never changes despite the orientation of the legs/hips.
Additional Information
This has been around for a while, at least the last 6-8 months, finally got around to adding a ticket for it now. The command works fine for all memory points above the hips on player models.
Event Timeline
Comment Actions
Confirmed. Xknee, Xknee_axis, Xfemur, Xanckle etc all have relative Z < 0, meaning they are in the ground under player model. They also do not update with the model:
oneachframe {hintsilent str (player selectionposition "lknee")}
compare to
oneachframe {hintsilent str (player selectionposition "lelbow")}
Comment Actions
Thank you for letting us know, the memory points should be in proper selections and it seems like it behaves correctly. Could You, please, give it a try tomorrow on a dev branch and close the issue if it works?
Comment Actions
This issue is still occuring with BLUFOR pilot models.
Also can we get a detailed idea of the fix, since it seems to be occurring on specific models and the same issue has been seen on RHS content.
I would like to help them fix it, but I am not sure where to start.
Comment Actions
This is still appearing broken with some units. Specifically, some modded units inherit from default BI Pilot models which cause all inherited models to also be broken with these selections.
As nou said, this is specifically due to the BLUFOR pilot model; but then is somehow an inherited break across other units as well. Is this a skeleton issue, or perhaps a unit config issue?
We are beginning to suspect this is a unit configuration issue regarding incorrectly aligned hiddenSelection configurations - or model types hardcoded into the engine.
The issue is becoming to appear systemic, but we are not sure what is causing the issue in vanilla nor modded units; but it appears to occur across the board with these specific selections, only on specific units.
See here in the ACE tracker, how the issue is appearing is non-vanilla units as well: https://github.com/acemod/ACE3/issues/1346
Comment Actions
[7:29:15 AM] jaynus: basically, its broken on a few vanilla units right? But we are finding its also broken on some mod units
[7:29:19 AM] jaynus: So there is some relationship between the vanilla units and the modded units that's causing the issue. So I thought it might help them hunt it down.
Comment Actions
Easy fix: delete all mem points and replace them with BIS Sample soldier mem points. The long story: LeftLeg and LeftUpLed (same for right) selections were missing in old setup.
Comment Actions
Looks like fixed in dev-branch EXE rev. 130903 (26-05-2015): http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2941973&viewfull=1#post2941973