Collision management in augmented reality scene description
By including collision information and physical parameters in the extended reality scenario description, the configuration of the physics engine is optimized, and the problem of waste of collision management resources in the existing technology is solved, and the performance and efficiency of extended reality applications are improved.
Patent Information
- Application Number
- CN202380028149.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-14
- Filing Date
- 2023-03-06
- Publication Date
- 2024-11-08
AI Technical Summary
The existing extended reality scenario description format lacks effective memory and processing resource management mechanisms when managing collision behavior between objects, resulting in waste of resources and poor performance.
By obtaining the description of the extended real-life scenario, including collision information in the scene graph, initializing the physics engine for collision detection using Boolean values and mesh information, and using physical body parameters and material information for physical simulation when needed, optimize the configuration of the physics engine. and parameters to save resources.
Effectively manage physics engine resources, improve the performance and efficiency of extended real-life applications, and reduce the consumption of memory and processing resources.
Smart Images

Figure CN118922233A_ABST
Abstract
Description
Technical Field
[0001] The present principles generally relate to the fields of extended reality scene description and extended reality scene rendering. Specifically, the present principles relate to the description of collision management between scene objects. This document can also be understood in the context of formatting and playing back extended reality applications when rendered on an end-user device, such as a mobile device or a head-mounted display (HMD). Background Art
[0002] This section is intended to introduce the reader to various aspects of the technology, which may be related to various aspects of the present principles described and / or claimed below. This discussion is considered to be helpful in providing the reader with background information to better understand various aspects of the present principles. Therefore, it should be understood that these statements should be read in this light and not as an admission of prior art.
[0003] Extended Reality (XR) is a technology that enables interactive experiences where the real world environment and / or video content is augmented by virtual content, which can be defined across multiple sensory modalities (including vision, hearing, touch, etc.). Virtual content (such as 3D content or audio / video files) is rendered in real time in a way that is consistent with the user context (environment, viewpoint, device, etc.) while the application is running. Scene graphs (such as those defined by Khronos / glTF and its extensions in the MPEG scene description format or the scene graph proposed by Apple / USDZ) are one possible way to present the content to be rendered. They combine, on the one hand, a declarative description of the scene structure that links real environment objects and virtual objects, and on the other hand, a binary representation of the virtual content. The scene description framework ensures that timed media and corresponding related virtual content are available at any time during application rendering. The scene description can also carry scene-level data that describes how scene objects interact at runtime to achieve an immersive XR experience. Collision management between objects (real and / or virtual, where the user is the real object) requires the use of a physics engine that consumes a lot of memory and processing resources. In the existing XR scene description format, there is a lack of mechanisms to manage memory and processing resources using different types of collision behaviors. Summary of the invention
[0004] A brief summary of the present principles is given below to provide a basic understanding of some aspects of the present principles. This summary is not a comprehensive review of the present principles. It is not intended to identify the key or critical elements of the present principles. The following summary only introduces some aspects of the present principles in a simplified form as a preface to the more detailed description below.
[0005] The present principles relate to a method for launching an extended reality application using a physics engine. The method includes the step of obtaining a description of an extended reality scene. The description includes a scene graph, and at least two nodes of the scene graph contain collision information according to the present principles. The scene graph includes at least two such nodes because a collision occurs between at least two objects described in these nodes. The collision information includes a first Boolean value indicating whether the object described in the node is static, mesh information, and a second Boolean value indicating whether the physical properties of the object described in the node are simulated, and in the case where the second Boolean value is true, also includes physical body parameters and material information. Then, the method includes, for the node of the scene graph containing the collision information, initializing the physics engine for collision detection using the first Boolean value and the mesh information. In the case where the second Boolean value is true, the method also includes the step of initializing the physics engine for physical simulation using the physical body parameters and the material information. When the physics engine is initialized using a configuration and parameters that allow saving memory and processing resources, the extended reality application is launched.
[0006] The present principles also relate to an extended reality rendering device, which includes a memory associated with a processor configured to implement the above method.
[0007] The present principles also relate to a data stream that carries data representing a description of an augmented reality scene. The description includes:
[0008] - A scene graph that links nodes;
[0009] - At least two nodes of the scene graph contain collision information, the collision information including:
[0010] a first Boolean value indicating whether the object described in the node is static, mesh information, and a second Boolean value indicating whether the physics of the object described in the node is simulated; and
[0011] • In case the second Boolean value is true, the physics body parameters and material information. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The present disclosure will be better understood, and other particular features and advantages will emerge, from reading the following description with reference to the accompanying drawings, in which:
[0013] - Figure 1 An example diagram showing an extended reality scene description according to the present principles;
[0014] - Figure 2 showing a non-limiting example of an extended reality scene including real objects and virtual objects;
[0015] - Figure 3 An example architecture of an XR processing engine according to the present principles is shown, which can be configured to implement Figure 5Related methods;
[0016] - Figure 4 An example embodiment of a data stream syntax for encoding an extended reality scene description according to the present principles is shown;
[0017] - Figure 5 A method of launching an extended reality application including a collision event according to the present principles is shown. DETAILED DESCRIPTION
[0018] The present principles will be described more fully below with reference to the accompanying drawings, in which examples of the present principles are shown. However, the present principles can be implemented in many alternative forms and should not be construed as being limited to the examples described herein. Therefore, although the present principles are susceptible to various modifications and alternative forms, specific examples thereof are shown by way of example in the accompanying drawings and will be described in detail herein. However, it should be understood that the present invention is not intended to limit the present principles to the specific forms disclosed, but rather, the present disclosure is intended to cover all modifications, equivalents, and alternatives that fall within the spirit and scope of the present principles as defined by the claims.
[0019] The terms used herein are only used to describe specific examples and are not intended to limit this principle. The singular forms "a", "an" and "the" used herein are also intended to include plural forms, unless the context clearly states otherwise. It should be further understood that when the terms "comprises", "comprising", "includes" and / or "including" are used in this specification, the existence of the features, integers, steps, operations, elements and / or components is specified, but the existence or addition of one or more other features, integers, steps, operations, elements, components and / or their combinations is not excluded. In addition, when it is mentioned that an element "responds" or "is connected" to another element, it can directly respond or be connected to another element, or there may be an intermediate element. On the contrary, when it is mentioned that an element "directly responds" or "is directly connected" to another element, there is no intermediate element. As used herein, the term "and / or" includes any and all combinations of one or more related listed items, and can be abbreviated as " / ".
[0020] It should be understood that although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the teaching of the present principle.
[0021] Although some diagrams include arrows on communication paths to show a primary direction of communication, it is understood that communication can occur in the opposite direction of the arrows shown.
[0022] Some examples are described with respect to block diagrams and operational flow charts, where each block represents a circuit element, module, or portion of code that includes one or more executable instructions for implementing a specified logical function. It should also be noted that in other embodiments, the functions shown in the blocks may not occur in the order shown. For example, two blocks shown in succession may actually be executed substantially simultaneously, or may sometimes be executed in reverse order, depending on the functions involved.
[0023] References herein to "according to an example" or "in an example" mean that a particular feature, structure, or characteristic described in connection with the example may be included in at least one embodiment of the present principles. The phrases "according to an example" or "in an example" appearing in multiple places in the specification do not necessarily all refer to the same example, nor are separate or alternative examples mutually exclusive of other examples.
[0024] Reference signs appearing in the claims are for illustration purposes only and shall not have a limiting effect on the scope of the claims.The examples and variations may be used in any combination or sub-combination even if not explicitly described.
[0025] Figure 1 An example of an extended reality scene description is shown in Figure 10. In this example, the scene graph may include descriptions of real objects, such as a "flat horizontal surface" (which could be a table or a road) and descriptions of virtual objects 12, such as an animation of a car. The scene description is organized as an array of nodes 10. Nodes may be linked to child nodes to form a scene structure 11. Nodes may carry descriptions of real objects (e.g., semantic descriptions) or descriptions of virtual objects. Figure 1 In the example of , node 101 describes a virtual camera located in the 3D volume of the XR application. Node 102 describes a virtual car and includes an index into a representation of the car, such as an index into an array of 3D meshes. The scene description may include multiple arrays containing descriptions of various aspects of the scene, such as an array containing instructions for multiple animations, an array containing meshes of multiple objects, or an array containing material descriptions. Node 103 is a child of node 102 and contains a description of one of the wheels of the car. Similarly, it contains an index into the 3D mesh of the wheel. Because the scale, position, and orientation of objects are described in scene nodes, the same 3D mesh can be used for multiple objects in a 3D scene. The scene graph 10 also includes nodes that describe the spatial relationships between real objects and virtual objects.
[0026] XR applications are diverse and can be applied to different contexts and real or virtual environments. For example, in an industrial XR application, a virtual 3D content item (e.g., part A of an engine) is displayed when a camera mounted on a head-mounted display device detects a reference object (part B of an engine) in the real environment. The 3D content item is positioned in the real world using a position and scale defined relative to the detected reference object. Similarly, when a collision between real or virtual objects is detected (i.e., a collision between two real objects, two virtual objects, or a real object and a virtual object), operations can be performed on the virtual object.
[0027] For example, in an XR application for interior design, the color of the displayed virtual furniture changes when the user touches a virtual control object or when the user touches a real table. In another application, certain audio files may start playing when two moving displayed virtual objects collide. In another example, when a user grabs a given can of soda in a real environment, an advertising ringtone file may play. However, detecting collisions (or contacts) between real or virtual objects and rendering realistic reactions of virtual objects requires the use of a physics engine that is scalable in terms of memory and processing resources. Therefore, it is important to have a scene description that accurately describes different types of behaviors related to collisions in order to optimize the use of the physics engine. According to the present principles, this article provides such an XR scene description format.
[0028] XR applications can also augment video content instead of the real environment. The video is displayed on the rendering device, and when a timed event is detected in the video, the virtual objects described in the node tree are overlaid. In this case, the node tree only contains virtual object descriptions.
[0029] Figure 2 A non-limiting example of an extended reality scene 20 is shown, which contains real and virtual objects 21 to 25. The XR scene description can include scene-level behavior data. Behaviors are associated with virtual objects, where runtime interactions on the virtual objects are allowed to achieve user-specific XR experiences. Like every element of the XR scene description, behaviors evolve over time and are updated due to the scene description update mechanism.
[0030] The behavior is described at the scenario level in the scenario description, which includes:
[0031] - Triggers, which define the conditions that need to be met to activate them;
[0032] - Trigger control parameters, which define the logical operations between triggers for applying actions;
[0033] – The actions to be processed when the trigger is activated according to the trigger control parameters;
[0034] - Operation control parameters, which define the order in which operations are performed;
[0035] - Priority number, which allows to select the behavior with the highest priority when there are multiple behaviors competing on the same virtual object at the same time;
[0036] - Optional break action that specifies how to terminate a behavior when it is no longer defined in a scene description update. For example, a behavior is no longer defined when the associated object no longer belongs to the new scene or the behavior is no longer relevant to the current media (e.g., audio or video) sequence.
[0037] In such a scene description, collisions are handled by scene-level collision triggers. A collision trigger is activated when a collision is detected between two objects described by two nodes referenced in the description.
[0038] In targeting Figure 2 In the example scene of the scenario:
[0039] - The objects described by nodes 21, 22, and 24 are collidable nodes; therefore, they must be managed by the physics simulation engine. They can be referenced by collision triggers. According to the present principles, the XR scene description identifies first-class objects so that the rendering device can instantiate the physics engine for collision detection and physics simulation.
[0040] -The object of node 23 is also a collidable node, but behaves as a "ghost" object whose movement is not managed by the physics simulation engine. Typically, another object (such as 21 or 22) can pass through the object described by node 23 without physical interaction. It is useful for scene creators to be able to introduce such objects in the scene. In fact, the object of node 23 only requires the physics engine for collision detection and does not need to use physics simulation for itself and other objects, thereby saving memory and processing resources of the XR rendering device. According to the present principle, the XR scene description identifies the second type of object, so the rendering device can instantiate the physics engine for collision detection only. Ghost objects can be referenced by collision triggers.
[0041] -The object of node 25 is a physical object, but the content creator builds the scene so that this object does not have any collision with another object in every possible development of the scene. For example, it can be an object that is visible but far away from the interaction volume and no moving objects can approach it. It is useful for scene creators to be able to introduce this type of object in the scene. In fact, the object of node 25 does not need to use the physics engine at all, saving memory and processing resources of the XR rendering device. According to the present principles, the XR scene description identifies the third category of objects, so that the rendering device can avoid them being managed by the physics engine.
[0042] Figure 2An example scenario may include the following behaviors. The first behavior includes a single trigger that is activated by a collision between the objects of nodes 21 and 22. For example, when this single trigger is activated, the object of node 25 turns red. The second behavior includes a single trigger that is activated by a collision between the objects of nodes 21 and 23 (i.e., ghost objects). For example, when this single trigger is activated, the object of node 25 turns green.
[0043] According to the present principles, as a complement to the scene-level behavior, node-level information indicates whether a node is a collidable node. The following table provides possible semantics for this information. In this embodiment, the physical material parameters are provided as a reference to the physical material array described above. In another embodiment, the physical material parameters can be described in the node.
[0044]
[0045] The collider mesh is the mesh (can be a simplified mesh) used for collision detection. For example, a box, sphere or capsule can be used to speed up collision detection. The fields "useGravity" and "mass" are physics body parameters. It is conceivable to use advanced parameters to further control the physics simulation, such as a "freeze rotation" boolean indicating whether the physics simulation should modify the object's rotation, a "max angular velocity" value to limit the angular velocity in radians per second, and / or a "max escape velocity" value to limit the object's velocity when leaving the collision state.
[0046] A physics material (described in a physics material item array or directly at the node level) may contain the following parameters:
[0047]
[0048] According to this principle, the collision detection parameters of a given node apply to the child nodes of this given node. Therefore, the parent and child nodes of a given node do not contain the fields listed in the first table above.
[0049] exist Figure 2In the example scene, nodes 21, 22, 23, and 24 contain information according to this principle and listed in the first table, making them collidable nodes. Therefore, they can be referenced by two collision triggers. Each node has its specific physical parameters defined according to this principle. For example, node 23 has a true allowOverlap Boolean value, which allows it to overlap with any other object to allow "ghost" behavior. Node 24 has a false useGravity Boolean value to allow ground behavior in the physics simulation (the ground will not fall). The gravity acceleration vector should be defined for the physics simulation, which defines the direction and strength of gravity. The gravity acceleration vector is expressed in meters per square second. If y is the vertical axis, the default value can be the earth's gravity (0.0, -9.81, 0.0). In a first embodiment, the gravity vector is defined at the scene level. In another embodiment, the gravity vector is defined at the node level (making it possible for scenarios where different objects do not fall at the same speed, such as simulating friction with low processing resource costs). According to the present principles, having collision parameters at the scene level allows defining other parameters, such as default values for certain physics body parameters.
[0050] Figure 3 shows that it can be configured to implement Figure 5 Example architecture of XR processing engine 30 of the related method. Figure 3 The devices of the architecture are linked to other devices via their bus 31 and / or via I / O interfaces 36 .
[0051] The device 30 comprises the following elements linked together by a data and address bus 31:
[0052] - a microprocessor 32 (or CPU), which is for example a DSP (or digital signal processor);
[0053] - ROM (or read-only memory) 33;
[0054] - RAM (or random access memory) 34;
[0055] - storage interface 35;
[0056] - an I / O interface 36 for receiving data to be transmitted from an application; and
[0057] -power supply( Figure 3 not shown), such as batteries.
[0058] According to an example, the power supply is located outside the device. In each memory mentioned, the word "register" used in the specification can correspond to a small capacity (a few bits) area or a very large area (such as an entire program or a large amount of received or decoded data). ROM 33 includes at least programs and parameters. ROM 33 can store algorithms and instructions for executing the technology according to the present principles. When turned on, CPU 32 loads the program into RAM and executes the corresponding instructions.
[0059] RAM 34 includes in registers the program executed by CPU 32 and loaded after device 30 is turned on, input data in registers, intermediate data at different states of the method in registers, and other variables in registers used to execute the method.
[0060] The embodiments described herein can be implemented, for example, in methods or processes, devices, computer program products, data streams or signals. Even if only discussed in the context of a single form embodiment (e.g., discussed only as a method or device), the implementation of the discussed features can also be implemented in other forms (e.g., programs). Devices can be implemented, for example, with appropriate hardware, software, and firmware. Methods can be implemented, for example, with devices (such as processors, which generally refer to processing equipment, such as computers, microprocessors, integrated circuits, or programmable logic devices). Processors also include communication devices, such as computers, mobile phones, portable / personal digital assistants ("PDAs") and other devices that facilitate information communication between end users.
[0061] The device 30 is linked to a set of sensors 37 and a set of rendering devices 38, for example, via a bus 31. The sensor 37 may be, for example, a camera, a microphone, a temperature sensor, an inertial measurement unit, a GPS, a humidity sensor, an infrared or ultraviolet light sensor, or a wind sensor. The rendering device 38 may be, for example, a display, a speaker, a vibrator, a heater, a fan, etc.
[0062] According to an example, the device 30 is configured to implement Figure 5 The method according to the present principles is described in and belongs to the following set:
[0063] -mobile device;
[0064] -communication equipment;
[0065] -Gaming equipment;
[0066] - Tablet computer (or tablet computer);
[0067] - Laptop;
[0068] -Still picture camera;
[0069] -Camcorder.
[0070] Figure 4 An example of an embodiment of a data stream syntax for encoding an extended reality scene description according to the present principles is shown. Figure 4 An example structure 4 of an XR scene description is shown. The structure consists of a container that organizes the stream into independent syntax elements. The structure may include a header portion 41, which is a set of data common to each syntax element of the stream. For example, the header portion includes some metadata about the syntax elements, describing the properties and role of each syntax element. The structure also includes a payload, which includes syntax element 42 and syntax element 43. Syntax element 42 includes data representing a media content item described in a scene graph node associated with a virtual element. Images, meshes, and other raw data may have been compressed according to a compression method. Syntax element 43 is part of the data stream payload and includes data for encoding a scene description described in accordance with the present principles.
[0071] Figure 5 A method 50 for launching an extended reality application including a collision event according to the present principles is shown. In step 51, a scene description is obtained. According to the present principles, the scene description includes scene-level behavior information related to collision triggering. According to the present principles, the nodes of the scene graph of the scene description may include the following information about Figure 2 The collision information described. The scene description may include physical parameters (e.g., gravity parameters) at the scene level. In step 52, the physics engine of the application is started and initialized using these physical parameters. In step 53, the scene graph of the scene description is parsed to distinguish three types of nodes. Nodes that do not contain collision information according to the present principle are not linked to the physics engine, that is, the physics engine does not manage the simulation of their collisions and their physical properties. In step 53, the nodes containing collision information according to the present principle are linked to the physics engine to manage collisions. For each of these nodes, a Boolean value indicating whether the object can move or is always static and a grid for detecting collisions (e.g., stored in a grid array and referenced by an index in the node's collision information) are used to initialize the physics engine. The additional parameters contained in the collision information of a given node can be used to initialize the collision detection function of the physics engine. In step 54, the nodes of the scene graph containing collision information with a Boolean value set to true (referred to herein as "allowOverlap") are linked to the physics engine for use in the physics simulation function of the physics engine, wherein the Boolean value indicates whether the object should be considered by the physics simulation. For such nodes, the physics engine is initialized using the physics body parameters (e.g., "useGravity" Boolean, mass or velocity parameters) and material descriptions (which may be stored in a material table or described in a node) contained in the node collision information. At step 55, when the physics engine is initialized using only relevant object properties, the XR application is started.
[0072] The following provides Figure 2 Example of the syntax of scene description as an extension of MPEG-I scene description.
[0073] A single interaction behavior is defined at the scene level and consists of a collision trigger between the first and second nodes and an activation action that enables the third node. The moon gravity acceleration vector (0, -1.625, 0) is defined. At the node level, the first node is a collidable dynamic (i.e. static = false) object using physics simulation, and its associated physics material corresponds to the first material in the materials array. The second node is a collidable static object that has no physics simulation (i.e. allowOverlap = true). The third node is a non-collidable object that is ignored by the physics engine. At the material level, the physical parameters of the first material are elasticity (0.8) and roughness (0.1).
[0074]
[0075]
[0076]
[0077]
[0078] The implementation described herein can be implemented, for example, in a method or process, a device, a computer program product, a data stream or a signal. Even if only discussed in the context of a single form embodiment (e.g., discussed only as a method or device), the implementation of the discussed features can also be implemented in other forms (e.g., programs). The device can be implemented, for example, with appropriate hardware, software, and firmware. The method can be implemented, for example, with a device (such as a processor, which generally refers to a processing device, such as a computer, a microprocessor, an integrated circuit, or a programmable logic device). The processor also includes a communication device, such as a smart phone, a tablet computer, a computer, a mobile phone, a portable / personal digital assistant ("PDA"), and other devices that facilitate information communication between end users.
[0079] The implementation of the various processes and features described herein may be embodied in a variety of different devices or applications, particularly, for example, devices or applications related to data encoding, data decoding, view generation, texture processing, and other processing of images and related texture information and / or depth information. Examples of such devices include encoders, decoders, post-processors for processing outputs from decoders, pre-processors for providing inputs to encoders, video encoders, video decoders, video codecs, network servers, set-top boxes, laptops, personal computers, mobile phones, PDAs, and other communication devices. It should be clear that the device can be mobile and can even be installed in a moving vehicle.
[0080] Furthermore, the methods may be implemented by instructions executed by a processor, and the instructions (and / or data values resulting from the implementation) may be stored on a processor-readable medium, such as an integrated circuit, a software carrier, or other storage device, such as a hard disk, a compact disk ("CD"), an optical disk (such as a DVD, commonly referred to as a digital versatile disk or digital video disk), a random access memory ("RAM"), or a read-only memory ("ROM"). The instructions may form an application tangibly embodied on a processor-readable medium. The instructions may, for example, be hardware, firmware, software, or a combination thereof. The instructions may, for example, be found in an operating system, a separate application, or a combination of both. Thus, a processor may, for example, be characterized as a device configured to perform a process and a device including a processor-readable medium (e.g., a storage device) having instructions for performing the process. Furthermore, the processor-readable medium may store data values resulting from the implementation in addition to or in lieu of the instructions.
[0081] As is known to those of ordinary skill in the art, implementations may generate signals that are formatted in a variety of ways to carry information that can be stored or transmitted, for example. The information may include, for example, instructions for executing a method, or data generated by one of the implementations. For example, a signal may be formatted to carry as data the rules for writing or reading the syntax of the embodiment, or to carry as data the actual syntax values written by the embodiment. Such a signal may, for example, be formatted as an electromagnetic wave (e.g., using the radio frequency portion of the spectrum) or a baseband signal. Formatting may, for example, include encoding a data stream and modulating a carrier with the encoded data stream. The information carried by the signal may, for example, be analog or digital information. As is well known, signals may be transmitted over a variety of different wired or wireless links. The signal may be stored on a processor-readable medium.
[0082] Many embodiments have been described. However, it should be understood that a variety of modifications may be made. For example, elements of different embodiments may be combined, supplemented, modified, or removed to produce other embodiments. In addition, it will be understood by those of ordinary skill in the art that other structures and processes may be substituted for the disclosed structures and processes, and that the resulting embodiments will perform at least substantially the same functions in at least substantially the same manner to achieve at least substantially the same results as the disclosed embodiments. Therefore, the present application includes these and other embodiments.
Claims
1. A method for starting an extended reality application using a physics engine, the method comprising: - Obtaining a description of an extended reality scene, the description comprising a scene graph linking nodes, at least two nodes of the scene graph comprising collision information, the collision information comprising: a first Boolean value indicating whether the object described in the node is static, mesh information, and a second Boolean value indicating whether the physical properties of the object described in the node are simulated; and In case the second Boolean value is true, physics body parameters and material information; - for a node of the scene graph containing collision information, initialize the physics engine using the first Boolean value and the mesh information to perform collision detection; and, if the second Boolean value is true, initialize the physics engine using the physics body parameters and the material information to perform physical simulation; and - Launching the extended reality application. The method of claim 1 , wherein the grid information is an index into a grid table of the description. The method of claim 1 , wherein the material information is an index into a material table of the description. The method according to claim 1 , wherein the material information is described in the collision information.
5. A device for starting an extended reality application using a physics engine, the device comprising a memory and a processor, the processor being configured to: - Obtaining a description of an extended reality scene, the description comprising a scene graph linking nodes, at least two nodes of the scene graph comprising collision information, the collision information comprising: a first Boolean value indicating whether the object described in the node is static, mesh information, and a second Boolean value indicating whether the physical properties of the object described in the node are simulated; as well as In case the second Boolean value is true, physics body parameters and material information; - for a node of the scene graph containing collision information, initialize the physics engine using the first Boolean value and the mesh information to perform collision detection; and, when the second Boolean value is true, initialize the physics engine using the physics body parameters and the material information to perform physical simulation; and - Launching the extended reality application. The apparatus of claim 5 , wherein the grid information is an index into a grid table of the description. The apparatus of claim 5 , wherein the material information is an index into a material table of the description. The apparatus according to claim 5 , wherein the material information is described in the collision information.
9. A data stream carrying data representing a description of an augmented reality scene, the description comprising: - A scene graph that links nodes; - at least two nodes of the scene graph contain collision information, the collision information comprising: a first Boolean value indicating whether the object described in the node is static, mesh information, and a second Boolean value indicating whether the physics of the object described in the node is simulated; and • In case the second Boolean value is true, physics body parameters and material information.
10. The data stream of claim 9, wherein the grid information is an index into a grid table of the description.
11. The data stream of claim 9, wherein the material information is an index into a material table of the description.
12. The data stream according to claim 9, wherein the material information is described in the collision information.
Citation Information
Cited By
Method to generate physics parameters in an ar experience
EP4842000A1
