Desktop contact notif#201
Conversation
Adding more avatars to the exclusion list, will add more and try to find more of the older popular avatars since their armatures are likelier to have been used as bases.
…der/reciever) and a soft wind notification when you can fly or loose the ability to fly.
|
Am changing things a little. The contacts will sit at the origin of the world now, requiring avatars that want to use the system to have 1 constraint for boolean toggles and two for float changes. However one issue I forsee is creators moving the OF root at runtime.. The notification system now also doesn't follow you anymore at all times (It was hitching along with the contact object), it simply moves to you once when it activates. I also added some simple support for flight zones, it is up to the creator how to implement it, but the methods overwrite the flight mode while still allowing it to change and update in the background for when it stops overwriting. |
…how contacts and the hud work, contact reciever sticks to the world origin now (requiring avatars to use one world constraint)
|
The 3.10.4-beta.3 SDK added the ability for tweens to enable and disable game objects after a delay, while simply a optimization with this I could forgo the animator on the notification prefab whose whole job is to disable the game object after the notification particles have done their job. In hindsight I am not sure whether simply keeping the object active or using an animation like I am to disable it was better, but to my understanding having the object be disabled when not required is best. (Am putting this here as a reminder) |
|
This is looking really good! I'll have a closer look at the code and whatnot over this weekend. Note to self: if there's a prefab for the avatar contact settings too (to be placed on the avatar), perhaps that could be included directly on the releases page. |
There is a prefab with everything, it just needs to be changed so it is world dropped instead, but it is really messy because it has everything and is more of a debug thing. In my head you would simply bake in the values into toggles and its default state instead of directly controlling them. Would be better to add good documentation for it and provide the debug prefab as reference if needed, using it as is isn't great. |
Desktop.Flight.Example.mp4
Contactexample.mp4
Notification.Example.mp4
Here is my testing world link to test the changes. https://vrchat.com/home/world/wrld_fbcb2db6-49cd-48ef-86cf-b128f7362c1d