Booping definitely seems rife for harassment and just pestering people, especially with how willy-nilly people are with adding people to their friends list. Very surprising that wasn’t really thought through.
I feel like the only use of this would be “hey look at discord”
I am very picky about my notifications.
I do agree “on my default but with option to turn off globally” would be the best compromise.
Ironically, if VRC actually allowed me to set permissions based on favorites groups (like orange status by default, and green/blue for favorites), they could have extended that functionality into boops, by only letting favorite/close friends do boops.
Lots of opportunity for growth here, and we’re wasting it on forced boops 
Going a bit further in on the solving order of the constraints: first of all, great to know that constraints that are being relied on by other constraints get solved first, but thus this also apply to parenting? Like if i got an gameobject with an position constraint, and then that gameobject has a child with an aimconstraint, would the parent be guarenteed to get solved first? Otherwise this could lead to improper visuals if the child get solved before or during the updating of the parent.
Second of all. Does freezing the constraint have an influence on the solving order. Like would they be solved at first or last?
This would mostly be importand for world constraints as the root of the worldconstraint should be calculated before all other constraint within the worl constraint hiargy.
Boops seem kind of limited in usefulness. If we could add messages to them, similar to adding messages to invites, that would make them a thousand times more useful as a sort of pseudo-DM feature. I’d use them all the time if that were implemented.
Pleased you’re looking forward to them! My understanding at least is that using world freezing on VRC constraints should mean fewer constraints would be needed to achieve this effect compared to what’s done with avatars currently. If you have additional constraints below the frozen transform, you should still be able to toggle those on and off with the same effect as before.
The at-rest and offset fields are disabled when the constraint is locked to replicate how Unity’s constraints work. These components include logic to recalculate values automatically if you change their values in the inspector while the constraint is active, but unlocked - allowing editing of these while the constraint is locked can interfere with this. That said, it could be looked at it if there’s enough interest.
Yes, in that case the position constraint would solve before the aim constraint, since the result of the aim constraint relies on the position constraint. The other condition for dependencies like this is if a constraint changes any source transforms used by another constraint.
A frozen constraint’s solve order would still be the same as when it was unfrozen, so dependencies like this would still apply.
The benefits of the new rank is they can make the limits much lower compared to banning avatars outright. I agree if an avatar is at 200 mb they’re already insanely unoptimized. But if suddenly a bunch of people have their avatar banned there would be riots. If you do it with a rank people can still make instances allowing them but the instances not allowing them will add friction to encourage them to stop using that avi without making everyone riot.
Any news on iOS? Like a date of when applicants are going to get accepted or get an email?
Any news on iOS? Like a date of when applicants are going to get accepted or get an email?
We stop accepting applications tomorrow. We’ll need some time to go through the applications before we accept people, so no date yet on when to expect an email. We can give an update in the next Dev Update if we haven’t sent out emails by then.
Boops seem like a VERY small, VERY awkward and VERY limited step to an actual messaging system and I have VERY mixed feelings about this feature in that state. Especially considering how ambiguous they are, the potential of annoying people and how it basically gives you a huge push to now replace your custom emojis with stuff for communicating using boops and waste their limited slots. Why not simple custom one-time messages or images like you can do with invites? I can’t help, but think of this system as just cluttering my notifications and UI, just for me to receive an emoji that who knows what meaning does it convey. I’m also not a fan of the particle animation that goes off with it. I find it overwhelming / over the top, and confusing from UX side of things (people already asking in comments if other players can see it).
I’d like to hear more on the thought process that went into going with this idea. Especially example real usage scenarios and why not text (and images) based system (basically custom invites minus the invite part).
making booping permissions similar to avatar interaction permissions could work
I’ve thought an in-game messaging feature might be good to have, but I feel this boop presentation is too annoying.
I think the root cause of this is that “friends” in VRChat are not as actual friends, as the dev team may think or presume to design the features. As you may know, because of historical reasons (we didn’t have a better way like Groups), users have added others to their friends even though they think this person will not be a friend.
This honestly makes a lot more sense as there are multiple scenarios where you’d wanna have multiple constraint types under one game object. Having them use the same script with a drop down is a bit of an issue with regards to animating.
If possible can we get an option like this be added in game similar to the option to convert dynamic bones to physbones?
This is honestly really nice, but there’s a question some of us have with this, like how will this behave with Physbones and Contacts, because currently they jitter if we use the current world constraint method which makes putting props in the world.
Also is there any consideration to adding parameter/shader property support to the constraints or would that be considered a separate idea?
Would you consider an “on by default” system?
(still including the option for users to disable it for them)
or a second pop-up when you add someone ⸤Allow user to send you boops?⸣
many desktop streamers, including the ones who top in the category depend on not being on DND to allow people into their instance.
I believe the 2nd option would be the best overall to allow usability for the feature or a setting to temporarily disable all. to avoid having to compensate for this feature and not need too remain in group instances, make a seperate account for making new friends and so forth ^.^
At the moment, the way to address this is by animating your initial offsets
How will the new constraint systems effect quest/android builds of avatars? If at all?
In addition to the constraint depth, does it also include the number of sub-objects that need to be affected by the constraint?
There is too much logic that you need to implement now, which makes it difficult to think about the impact of operating transforms and optimizing transforms.
Is there an internal performance testing benchmark with relatively good coverage?
I’m a little doubtful whether it’s not finished yet, and I’d like to know how much better the current constraint performance is compared to traditional constraints?
Does avatar reloading due to culling or safety change or whatever resets the constraint state? (I assume yes)
Boops are pretty fun, but as more and more social features are introduced, there is a need for more access control.
For example, make more friend lists and assign different levels of access to them. Or better yet, convert them into “roles”.
In general, I don’t like the trust system in VRChat. For some reason, the system decides who the user should trust and who should not. What is the fundamental difference between the ranks is not obvious. Why is someone obliged to trust “trusted” more than just “user”? And the only way for a user to decide who is trusted is to use drastic measures like block or mute. I can’t decide for myself who to show my status to and whether I trust a person with a 200mb avatar to use my computer’s resources. It turns out you’re either friends with the person for everything, or they’re a complete stranger. It’s all or nothing. This is a bad scheme in general and it will only get worse as new social interactions emerge.
At one time Google+ had an elaborate system of access levels aka “circles”. It is very sad that this social network died before it became popular.
This thread: people are terrified of the idea of their friends DM-ing them a sticker 
the post is cool n all but i hope this gets used for the avatars by default for performance reasons & the whole boop thing… kinda a weird feature to add ngl and i really hope that users can turn it off for themselves because i know of alot of people on my friends list who’d abuse that and it’d get pretty annoying