You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
This command to stop keyframed motion should always succeed, and never shout an error: llSetKeyframedMotion([], []);
It should not shout the error "Cannot use llSetKeyframedMotion() on a physical object."
It should not shout the error "Only linksets which uses the new prim equivalency system may be animated."
It should not shout the error "Cannot use llSetKeyframedMotion() on an attachment."
The errors should be retained when starting an animation, or resuming one, but not on stopping one. Stopping should always succeed, and always put the prim in the normal un-animated state without error messages
Stopping llSetKeyframedMotion should always succeed and never shout an error
Type
New Feature Request
Priority
Unset
Status
Accepted
Resolution
Accepted
Reporter
Tapple Gao (tapple.gao)
Created at
2020-11-14T23:17:30Z
Updated at
2020-11-18T18:47:54Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'How would you like the feature to work?': 'See description',
'Original Reporter': 'Tapple Gao (tapple.gao)',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'This command to stop keyframed motion should always succeed, and never shout an error: llSetKeyframedMotion([], []); \r\n\r\nIt should not shout the error "Cannot use llSetKeyframedMotion() on a physical object."\r\n\r\nIt should not shout the error "Only linksets which uses the new prim equivalency system may be animated."\r\n\r\nIt should not shout the error "Cannot use llSetKeyframedMotion() on an attachment."\r\n\r\nrelated: https://jira.secondlife.com/browse/SVC-7485',
'What were you doing when it happened?': 'x',
'What were you expecting to happen instead?': 'x',
'Why is this feature important to you? How would it benefit the community?': 'See description',
}
The text was updated successfully, but these errors were encountered:
Tapple Gao commented at 2020-11-14T23:28:58Z, updated at 2020-11-14T23:31:59Z
The error messages are pointless in this case, cause customer complaints, and it's also very hard to eliminate them in a complex script like my own teeglepet horses, which have a switch between vehicle physics and nonphysical keyframed motion. The errors persist despite me doing my best to get rid of them. This segment still sometimes shouts the error "Cannot use llSetKeyframedMotion() on a physical object.":
if (!llGetStatus(STATUS_PHYSICS)) llSetKeyframedMotion([], []);
The script occasionally gets interrupted by another script in between the if and the llSetKeyframedMotion by another script that turns physics back on, and so the error "Cannot use llSetKeyframedMotion() on a physical object." is shouted, dispite my best effort to suppress it
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This command to stop keyframed motion should always succeed, and never shout an error: llSetKeyframedMotion([], []);
It should not shout the error "Cannot use llSetKeyframedMotion() on a physical object."
It should not shout the error "Only linksets which uses the new prim equivalency system may be animated."
It should not shout the error "Cannot use llSetKeyframedMotion() on an attachment."
The errors should be retained when starting an animation, or resuming one, but not on stopping one. Stopping should always succeed, and always put the prim in the normal un-animated state without error messages
related: https://jira.secondlife.com/browse/SVC-7485
Original Jira Fields
The text was updated successfully, but these errors were encountered: