Merging virtual object kits

In various implementations, a method includes obtaining a first virtual object kit that corresponds to a first virtual object type. In various implementations, the method includes obtaining a second virtual object kit corresponding to a second virtual object type that is different from the first virtual object type. In various implementations, the method includes merging the first virtual object kit and the second virtual object kit in order to form a third virtual object kit. In some implementations, the third virtual object kit includes a set of virtual object templates of a third virtual object type that is different from the first virtual object type and the second virtual object type. In some implementations, the third virtual object kit includes a plurality of groups of components associated with respective portions of a virtual object.

TECHNICAL FIELD

The present disclosure generally relates to merging virtual object kits.

BACKGROUND

Some devices are capable of generating and presenting computer-generated reality (CGR) environments. Some CGR environments include virtual environments that are simulated replacements of physical environments. Some CGR environments include augmented environments that are modified versions of physical environments. Some devices that present CGR environments include mobile communication devices such as smartphones, head-mountable displays (HMDs), eyeglasses, heads-up displays (HUDs), and optical projection systems. Most previously available devices that present CGR environments are ineffective at presenting representations of certain objects. For example, some previously available devices that present CGR environments are unsuitable for presenting representations of objects that are associated with an action.

SUMMARY

Various implementations disclosed herein include devices, systems, and methods for merging virtual object kits. In various implementations, a device includes a non-transitory memory and one or more processors coupled with the non-transitory memory. In various implementations, a method includes obtaining a first virtual object kit that corresponds to a first virtual object type. In various implementations, the method includes obtaining a second virtual object kit corresponding to a second virtual object type that is different from the first virtual object type. In various implementations, the method includes merging the first virtual object kit and the second virtual object kit in order to form a third virtual object kit. In some implementations, the third virtual object kit includes a set of virtual object templates of a third virtual object type that is different from the first virtual object type and the second virtual object type. In some implementations, the third virtual object kit includes a plurality of groups of components associated with respective portions of a virtual object.

In accordance with some implementations, a device includes one or more processors, a non-transitory memory, and one or more programs. In some implementations, the one or more programs are stored in the non-transitory memory and are executed by the one or more processors. In some implementations, the one or more programs include instructions for performing or causing performance of any of the methods described herein. In accordance with some implementations, a non-transitory computer readable storage medium has stored therein instructions that, when executed by one or more processors of a device, cause the device to perform or cause performance of any of the methods described herein. In accordance with some implementations, a device includes one or more processors, a non-transitory memory, and means for performing or causing performance of any of the methods described herein.

DESCRIPTION

The present disclosure provides methods, systems, and/or devices for merging virtual object kits to form a new virtual object kit. In various implementations, a user of a device can use the new virtual object kit to assemble virtual objects. Merging virtual object kits allows the user to build a virtual object that includes components from different virtual object kits. As such, the user is not limited to components that are in a particular virtual object kit. Merging virtual object kits also enables the user to build virtual objects that are of a new virtual object type. As such, the user is not limited to building virtual objects of existing virtual object types. Merging virtual object kits enables the user to use components from one virtual object kit to build a virtual object from another virtual object kit. Merging virtual object kits enhances the user experience of a device by allowing a user of the device to create a customized virtual object kit. Merging virtual object kits improves the functionality of the device by enabling the device to synthesize virtual objects of a new virtual object type.

Examples of CGR include virtual reality and mixed reality.

FIG.1Ais a diagram of a user interface10for creating a new virtual object kit. In some implementations, the user interface10enables a user of a device to create a new virtual object kit by merging two or more existing virtual object kits. In some implementations, the user interface10displays affordances20for selecting at least some of the existing virtual object kits. In some implementations, the user interface10includes an import kit element30that enables a user to import an existing virtual object kit. As illustrated inFIG.1A, in some implementations, the user interface10includes a selected kits area40that indicates which existing virtual object kits the user has selected to create a new virtual object kit. In some implementations, the user interface10includes a create kit affordance50that, when activated, triggers the creation of a new virtual object kit by merging existing virtual object kits identified in the selected kits area40.

In the example ofFIG.1A, the affordances20include a multipede kit affordance20afor selecting a multipede virtual object kit that is used to synthesize multipede virtual objects. In some examples, the affordances20include a spaceship kit affordance20bfor selecting a spaceship virtual object kit that is used to synthesize spaceship virtual objects. In some implementations, the affordances20include a robot kit affordance20cfor selecting a robot virtual object kit that is used to synthesize robot virtual objects. In the example ofFIG.1A, the affordances20include an Xmas kit affordance20ffor selecting an Xmas virtual object kit that is used to synthesize Xmas virtual objects. In some examples, the affordances20include a candy kit affordance20efor selecting a candy virtual object kit that is used to synthesize candy virtual objects. Although the example ofFIG.1Ashows five particular affordances20a-20e, in some implementations, the user can view additional affordances (e.g., by tapping the right arrow shown inFIG.1A).

In some implementations, the affordances20represent virtual object kits that are available in a digital asset store (e.g., a virtual object kit store). In some implementations, the affordances20represent virtual object kits that are available for purchase from the digital asset store. In some implementations, the affordances20represent virtual object kits that a user of a device has purchased (e.g., from the digital asset store). In some implementations, the affordances20represent virtual object kits that are stored on a device displaying the user interface10.

In some implementations, the import kit element30enables a user of the device displaying the user interface10to import an existing virtual object kit in order to merge the imported virtual object kit with another existing virtual object kit to form a new virtual object kit. In some implementations, the import kit element30enables a user to drag-and-drop an existing virtual object kit into the import kit element30.

In some implementations, the selected kits area40indicates existing virtual object kits that the user has selected to merge. For example, in some implementations, the selected kits area40displays representations of virtual object kits that the user selected from the available virtual object kits represented by the affordances20. In some implementations, the selected kits area40provides an option to remove virtual object kits that the user inadvertently selected.

In some implementations, the create kit affordance50, when selected, triggers the creation of a new virtual object kit by merging the existing virtual object kits identified in the selected kits area40. In some implementations, the create kit affordance50is disabled (e.g., inactive, for example, unselectable) prior to the user selecting at least two existing virtual object kits. In such implementations, the create kit affordance is enabled (e.g., rendered selectable) after the user selects at least two existing virtual object kits.

FIG.1Billustrates a user input60aselecting the multipede kit affordance20a. In some implementations, the user input60acorresponds to a request to use the multiple virtual object kit in order to form a new virtual object kit.

As shown inFIG.1C, in response to receiving the user input60ainFIG.1B, the selected kits area40indicates that the user has selected the multipede virtual object kit in order to form a new virtual object kit. In the example ofFIG.1C, an appearance of the multipede kit affordance20ais changed (e.g., the multipede kit affordance20ais grayed-out) in order to indicate that the user has selected the multipede virtual object kit to create a new virtual object kit. In some implementations, the selected kits area40provides an option to remove (e.g., unselect) the multipede virtual object kit (e.g., by left-swiping the representation of the multipede virtual object kit shown in the selected kits area40).

FIG.1Dillustrates a user input60bselecting the candy kit affordance20e. In some implementations, the user input60bcorresponds to a request to use the candy virtual object kit along with the multipede virtual object kit in order to form the new virtual object kit.

As shown inFIG.1E, in response to receiving the user input60binFIG.1D, the selected kits area40indicates that the user has selected the candy virtual object kit along with the multipede virtual object kit in order to form the new virtual object kit. As such, the user interface10displays a representation of the candy virtual object kit adjacent to the representation of the multipede virtual object kit in the selected kits area40.

FIG.1Fillustrates a user input60cselecting the create kit affordance50. The user input60ccorresponds to a request to create a new virtual object kit based on the multipede virtual object kit and the candy virtual object kit. In some implementations, the user input60ccorresponds to a request to merge the multipede virtual object kit and the candy virtual object kit in order to form a new virtual object kit.

FIG.1Gillustrates a new kit notification70. In some implementations, the new kit notification70displays information regarding the new virtual object kit. For example, in some implementations, the new kit notification70displays a kit name72, kit components74, composition percentages76, and credits used78to create the new virtual object kit. In some implementations, the kit name72is a concatenation of the virtual object kits that were used to create the new virtual object kit. In some implementations, the kit components74identify the virtual object kits that were merged to form the new virtual object kit. In some implementations, the composition percentages76indicate percentages of the new virtual object kit that are attributable to respective kit components74(e.g., 80% of the new multipede-candy virtual object kit is made from the multipede virtual object kit, and 20% of the new multipede-candy virtual object kit is made from the candy virtual object kit). In some implementations, the credits used78indicate an amount of credits that were distributed (e.g., paid) to respective entities that created the kit components74(e.g., three credits were distributed to a creator of the multipede virtual object kit, and one credit was distributed to a creator of the candy virtual object kit).

In some implementations, the new kit notification70includes various affordances to perform operations with respect to the new multipede-candy virtual object kit. For example, in some implementations, the new kit notification70includes a rename kit affordance80a, a delete kit affordance80b, a modify kit affordance80c, a save kit affordance80d, a share kit affordance80e, and a publish kit affordance80f. The rename kit affordance80aprovides an option to rename the new multipede-candy virtual object kit. The delete kit affordance80b, when selected, deletes the new multipede-candy virtual object kit.

FIG.1Hillustrates a user input60dselecting the modify kit affordance80c. In some implementations, the user input60dcorresponds to a request to modify the new multipede-candy virtual object kit.

As illustrated inFIG.1I, in some implementations, in response to receiving the user input60dshown inFIG.1H, the user interface10provides an option to modify the newly created multipede-candy virtual object kit. In the example ofFIG.1I, the user interface10provides an option to remove the multipede virtual object kit (e.g., by left-swiping the representation of the multipede virtual object kit displayed in the selected kits area40) and/or the candy virtual object kit (e.g., by left-swiping the representation of the candy virtual object kit displayed in the selected kits area40). The user interface10also provides an option to merge additional virtual object kits with the newly created multipede-candy virtual object kit. For example, the user interface10provides an option to merge the spaceship virtual object kit with the newly created multipede-candy virtual object kit by selecting the spaceship kit affordance20b. Similarly, the user interface10provides an option to merge the robot virtual object kit with the newly created multipede-candy virtual object kit by selecting the robot kit affordance20c. In the example ofFIG.1I, the user interface10displays a modify kit affordance52that, when selected, modifies the newly created multipede-candy virtual object kit. In some implementations, the user interface10enables the user to modify virtual object kits that were created within a threshold amount of time prior to a current time (e.g., the user interface10enables the user to modify virtual object kits that were created in the last one hour/day/week).

FIG.1Jillustrates a user input60eselecting the save kit affordance80d. In some implementations, the user input60ecorresponds to a request to save the newly created multipede-candy virtual object kit.

As illustrated inFIG.1K, in some implementations, in response to receiving the user input60eshown inFIG.1J, the user interface10displays a saved kits area32(e.g., a ‘My kits’ area). In some implementations, the saved kits area32displays representations of virtual object kits that are saved on the device displaying the user interface10. In some implementations, the saved kits area32displays representation of virtual object kits that are associated with an account of a user of the device displaying the user interface10. For example, in some implementations, the saved kits area32displays representations of virtual object kits that the user has purchased from a digital asset store (e.g., a virtual object kit store). In the example ofFIG.1K, the saved kits area32displays a multipede-candy affordance20frepresenting the multipede-candy virtual object kit. In some implementations, virtual object kits in the saved kits area32can be used to form new virtual object kits. As such, the multipede-candy virtual object kit can be used to form other new virtual object kits.

FIG.1Lillustrated a user input60fselecting the share kit affordance80e. In some implementations, the user input60fcorresponds to a request to share the newly created multipede-candy virtual object kit.

As illustrated inFIG.1M, in some implementations, in response to receiving the user input60fshown inFIG.1L, the user interface10displays sharing options82. In some implementations, the sharing options82include a local sharing affordance82a, a messaging affordance82b, and a mail affordance82c. The local sharing affordance82a, when selected, provides an option to share the newly created multipede-candy virtual object kit with nearby devices. The messaging affordance82b, when selected, provides an option to share the newly created multipede-candy virtual object kit via an instant message. The mail affordance82c, when selected, provides an option to share the newly created multipede-candy virtual object kit via e-mail.

FIG.1Nillustrates a user input60gselecting the publish kit affordance80f. In some implementations, the user input60gcorresponds to a request to publish (e.g., distribute) the newly created multipede-candy virtual object kit. In some implementations, the user input60gcorresponds to a request to make the newly created multipede-candy virtual object kit available to other users through the digital asset store (e.g., the virtual object store). In some implementations, publishing the multipede-candy virtual object kit enables other users to create virtual objects from the multipede-candy virtual object kit. In some implementations, publishing the multipede-candy virtual object kit enables other users to merge the multipede-candy virtual object kit with other virtual object kits in order to create other new virtual object kits.

As illustrated inFIG.1O, in some implementations, in response to receiving the user input60gshown inFIG.1N, the user interface10displays publishing options84. In some implementations, the publishing options84include a credit selection field84athat enables the user to select an amount of credits associated with the multipede-candy virtual object kit. In some implementations, the user receives the amount of credits specified in the credit selection field84awhen the multipede-candy virtual object kit is used to form other new virtual object kits. In some implementations, a default value of the credit selection field84ais a sum of the credits used78(shown inFIG.1L) to create the multipede-candy virtual object kit. In some implementations, a minimum value that the credit selection field84aaccepts is the credits used78to create the multipede-candy virtual object kit. In some implementations, a number of credits that the creator of the multipede-candy virtual object kit receives when the multipede-candy virtual object kit is used to create other new virtual object kits is equal to a difference between a value of the credit selection field84aand the credits used78(shown inFIG.1L).

Referring toFIG.1P, in some implementations, the multipede kit affordance20ais associated with an availability indicator22athat indicates a number of instances of the multipede virtual object kit that are available. In the example ofFIG.1P, the availability indicator22ahas a value of five. As such, in the example ofFIG.1P, there are five instances of the multipede virtual object kit available for use.

InFIG.1Q, a representation of the multipede virtual object kit is displayed in the selected kits area40indicating that an instance of the multipede virtual object kit has been selected to form a new virtual object kit. Since an instance of the multipede virtual object kit was used or is about to be used, the user interface10updates the availability indicator22ato indicate that four of the five instances of the multipede virtual object kit are still available for use. More generally, in various implementations, the user interface10decrements a value of the availability indicator22ain response to a selection of the multipede kit affordance20a.

FIG.1Rillustrates a multipede virtual object kit110, a candy virtual object kit120, and a multipede-candy virtual object kit130. In the example ofFIG.1R, the multipede-candy virtual object kit130is synthesized by merging the multipede virtual object kit110and the candy virtual object kit120.

