| Re: Set_Attack no longer seems to account for Bullseye offset [message #487656 is a reply to message #487630] |
Tue, 20 May 2014 00:57   |
 |
danpaul88
Messages: 5795
Registered: June 2004
Location: England
Karma:
|
General (5 Stars) |
|
|
My guess would be that the only cases that are ever hitting the last return statement in the current code would be Jerad's custom rigs, since all the stock rigs have C SPINE1. Thus changing it to add the Z bullseye offset to that last return value shouldn't impact any other scripts users nor stock Renegade.
That said, it might be better for Jerad to be more specific about where he wants the AI and homing missiles to aim at on his units and add the custom bone as per
| jonwil wrote on Mon, 19 May 2014 14:26 |
Oh and it should be possible to add another bone to a skeleton without needing to re-export any animations as long as the new bone have no child bones, geometry or animations attached to it anywhere. If adding a new bone and re-exporting causes the order/bone number of the bones in the output skeleton file to change, its possible to fix that up by taking the file containing the new bone and copying the new bone into the original skeleton such that the new bone is the last bone in the skeleton (keeping the numbers for the existing bones the same and hence keeping the animations functioning)
|
@Jerad it's a shame you weren't testing this stuff whilst 4.x was being beta tested, it was more likely to get fixed at that time...
[Updated on: Tue, 20 May 2014 01:00] Report message to a moderator |
|
|
|
Search
Help
Members
Register
Login
Home
