View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0031616 | Runner | Spine | Public | 2020-02-10 16:27 | 2021-01-12 10:33 |
| Reporter | Scott Dunbar | Assigned To | Mike Rennie | ||
| Priority | Low | Severity | C - General | Reproducibility | Unable To Reproduce |
| Status | Assigned | Resolution | Open | ||
| Product Version | 2.2.5 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0031616: Spine: IK Target implementation is lacking | ||||
| Description | Issue: As per ticket linked in comment the IK Target implementation for Spine is lacking usable functionality for IK Targets. It would appear we do not allow the setting of critical properties to allow for full use of IK from Spine As per linked ticket : " However I did notice that in GMS2 that the bone properties "worldX" and "worldY" are readonly, and this is what seems to be causing the issues. I checked the Spine API Reference and they are not readonly properties in the runtime, so this is specific to GMS2 where they have been made readonly for some reason: http://esotericsoftware.com/spine-api-reference#Bone-worldX It seems that if the worldX and worldY properties could be set directly then positioning the IK Bones would work by just setting the worldX and worldY to mouse_x, mouse_y, although I'm not sure if this is an oversight / bug in the integration or intended for some reason that I'm not aware of. " | ||||
| Steps To Reproduce | This is likely more a feature request than a bug - but it was requested as a bug from CoreTech | ||||
| Tags | No tags attached. | ||||
| 1.4 Found In | |||||
| 2.x Runtime Found In | 2.2.5.378 | ||||
| 2.x Runtime Verified In | |||||