Dynamic interaction between avatars and attachments
The SDK allows users to define avatar parts as colliders and receivers, facilitating realistic physical interactions and consent-based management, enhancing virtual reality systems with efficient collision detection and processing.
Patent Information
- Application Number
- JP2024526852
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-10-14
- Filing Date
- 2023-09-21
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2043-09-21
AI Technical Summary
Existing virtual reality systems lack the capability to support realistic and efficient physical interactions between avatars, including reactions to contact, consent management, and efficient processing of such interactions.
A software development kit (SDK) that allows users to define avatar parts as colliders and receivers, enabling collisions to trigger animations, sounds, and secondary motion effects, with consent-based interaction management and efficient collision detection mechanisms.
Enables realistic physical interactions between avatars, ensures user consent, and optimizes processing efficiency for avatar interactions in virtual environments.
Smart Images

Figure 2024542402000001_ABST
Abstract
Description
[Background technology]
[0001] Users of computing systems use avatars as substitutes for their physical presence in a variety of applications, ranging from simple chat applications to elaborate three-dimensional (3D) environments used in video games and virtual reality applications. A simple version of an avatar may be a shape of shoulders and a head without any distinguishing features. Some avatars may be complex, associated with detailed graphics, textures, and capable of a variety of animations. For example, some avatars may include many parts, such as hair, tails, ears, and clothing, that are animated separately for realistic and non-realistic movements.
[0002] The details of one or more aspects of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. However, the accompanying drawings only illustrate some typical aspects of the present disclosure and therefore should not be considered as limiting its scope. Other features, aspects, and advantages will be apparent from the description, drawings, and claims. [Brief description of the drawings]
[0003] [Figure 1] FIG. 1 illustrates an exemplary virtual world platform for playing and hosting multiplayer virtual reality (VR) experiences in accordance with some aspects of the present technology.
[0004] [Diagram 2] FIG. 2 illustrates an example of a quick menu in accordance with some aspects of the present technology.
[0005] [Diagram 3] FIG. 3 illustrates an example method for triggering an action in response to a collision with a first avatar and a second avatar, in accordance with some aspects of the present technology.
[0006] [Figure 4] FIG. 4 illustrates an example method for supporting interactions that affect secondary motion of a portion of an avatar in accordance with some aspects of the present technology.
[0007] [Figure 5A] FIG. 5A illustrates an example method for determining whether an avatar contact interaction is permitted, according to some aspects of the present technology. [Figure 5B] FIG. 5B illustrates an example method for determining whether avatar contact interaction is permitted, according to some aspects of the present technology. [Figure 5C] FIG. 5C illustrates an example method for determining whether avatar contact interaction is permitted, in accordance with some aspects of the present technology.
[0008] [Figure 6] FIG. 6 illustrates an example method for determining whether there is mutual agreement between a pair of avatars to allow a supported touch interaction, in accordance with some aspects of the present technology.
[0009] [Figure 7] FIG. 7 illustrates an example table showing example touch settings and whether those settings allow touch interaction, in accordance with some aspects of the present technology.
[0010] [Figure 8] FIG. 8 illustrates a portion of an avatar composed of one or more colliders, in accordance with some aspects of the present technology.
[0011] [Figure 9A] FIG. 9A illustrates two avatars engaging in a touch interaction in accordance with some aspects of the present technology.
[0012] [Figure 9B]FIG. 9B illustrates a moment immediately after a high-touch contact interaction occurs in accordance with some aspects of the present technology.
[0013] [Figure 10] FIG. 10 illustrates an avatar having a portion configured as a collider and a portion configured as a secondary motion behavior, in accordance with some aspects of the present technology.
[0014] [Figure 11] FIG. 11 illustrates an example interface for setting secondary motion attributes for a portion of an avatar, in accordance with some aspects of the present technology.
[0015] [Figure 12] FIG. 12 illustrates an example of a system for implementing certain aspects of the present technology. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] Interaction between users in virtual worlds, such as those hosted by some virtual reality platforms, continues to evolve. Initially, interaction was limited to coexisting in the same world and playing games together. Interaction progressed to live communication and eventually participating in virtual events together. Recently, users have been able to increase the range of motion of their avatars, allowing for more physical interactions in these virtual worlds. For example, they can exercise in the virtual world or dance in a nightclub.
[0017] The next advancement in interaction between humans (albeit avatars) in virtual worlds is physical interaction. That is, there has been a need in the art to support physical interaction between avatars. The present technology solves this problem and other related problems associated with contact-based interaction between avatars.
[0018] Previously, it was possible for parts of an avatar to come into contact with parts of another avatar, but this was no more than the proximity of two objects in space. Each avatar occupied a volume in space and could bump into each other, but there was no interaction or reaction due to the contact. The technology can support an avatar that receives a contact interaction to react to the interaction. In some embodiments, the reaction to the interaction can be an animation, sound, or other effect. The technology can also support ongoing interaction between parts of avatars. For example, the technology can enable one avatar to comb the hair of another avatar.
[0019] The technology includes a software development kit for building avatars that allows a user to define parts of the avatar as colliders (representations of objects for the purposes of physics collision determination). In some embodiments, parts of the avatar, such as hands or other appendages, may be automatically considered colliders. The technology also allows a user to define parts of the avatar as receivers, which are parts of the avatar that can trigger animations, sounds, or other effects when the receiver receives contact from a collider.
[0020] The technology also relates to methods for detecting collisions between colliders and receivers and enabling the resulting effects. Colliders define the shape of an object for the purposes of physical collisions. Colliders, which are generally invisible, do not need to be the exact same shape as the object, and in fact a rough approximation is more efficient and often indistinguishable in gameplay. In some instances, a collider does not need to behave as a solid object, but simply allows other colliders to pass through it.
[0021] A receiver can be a collider with a trigger that results in an effect. When an object enters the receiver's space, the receiver calls a function on it to execute the script configured for the receiver. The scripting system or physics engine can detect that a collision has occurred between the collider and the receiver and initiate an action.
[0022] The technology includes a software development kit for building avatars that allows a user to define portions of the avatar to support ongoing interaction. Some portions of the avatar are configured to have secondary motion, and such portions of the avatar can be manipulated by forces from colliders that are exerted on the portions of the avatar configured to have secondary motion. As discussed herein, a collider on a portion of the avatar (the same avatar or a different avatar) can interact with the portion of the avatar configured to have secondary motion to cause movement of the portion of the avatar configured to have secondary motion.
[0023] Primary motion refers to explicit movement of an avatar caused by explicit inputs to drive the movement, such as limb movement with explicit controls to move the limbs, or movement through space where the volume of space the avatar occupies is translated to a different coordinate location in the virtual world. Secondary motion refers to movement caused by environmental forces, such as physical forces incidental to the movement of parts of the avatar, wind blowing, or forces exerted by other avatars. These movements are generated by physical forces exerted on parts of the avatar that are configured with secondary motion attributes as a result of the primary motion. For example, inertial and gravity forces are exerted on hair, causing it to bounce as a result of the primary motion of walking.
[0024] In addition to supporting interactions between avatars and parts of avatars, the technology also solves other problems associated with supporting interactions between avatars, one of which is the issue of consent. Just because touch interactions are supported does not mean that users want their avatars to be touched. The essence of a virtual reality environment is that users can be intimately connected with their avatars. Often, users choose to view the world from a first-person perspective, and as a result, interactions in which one avatar touches another avatar are perceived as touching in a first-person perspective. Thus, just as some touching is unwelcome in the real world, it is also unwelcome in the virtual world. Thus, the technology provides a safety framework to declare the user's consent to touching and to disable touching if it is not desired.
[0025] Another problem that the present technology solves is improving the efficiency of the processing required to support such contact interactions. The technology utilizes an efficient mechanism for detecting when a contact interaction is taking place. Since detecting overlapping volumes is a difficult problem, an efficient mechanism has been devised to make this determination. Another area of efficiency improvement is in isolating secondary motion caused by contact interactions from the main thread used to render the virtual world, which allows secondary motion of these objects to be supported more efficiently.
[0026] These and other advantages of the present technology are further described herein.
[0027] 1 illustrates an exemplary virtual world platform 102 for playing and hosting multiplayer virtual reality (VR) experiences suitable for implementing the present technology. The virtual world platform 102 connects clients 104 via web services 110 and networking services 112 so that they can socially interact together in virtual worlds hosted by the virtual world platform 102.
[0028] The virtual world platform 102 includes clients 104, which are primarily instances of applications running on client devices 106. The clients 104 interact over a network connection with web services 110, which support the clients 104 by providing various services through one or more application programming interfaces (APIs). Some of the main services provided by the web services 110 relate to virtual world support through a world API 128, user profiles through a user API 132, trust and safety through a trust API 144, and complex avatars through an avatar API 136. The web services 110 generally store and provide long-term state information, among other functions.
[0029] The client 104 also interacts with a networking service 112, which provides communication services between the client 104, the networking service 112, and remote instances of the client 104 (not shown), and shares state information between each instance of the client 104. In particular, state information is received by the networking service 112 from multiple instances of the client 104 as each instance of the client 104 controls its local player 116. The networking service 112 can forward state information about each player to other instances of the client 104 when the local players 116 of each client instance are all engaged in gameplay in the same virtual world. The networking service 112 provides optimized packet routing through an optimized packet routing service 140 and provides moderation between one or more clients through a moderation service 142.
[0030] A client 104 is a runtime environment that executes on a particular client device 106. As used herein, we may refer to a client 104, a local client, and a remote client, all of which are instances of a client 104 executing on a respective client device 106. A particular instance of a client 104 has one particular user account logged into it. The local and remote clients are distinguished to describe how the client 104 processes first-person input from a user of the client device 106 on which the client 104 is executing and processes third-person input received from another user operating the client device on which the remote client is executing.
[0031] The client device 106 can be any computing device. The client 104 is particularly adapted for providing an immersive virtual reality experience through interactions that require a VR headset to be experienced, but the client 104 can also be executed by computers and mobile devices. Some virtual worlds or complex avatars may not be configured to work well with a particular device type, and thus, although the client 104 is operable on many platforms and devices, not all virtual worlds or complex avatars are available or have full functionality on all client devices 106.
[0032] User interface service 108 is one of the services that is part of client 104. User interface service 108 is configured to provide various user interface elements such as menus that display various user settings, available worlds, saved complex avatars, friends lists, etc. User interface service 108 can populate its menus through interactions with one or more APIs provided by web services 110, while other portions of the menus are loaded directly from user interface service 108.
[0033] The user interface services 108 can provide a menu of available worlds by calling the worlds API 128 to obtain a list of worlds that the user account logged into the client 104 is authorized to enter. The worlds API 128 can obtain all public worlds from the world asset database 130 and send the list to the client 104. Additionally, the worlds API 128 can request world IDs for any private worlds associated with the user account logged into the client 104, and retrieve the private worlds from the world asset database 130 and send them to the client 104. The user interface services 108 can receive user input via the hardware interface to navigate the worlds menu and receive a selection of a world to visit.
[0034] Another user interface provided by user interface services 108 relates to various user settings, which may relate to whether a human player is sitting or standing, settings for minimizing motion sickness for players prone to motion sickness when playing in VR, settings for selecting complex avatars, settings related to how the player is seen in the virtual world and by whom the player is seen, etc.
[0035] One notable user interface provided by the user interface services 108 is the Trust and Safety menu. The user interface services 108 can contact the user API 132 to retrieve current trust and safety settings from the user profile database 134 and display these settings in the Trust and Safety menu. The Trust and Safety menu provides a user account with the ability to determine which remote players 124 can see the user's avatars (local player 116) or be seen by the user's avatars when both are in the same world. For example, it may be desirable to avoid interacting with a new user of the virtual world platform 102 since they have not established a trust relationship within the virtual world platform 102. It may also be desirable to limit the functionality of the remote player's avatars that are handled by the instance of the client 104 that the local user is logged into. This is because some avatars may have malicious data embedded in them, or may be too complex to render without degrading the performance of the client device 106. For example, the user account may decide to turn off lights for remote avatars to avoid shaders, not allow custom animations, etc. In some embodiments, each of these options may be set based on how much the remote player is trusted: for example, a user account may allow friends' avatars to have full functionality, while other user accounts may only display basic avatar functionality.
[0036] The user interface services 108 may also provide options to mute or block specific remote players. Additionally, the user interface services 108 may provide a panic mode that audio-visually mutes anyone other than friends.
[0037] After a user selects a virtual world from a menu provided by user interface services 108, the client 104 can download an instance of the virtual world by calling the world API 128, which can retrieve the virtual world from the world in the world asset database 130 and send it to the client 104 for execution.
[0038] World assets are large binary files built for game engines such as UNITY using an editor with a software development kit (SDK) provided for use with the virtual world platform 102. When a user travels to a world, the world assets need to be downloaded from the world asset database 130. If there are people already in that instance of the world, the client 104 also needs a list of their avatars so that they can be rendered in the virtual world instance.
[0039] In some embodiments, functionality in the Worlds API 128 can verify that a user account has access to a requested world. Although a user account should only have the ability to see public worlds in user interface menus or only have knowledge of links to worlds that have been shared with the user account, the Worlds API 128 can verify that a user account is authorized to access a virtual world as a redundancy measure.
[0040] In addition to downloading an instance of a virtual world, the client 104 can also establish a session with the networking service 112 for a particular instance of a virtual world. The networking service 112 can provide information regarding the current state of the virtual world instance. For example, the networking service 112 can provide the client 104 with a list of remote avatars 126 that exist in the virtual world instance. The client 104 can then contact the avatar API 136 to download composite avatar assets for the list of remote composite avatars from the avatar asset database 138.
[0041] If the client 104 does not have assets for the local avatar 118, the client 104 can also contact the avatar API 136 to request and receive local avatar assets. An avatar asset is a single binary file that contains all of the texture, model, and animation data required to render the avatar. In some cases, it can include more complex features, such as data about particle systems and light sources, whether the avatar should follow or defy the laws of physics established in the virtual world, and if the avatar has non-standard movement dynamics. In some embodiments, the avatar asset includes colliders and receivers defined for parts of the avatar, or a tree of transforms that allow parts of the avatar to exhibit secondary motion behavior (e.g., dynamic bones or physics bones (aka phys.bones) are examples of systems that can be configured to cause parts of an avatar to exhibit secondary motion behavior).
[0042] The downloaded instance of the virtual world may be executed by the client 104 as a current world 120. The current world 120 may include the coordinates within the current world 120 where the local player 116 and each remote player 124 are located, as well as respective collision volumes of the space occupied by the respective local player 116 or remote player 124.
[0043] A local avatar 118 can be mapped to a local player 116, and each remote avatar 126 can be mapped to a respective remote player 124, allowing each player to appear as their own avatar in the current world 120. Movement of the remote avatars 126 is handled by the client 104 by receiving state data regarding each remote avatar / player and rendering the movement or sound.
[0044] The VR tracking service 114 is associated with a client 104 running on a client device 106 that has access to VR tracking peripherals. For example, some VR headsets have cameras (integral or external) for tracking the player's limbs. Many VR headsets can be paired with controllers that can report the position of the user's hands in space. Some client devices 106 also include other peripherals configured to do full skeletal tracking. The VR tracking service 114 can fuse all VR inputs connected to the client.
[0045] The VR tracking service 114 can map the blended VR input to the local player 116, allowing the local player 116 to interact in and with the current world 120. The local player 116 can in turn interact with a local avatar 118, mapping the local avatar 118 to the local player and causing the local player 116 to appear as his or her avatar.
[0046] In some embodiments, there is a variety of which parts of the user's body are tracked by the VR tracking service 114. Some users may have full skeleton tracking, while many users may only have the ability to do hand tracking. To accommodate such differences in possible client device 106 hardware capabilities, the local player 116 can derive parts of the skeleton that are not tracked by the VR tracking service 114. For example, even if the VR tracking service 114 only provides information about the tracking of the user's hands, the local player can still derive the user's full skeleton and move parts of the skeleton to correspond to the movement of the hands. In this way, the avatar's hands do not move in isolation from the rest of the avatar.
[0047] The local player 116 is an entity that moves around the environment in the current world 120. It can pick up and place things. It has no animations and is a collision volume. It can do anything in the world, but it has no appearance and does not need to be animated.
[0048] The local player is further connected to a networking layer, shown as runtime networking services 122, which broadcasts state information about the local player 116 to other users within the current instance of the world 120 over the network.
[0049] The local player 116 and the remote player 124 are similar in that they are collision volumes that move through the environment of the current world 120. The main difference is that the local player 116 is controlled by the client 104, and the user of the client 104 is authoring the experience. In contrast, the remote player 124 is a playback mechanism that represents actions that are broadcast to clients 104 that represent other players present in the current world 120.
[0050] As described above, the local avatar 118 is overlaid with the local player 116 to give the user a visual appearance. Actions by the local player 116 are animated as the local player interacts with the current world. For example, the local player 116 can interact to pick up an object in the current world 120, but without the local avatar 118, the object would appear to be floating in the air. When the local avatar 118 is overlaid on top of the local player 116, the object appears to be held by the avatar's hand.
[0051] The remote player 124 and remote avatar 126 operate similarly to a local player, except for where the input that controls the remote player 124 comes from. The remote player 124 and remote avatar 126 are the playback devices for the state information that the runtime networking services 122 receives from the networking services 112. Although Figure 1 shows only one remote player 124 and remote avatar 126, there may be many.
[0052] Client 104 may also support contact interactions between avatars, between a portion of an avatar and another portion of the same avatar, or between a portion of an avatar and an object in the virtual world. To detect these interactions, client 104 may be configured to detect collisions between the objects using collision detection system 148. In some embodiments, collision detection system 148 may be a wideband phase collision detection system.
[0053] Additionally, the current world 120 has functionality that requires a network: the current world 120 may have objects, such as scissors or light switches, that the user can pick up, and the objects need to broadcast their state over the network so that other users in the current world 120 can see the current state of the object.
[0054] Each of the local player 116, the current world 120, and the remote player 124 are connected to a runtime networking service 122. The local player 116 primarily sends updated state information of the local player 116 to remote instances of clients 104 that are also running the same virtual world. The current world 120 can send and receive state information about instances of the virtual world. The current world running on the client 104 sends state information when a state change is owned by the local player 116 and receives state information when a state change is owned by the remote player 124.
[0055] Networking services 112 are the network side portion of the networking layer of virtual world platform 102. In some embodiments, part of networking services 112 is provided by a networking plug-in, such as the PHOTON networking engine, that broadcasts state information to all users within an instance of a virtual world.
[0056] In addition to general broadcasting of state information to all users interacting with a virtual world instance, the optimized packet routing service 140 provides more advanced capabilities to provide an enhanced user experience and implement other virtual world platform 102 features such as trust and security configurations.
[0057] For example, to provide an enhanced user experience, the optimized packet routing service 140 can filter audio packets coming from remote players 124 that may be far away from the local player 116 in the current instance of world 120. Without such optimization, a remote player 124 that is not interacting with or visible to the local player may receive audio packets from dozens or hundreds of remote players 124, making it difficult to communicate with any subset of the remote players 124.
[0058] In another example, the optimized packet routing service 140 can implement trust and safety settings. As discussed above, the trust and safety settings can specify certain user accounts or groups of user accounts that are filtered out so that they cannot interact with the local player 116 or that have limited interaction with the local player 116. The optimized packet routing service 140 can call the trust API 144 to learn a list of remote players 124 that may need to undergo some level of filtering or blocking of network traffic to or from the client 104 for the local player 116 that has the trust and safety settings.
[0059] The trust API 144 can determine which remote players 124 should be blocked for the local player 116 or which remote players 124 should have aspects of their avatars limited in complexity. Some of these decisions are based on logic and rules that categorize the remote players 124 based on the amount and type of past interactions with the virtual world platform 102. The trust API 144 can make these decisions by using settings stored in the user profile of the local player 116 and comparing these settings to data stored in the user profile of the remote players 124.
[0060] Another of the networking services 112 is the moderation service 142, which can provide conflict resolution and access control. For example, before a user accesses a world, especially a private world, the moderation service 142 can call the world API 128 to verify that the user can enter the world. In another example, there may be a case where two different users try to request control of an object in the virtual world at approximately the same time. The moderation service 142 can handle such types of conflicts by selecting a particular user to control the object until the user relinquishes control of the object. The user controlling the object can broadcast a packet informing the remote players 124 of the state of the object.
[0061] In some embodiments, the client 104, the virtual world, and the complex avatars can be configured to run on a particular game engine, particularly one that supports three-dimensional (3D) environments. Two common game engines include UNITY and UNREAL ENGINE.
[0062] In some embodiments, to be supported by the virtual world platform 102, virtual worlds and complex avatars need to be developed in compliance with a software development kit (SDK). For example, a complex avatar requires specific scripts to be usable by the virtual world platform 102. In another example, there may be many requirements that must be followed to play the animations of the avatar. In some embodiments, the SDK may define other details necessary to support a particular client device. For example, the SDK may define specific shaders to be used if the avatar is to be used with an OCULUS QUEST VR headset.
[0063] In some embodiments, the SDK requires that the virtual world utilize a particular coding language to ensure that the world has compliant behavior. For example, the SDK may require that behavior within the world be defined using UDON, a programming language specific to a particular virtual world platform 102, VR Chat. In some embodiments, the programming language facilitates worlds built using the programming language to comply with file access protections provided by the virtual world platform 102. For example, a world cannot read or write anything to a hard drive, and only approved web pages can be rendered in a world on the virtual world platform 102.
[0064] In some embodiments, the virtual world platform 102 also includes a simplified avatar service 146. As described herein, the simplified avatar service 146 can create simplified versions of complex avatars and store avatar assets for the simplified versions of the complex avatars in the avatar asset database 138.
[0065] Although the virtual world platform 102 is well suited for implementing the present technology, those skilled in the art will appreciate that the technology can be used in other environments.
[0066] 2 illustrates an exemplary quick menu 202 in accordance with some aspects of the present technology. In particular, the quick menu 202 can be displayed by the user interface service 108 on the client 104 at any time or place in the virtual world platform 102.
[0067] The quick menu 202 includes a quick links 204 section that contains many commonly used menu options, such as menus for browsing worlds, avatars, and friends, and a safety menu 208 for setting safety settings for the user's profile.
[0068] The trust and safety menu 208 provides a user account with the ability to determine which remote players 124 can see or be seen by the user's avatars (local player 116) when both are in the same world. For example, it may be desirable to avoid interacting with newer users of the virtual world platform 102 because they have not yet established a trust relationship within the virtual world platform 102. It may also be desirable to limit the functionality of remote player avatars handled by the instance of client 104 in which the local user is logged in. This is because some avatars may be embedded with malicious data or may be too complex to render without degrading the performance of the client device 106. For example, the user account may decide to turn off lights on remote avatars to avoid shaders, not allow custom animations, etc. In some embodiments, each of these options may be set based on how much the remote players are trusted. For example, the user account may allow friends' avatars to have full functionality while others can only view basic avatar functionality.
[0069] The user interface services 108 may also provide options to mute or block specific remote players. Additionally, the user interface services 108 may provide a panic or safe mode 210 to audio-visually mute anyone other than friends.
[0070] The quick menu 202 can also include a quick actions 206 section to provide commonly used actions in a convenient location. Some example quick actions include an action to go to the home world, an action to resume from the world you were last in, an action to select another user's avatar (for personal communication, copying the avatar or other functionality), and an interaction toggle 216 to turn on or off interaction between the user and the local player 116.
[0071] The quick menu 202 also includes a dock 212 that provides access to several common features such as a virtual camera, volume settings, and a settings menu, among other features.
[0072] Throughout this description of the technology, reference is made to avatars, users, and user accounts. Those skilled in the art will appreciate that an avatar is a representation of a user in a virtual environment, and that configuration attributed to an avatar may be configuration attributed to a user account that is applied to the avatar. Thus, the term avatar may in some cases describe an aspect of a user account. Regardless of which term is used, the appropriate meaning will be understood by those skilled in the art.
[0073] 3 illustrates an example method for triggering an action in response to a collision with a first avatar and a second avatar. Although the example method illustrates a particular sequence of operations, the sequence may be altered without departing from the scope of the present disclosure. For example, some of the operations illustrated may be performed in parallel or in a different order without substantially affecting the functionality of the method. In other examples, different components of an example device or system implementing the method may perform functions substantially simultaneously or in a particular order.
[0074] As described above, this technology can support an avatar that receives a touch interaction to react to the interaction. In some embodiments, a reaction to an interaction may be an animation, a sound, or other effect.
[0075] The technology includes a software development kit for building avatars that allows a user to define portions of an avatar as colliders. In some embodiments, portions of an avatar, such as parts of a hand or other appendage, may be automatically considered colliders. The technology also allows a user to define portions of an avatar as receivers. A receiver is a portion of an avatar that can trigger animations, sounds, or other effects when the receiver receives contact from a collider. The technology also allows a user to define portions of an avatar that are configured to exhibit secondary motion behavior. The secondary motion behavior can be triggered or effected by contact by a collider.
[0076] The present technology also relates to a method for detecting collisions between a collider and a receiver and effecting the resulting effects, as described in the method of FIG.
[0077] According to some examples, the method includes detecting a collision between a collider configured on a first avatar and a receiver configured on a second avatar, at block 302. For example, the client 104 shown in FIG. 1 may detect a collision between a collider configured on a first avatar and a receiver on a second avatar. The first avatar may be the local avatar 118 or a remote avatar 126. The second avatar may be the remote avatar 126. In other words, the collision may occur between a local avatar and one or more remote avatars, or may occur between two or more remote avatars.
[0078] In some embodiments, as described in more detail with respect to Figures 5A and 5B, colliders and receivers may be turned on or off according to a set of rules that govern mutual agreement regarding interaction and contact between avatars.
[0079] In some embodiments, collisions can be detected by the wideband phase collision detection system 148. For example, the wideband phase collision detection system 148 can be configured to divide the rendered area of the virtual world into a grid. In one example, the grid can be a grid area covering an area of 10m by 10m, but any suitable area can be used. Each cell in the grid is entered into a dictionary for quick lookup by a hash created from the XYZ coordinates in the grid space of each grid. Within each grid, the wideband phase collision detection system 148 creates a sorted list in a first-in-first-out memory structure of all objects that are arranged in order across the axes in the area in the grid. For example, the objects can be arranged along the X axis as they occur within the area in the grid. The wideband phase collision detection system 148 determines whether each object is involved in a collision by evaluating the objects one at a time in the sorted order. Evaluating the object can include determining whether the object is of a nature that is affected by the collision. For example, if the object is not a collider or receiver, the collision may not be relevant to the object, and processing of the object can be discontinued. However, if the object is susceptible to a collision, the broadband phase collision detection system 148 determines whether the object may overlap or is overlapped by other objects.
[0080] In some embodiments, detecting a collision by the client 104 may also include determining physical attributes associated with the collision. For example, when a collision is detected by the wideband phase collision detection system 148, the client 104 may determine physical attributes associated with the collision. The physical attributes may include attributes such as physical forces, such as force, velocity, mass, etc. of the colliding objects. In some embodiments, an action may depend on the physical attributes. For example, if the collision was the result of a high-five action, a sound effect may be generated only if the collider is moving at a velocity equal to or greater than a threshold value.
[0081] According to some embodiments, the method includes reporting the detected collision to the contacted player at block 304. For example, a broadband phase collision detection system 148 executing on the client 104 shown in FIG. 1 may report the detected collision to an avatar controller, such as the local player 116 or the remote player 124 shown in FIG.
[0082] According to some examples, the method includes, at block 306, updating a parameter on an avatar associated with the receiver in response to the detected collision. For example, an avatar controller, such as local player 116 or remote player 124 shown in FIG. 1, can update a parameter on an avatar associated with the receiver in response to the detected collision. For example, if remote player 124 is the receiver of the contact interaction, remote player 124 can update a parameter on remote avatar 126. In some embodiments, the parameter can be a binary parameter indicating that a collision has occurred. In some embodiments, the parameter can describe attributes of the contact interaction, such as the type of collider, the physics of the collision (such as the velocity of one of the objects or the force of the collision), etc.
[0083] A receiver can be linked to an associated response that is executed when the receiver becomes active. The response can be embodied in data or algorithms that are part of the avatar package. Non-limiting examples or responses that can be associated with a receiver can be to play an animation, play a sound effect, or change state. For example, in a high-five interaction between two avatars, the receiver on one of the avatars can be configured to trigger a slap sound, animate a custom change or appearance change, or trigger any type of animation. The response can be triggered through an update of the avatar's parameters.
[0084] In some embodiments, mutual agreement between the parties to a collision may be confirmed after the collision is reported to an avatar controller (such as the local player 116 or remote player 124) and before the parameter change is reported to the avatar (such as the local avatar 118 or the remote avatar 126).
[0085] According to some examples, if there is mutual agreement, the method includes triggering an action at block 308. For example, the client 104 shown in FIG. 1 may trigger the action. In some embodiments, the action is triggered by an animation controller that animates an avatar (local avatar 118 or remote avatar 126) based on data and parameters associated with the avatar. Some non-limiting examples or responses that may be associated with the receiver may be to play an animation, play a sound effect, or cause a state change to occur.
[0086] According to some examples, the method includes, at decision block 310, determining whether the action is associated with a permanent state change of the second avatar. For example, the client 104 shown in FIG. 1 can determine whether the action is associated with a permanent state change of the second avatar. A permanent state change can include any action beyond a played animation. For example, the avatar can change its appearance (persistently, until changed by the player or another interaction, or for a set duration) and continue interacting with the changed appearance.
[0087] According to some examples, the method includes sending the state change notification to a remote instance of an application that renders the first avatar and the second avatar, at block 314. For example, the client 104 shown in FIG. 1 may send the state change notification via the networking service 112 to the remote instance of an application that renders the first avatar and the second avatar.
[0088] 4 illustrates an example method for supporting interactions that affect secondary motions of parts of an avatar. Although the example method depicts a particular sequence of operations, the sequence may be altered without departing from the scope of the present disclosure. For example, some of the operations depicted may be performed in parallel or in a different order without substantially affecting the functionality of the method. In other examples, different components of an example device or system implementing the method may perform functions substantially simultaneously or in a particular order.
[0089] According to some examples, the method includes instantiating one or more jobs as part of a job system. A job may be responsible for processing tasks such as evaluating collisions, determining secondary motion behavior as a result of the collisions, etc. The job system may perform its tasks by assigning the job to one or more threads other than a primary thread used to render a larger game environment (virtual world). The job may be compiled at runtime for execution on the thread other than the primary thread. In some embodiments, the creation of the job is performed utilizing a BURST COMPILING feature of the UNITY rendering engine.
[0090] The execution of jobs is handled by a job system, which assigns its own priority to the order in which jobs are executed. Thus, in some embodiments, the client 104 can check that the job has been completed by the job system when a frame needs to be rendered. If the job has not been completed, the method includes instructing the job system to terminate the job.
[0091] According to some examples, the method includes loading parameters for an avatar at block 402. For example, the client 104 shown in FIG. 1 may load parameters for an avatar (e.g., a remote avatar or a local avatar 118). As described with respect to FIG. 1, the avatar may be defined by an avatar asset. An avatar asset is a single binary file that contains all of the texture, model, and animation data required to render the avatar. In some examples, more complex features may be included, such as data about particle systems and light sources, whether the avatar should follow or defy the laws of physics established in the virtual world, and if the avatar has non-standard movement dynamics. An avatar asset may also define portions of the avatar that are designated as colliders and receivers. An avatar asset may also define portions of the avatar for which secondary motion behaviors are set. An avatar asset may define a complete skeleton for a humanoid or non-humanoid avatar, and any portion of the avatar may be configured as a collider or receiver. Additionally, any portion of the avatar may have secondary motion behaviors set. However, secondary motion behaviors are typically only used for flexible or malleable parts of an avatar, and are not typically used for rigid objects, such as the avatar's main skeleton, since rigid objects are less likely to respond with perceptible movement in response to small forces like most contact interactions.
[0092] The portions of the avatar that are configured for secondary motion are defined by a tree of transforms. For example, the root of the transform can be the avatar's head, and the branches from the root can include a hair strand (or a collection of hair strands). The hair strands can be represented by multiple additional branches. Each branch can be associated with different properties, such as whether the portion of the avatar associated with the tree of transforms is pulled, whether it has spring-like properties, how susceptible it is to inertial forces, how much it should be affected by gravity, etc. In some embodiments, the transforms are configured to be compiled at runtime. More details regarding the trees of transforms that define the portions of the avatar that exhibit secondary motion behaviors are described with reference to Figures 10 and 11.
[0093] According to some examples, the method includes storing parameters of the avatar in a memory, including the portion of the avatar configured to exhibit the secondary motion behavior, at block 404. For example, the client 104 shown in FIG. 1 may store parameters of the portion of the avatar in a memory accessible by the job system.
[0094] In some embodiments, the memory structure that stores information about the transform that defines the portion of the avatar that exhibits secondary motion behavior is stored in a memory structure accessible by threads controlled by a job system that executes on multiple cores of a multi-core processor. In some embodiments, the memory structure is a flat memory structure such as the NATIVE CONTAINER provided by UNITY, which allows access to data by secondary threads that execute jobs and a main thread that is responsible for rendering the virtual world and objects therein.
[0095] According to some examples, the method includes detecting that the avatar has an active contact acceptor configured to accept contact, at block 406. For example, the client 104 shown in FIG. 1 may detect that the avatar has an active contact acceptor configured to accept contact.
[0096] In some embodiments, a contact acceptor is configured to only receive interactions from designated colliders, which may be a class of colliders, such as finger or hand colliders, which may be on a particular avatar, or which may be on a category of avatars, such as humanoid avatars.
[0097] According to some examples, the method includes detecting an interaction between a collider and a portion of an avatar configured to exhibit a secondary motion behavior, at block 408. For example, the client 104 shown in FIG. 1 may detect an interaction between a collider and a portion of an avatar configured to exhibit a secondary motion behavior.
[0098] In some embodiments, the detection of interactions between colliders and parts of the avatar configured to exhibit secondary motion behavior is performed on a frame-by-frame basis. The detection of interactions between colliders and parts of the avatar configured to exhibit secondary motion behavior may be performed by the broadband phase collision detection system 148 discussed with respect to FIG. 3. The broadband phase collision detection system may also be processed by a job under the control of the job system. The collision job only determines the approximation of a collision and is not guaranteed to affect the secondary motion. Possible collisions detected by the collision job can be passed to a secondary motion job that actually determines whether the collider is actually touching the part of the avatar configured to exhibit secondary motion behavior and whether it needs to move as a result. This is for efficiency reasons, as it is faster to have all of the collision data inside the secondary motion job, since the collision data is also needed for the movement calculations.
[0099] According to some examples, prior to animating the motion of the portion of the avatar configured to exhibit a secondary motion behavior when manipulated to move by the collider according to the set secondary motion, the method includes determining, at decision block 410, whether there is mutual agreement between the pair of the first avatar and the second avatar to allow the animated motion. For example, the client 104 shown in FIG. 1 may determine whether there is mutual agreement between the pair of the first avatar and the second avatar to allow the animated motion. Further details regarding mutual agreement are described with respect to FIG. 5A and FIG. 5B. If there is no mutual agreement between the avatars, the method ends at 412.
[0100] According to some examples, if there is mutual agreement between the avatars, the method includes reporting the detected interaction to an avatar controller, at block 414. For example, the wideband phase collision detection system 148 can report the detected interaction to an avatar controller, such as the local player 116 or the remote player 124.
[0101] According to some examples, the method includes determining that an interaction between a collider and a portion of the avatar configured to exhibit a secondary motion behavior triggers a physics simulation of a tree of transforms, at block 416. For example, the client 104 shown in FIG. 1 may determine that an interaction between a collider and a portion of the avatar configured to exhibit a secondary motion behavior triggers a physics simulation of a transform.
[0102] According to some examples, the method includes determining whether the interaction is a grab interaction at decision block 418. For example, the client 104 shown in FIGURE 1 may determine whether the interaction is a grab interaction. A grab interaction may occur when a portion of an avatar is designated as grabbable.
[0103] If the interaction is a grab, according to some examples, the method includes assigning control over the grabbed portion of the avatar at block 420. For example, the client 104 shown in FIG. 1 may assign control over the grabbed portion of the avatar. The grabbed portion of the avatar has an attachment point at the location where the grab portion of the avatar is grabbed. Information reporting that the grab has occurred is also sent over the network to a remote instance of the client 104. Further details regarding grab interactions are discussed with respect to FIG.
[0104] According to some examples, the method includes animating, at block 422, the motion of the portion of the avatar manipulated to move by the collider according to the configured secondary motion. For example, the client 104 shown in FIG. 1 may animate the motion for the portion of the avatar manipulated to move by the collider according to the configured secondary motion (configured by a tree of transforms). The execution of the job utilizes local physics, which is limited to the interaction between the collider and the properties of the tree of transforms and does not affect other objects in the virtual world. As described above, the job is executed on a thread other than the main thread, resulting in the animation of the motion of the portion of the avatar as manipulated to move by the collider according to the configured secondary motion.
[0105] In some embodiments, a portion of an avatar configured to exhibit a secondary motion behavior can remain pinned as a result of manipulation by a collider. According to some examples, the method includes determining whether the portion of the avatar was pinned at decision block 424. For example, the client 104 shown in FIG. 1 can determine whether the portion of the avatar remained pinned. A portion of an avatar configured to exhibit a secondary motion behavior can remain pinned when an avatar with a collider presses a trigger input to pin the portion of the avatar.
[0106] According to some examples, the method includes sending a state change notification with information about the state change to a remote instance of an application that renders the first avatar and the second avatar at block 428. For example, the client 104 shown in FIG. 1 can send a state change notification with information about the state change to a remote instance of an application that renders the first avatar and the second avatar. For example, the information about the state change can be information about a pinned state of a portion of the avatar, or information that a portion of the avatar has been grabbed and which avatar has control over the portion.
[0107] According to some examples, the method includes returning the portion of the avatar to its original state if the portion of the avatar is determined to be unpinned in block 426. For example, the client 104 shown in FIG. 1 may return the portion of the avatar to its original state when the portion of the avatar is determined to be unpinned.
[0108] While Figure 4 has been described in the context of a first avatar interacting with a second avatar, manipulation of the portions of the avatar configured to exhibit secondary motion behaviors can be from the same avatar. In some embodiments, an avatar may wish to use its hands to manipulate its hair, tail, ears, clothing, etc. All of the aspects described with respect to Figure 4 function similarly when the portions of the avatar configured to exhibit secondary motion behaviors are manipulated through self-interaction or avatar-to-avatar interaction, except that in the case of self-interaction, mutual consent is not required.
[0109] 5A, 5B, and 5C illustrate an example method for determining whether avatar contact interaction is permitted. Although the example method illustrates a particular sequence of operations, the sequence may be modified without departing from the scope of the present disclosure. For example, some of the operations illustrated may be performed in parallel or in a different order without substantially affecting the functionality of the method. In other examples, different components of an example device or system implementing the method may perform functions substantially simultaneously or in a particular order.
[0110] The technology is intended to support interaction between avatars or parts of avatars. It also provides a mechanism to ensure that both participants of the interaction consent to the interaction. Just because touch interaction is supported by an avatar does not mean that the user wants his avatar to be touched. The nature of a virtual reality environment is that the user is intimately connected to his avatar. Since users often choose to see the world from a first-person perspective, an interaction in which one avatar touches another avatar may be perceived as a touch from a first-person perspective. To the user, the touch may be perceived the same as in real life. Just as there are touches that are unwelcome in the real world, there are also touches that are unwelcome in the virtual world. Therefore, the technology provides a secure framework to declare the user's consent to touch and to disable touch if the touch is not desired. The important thing is that consent must be obtained from all parties involved in the touch.
[0111] According to some examples, the method includes receiving avatar contact settings for a first user and at least one second user in a world instance, at block 502. For example, the client 104 shown in FIG. 1 may receive avatar contact settings for a first user and at least one second user in a world instance.
[0112] The contact settings for an avatar include contact categories. Every player configures in their user profile whether or not they allow contact using the contact categories. The content categories are: (1) allow avatar contact interactions with all avatars, (2) allow avatar contact interactions only with avatars in the friend list, and (3) do not allow any avatar contact interactions.
[0113] Avatar contact settings also include allow lists and block lists to specify certain users / avatars that are exempt from any determinations made due to contact categories. For example, users on the local user's allow list are categorically and affirmatively allowed to interact with the local user's avatars if the remote user's settings permit such interaction. Similarly, users on the local user's block list are categorically not allowed to interact with the local user's avatars even if the contact categories normally permit the interaction. The allow and block lists of specified avatars override the contact categories.
[0114] Regardless of any contact settings configured for a user account, the user account can also turn on / off interactions with all other avatars using the interaction toggle 216 shown in Figure 2. Thus, a user account that has a user account setting to interact with all other accounts or to interact with all friends can still utilize the interaction toggle 216 to quickly turn off contact interactions. Although the interaction toggle 216 can override any other contact settings associated with the user account to turn off interactions, if the interaction toggle 216 is set to allow contact interactions, the interactions allowed are limited by the interactions configured for the user account.
[0115] According to some examples, the method includes, at decision block 504, determining whether there is mutual agreement between the pair of avatars to allow avatar contact interaction. For example, the client 104 shown in FIG. 1 may determine whether there is mutual agreement between the pair of users to allow avatar contact interaction. The determination of whether mutual agreement exists is updated each time a user joins or leaves a world, or each time any user in the world changes an avatar setting or contact interaction setting. In some embodiments, the determination of whether mutual agreement exists is performed without considering whether an interaction is set for the avatar. A user may change his or her avatar at any time, but the agreement remains the same until the mutual agreement determination is updated by the user leaving or joining the world.
[0116] The determination of whether there is mutual agreement is the product of the combination of the contact settings of the pair of users. FIG. 6 illustrates an exemplary method of determining whether there is mutual agreement between users in a pair to allow a supported contact interaction. The method first determines, in decision block 602, whether a first user in the pair allows contact with a second user in the pair. The method then determines, in decision block 604, whether the second user in the pair allows contact with the first user. If and only if the answer to both decision blocks 602 and 604 is yes, then the contact interaction is allowed in block 606. If the answer to either decision block 602 or decision block 604 is no, then the contact interaction is not allowed in block 608. Although FIG. 6 (and much of the discussion associated with FIGS. 5A, 5B, and 5C) is in terms of a pair of interacting users, it should be understood that this can be extended to many users that can participate in a particular contact interaction. If any user that is to be part of a contact interaction does not allow the contact interaction with the other party to the interaction, then the group of users cannot engage in the contact interaction together.
[0117] According to some examples, the method includes, at decision block 506, determining whether either of the avatars in the avatar pair is configured with a receiver associated with avatar contact interaction. For example, the client 104 shown in FIG. 1 may determine whether either of the avatars in the avatar pair is configured with a receiver associated with avatar contact interaction. This step is performed by the client 104 for all avatar pairs in the local world. The purpose of this step is to identify all pairs of avatars that can interact. In some embodiments, for efficiency reasons, this step may be performed only for avatars that are actually rendered by the client 104 in the world instance, since the client 104 does not render animations for avatars in worlds that are not rendered in its field of view. When it is determined in decision block 506 that neither avatar in the pair of avatars has a receiver or portion of the avatar configured to exhibit a secondary motion behavior, the client 104 may determine in block 508 that no contact interaction exists between the pair of avatars because neither avatar has a way to receive a contact interaction.
[0118] Effectively, decision block 506 is used to determine whether either avatar in the pair of avatars supports touch interaction.
[0119] As mentioned above, with respect to FIG. 3, the client 104 is responsible for detecting and animating avatar interactions locally, so while the client 104 cannot control the input received in relation to a remote avatar, it is responsible for determining whether any animations or effects should be played for a remote avatar due to an interaction between two remote avatars or between a local avatar 118 and a remote avatar 126.
[0120] FIG. 7 shows an example table of example touch settings and whether or not touch interaction is permitted by those settings.
[0121] In line 702, both users have their contact categories set to allow all interactions, so it doesn't matter if the users are considered friends or not, because both users allow interactions with all others. Contact is allowed.
[0122] In row 704, one user allows contact interactions only with friends, while the other user allows interactions with all users. Because the user is not a friend (e.g., not in the user's account's friend list), no interaction is allowed. However, in row 706, the contact category settings for the same user also allow contact interactions because the user is a friend.
[0123] In row 708, one of the users has not allowed touch interactions, so the other users' settings are irrelevant: touch interactions are not allowed.
[0124] In line 710, the first user allows contact interaction with any user other than the user account associated with the second avatar. Thus, the first user does not allow contact interaction with the second user, so no contact is allowed.
[0125] In line 712, the first user does not allow touch interactions with any users other than the user account associated with the second avatar. The second avatar allows all interactions. Therefore, touch is allowed because both avatars allow touch interactions with each other.
[0126] In line 714, the first user does not allow touch interactions with any users other than the user account associated with the second avatar. The second user does not allow touch interactions with any avatars other than the user account associated with the first avatar. Thus, touch is allowed because both users have allowed touch interactions with each other.
[0127] Returning to the discussion of FIG. 5A, while thus far the determination of whether contact interaction is permitted between particular users has been described as being made by client 104, in some embodiments the determination of whether there is mutual agreement between a pair of users to permit avatar contact interaction may be made by a network service, such as moderation service 142 or another service.
[0128] In some embodiments, an invisible boundary may be created when a pair of non-mutually consenting avatars are within a threshold distance of each other to ensure that a contact interaction is not even attempted, in some embodiments, a remote avatar with which interaction is not allowed may be removed from the local player's view of the scene when the remote avatar approaches a threshold distance.
[0129] According to some examples, the method includes storing a determination of whether touch interaction is allowed between respective pairs of avatars in the world instance at block 510. For example, the client 104 shown in FIG. 1 may store a determination of whether touch interaction is allowed between respective pairs of avatars in the world instance. For example, once a determination is made of whether touch interaction is allowed between any pair of avatars in the world instance, this may be recorded in a table and saved for later determination and use at block 512.
[0130] According to some examples, the method includes, at block 512, displaying an indicator associated with at least one remote avatar indicating an avatar contact interaction status indicating whether avatar contact interaction is permitted between the local avatar and a remote avatar associated with the indicator. For example, the client 104 shown in FIG. 1 may display an indicator associated with at least one remote avatar indicating an avatar contact interaction status. In some embodiments, it may be useful to identify remote avatars 126 with which the local avatar 118 can interact with a user associated with the local avatar. For example, without any indication, a user controlling the local avatar 118 may move around trying to participate in contact interactions with remote avatars that do not support contact interactions or do not allow contact interactions with the local avatar. This may result in a degraded user experience. Thus, remote avatars that support contact interactions and allow the local avatar 118 to engage in contact interactions may be identified to a user associated with the local avatar 118. The indicator may be a symbol or color of a nameplate associated with the remote avatar 126. The indicator may be that the location of the receiver on the remote avatar 126 is highlighted or otherwise indicated when the remote avatar 126 allows contact interaction with the local avatar 118. In some embodiments, the indicator associated with the remote avatar 126 may also indicate that avatar contact interaction is not allowed.
[0131] According to some examples, the method includes detecting a collision between a collider configured on the first avatar and a receiver on the second avatar at block 514. For example, the client 104 shown in Figure 1 may detect a collision between a collider configured on the first avatar and a receiver on the second avatar. The collision may be detected by a broadband phase collision detection system 148 in a manner similar to that described with respect to block 302 of Figure 3.
[0132] According to some examples, the method includes reporting the detected collision to an avatar controller at block 516. For example, the client 104 shown in FIG.
[0133] The method continues at block 518 of FIG. 5B.
[0134] According to some examples, the method includes verifying that there is mutual agreement between the pair of users after detecting a collision between a collider configured on the local avatar and a receiver on the remote avatar at block 522. For example, the client 104 shown in FIG. 1 may verify that there is mutual agreement between the pair of users after detecting a collision between a collider configured on the local avatar and a receiver on the remote avatar. Although mutual agreement was already determined at decision block 504, in some embodiments the client 104 may verify that mutual agreement still exists before triggering an action.
[0135] According to some examples, if mutual agreement does not exist between the pair of users, the method includes terminating the process related to the avatar contact interaction, at block 532. For example, the client 104 shown in FIG. 1 may terminate the process related to the avatar contact interaction.
[0136] In some embodiments, an invisible boundary may be created when a pair of non-mutually consenting avatars are within a threshold distance of each other to ensure that a contact interaction is not even attempted, in some embodiments, a remote avatar with which interaction is not allowed may be removed from the local player's view of the scene when the remote avatar approaches a threshold distance.
[0137] In some cases, user settings can also regulate what types of animations a user wants to engage with. For example, a user may want to engage with other avatars in touch interactions, but filter out vulgar or suggestive content. In such an embodiment, animations that are preferred by the recipient may be labeled with a content flag. This is another way that user rights, privacy, and boundaries can be placed under the control of the user receiving the content.
[0138] According to some examples, the method includes determining that an animation associated with the avatar touch interaction is labeled with a content flag at block 524. For example, the client 104 shown in FIG. 1 may determine that an animation associated with the avatar touch interaction is labeled with a content flag.
[0139] According to some examples, the method includes determining that a user account associated with the local avatar is associated with a setting to filter content with content flags, at block 526. For example, the client 104 shown in FIG. 1 may determine that a user account is associated with a setting to filter content with content flags.
[0140] According to some examples, the method includes terminating the avatar touch interaction because it has been labeled with the filtered type of content, at block 528. For example, the client 104 shown in FIG. 1 may terminate the avatar touch interaction because it has been labeled with the filtered type of content.
[0141] According to some examples, if the contact interaction is allowed and animation resulting from the contact interaction is not filtered due to the presence of a content flag, the method includes triggering an action at block 530. For example, the client 104 shown in FIG. 1 may trigger the action by playing an animation preferred by the recipient or by executing a transform associated with a portion of an avatar configured to exhibit a secondary motion behavior.
[0142] After receiving the avatar settings at block 502 of FIG. 5A, the method proceeds at block 520 to FIG. 5C, which illustrates an alternative and / or additional method for processing content labeled with a content flag.
[0143] According to some examples, the method includes determining that a remote avatar associated with the avatar contact interaction is labeled with a content flag at block 534. For example, the client 104 shown in FIG. 1 may determine that a remote avatar associated with the avatar contact interaction is labeled with a content flag.
[0144] According to some examples, the method includes determining that the local avatar is associated with a setting that filters content with a content flag, at block 536. For example, the client 104 shown in FIG. 1 may determine that the local avatar is associated with a setting that filters content with a content flag.
[0145] According to some examples, the method includes downloading an alternative remote avatar not associated with a content flag at block 538. For example, the client 104 shown in FIG. 1 may download an alternative remote avatar not associated with a content flag by interacting with the avatar API 136 to request the alternative asset. Or, in some embodiments, certain content within an avatar asset labeled with a content flag may not be downloaded with the remainder of the remote avatar and its functionality intact, except for the portion associated with the content flag.
[0146] 8 is a diagram illustrating a portion of an avatar that is composed of one or more colliders. The technology includes a software development kit for building avatars that allows a user to define portions of the avatar as colliders and receivers.
[0147] In some embodiments, some parts of an avatar may be automatically considered colliders. The technology also allows the user to define parts of an avatar as receivers. Any part of an avatar may be defined as a collider or receiver, including parts of humanoid and non-humanoid avatars.
[0148] Colliders define the shape of an object for the purposes of physical collisions. Colliders, which are generally invisible, do not need to be the exact same shape as the object, and in fact, in gameplay, a rough approximation is more efficient and often indistinguishable. In some instances, colliders do not need to behave as solid objects, but simply allow other colliders to pass through them. A receiver can be a collider that is made up of triggers that result in an effect. When a collider enters its space, the trigger associated with the receiver calls a function that executes a script configured for the receiver. A scripting system or physics engine can detect when a collision occurs between a collider and a receiver and can initiate an action. For example, a receiver can trigger an animation, sound, or other effect when contact from a collider is received by the receiver.
[0149] In some embodiments, a receiver is associated with tags that restrict the colliders or types of colliders that can interact with the receiver. In such embodiments, animations can only be triggered by contact from colliders that match the tags specified by the receiver.
[0150] For example, Figure 8 shows an avatar's hand with colliders 802a, 802b, 802c, 802d on the fingers and collider 802e on the palm. The colliders are configured to apply interaction to other parts of the avatar, either configured with receivers or with secondary motion attributes, for the avatar to react to forces applied by the colliders.
[0151] 9A shows two avatars engaged in a touch interaction. More specifically, the two avatars are high-fiving, with the hand 902 of a first avatar making contact with the hand 904 of a second avatar. Both hands may be composed of colliders, but at least one hand is composed of a receiver.
[0152] 9B shows the moment just after a high-five contact interaction has occurred. The hand 906 consists of a receiver that draws an animation of a percussive bubble 908 and is linked to an effect that plays a slapping sound.
[0153] FIG. 10 shows an avatar with parts configured as colliders and parts configured as secondary motion behaviors. For example, the avatar has a hand 1020 configured with a collider 1008 and a hand 1022 configured with a collider 1002. The avatar also has an ear configured with secondary motion behaviors. The secondary motion behaviors are provided by a tree of bones, and each bone in the tree of bones can be linked to a transform, thus creating a tree of transforms. For example, the avatar as a tree transforms to configure its ears. At the root of the transform is the head 1018, followed by a first bone 1016, a second bone 1014, and a third bone 1012. Each of the bones 1016, 1014, and 1012 is configured with one or more transforms that provide the ear with properties that allow the ear to bend or bendable, or elastic, and to react to forces applied by colliders, inertia, or gravity, etc.
[0154] In addition to the transform tree, the ears and hands of the avatar shown in Figure 10 are also configured with attachment points. For example, as shown in Figure 10, hand 1020 has attachment point 1006, hand 1022 has attachment point 1004, and the avatar's right ear has attachment point 1010. The attachment points can be used as locations where objects can be grabbed. In Figure 9, the avatar has a shoe hand 1020 for grabbing attachment point 1010.
[0155] The avatar shown in Figure 10 has space between the hand 1020 and the attachment point 1010, yet the hand 1020 is gripping the ear by the attachment point 1010. This space could be the result of the fact that the user controlling the avatar moved the avatar's hand farther than the ear is set to move. This space could also be the result of an animation delay where the user grabbed the ear by the attachment point at the moment the hand was over the ear, but did not trigger the attachment until after the hand had moved some.
[0156] Notwithstanding this statement, it may not be necessary for one attachment point to overlap another in order to grasp an object. In some embodiments, attachment between attachment points may be based on relative proximity and may not require a hand, such as hand 920, to be directly over an ear to be grasped at attachment point 1010.
[0157] Once the ear is grabbed by the attachment point 1010, the avatar can use their hands to move the ear into various poses, providing effects similar to those that would occur in real life. Once the avatar is done manipulating the ear with the attachment point 1010, the avatar can open their hands to release the ear, in which case the ear will return to its default position, or the user controlling the avatar can press a trigger button to pin the ear, leaving it in the position it was in just before the grab was released.
[0158] 10 shows an example of an avatar using its hands to manipulate its ears for ease of explanation, as another avatar could similarly attach and grab the ears at attachment points 1010 using their own avatar's attachment points, as described herein.
[0159] Ears with secondary motion behaviors can also be manipulated by pushing or pulling them. An avatar can apply forces to the ears using colliders, which will react based on the attributes associated with the parts of the avatar that are configured to exhibit secondary motion behaviors. In this way, an avatar can move hair, ears, tails, clothing, or the same features of another avatar. An avatar can also comb their own hair or the hair of another avatar.
[0160] FIG. 10 shows the avatar's head (ears) configured with secondary motion, but this is just one example. Any part can have secondary motion behavior. An avatar can include a complete skeleton, either humanoid or non-humanoid, and various controllers on the user can be mapped to the skeleton of the humanoid or non-humanoid avatar to cause the skeleton to perform primary motion. Additionally, any part of an avatar can have secondary motion behavior. However, secondary motion behavior is typically reserved for flexible or pliable parts of an avatar and is not typically used for rigid objects, such as the primary skeleton of an avatar, because rigid objects are unlikely to respond with perceptible movement in response to small forces, such as most contact interactions. Common examples of parts of an avatar configured to exhibit secondary motion behavior include accessories, such as hair, ears, tails, clothing, skin, and jewelry.
[0161] Figure 11 shows an example of an interface for setting secondary motion attributes for parts of an avatar. In this example, the secondary motion is applied to hair. The interface includes a collapsed transform tree 1102 for hair. This transform tree has its base on the avatar's Head, and the additional bones that make up the hair are collapsed under the term "HairBase."
[0162] The menu shown in FIG. 11 also allows the user to set parameters related to these forces to define how the bones that make up the hair should react to various forces. For example, a Pull force 1104 can be configured to define how the hair should react when it is pulled from its attachment point. A Spring force 1106 defines how quickly the hair should return to its original position after being pulled. The pull can be from the avatar grabbing the hair or from another force, such as gravity while the avatar is walking. Gravity 1108 defines the effect of how the hair reacts to gravity. Bouncy hair may be slightly less affected by gravity than heavy, long hair. These and other forces can be configured and adjusted to provide the desired motion dynamics to mimic real hair.
[0163] FIG. 11 shows secondary motion set on hair, but secondary motion can be set on any part of the avatar.
[0164] Although the technology has been described with respect to contact interactions between avatars, the technology can also be applied to interactions between avatars and the environment with which the avatars interact. For example, parts of the world, or objects within the world, can be configured with colliders and receivers and can be configured to exhibit secondary motion behaviors. For example, a user can manipulate an avatar to kick a ball, where the avatar's feet are configured with colliders and the ball is also configured with colliders and / or receivers. In another example, as a user walks through a patch of grass, the grass, configured to have secondary motion behaviors, can bend and move with the avatar's movements as the avatar walks through the grass or wags its tail in the grass. In another example, a user may have trackers on each finger of their avatar, allowing the motion of each individual finger to be tracked sufficiently to allow the individual colliders on the fingers to collide with keys on a virtual keyboard, allowing the user to play the keyboard or piano.
[0165] As with avatar-to-avatar contact interactions, a world or objects within a world may be configured with interaction permissions such that a user account can interact with interactable portions of a world or objects within a world only if mutual consent for the interaction exists.
[0166] Thus, although the technology has been described primarily with respect to avatar-to-avatar interactions, the technology is equally applicable when one or both of the avatars are replaced by an object or part of the world.
[0167] 12 illustrates an example of a computing system 1200, which may be, for example, any computing device constituting a client device 106, or a web service 110, or any of those components in which components of the system communicate with each other using connections 1202. The connections 1202 may be physical connections over a bus or direct connections to a processor 1204, such as in a chipset architecture. The connections 1202 may also be virtual connections, network connections, or logical connections.
[0168] In some embodiments, computing system 1200 is a distributed system in which the functionality described in this disclosure may be distributed within a data center, multiple data centers, a peer network, etc. In some embodiments, one or more of the system components described represent multiple such components, each performing some or all of the functionality for which that component is described. In some embodiments, a component may be a physical or virtual device.
[0169] The exemplary computing system 1200 includes at least one processing unit (CPU or processor) 1204 and connections 1202 coupling various system components to the processor 1204, including system memory 1208, such as read only memory (ROM) 1210 and random access memory (RAM) 1212. The computing system 1200 may include a cache of high speed memory 1206 directly connected to the processor 1204, closely connected to the processor 1204, or integrated as part of the processor 1204.
[0170] The processor 1204 may include any general-purpose processor, hardware or software services such as services 1216, 1218, and 1220 stored in a storage device 1214 and configured to control the processor 1204, and special purpose processors where software instructions are incorporated into the actual processor design. The processor 1204 may essentially be a completely self-contained computing system including multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.
[0171] To enable interaction with a user, the computing system 1200 includes input devices 1226, which may represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, speech, etc. The computing system 1200 may also include output devices 1222, which may be one or more of a number of output mechanisms known to those skilled in the art. In some examples, a multimodal system may allow a user to provide multiple types of input / output to communicate with the computing system 1200. The computing system 1200 may generally include a communication interface 1224, which may govern and manage user input and system output. There is no restriction to operating with any particular hardware arrangement, and thus the basic functions herein may be easily replaced with improved hardware or firmware configurations as they are developed.
[0172] The storage device 1214 may be a non-volatile memory device and may be a hard disk or other type of computer-readable medium capable of storing data accessible by a computer, such as a magnetic cassette, a flash memory card, a solid-state memory device, a digital versatile disk, a cartridge, a random access memory (RAM), a read-only memory (ROM), and / or some combination of these devices.
[0173] Storage devices 1214 may include software services, servers, services, etc., where code defining such software, when executed by processor 1204, causes the system to perform functions. In some embodiments, a hardware service that performs a particular function may include software components stored in a computer-readable medium in connection with the hardware components necessary to perform that function, such as processor 1204, connections 1202, output devices 1222, etc.
[0174] For clarity of explanation, in some cases, the technology may be presented as including individual functional blocks, including devices, components, steps or routines in a software-implemented method, or functional blocks including combinations of hardware and software.
[0175] Any of the steps, operations, functions, or processes described herein may be performed or implemented by a hardware and software service or combination of services, alone or in combination with other devices. In some embodiments, a service may be software that resides in memory of one or more servers of a client device and / or a content management system and performs one or more functions when a processor executes the software associated with the service. In some embodiments, a service is a program or collection of programs that perform a particular function. In some embodiments, a service may be considered a server. The memory may be a non-transitory computer-readable medium.
[0176] In some embodiments, computer-readable storage devices, media, and memories may include cable or wireless signals containing bit streams, etc. However, when mentioned, non-transitory computer-readable storage media explicitly excludes media such as energy, carrier signals, electromagnetic waves, and the signals themselves.
[0177] Methods according to the above-described examples may be implemented using computer-executable instructions stored or otherwise available from a computer-readable medium. Such instructions may include, for example, instructions and data that cause or otherwise configure a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a particular function or group of functions. Some of the computer resources used may be accessible over a network. The executable computer instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and / or information created during methods according to the described examples include magnetic or optical disks, solid-state memory devices, flash memory, USB devices with non-volatile memory, networked storage devices, and the like.
[0178] Devices implementing methods according to these disclosures may comprise hardware, firmware and / or software and may take any of a variety of form factors. Typical examples of such form factors include servers, laptops, smartphones, small form factor personal computers, personal digital assistants, etc. The functionality described herein may also be embodied in peripheral devices or add-in cards. Such functionality may also be implemented on a circuit board among different chips or different processes running within a single device, as further examples.
[0179] The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functionality described in these disclosures.
[0180] Although various examples and other information have been used to describe aspects within the appended claims, no limitation of the claims based on the specific features or configurations in such examples should be suggested, since those skilled in the art may use these examples to derive a wide variety of implementations. Moreover, while some subject matter may have been described in language specific to example structural features and / or method steps, it should be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or operations. For example, such functions may be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as example components of systems and methods within the appended claims.
[0181] Aspect 1. A method for triggering an action in response to a collision between a first avatar and a second avatar, the method including: detecting a collision between a collider configured on the first avatar and a receiver configured on the second avatar, reporting the detected collision to an avatar controller, determining an action for the second avatar associated with the receiver, and triggering the action.
[0182] Aspect 2. The method of aspect 1, wherein the collision is detected by a local instance of an application that renders the first avatar and the second avatar, and the action is triggered by the local instance of the application.
[0183]
[0023] Aspect 3. The method of any of aspects 1 to 2, further comprising: determining whether the action is associated with a permanent state change of the second avatar; and if the action is determined to be associated with a permanent state change of the second avatar, sending a state change notification to a remote instance of an application that renders the first avatar and the second avatar.
[0184]
[0013] Aspect 4. The method of any of aspects 1 to 3, wherein the second avatar can be a local avatar or a remote avatar.
[0185] Aspect 5. The method of any of aspects 1 to 4, wherein the action is playing a sound effect or rendering an animation.
[0186]
[0023] Aspect 6. The method of any of aspects 1 to 5, wherein the detecting the collision between the collider and the receiver further comprises determining a physical attribute associated with the collision, and the action may depend on the physical attribute.
[0187]
[0013] Aspect 7. The method of any of aspects 1-6, further comprising determining whether there is mutual agreement between the pair of the first avatar and the second avatar to allow an action resulting from the detected collision prior to triggering the action.
[0188] Aspect 8. A method of supporting interactions affecting a secondary motion of a portion of an avatar, the method including: detecting an interaction between a collider and the portion of the avatar, the portion of the avatar being configured to have a secondary motion, reporting the detected interaction to an avatar controller, and animating movement of the portion of the avatar that is manipulated to move by the collider in accordance with the configured secondary motion.
[0189] Aspect 9. The method of aspect 8, further comprising loading parameters of the portion of the avatar and storing the parameters of the portion of the avatar in a memory.
[0190]
[0023] Aspect 10. The method of any of aspects 8 to 9, wherein the portions of the avatar are defined by a tree of transforms.
[0191]
[0023] Aspect 11. The method of any of aspects 8-10, further comprising determining that the interaction between the collider and the portion of the avatar triggers a physics simulation of a transform in the tree of transforms.
[0192]
[0023] Aspect 12. The method of any of aspects 8-11, further comprising: if it is determined that the interaction between the collider and the portion of the avatar triggers a physics simulation of the transform, creating, in a rendering engine, a job that is processed on a thread other than a primary thread, the job being the physics simulation of the transform.
[0193]
[0023] Aspect 13. The method of any of aspects 8 to 12, further comprising: checking that the job is completed by the rendering engine; and if the job is not completed, instructing the rendering engine to complete the job.
[0194]
[0023] Aspect 14. The method of any of aspects 8-13, wherein the transform is configured to be compiled at runtime, and the creating the job includes compiling the transform at runtime for execution on a thread other than a primary thread.
[0195]
[0023] Aspect 15. The method of any of aspects 8 to 14, further comprising: executing the job on a thread other than the main thread to effect the physics simulation of movement of the portion of the avatar that is manipulated by the collider to move according to the set secondary motion.
[0196] Aspect 16. The method of any of aspects 8 to 15, wherein the execution of the job utilizes local physics, where local physics is limited to the interaction between the colliders and the properties of the tree of transforms.
[0197]
[0023] Aspect 17. The method of any of aspects 8-16, wherein the memory includes a memory structure that supports access to data in the memory by jobs executing on multiple threads.
[0198]
[0023] Aspect 18. The method of any of aspects 8-17, wherein the detection of the interaction between a collider and the portion of the avatar occurs on a frame-by-frame basis.
[0199]
[0023] Aspect 19. The method of any of aspects 8 to 18, further comprising detecting, by a first instance of a client application associated with the local avatar, that the remote avatar has an active receiver configured to accept contact.
[0200] Aspect 20. The method of any of aspects 8-19, wherein the detected interaction is a grab, and the method further includes assigning control over the portion of the avatar that is grabbed, the portion of the avatar that is grabbed having an attachment point at a location where the portion of the avatar is grabbed.
[0201]
[0023] Aspect 21. The method of any of aspects 8-20, further comprising determining whether the portion of the avatar is pinned.
[0202]
[0023] Aspect 22. The method of any of aspects 8-21, further comprising, if the portion of the avatar is determined to be unpinned, returning the portion of the avatar to an original state.
[0203]
[0026] Aspect 23. The method of any of aspects 8-22, further comprising: determining that a portion of an avatar has been posed by the grab; and sending a state change notification to a remote instance of an application that renders the first avatar and the second avatar using information about the pinned state of the portion of the avatar.
[0204]
[0023] Aspect 24. The method of any of aspects 8-23, further comprising, prior to animating a movement of the portion of the avatar that is manipulated by the collider to move according to the set secondary motion, determining whether there is mutual agreement between the pair of the first avatar and the second avatar to allow the animated movement.
[0205]
[0023] Aspect 25. The method of any of aspects 8-24, wherein the receiver is configured to receive interactions only from designated colliders.
[0206]
[0023] Aspect 26. The method of any of aspects 8 to 25, wherein the designated collider is a class of colliders, such as a finger or hand collider, the designated collider is on a particular avatar, or the designated collider is on a category of avatars, such as a humanoid avatar.
[0207] Aspect 27. A method for determining whether avatar contact interaction is allowed, the method comprising: receiving avatar contact settings for a local avatar and at least one remote avatar in a world instance, determining for a pair of avatars in the world instance whether there is mutual agreement between the pair of avatars to allow avatar contact interaction, and displaying an indicator associated with at least one remote avatar indicating an avatar contact interaction status indicating whether avatar contact interaction is allowed between the local avatar and the remote avatar.
[0208]
[0023] Aspect 28. The method of aspect 27, wherein the determining whether there is mutual agreement between the pair of avatars to allow avatar contact interaction occurs on an instance of a client application.
[0209]
[0023] Aspect 29. The method of any of aspects 27 to 28, wherein the determining whether there is mutual agreement between the pair of avatars to allow avatar contact interaction is performed by a networked service.
[0210]
[0023] Aspect 30. The method of any of aspects 27-29, wherein the avatar contact settings include a contact category that allows avatar contact interactions with all avatars, a contact category that allows avatar contact interactions only with avatars in a friend list, and a contact category that does not allow all avatar contact interactions.
[0211]
[0023] Aspect 31. The method of any of aspects 27 to 30, wherein the list of designated avatars associated with the setting overrides the contact category.
[0212]
[0023] Aspect 32. The method of any of aspects 27-31, wherein the avatar contact settings include a list of designated avatars associated with settings that allow or disallow avatar contact interaction.
[0213]
[0023] Aspect 33. The method of any of aspects 27-32, further comprising, for the pair of avatars in the world instance, storing in metadata associated with the remote avatar a determination of whether there is mutual agreement between the pair of avatars to allow avatar contact interaction.
[0214]
[0023] Aspect 34. The method of any of aspects 27-33, further comprising: detecting a collision between a collider configured on a local avatar and a receiver on a remote avatar; reporting the detected collision to an avatar controller; and, if there is mutual agreement between the pair of avatars to allow avatar contact interaction, determining an action for a remote avatar associated with the receiver; and triggering the action.
[0215]
[0023] Aspect 35. The method of any of aspects 27-34, further comprising: after detecting the collision between the collider configured on the local avatar and the receiver configured on the remote avatar, verifying that there is mutual agreement between the pair of avatars and triggering the action.
[0216] Aspect 36. The method of any of aspects 27-35, further comprising: detecting a collision between a collider set on the local avatar and a receiver on the remote avatar; reporting the detected collision to an avatar controller; and terminating a process related to the avatar contact interaction if there is no mutual agreement of a pair of avatars to allow the avatar contact interaction.
[0217] Aspect 37. The method of any of aspects 27-36, in some embodiments, further comprising: an invisible boundary being created when said pair of non-mutually consenting avatars are within a threshold distance of each other.
[0218] Aspect 38. The method of any of aspects 27-37, further including determining that system safety settings prohibit animation from a remote avatar, detecting a collision between a collider configured on a local avatar and a receiver on a remote avatar, and terminating the avatar contact interaction because the system safety settings prohibit animation resulting from the avatar contact interaction.
[0219] Aspect 39. The method of any of aspects 27-38, further comprising determining that a system safety setting prohibits animation from a remote avatar, wherein an indicator associated with at least one remote avatar indicating an avatar contact interaction status indicates that avatar contact interaction is not allowed as a result of the system safety setting.
[0220]
[0023] Aspect 40. The method of any of aspects 27-39, further comprising: determining that an animation associated with an avatar contact interaction is content-flagged, determining that the local avatar has associated settings that filter the content-flagged content, and terminating the avatar contact interaction due to the presence of a filtered type of content.
[0221]
[0023] Aspect 41. The method of any of aspects 27-40, further comprising: determining that a remote avatar associated with an avatar contact interaction is labeled with a content flag; determining that the local avatar has associated settings that filter content labeled with the content flag; and downloading an alternative remote avatar that is not associated with the content flag.
[0222]
[0023] Aspect 42. The method of any of aspects 27-41, further comprising determining whether any avatar of the pair of avatars is configured as a receiver associated with an avatar contact interaction prior to determining whether there is mutual consent between the pair of avatars.
Claims
1. 1. A method for triggering an action in response to a collision between a collider and a portion of an avatar configured to react to the collision, comprising: Detecting a collision between the collider and the portion of the avatar configured to react to the collision; reporting the detected collision to an avatar controller associated with the avatar; animating reactions to said collisions; A method comprising:
2. The method of claim 1 , wherein the portion of the avatar configured to react to the collision includes a receiver, the receiver configured to trigger an animation or effect in response to the collision.
3. The method of claim 1 , wherein the collider is on a first avatar and the portion of the avatar configured to react to the collision is on a second avatar.
4. The method of claim 1 , wherein the portion of the avatar configured to react to the collision is configured to have a secondary motion behavior.
5. determining whether the action is associated with a persistent state change to the avatar; sending a state change notification to a remote instance of an application that renders the first avatar and the second avatar if the action is determined to be associated with the persistent state change to the avatar; The method of claim 3 further comprising:
6. determining whether there is mutual agreement between the first avatar and the second avatar to allow the reaction resulting from the detected collision prior to animating the reaction to the collision; The method of claim 3 further comprising:
7. The animating the reaction resulting from the detected collision further comprises: animating a motion of the portion of the avatar that is manipulated to move by the collider according to the configured secondary motion. The method according to claim 4.
8. determining that the collision between the collider and the portion of the avatar triggers a physics simulation of a transform in a tree of transforms that constitute the portion of the avatar configured with the secondary motion movements; The method of claim 4 further comprising:
9. if it is determined that the interaction between the collider and the portion of the avatar triggers the physics simulation of the transform, passing information about the interaction to a job that is processed in a thread other than a primary thread, the job being the physics simulation of the transform; The method of claim 8 further comprising:
10. A non-transitory computer-readable storage medium containing instructions, The instructions, when executed by a computer, cause the computer to: Detecting a collision between a collider and a portion of an avatar configured to react to the collision; reporting the detected collision to an avatar controller; animating reactions to said collisions; Execute the A computer-readable storage medium.
11. The computer-readable storage medium of claim 10 , wherein the portion of the avatar configured to react to the collision includes a receiver, the receiver configured to trigger an animation or effect in response to the collision.
12. The computer-readable storage medium of claim 10 , wherein the portion of the avatar configured to react to the collision is configured to have a secondary motion behavior.
13. The animating the reaction to the collision results from the detected collision, and the instructions further include causing the computer to: The computer-readable storage medium of claim 12 , configured to animate motion of the portion of the avatar that is manipulated to move by the collider according to the configured secondary motion.
14. The instructions further cause the computer to: determining that the collision between the collider and the portion of the avatar triggers a physics simulation of a transform in a tree of transforms that constitute the portion of the avatar that is configured with the secondary motion behavior; 13. The computer readable storage medium of claim 12.
15. The instructions further cause the computer to: if it is determined that the interaction between the collider and the portion of the avatar triggers the physics simulation of the transform, passing information about the interaction to a job that is processed in a thread other than a primary thread and that is the physics simulation of the transform.
15. The computer readable storage medium of claim 14.
16. A processor; a memory storing instructions that, when executed by the processor, cause the system to: Detecting a collision between a collider and a portion of an avatar configured to react to the collision; reporting the detected collision to an avatar controller; animating a reaction to the collision. A computing system comprising:
17. 17. The computing system of claim 16, wherein the portion of the avatar configured to react to the collision includes a receiver, the receiver configured to trigger an animation or effect in response to the collision.
18. The computing system of claim 16 , wherein the collider is on a first avatar and the portion of the avatar configured to react to the collision is on a second avatar.
19. The computing system of claim 16 , wherein the portion of the avatar configured to react to the collision is configured to have a secondary motion behavior.
20. The animating of the reaction to the collision results from the detected collision, and the computing system 20. The computing system of claim 19, configured to animate motion of the portion of the avatar that is manipulated to move by the collider according to the configured secondary motion.
Citation Information
Patent Citations
Information processing method, apparatus, and program for implementing that information processing method in computer
JP2018175849A
Avatar display system in virtual space, avatar display method in virtual space, and computer program
JP2020091504A
Mixed reality gaming system
US20200368616A1
Information processing device, information processing method, and program
WO2020017261A1
Information processing device, information processing method, and program
WO2022201509A1
