-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with props used in DEFAULT pose set not deleting as expected #67
Comments
First I tested this: with rez prop card as follows: This works as expected, where the prop will rez when someone sits seat1 and only when someone sits in seat1. If 2default=on, the pose set changes to the DEFAULT pose set when everyone stands and the pose change to end the original pose set. The prop dies and the SATMSG is again armed and waiting for a new sitter in seat1. Next I changed the prop to 'explicit' and added the NOTSATMSG to derez the prop. Everything is working as it should (in my opinion). |
Since we never touched 2default in our implementation I would assume nPose should work in the manner described on the wiki page at https://github.com/HowardBaxton/nPose-V2/wiki/NC-Contents but in our observations this was not the case. The prop remained in place regardless of animations being selected from the menu by the user on seat 1, or standing from the object while seated upon seat 1. Both of these should have caused the prop to derez, but in both cases the prop still persisted in spite of any combination or type of changes on seat 1. This may require some additional investigation with the problematic object in this case to ensure that it is indeed user error in some way and not a bug as it appears. |
We have determined that all other cards other than the DEFAULT are using SCHMO in BTN cards and do not meet the requirement to make normal props die. We also determined that the wiki does not explain this exact point well at all. The use of explicit props solve the issue so I've not been able to determine if this should be called a bug, or an enhancement, or simply a wiki that is lacking robust documentation. |
Before implementing the SCHMO(E) there was only one way to change the "current scene" (animation). That was done by using the SET NCs. So it was easy to decide when a "normal" prop should die.
(I already suggested to remove the differences completly.) My suggestion for the props is: |
This issue creates an opportunity to set up scenes with normal props. In "! nPose Demos Sept 2015" look for "nPose normal props playing around" as an example of how this is done. It is using SET cards specifically for DEFAULT and sub menu buttons, where all others are using BTN type cards and SCHMOE to change poses. The sub menu actually sets up a scene and pose changes within a sub menu are by BTN so no changing of normal props within. I see this as a viable option if controlled correctly. |
solved with nPose V3.00 and the Prop plugin V1.00 |
Documentation says: A normal prop will live only as long as the pose set and will be deleted.
When using a normal prop within the DEFAULT:anim notecard as follows:
ANIM|anim1|<0.71023, 0.26212, -0.94788>|<0.00000, 0.00000, 173.00100>|
SATMSG|207|rez prop||1
ANIM|anim2|<0.71613, 0.58121, 0.60107>|<0.00000, 0.00000, 180.00000>|
with rez prop card as follows:
PROP|propName|<0.92988, 0.46866, -0.52429>|<3.76870, 67.95267, -87.84647>|
Attempted testing using a NOTSATMSG line as well in the DEFAULT:anim card as follows:
ANIM|anim1|<0.71023, 0.26212, -0.94788>|<0.00000, 0.00000, 173.00100>|
SATMSG|207|rez prop||1
NOTSATMSG|207|derez prop||1
ANIM|anim2|<0.71613, 0.58121, 0.60107>|<0.00000, 0.00000, 180.00000>|
with a derez prop notecard as follows:
PROP|propName|propName=die
Results in both instances (with or without the NOTSATMSG and explicit die command):
When user on seat 1 changes pose, or stands up from the object, the prop persists as though it was given the explicit flag. This remains the case even if the user on seat 2 changes pose, or stands from the object as well to leave no avatars in the default poses.
The text was updated successfully, but these errors were encountered: