Improved animation handling #19

Open
opened 2024-07-20 08:51:32 -04:00 by Elijah · 1 comment
Owner

Currently, the webapp is hardcoded to play the "Show" animation when an agent enters, and "Hide" when they leave.

This creates problems as some agents are meant to use different animations for these, or to show multiple animations in a row.

In addition, animations should be added for chatting and idling.

This can be resolved by adding a configurable sequence of animations for different actions to the agent config on the server, which is sent to the client in the init message.

Currently, the webapp is hardcoded to play the "Show" animation when an agent enters, and "Hide" when they leave. This creates problems as some agents are meant to use different animations for these, or to show multiple animations in a row. In addition, animations should be added for chatting and idling. This can be resolved by adding a configurable sequence of animations for different actions to the agent config on the server, which is sent to the client in the init message.
Elijah added the
enhancement
important feature
labels 2024-07-20 08:51:34 -04:00
Member

Current issues:

  • Animations need to follow branching, Most Office Assistants have branched Greeting/Goodbye animations, which look absurd out of context of being a random animation. We could express this on the server if the client sends a 0-100 value during an animation, where the roll determines the branches taken.
  • Sometimes the Agents can be opaque for no reason (Victor Show). I'm blaming this on frame deltas? Figure out if this is the case.
Current issues: * Animations need to follow branching, Most Office Assistants have branched Greeting/Goodbye animations, which look absurd out of context of being a random animation. We could express this on the server if the client sends a 0-100 value during an animation, where the roll determines the branches taken. * Sometimes the Agents can be opaque for no reason (Victor `Show`). I'm blaming this on frame deltas? Figure out if this is the case.
Elijah added the
bug
label 2024-07-29 15:58:44 -04:00
Elijah pinned this 2024-07-29 16:05:24 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: computernewb/MSAgent-Chat#19
No description provided.