As shown inFIG.1R, the multipede virtual object kit110includes one or more templates112for building a multipede virtual object. In the example ofFIG.1R, the template112is for synthesizing a multipede virtual object that includes a head112a, a body112band appendages112c. The multipede virtual object kit110also includes possible head components114a(e.g., a teapot, a soccer ball and/or a watermelon (not shown)) for the head112a, possible body components114b(e.g., a burrito (not shown) for the body112b, and possible appendages114c(e.g., twigs and/or fries (not shown) for the appendages112c.

In the example ofFIG.1R, the candy virtual object kit120includes candy canes120a, candy bars120b, truffles120c, sweets120d, donuts120e, and cotton candy120f. In some implementations, the candy virtual object kit120includes templates (not shown) for creating edible virtual objects using the candy canes120a, the candy bars120b, the truffles120c, the sweets120d, the donuts120e, and the cotton candy120f.

In the example ofFIG.1R, the multipede-candy virtual object kit130includes at least some of the one or more templates112from the multipede virtual object kit110. As shown inFIG.1R, the multipede-candy virtual object kit130includes possible head components134afor the head112a, possible body components134bfor the body112, and possible appendages for the appendages112c.

As illustrated inFIG.1R, the possible head components134aof the multipede-candy virtual object kit130include some components from the candy virtual object kit120. For example, the possible head components134ainclude truffles120cfrom the candy virtual object kit120. In some implementations, the possible head components134ain the multipede-candy virtual object kit130are different from the possible head components114ain the multipede virtual object kit110. For example, unlike the possible head components114aof the multipede virtual object kit110, the possible head components134aof the multipede-candy virtual object kit130do not include a teapot, a soccer ball and/or a watermelon.

As illustrated inFIG.1R, the possible body components134bof the multipede-candy virtual object kit130include some components from the candy virtual object kit120. For example, the possible body components134binclude candy bars120band cotton candy120ffrom the candy virtual object kit120. In some implementations, the possible body components134bin the multipede-candy virtual object kit130are different from the possible body components114bin the multipede virtual object kit110. For example, unlike the possible body components114bof the multipede virtual object kit110, the possible body components134bof the multipede-candy virtual object kit130do not include a burrito.

As illustrated inFIG.1R, the possible appendages134cof the multipede-candy virtual object kit130include some components from the candy virtual object kit120. For example, the possible appendages134cinclude candy canes120afrom the candy virtual object kit120. In some implementations, the possible appendages134cin the multipede-candy virtual object kit130are different from the possible appendages114cin the multipede virtual object kit110. For example, unlike the possible appendages114cof the multipede virtual object kit110, the possible appendages134cof the multipede-candy virtual object kit130do not twigs and/or fries.

As shown inFIG.1R, the multipede-candy virtual object kit130includes templates112from the multipede virtual object kit110, and components from the candy virtual object kit120that are compatible with the templates112. More generally, in various implementations, a new virtual object kit includes templates from a first existing virtual object kit and components that are compatible with the templates from a second existing virtual object kit.

As shown inFIG.1S, the tree virtual object kit140includes one or more templates142for building a tree virtual object. In the example ofFIG.1S, the template142is for synthesizing a tree virtual object that includes a trunk142a, branches142b, and leaves142c. The tree virtual object kit140also includes possible trunk components144a(e.g., a flag pole, a baseball bat and/or a 2×4 piece of wood (not shown)) for the trunk142a, possible branch components144b(e.g., a gold club (not shown) for the branches142b), and possible leaf components144c(e.g., paper plates (not shown) for the leaves142c).

In the example ofFIG.1S, the multipede-tree virtual object kit150includes one or more templates152for synthesizing a multipede-tree virtual object that is different from a multipede virtual object and a tree virtual object. For example, as illustrated by the template152, a multipede-tree virtual object includes the trunk142afrom the template142of the tree virtual object kit140, and tentacles154bthat are neither in the tree virtual object kit140nor in the multipede virtual object kit110. More generally, in some implementations, a merged virtual object kit includes a template with portions that are not found in any of the existing virtual object kits that were used to create the merged virtual object kit.

As illustrated inFIG.1S, the multipede-tree virtual object kit150includes possible trunk components154afor the trunk142ain the template152, and possible tentacle components154bfor the tentacles154bin the template152.

In the example ofFIG.1S, the possible trunk components154ainclude at least some of the possible body components114bfrom the multipede virtual object kit110(e.g., the possible trunk components154ainclude a burrito). In some implementations, the possible trunk components154aof the multipede-tree virtual object kit150are different from the possible trunk components144aof the tree virtual object kit140(e.g., unlike the possible trunk components144aof the tree virtual object kit140, the possible trunk components154aof the multipede-tree virtual object kit150do not include a flag pole, a baseball bat and/or a 2×4 piece of wood). However, in some implementations, the possible trunk components154aof the multipede-tree virtual object kit150include at least some of the possible trunk components144afrom the tree virtual object kit140.

As illustrated inFIG.1S, the possible tentacle components154binclude at least some of the possible appendages114cfrom the multipede virtual object kit110(e.g., the possible tentacle components154binclude fries).

As shown inFIG.1S, the multipede-tree virtual object kit150includes templates152that are different from the templates112of the multipede virtual object kit110and the templates142of the tree virtual object kit140. More generally, in various implementations, a merged virtual object kit includes templates that are different from the templates of the existing virtual object kits that were merged to create the merged virtual object kit.

In some implementations, a virtual object kit enables a user to create (e.g., synthesize or generate) virtual objects of a virtual object type associated with the virtual object kit. In various implementations, allowing a user to create a new virtual object kit enables the user to synthesize virtual objects that are of a new virtual object type associated with the new virtual object kit.

In various implementations, a virtual object represents a character or a variation thereof from fictional material such as a movie, a video game, a comic, and/or a novel. In various implementations, a virtual object represent things (e.g., tangible objects). For example, in some implementations, a virtual object represents equipment (e.g., machinery such as planes, tanks, robots, cars, etc.). In some implementations, a virtual object represents things (e.g., equipment) from fictional material. In some implementations, a virtual object represent a thing from the real-world.

In various implementations, a virtual object performs an action in order to satisfy (e.g., complete or achieve) an objective. In some implementations, a virtual object is associated with a particular objective, and the virtual object performs actions that improve the likelihood of satisfying that particular objective. In some implementations, the virtual objects are referred to as object representations, for example, because the virtual objects represent various objects (e.g., real-world objects, or fictional objects).

In some implementations, a virtual object representing a character is referred to as a character virtual object. In some implementations, a character virtual object performs actions in order to advance a character objective. In some implementations, a virtual object kit that synthesizes character virtual objects is referred to as a character virtual object kit.

In some implementations, a virtual object representing an equipment is referred to as an equipment virtual object. In some implementations, an equipment virtual object performs actions in order to advance an equipment objective. In some implementations, a virtual object kit that synthesizes equipment virtual objects is referred to as an equipment virtual object kit.

In some implementations, a virtual object representing an environment is referred to as an environmental virtual object. In some implementations, an environmental virtual object performs environmental actions in order to advance an environmental objective. In some implementations, a virtual object kit that synthesizes environmental virtual objects is referred to as an environmental virtual object kit.

FIG.2Ais a flowchart representation of a method200of merging virtual object kits to form a new virtual object kit. In various implementations, the method200is performed by a device with a display, a non-transitory memory, and one or more processors coupled with the display and the non-transitory memory. In some implementations, the method200is performed by processing logic, including hardware, firmware, software, or a combination thereof. In some implementations, the method200is performed by a processor executing code stored in a non-transitory computer-readable medium (e.g., a memory). Briefly, in some implementations, the method200includes obtaining a first virtual object kit, obtaining a second virtual object kit, and merging the first virtual object kit and the second virtual object kit in order to form a third virtual object kit.

As represented by block210, in some implementations, the method200includes obtaining a first virtual object kit that corresponds to a first virtual object type (e.g., obtaining the multipede virtual object kit represented by the multipede kit affordance20ashown inFIG.1A). In some implementations, the method200includes receiving the first virtual object kit from a digital asset store (e.g., a virtual object kit store) where a first entity (e.g., a creator of the first virtual object kit) uploaded the first virtual object kit.

As represented by block220, in some implementations, the method200includes obtaining a second virtual object kit that corresponds to a second virtual object type that is different from the first virtual object type (e.g., obtaining the spaceship virtual object kit represented by the spaceship kit affordance20bshown inFIG.1A). In some implementations, the method200includes receiving the second virtual object kit from a digital asset store (e.g., a virtual object kit store) where a second entity (e.g., a creator of the second virtual object kit) uploaded the second virtual object kit.

In some implementations, virtual objects of the first virtual object type are associated with a first set of objectives and a first set of actions that, when performed by the virtual objects of the first virtual object type, satisfy the first set of objectives. In some implementations, virtual objects of the second virtual object type are associated with a second set of objectives and a second set of actions that, when performed by the virtual objects of the second virtual object type, satisfy the second set of objectives. In some implementations, the second set of objectives are different from the first set of objectives, and the second set of actions are different from the first set of actions.

As represented by block230, in some implementations, the method200includes merging the first virtual object kit and the second virtual object kit in order to form a third virtual object kit (e.g., as shown inFIG.1S, the multipede virtual object kit110and the tree virtual object kit140are merged to form the multipede-tree virtual object kit150). In some implementations, the third virtual object kit includes a set of virtual object templates of a third virtual object type (e.g., as shown inFIG.1S, the multipede-tree virtual object kit150includes one or more templates152of a multipede-tree virtual object type). In some implementations, the third virtual object type is different from the first virtual object type and the second virtual object type (e.g., as shown inFIG.1S, the multipede-tree virtual object type is different from the multipede virtual object type and the tree virtual object type). In some implementations, the third virtual object kit includes a plurality of groups of components associated with respective portions of a virtual object (e.g., as shown inFIG.1S, the multipede-tree virtual object kit150includes the possible trunk components154aassociated with the trunk142aportion of a multipede-tree virtual object, and the possible tentacle components154bassociated with the tentacles154bportion of the multipede-tree virtual object). In various implementations, merging the first and second virtual object kits enables the creation of a new virtual object kit that can be used by a user to create a new type of virtual object thereby enhancing the functionality of the device.

As represented by block230a, in some implementations, the method200includes selecting a first portion of the plurality of groups of components from the first virtual object kit, and selecting a second portion of the plurality of groups of components from the second virtual object kit (e.g., as shown inFIG.1S, the possible trunk components154aof the multipede-tree virtual object kit150include at least some of the possible body components114bfrom the multipede virtual object kit110and at least some of the possible trunk components144afrom the tree virtual object kit140). Selecting components from the first and second virtual object kits saves the user time by not requiring the user to create new components for the third virtual object kit from scratch. Saving the user time results in fewer user interactions with the device thereby extending the battery life of the device and/or reducing wear-and-tear of the device.

As represented by block230b, in some implementations, the method200includes verifying that the first portion of the plurality of groups of components are compatible with the second portion of the plurality of groups of components. Verifying compatibility of components ensures that the third virtual object kit does not include incompatible components that cannot be combined to create virtual objects.

As represented by block230c, in some implementations, the method200includes importing at least a portion of the set of virtual object templates from the first virtual object kit into the third virtual object kit (e.g., as shown inFIG.1R, the multipede-candy virtual object kit130includes the templates112from the multipede virtual object kit110). Importing templates from the first virtual object kit into the third virtual object kit saves the user time by not requiring the user to create new virtual object templates from scratch. Saving the user time results in fewer user interactions with the device thereby extending the battery life of the device and/or reducing wear-and-tear of the device.

As represented by block230d, in some implementations, the method200includes selecting a portion of the plurality of groups of components from the second virtual object kit (e.g., as shown inFIG.1R, the possible head components134aof the multipede-candy virtual object kit130includes truffles120cfrom the candy virtual object kit120). As such, in some implementations, the method200enables a user to select a virtual object template from one virtual object kit and populate that virtual object template with components from another virtual object kit.

As represented by block230e, in some implementations, the method200includes determining that a first portion (e.g., a first percentage) of the third virtual object kit is made from the first virtual object kit, and determining that a second portion (e.g., a second percentage) of the third virtual object kit is made from the second virtual object kit (e.g., as shown inFIG.1G, the new kit notification70displays the composition percentages76).

As represented by block230f, in some implementations, the method200includes distributing, based on the first portion, a first amount of credits to a first entity that created the first virtual object kit, and distributing, based on the second portion, a second amount of credits to a second entity that created the second virtual object kit (e.g., as shown inFIG.1G, three credits are distributed to a creator/owner of the multipede virtual object kit and one credit is distributed to a creator/owner of the candy virtual object kit).

As represented by block230g, in some implementations, the method200includes transmitting (e.g., distributing or publishing) the third virtual object kit (e.g., so that other users can use the third virtual object kit to create additional virtual object kits). In some implementations, the method200includes distributing (e.g., publishing or uploading) the third virtual object kit via a digital asset store (e.g., a virtual object kit store).

As represented by block230h, in some implementations, the method200includes receiving one or more credits for synthesizing the third virtual object kit. In some implementations, the method200includes receiving a credit in response to the third virtual object kit being used to synthesize a virtual object of the third virtual object type. In some implementations, the method200includes receiving a credit in response to the third virtual object kit being merged with a fourth virtual object kit in order to form a fifth virtual object kit. In some implementations, an amount of credits is established by the user (e.g., via the credit selection field84ashown inFIG.1O).

As represented by block230i, in some implementations, the method200includes merging the third virtual object kit with a fourth virtual object kit in order to form a fifth virtual object kit. In some implementations, after merging the first virtual object kit and the second virtual object kit in order to form the third virtual object kit, the method200includes obtaining a fourth virtual object kit that corresponds to a fourth virtual object type, and merging the third virtual object kit with the fourth virtual object kit in order to form a modified third virtual object kit (e.g., as illustrated inFIG.1I, the multipede-candy virtual object kit can be modified).

In some implementations, merging the third virtual object kit with the fourth virtual object kit includes adding a virtual object template from the fourth virtual object kit to the set of virtual object templates in the third virtual object kit.

In some implementations, merging the third virtual object kit with the fourth virtual object kit includes adding one or more components from the fourth virtual object kit to the plurality of groups of components in the third virtual object kit.

Referring toFIG.2B, as represented by block230j, in some implementations, the method200includes merging the first virtual object kit and the second virtual object kit based on a merge criterion. In some implementations, the method200includes, prior to merging the first virtual object kit and the second virtual object kit, determining whether the first virtual object kit and the second virtual object kit satisfy a merge criterion. In some implementations, in response to determining that the merge criterion is satisfied, the method200includes merging the first virtual object kit with the second virtual object kit. In some implementations, in response to determining that the merge criterion is not satisfied, the method200includes displaying a prompt indicating that the first virtual object kit and the second virtual object kit cannot be merged.

In some implementations, the method200includes determining whether components from the first virtual object kit are compatible with a template from the second virtual object kit. In some implementations, the method200includes determining whether components from the first virtual object kit can be used to populate a template in the second virtual object kit.

As represented by block230k, in some implementations, the third virtual object kit includes a construction kit that defines physical form of virtual objects. For example, the third virtual object kit defines what the virtual object looks like. In some implementations, the third virtual object kit includes an animation kit that defines responses of virtual objects. For example, the third virtual object kit defines what actions the virtual object performs and/or how the virtual object performs actions. In some implementations, the third virtual object kit includes a behavioral kit that defines responses to stimuli. For example, the third virtual object kit defines how virtual objects interact with other virtual objects.

As represented by block230l, in some implementations, the method200includes determining an availability of the first virtual object kit and/or the second virtual object kit. In some implementations, the method200includes prior to merging the first virtual object kit and the second virtual object kit, determining whether a number of available instances of the first virtual object kit is greater than zero. In some implementations, in response to determining that the number of available instances of the first virtual object kit is greater than zero, the method200includes merging the first virtual object kit with the second virtual object kit, and decrementing the number of available instances of the first virtual object kit (e.g., as shown inFIGS.1P-1Q, a value of the availability indicator22ais decremented).

As represented by block230m, in some implementations, at least one of the plurality of groups of components in the third virtual object kit includes accessories for the virtual object (e.g., hats, sunglasses, etc.). In some implementations, at least one of the plurality of groups of components includes augmentation components for the virtual object (e.g., color, texture, materials, skin, etc.). In some implementations, obtaining the first virtual object kit includes obtaining a virtual object supplemental kit that includes supplemental components to supplement the virtual object (e.g., the first virtual object kit is a dedicated accessories kit).

As represented by block240, in some implementations, the method200includes building (e.g., synthesizing or assembling) a virtual object using the third virtual object kit. As represented by block240a, in some implementations, the method200includes receiving a request to assemble a virtual object. In some implementations, the request includes a selection of components from at least some of the plurality of groups of components. As represented by block240b, in some implementations, the method200includes synthesizing the virtual object in accordance with the request. As represented by block240c, in some implementations, the method200includes instantiating the virtual object in a CGR environment (e.g., in one of an augmented reality (AR) environment and a virtual reality (VR) environment).

FIG.3is a block diagram of a server system300enabled with one or more components of a device in accordance with some implementations. While certain specific features are illustrated, those of ordinary skill in the art will appreciate from the present disclosure that various other features have not been illustrated for the sake of brevity, and so as not to obscure more pertinent aspects of the implementations disclosed herein. To that end, as a non-limiting example, in some implementations the server system300includes one or more processing units (CPUs)301, a network interface302, a programming interface303, a memory304, and one or more communication buses305for interconnecting these and various other components.

In some implementations, the network interface302is provided to, among other uses, establish and maintain a metadata tunnel between a cloud hosted network management system and at least one private network including one or more compliant devices. In some implementations, the communication buses305include circuitry that interconnects and controls communications between system components. The memory304includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory304optionally includes one or more storage devices remotely located from the CPU(s)301. The memory304comprises a non-transitory computer readable storage medium.

In some implementations, the memory304or the non-transitory computer readable storage medium of the memory304stores the following programs, modules and data structures, or a subset thereof including an optional operating system306, a virtual object kit obtainer310, a virtual object kit synthesizer320, and a virtual object synthesizer330.

In various implementations, the virtual object kit obtainer310obtains existing virtual object kits. For example, the virtual object kit obtainer310obtains the multipede virtual object kit, the spaceship virtual object kit, the robot virtual object kit, the Xmas virtual object kit, and the candy virtual object kit represented by the affordances20inFIG.1A. In some implementations, the virtual object kit obtainer310obtains the existing virtual object kits by accessing a digital asset store (e.g., a virtual object kit store).

In some implementations, the virtual object kit synthesizer320synthesizes a new virtual object kit by merging two or more existing virtual object kits. For example, as shown inFIG.1G, the virtual object kit synthesizer320synthesizes the multipede-candy virtual object kit by merging the multipede virtual object kit and the candy virtual object kit.

In some implementations, the virtual object synthesizer330utilizes a virtual object kit (e.g., a newly created virtual object kit such as the multipede-candy virtual object kit shown inFIG.1G) to synthesize virtual objects. In some implementations, the virtual object synthesizer330instantiates the virtual object in a CGR environment (e.g., an AR/VR environment) after synthesizing the virtual object.