Compatible rendering method, device, equipment, storage medium and program product

Abstract

This application discloses a compatible rendering method, apparatus, device, storage medium, and program product, relating to the field of rendering technology. The method includes: obtaining a new SDK object in response to an adjustment operation on an SDK object; assigning a rendering engine to the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and another rendering engine; and rendering the new SDK object by calling the interface of the assigned rendering engine to obtain a rendering result. This application is compatible with multiple rendering methods and reduces processing costs.

Description

Technical Field

[0001] The present application relates to the field of rendering technology, and in particular to a compatible rendering method, a compatible rendering apparatus, a compatible rendering device, a storage medium, and a computer program product. Background Art

[0002] Currently, there are many rendering methods. For example, cloud rendering leverages the powerful computing resources of the cloud to place rendering tasks on cloud servers, transmits data over the network, and returns the results after rendering is completed. It is suitable for processing complex scenes. For example, end-to-end rendering relies on local device hardware, such as the computer's GPU and CPU, to perform rendering operations, and focuses more on local resource utilization and immediate response. Because different rendering methods such as cloud rendering and end-to-end rendering have significant differences in many aspects such as resource utilization, data transmission, and rendering algorithms, in order to support different rendering engines simultaneously in application development, it is often necessary to adapt different SDKs (Software Development Kits) separately. This makes the development process complicated and the processing costs such as manpower and time are quite high, increasing processing costs and becoming a technical problem that needs to be solved urgently. Summary of the Invention

[0003] The main purpose of this application is to provide a compatible rendering method, a compatible rendering device, a compatible rendering equipment, a storage medium and a computer program product, aiming to solve the technical problem of high processing cost when supporting multiple rendering engines.

[0004] To achieve the above objectives, this application proposes a compatible rendering method, which includes:

[0005] In response to an adjustment operation on the SDK object, a new SDK object is obtained, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object;

[0006] Allocate a rendering engine for the new SDK object, wherein the rendering engine includes a cloud rendering engine, a terminal rendering engine, and other rendering engines;

[0007] By calling the interface of the assigned rendering engine, the new SDK object is rendered to obtain a rendering result.

[0008] In one embodiment, the adjustment operation is an editing operation, and the compatible rendering method includes:

[0009] In response to an edit operation on an attribute of an sdk object, a diff object is obtained according to the changed attribute and attribute value of the sdk object;

[0010] Parse the diff objects according to the rendering engine type, and assign corresponding rendering engines to the new sdk objects restored from the diff objects;

[0011] The new SDK object is rendered by calling the interface of the assigned rendering engine to obtain a rendering result.

[0012] In one embodiment, the step of parsing the diff objects separately according to the rendering engine type includes:

[0013] The cloud rendering engine parses the diff object according to the cloud rendering logic through the cloud rendering object to obtain a first parsing result, and allocates the cloud rendering engine according to the first parsing result;

[0014] The end rendering engine parses the diff object according to the end rendering logic through the end rendering object to obtain a second parsing result, and allocates the end rendering engine according to the second parsing result;

[0015] For other rendering engines, the diff object is parsed according to preset parsing rules through other rendering objects to obtain a third parsing result, and other rendering engines are allocated according to the third parsing result.

[0016] In one embodiment, the adjustment operation is a new operation, and the compatible rendering method includes:

[0017] In response to the new operation on the sdk object attribute, a new sdk object is obtained;

[0018] Get the attribute value of the newly added attribute of the new SDK object;

[0019] The rendering engine interface is called according to the attribute value to render the new SDK object to obtain a rendering result.

[0020] In one embodiment, the adjustment operation is a deletion operation, and the compatible rendering method includes:

[0021] In response to the deletion operation on the sdk object attribute, a new sdk object is obtained;

[0022] According to the attributes of the new SDK object after deletion, the interface of the rendering engine is called to render the new SDK object to obtain a rendering result.

[0023] In one embodiment, the method includes:

[0024] Add an object call state attribute to the SDK object, wherein the default state of the object call state attribute is the call end state;

[0025] When calling the rendering engine to render the SDK object, the state of the object call state attribute is set to the calling state;

[0026] When the rendering engine is called to complete rendering of the SDK object, the state of the object call state attribute is modified to the call end state.

[0027] In addition, to achieve the above-mentioned purpose, the present application also proposes a compatible rendering device, which includes: an adjustment module, configured to obtain a new SDK object in response to an adjustment operation on an SDK object, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object;

[0028] An allocation module, configured to allocate a rendering engine to the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and other rendering engines;

[0029] The rendering module is used to render the new SDK object by calling the interface of the assigned rendering engine to obtain a rendering result.

[0030] In addition, to achieve the above-mentioned purpose, the present application also proposes a compatible rendering device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the compatible rendering method described above.

[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the steps of the compatible rendering method described above are implemented.

[0032] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the compatible rendering method described above are implemented.

[0033] One or more technical solutions proposed in this application have at least the following technical effects:

[0034] Compared with the existing technology, which requires building multiple different SDKs to adapt to different rendering methods, which increases processing costs, this application obtains a new SDK object in response to the adjustment operation of the SDK object, and then allocates a rendering engine. It only needs to operate based on one set of SDK architecture, which reduces the workload of developing multiple sets of SDKs. Based on the unified SDK object operation, different rendering engines are allocated, which can flexibly select the most suitable rendering method according to actual needs, breaking the previous limitation of strictly relying on fixed SDKs to select corresponding rendering methods. When facing different rendering scenarios, hardware conditions and business needs, the appropriate rendering engine can be selected to complete the rendering task, reducing processing costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0036] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0037] Figure 1 A flowchart illustrating an embodiment of a compatible rendering method of the present application is provided;

[0038] Figure 2 A flowchart illustrating another embodiment of the compatible rendering method of the present application is provided;

[0039] Figure 3 A flowchart of the rendering engine processing provided by the compatible rendering method of this application;

[0040] Figure 4 A flowchart illustrating another embodiment of the compatible rendering method of the present application is provided;

[0041] Figure 5 A brief flowchart of the compatible rendering method provided for this application;

[0042] Figure 6 A schematic diagram of the module structure of a rendering device compatible with this application;

[0043] Figure 7 A schematic diagram of the device structure of the hardware operating environment involved in the compatible rendering method of this application.

[0044] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0045] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0046] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0047] Generally speaking, software development kits (SDKs) are typically designed and built around specific functionality or a single core engine. Rendering engines themselves have complex internal architectures, diverse rendering logic, and unique resource requirements and invocation methods. Breaking this convention by integrating multiple rendering engines with diverse features into a single SDK and orchestrating their operation with a single call is challenging and requires a deep and comprehensive understanding of the underlying principles, interface specifications, and data interaction methods of each rendering engine. While a variety of rendering engines are emerging, and there are practices for selecting different rendering engines for different scenarios, switching and invoking different rendering engines is often done through a relatively complex process involving separate code modules and configuration files. There is no universal solution that directly integrates multiple rendering engines within a single SDK and simplifies multi-engine collaboration with a single call.

[0048] This application adjusts the SDK object to obtain a new SDK object, flexibly assigns the corresponding rendering engine to the new SDK object, and integrates multiple rendering engines into a set of SDKs. When faced with the need to flexibly switch and comprehensively use different rendering engines to meet diverse rendering needs, a unified calling method is used to select the appropriate rendering engine to complete the rendering task, thereby reducing processing costs.

[0049] It should be noted that the execution subject of this embodiment can be a compatible rendering device, or a computing service device with data processing, network communication, and program execution capabilities, such as a tablet computer, personal computer, mobile phone, etc., or an electronic device or processor capable of implementing the above functions. This embodiment and the following embodiments will be described below using a compatible rendering device as an example.

[0050] Based on this, the embodiment of the present application provides a compatible rendering method, referring to Figure 1 , Figure 1 This is a flowchart of an embodiment of the compatible rendering method of the present application.

[0051] In this embodiment, the compatible rendering method includes steps S10 to S30:

[0052] Step S10, in response to the adjustment operation on the SDK object, a new SDK object is obtained, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object;

[0053] It's important to note that some adjustments are performed on the original SDK objects. An SDK object is a collection of various properties, including scene objects, light objects, geometry objects, and model objects. SDK objects expose callable APIs (Application Programming Interfaces). Users can save desired operations to the object by calling the SDK object's APIs. Scene objects include 3D modeling scenes, light objects are used to set lighting effects within the scene, such as the position, intensity, and color of light sources. Geometry objects are various geometric shapes, such as cubes and spheres, or complex shapes composed of these basic shapes. Model objects are pre-built object models with specific appearances and properties, such as character models and building models. By adjusting SDK objects, such as changing the position of an object in the scene, adjusting the intensity of a light, or replacing a model, a new SDK object is generated. This new object contains the adjusted state of the scene, light, geometry, and model properties. Adjustment operations can include adding, editing, and deleting.

[0054] Step S20: assigning a rendering engine to the new SDK object, where the rendering engine includes a cloud rendering engine, a client rendering engine, and other rendering engines;

[0055] It should be noted that after obtaining a new SDK object, you need to select a suitable rendering engine to render it. Rendering engines include cloud rendering engines, end-to-end rendering engines, and other rendering engines. The cloud rendering engine is an engine that uses cloud computing resources for rendering, using the powerful computing power of cloud servers, and is suitable for processing complex scenes and high-quality rendering tasks; the end-to-end rendering engine is an engine that renders on local devices (such as computers, mobile phones and other terminal devices), with good real-time performance, and is suitable for some scenarios with high interactivity requirements and where the local device performance can meet the rendering requirements; other rendering engines include some rendering engines for special needs or specific platforms.

[0056] Step S30: Render the new SDK object by calling the interface of the assigned rendering engine to obtain a rendering result.

[0057] It's important to note that once the rendering engine is determined, rendering operations are performed by calling its interface. The rendering engine's interface is a channel that allows external programs to interact with the rendering engine. Through this interface, the relevant data of the new SDK object (such as scene layout, lighting settings, geometry and model properties, etc.) is passed to the rendering engine. The rendering engine calculates and processes this data, converting the attributes of the new SDK object into visual content such as images or videos that can be displayed on compatible rendering devices. This final visual content is the rendering result.

[0058] In this embodiment, by obtaining a new SDK object in response to the adjustment operation of the SDK object and then assigning a rendering engine, operations only need to be performed based on one set of SDK architecture, reducing the workload of developing multiple sets of SDKs; based on unified SDK object operations, different rendering engines are then assigned, which can flexibly select the most suitable rendering method according to actual needs, breaking the previous limitation of strictly relying on a fixed SDK to select the corresponding rendering method, so that when facing different rendering scenarios, hardware conditions and business needs, a suitable rendering engine can be selected to complete the rendering task, reducing processing costs.

[0059] In one embodiment, the compatible rendering method includes steps T10 to T30:

[0060] Step T10, adding an object call state attribute to the SDK object, wherein the default state of the object call state attribute is the call end state;

[0061] It should be noted that an object call status attribute is added to the SDK object to record the state of the SDK object during the call process. Its default state is set to the call end state, providing an initial reference point for subsequent tracking of the SDK object call state.

[0062] Step T20, when calling the rendering engine to render the SDK object, setting the state of the object calling state attribute to the calling state;

[0063] It's important to note that when the rendering engine begins to render an SDK object, the object's invocation state property must be changed. Setting it to the invocation state indicates that the SDK object is being invoked by the rendering engine and is in the rendering process. For example, in a multi-tasking or multi-threaded environment, this state can be used to determine whether other operations can be performed on the SDK object. If it is in the invocation state, you need to wait for rendering to complete before performing other related operations.

[0064] Step T30: After the rendering engine is called to complete rendering of the SDK object, the state of the object call state attribute is modified to the call end state.

[0065] It should be noted that once the rendering engine completes the rendering operation of the SDK object, it is necessary to change the state of the object's call state attribute again and set it back to the call end state, which indicates that the call process of the SDK object has ended.

[0066] In one embodiment, a function type is defined in the SDK object to clearly indicate the various states of the function, such as "call completed" and "calling in progress". An attribute named "getStrustTree getStrustTree" is added to the SDK object, and the attribute value defaults to the "call completed" state. When the call operation of the SDK object is triggered, the attribute value of "getStrustTree getStrustTree" is set to the "calling in progress". The rendering object of the rendering engine monitors changes in the attribute value of "getStrustTree getStrustTree". In the calling logic, when it is determined that the attribute "getStrustTree getStrustTree" exists and the attribute value is "calling in progress", the rendering engine is called for rendering. After the rendering is completed, the attribute value is changed back to the "call completed" state. Only when the SDK object is called again and a specific call operation is triggered, the operation of calling the rendering engine will be executed again to avoid repeated calls.

[0067] In this embodiment, the setting of the object call status attribute helps to clearly track the call status of the SDK object. The status attribute can be used to determine whether the SDK object can be used for other operations, avoiding unnecessary interference operations when the SDK object is being rendered, avoiding repeated calls, achieving orderly collaboration between multiple tasks, and improving concurrent processing capabilities.

[0068] Based on the above embodiment of the present application, in another embodiment of the present application, the same or similar contents as the above embodiment can be referred to the above introduction, and no further details will be given later. Figure 2 The compatible rendering method further includes steps D10 to D30:

[0069] Step D10, in response to the edit operation on the SDK object attribute, obtaining a diff object according to the changed attribute and attribute value of the SDK object;

[0070] It's important to note that when editing the properties of an SDK object, such as modifying the color of an object in a scene object or adjusting the intensity of a light object, the changed property refers to the specific property being edited (such as color or intensity), while the property value is the specific value assigned to the property after the edit. Based on these changed properties and their corresponding values, a diff object is generated. This diff object essentially records the changed parts of the SDK object and is primarily used to track and manage changes to SDK object properties.

[0071] In one embodiment, the steps of obtaining a diff object according to the changed attributes and attribute values of the sdk object include:

[0072] Determine the changed properties of the new and old SDK objects;

[0073] According to the changed attributes, the changed attributes of the new and old SDK objects and the attribute values of the changed attributes are merged to obtain a diff object.

[0074] For example: Initial scene object: {

[0075] objectId: -1,

[0076] objectType: Scene3D,

[0077] children: {

[0078] 12345: {

[0079] objectId: 12345,

[0080] objectType: Light3D,

[0081] lightColor: "red",

[0082] intensity: "Intensity is 3",

[0083] };

[0084] };

[0085] }.

[0086] Edited scene object: {

[0087] objectId: -1,

[0088] objectType: Scene3D,

[0089] children: {

[0090] 12345: {

[0091] objectId: 12345,

[0092] objectType: Light3D,

[0093] lightColor: "white",

[0094] intensity: "Intensity is 5",

[0095] };

[0096] 56789: {

[0097] objectId: 56789,

[0098] objectType: Camera3D,

[0099] flySpeed: 100,

[0100] };

[0101] };

[0102] }.

[0103] diff object:

[0104] objectId: -1,

[0105] objectType: Scene3D,

[0106] children: {

[0107] 12345: {

[0108] objectId: 12345,

[0109] objectType: Light3D,

[0110] lightColor: {

[0111] newValue: "white",

[0112] oldValue: "red",

[0113] };

[0114] intensity:

[0115] newValue: "Intensity is 5",

[0116] oldValue: "Intensity is 3",

[0117] };

[0118] };

[0119] 56789: {

[0120] newValue: {

[0121] objectId: 56789,

[0122] objectType: Camera3D,

[0123] flySpeed: 100,

[0124] };

[0125] oldValue: null,

[0126] };

[0127] };

[0128] }.

[0129] Step D20: Parse the diff objects according to the rendering engine type, and assign a corresponding rendering engine to the new sdk object restored from the diff object;

[0130] It's important to note that different types of rendering engines (such as cloud rendering engines and end-to-end rendering engines) handle SDK objects differently. Parsing a diff object involves analyzing the changed properties of the SDK object. Parsing the diff object restores the new SDK object, which contains its state after the edit operation. Based on the characteristics of the new SDK object (i.e., the rendering engine-compatible information obtained by parsing the diff object), an appropriate rendering engine is assigned to it. For example, if the parsed new SDK object's changed properties are more suitable for the processing capabilities and characteristics of a cloud rendering engine (such as complex lighting calculations), the cloud rendering engine is assigned to it. If it is more suitable for the fast rendering needs of the local device, the end-to-end rendering engine is assigned to it.

[0131] For example, restore the diff object to obtain a new sdk object:

[0132] diff object: {

[0133] objectId: 12345,

[0134] objectType: Light3D,

[0135] lightColor: {

[0136] newValue: "white",

[0137] oldValue: "red",

[0138] },

[0139] intensity:

[0140] newValue: "Intensity is 5",

[0141] oldValue: "Intensity is 3",

[0142] }

[0143] }.

[0144] New SDK object: {

[0145] objectId: 12345,

[0146] objectType: Light3D,

[0147] lightColor: "white",

[0148] intensity: "Intensity is 5",

[0149] }.

[0150] For example, Figure 3 As shown, Figure 3 The specific rendering process in the rendering engine: First, a mapping table is stored in the compatible rendering device. In the mapping table, object types (objectType) are associated with corresponding rendering objects (scene objects, light objects, geometry objects, and model objects). The mapping table includes key-value pairs. For example, the mapping table stores objectType-Light3D, where the key is objectType (object type) and the value is the light object (rendering object). Based on the object type (objectType), the corresponding rendering object is obtained, and then the rendering engine to be called is determined.

[0151] Then, traverse and parse the diff object. The diff object contains the properties of the SDK object and the properties of the new SDK object, such as object type (objectType), new property value (newValue), old property value (oldValue), etc. For example: SDK object: objectType: Light3D, lightColor: {oldValue: "red"};

[0152] New SDK object: objectType: Light3D, lightColor: {newValue: "white", oldValue: "red"};

[0153] diff object: objectType: Light3D, lightColor: {newValue: "white", oldValue: "red"};

[0154] From the analysis, we can see that the object type is a light object, the new attribute value of the light color corresponding to the light object is white, and the old attribute value of the light color corresponding to the light object is red.

[0155] At the same time, based on the object type obtained from the parsing, the render object is obtained and the render object to be rendered is determined. The diff object is parsed to obtain the new attribute value (newValue) and the old attribute value (oldValue). Next, the new attribute value (newValue) and the old attribute value (oldValue) are used to determine what operation to perform on the render object: If neither the old attribute value (oldValue) nor the new attribute value (newValue) exist, it indicates a delete operation, and the corresponding delete function in the render object is called. If the old attribute value (oldValue) does not exist but the new attribute value (newValue) exists, it indicates an add operation, and the corresponding add function in the render object is called. If both the old attribute value (oldValue) and the new attribute value (newValue) exist, it indicates an edit operation, and the edit function in the render object is called.

[0156] In one embodiment, step D20 includes steps A10 to A30:

[0157] Step A10: The cloud rendering engine parses the diff object according to the cloud rendering logic using the cloud rendering object to obtain a first parsing result, and allocates the cloud rendering engine according to the first parsing result.

[0158] It's important to note that the cloud rendering engine uses the cloud rendering object to parse the diff object according to cloud rendering logic, which considers large-scale data processing, allocation of complex computing resources, and cloud storage utilization. When parsing the diff object (an object that records changes to SDK object properties), the cloud rendering engine identifies changes relevant to cloud rendering based on the rules defined by the cloud rendering object. For example, these changes impact large-scale scene rendering and high-precision computation in cloud rendering. The first parsing result includes the factors that influence the selection of rendering engines based on the attribute changes in the diff object from a cloud rendering perspective. Based on this first parsing result, if the modified SDK object is more suitable for the cloud rendering engine's capabilities (e.g., the modified scene is more complex and requires significant computing resources that the cloud rendering engine can provide), the cloud rendering engine is assigned.

[0159] Step A20: The end rendering engine parses the diff object according to the end rendering logic using the end rendering object to obtain a second parsing result, and allocates the end rendering engine according to the second parsing result.

[0160] It's important to note that during the parsing process, the end-rendering engine utilizes the end-rendering object and operates according to the end-rendering logic. When parsing the diff object, the end-rendering engine identifies attribute changes related to end-rendering based on the rules set by the end-rendering object (such as the local device's hardware characteristics and real-time rendering requirements). Based on this second parsing result, if the changed SDK object is suitable for the end-rendering engine's capabilities (for example, the changed scene is relatively simple, has high real-time requirements, and the local device can meet the rendering requirements), it will be assigned to the end-rendering engine.

[0161] In step A30 , other rendering engines parse the diff object according to preset parsing rules through other rendering objects to obtain a third parsing result, and allocate other rendering engines according to the third parsing result.

[0162] It should be noted that for rendering engines other than the cloud rendering engine and the end rendering engine, other rendering objects are used for parsing according to preset parsing rules, where the preset parsing rules are formulated based on the characteristics of the other rendering engines themselves, and may be for special rendering algorithms, specific platforms or specific application scenarios. When parsing the diff object, the attribute changes related to these special requirements will be found to obtain a third parsing result. According to this third parsing result, if the changed SDK object is suitable for the capabilities of other rendering engines, then other rendering engines will be assigned.

[0163] In this embodiment, the original logic can be extended through a customized rendering object to parse the diff object, thereby handling the special cases of a specific rendering engine. Specifically, parsing is performed separately according to the category of the rendering engine to obtain parsing results, and the corresponding rendering engine is assigned according to the parsing results. This can accurately assign appropriate tasks to the corresponding rendering engine, thereby improving adaptability in different scenarios.

[0164] Step D30: Render the new SDK object by calling the interface of the assigned rendering engine to obtain a rendering result.

[0165] It should be noted that a new SDK object is assigned a suitable rendering engine, and rendering is performed by calling the rendering engine's interface. The new SDK object is passed to the rendering engine, which processes this information based on its own algorithms and functions, such as calculating lighting effects and object display effects. Ultimately, the new SDK object is converted into visual content such as images and videos that can be displayed on the screen, resulting in a rendering result.

[0166] This step can simplify the call to the rendering engine. The functions that need to be implemented by calling the APIs of multiple rendering engines can be implemented by calling the API of the SDK object once.

[0167] In one embodiment, the step of rendering the new SDK object by calling the interface of the assigned rendering engine to obtain the rendering result includes:

[0168] Determine whether the changed attribute exists in the old SDK object;

[0169] If the changed attribute exists in the old SDK object, the rendering engine interface is called to render the new SDK object according to the attribute value of the changed attribute to obtain the rendering result.

[0170] like Figure 4 As shown, when the changed attribute exists in the old SDK object, the interface of the rendering engine is called to render the new SDK object according to the attribute value of the changed attribute to obtain the rendering result.

[0171] If the changed attribute does not exist in the old SDK object, no processing is performed. This is equivalent to a new or delete operation instead of an edit operation.

[0172] In this embodiment, by specially creating a diff object to record changes, we can more clearly understand the state changes of the SDK object under different operations. In the scenario where the SDK object is edited multiple times, the diff object can accurately reflect the content of each change; by parsing the diff object to assign the rendering engine, we can reasonably assign the task to the appropriate rendering engine, so that the rendering effect can better match the scene requirements, and obtain high-quality rendering results based on the actual changes of the SDK object and the characteristics of the rendering engine.

[0173] Based on the above embodiment of the present application, in another embodiment of the present application, the same or similar contents as the above embodiment can be referred to the above introduction and will not be described in detail later. The compatible rendering method further includes:

[0174] In response to the new operation on the sdk object attribute, a new sdk object is obtained;

[0175] Get the attribute value of the newly added attribute of the new SDK object;

[0176] The rendering engine interface is called according to the attribute value to render the new SDK object to obtain a rendering result.

[0177] It's important to note that adding new attributes to an SDK object adds new elements to the existing SDK object structure. The original SDK object only contained basic attributes like color and shape. By adding attributes like texture and transparency, a new SDK object is created. This new SDK object differs from the original in its data structure; it expands upon the original and contains more information needed to implement specific functionality, such as more complex rendering effects.

[0178] After obtaining a new SDK object, you need to obtain the attribute values of the newly added attributes because of the newly added attributes. Attribute values are used to determine the specific content of the attributes. Obtaining attribute values is necessary so that the rendering engine can accurately render the new SDK object according to the specific values of the new attributes in subsequent rendering operations.

[0179] According to the attribute values of the newly added attributes of the new SDK object obtained, the rendering engine interface is called to perform rendering operations, converting the SDK object into a visual image or scene to produce the final rendering effect.

[0180] In this embodiment, by adding attributes to the SDK object and calling the rendering engine interface to render the new SDK object with the newly added attributes, a rendering result is obtained. The ability to flexibly add attributes to SDK objects as needed allows the SDK to meet more diverse needs without the need for redevelopment. This allows for quick additions to SDK objects and new rendering results, which is more efficient than rebuilding rendering logic.

[0181] In a feasible implementation manner, the compatible rendering method further includes: obtaining a new SDK object in response to a deletion operation on an SDK object attribute;

[0182] According to the attributes of the new SDK object after deletion, the interface of the rendering engine is called to render the new SDK object to obtain a rendering result.

[0183] It should be noted that deleting an SDK object's attributes is equivalent to removing the attributes from the SDK object. For example, if an SDK object used for rendering originally contains attributes such as color, shape, and texture, and the texture attribute is deleted, the SDK object after the attribute deletion operation becomes a new SDK object.

[0184] After obtaining the new SDK object (that is, the object after the attributes are deleted), since its attributes have changed, the rendering engine interface is called according to these deleted attributes for rendering. The rendering engine renders the new SDK object based on the remaining attributes of the new SDK object to obtain a rendering result that conforms to the characteristics of the new SDK object.

[0185] In this embodiment, when a new SDK object is obtained after the attribute deletion operation is performed on the SDK object and rendered, the rendering engine does not need to perform complex calculations related to these attributes when rendering the new SDK object, which can reduce the time and computing resources required for rendering, thereby improving rendering efficiency.

[0186] For example, Figure 5 A brief diagram of the compatible rendering method: First, construct the SDK object, including scene objects, light objects, geometry objects, and model objects. After adjusting the SDK object (adding operations, editing operations, and deleting operations), a new SDK object is obtained. After comparing the new SDK object with the old SDK object, the changed attributes in the SDK object are obtained; then, the cloud rendering object, end rendering object, and other rendering objects use the parsing rules of the corresponding rendering engine to parse the results of the comparison between the new SDK object and the old SDK object; based on the parsing results, the API of the corresponding rendering engine is called to render the changed attributes in the SDK object to obtain the rendering result.

[0187] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the compatible rendering method of the present application. More forms of simple transformations based on this technical concept, such as the interaction and combination of various embodiments, are all within the scope of protection of the present application.

[0188] This application also provides a compatible rendering device, please refer to Figure 6 , the compatible rendering device includes:

[0189] An adjustment module 10 is configured to obtain a new SDK object in response to an adjustment operation on an SDK object, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object;

[0190] An allocation module 20 is configured to allocate a rendering engine to the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and other rendering engines;

[0191] The rendering module 30 is used to render the new SDK object by calling the interface of the assigned rendering engine to obtain a rendering result.

[0192] Optionally, the compatible rendering device includes an editing module: configured to obtain a diff object according to the changed attributes and attribute values of the SDK object in response to an editing operation on the attributes of the SDK object;

[0193] Parse the diff objects according to the rendering engine type, and assign corresponding rendering engines to the new sdk objects restored from the diff objects;

[0194] The new SDK object is rendered by calling the interface of the assigned rendering engine to obtain a rendering result.

[0195] Optionally, the editing module is configured to parse the diff object according to the cloud rendering logic for the cloud rendering engine through the cloud rendering object to obtain a first parsing result, and allocate the cloud rendering engine according to the first parsing result;

[0196] The end rendering engine parses the diff object according to the end rendering logic through the end rendering object to obtain a second parsing result, and allocates the end rendering engine according to the second parsing result;

[0197] For other rendering engines, the diff object is parsed according to preset parsing rules through other rendering objects to obtain a third parsing result, and other rendering engines are allocated according to the third parsing result.

[0198] Optionally, the compatible rendering device includes a new adding module: in response to a new adding operation on an attribute of an sdk object, obtaining a new sdk object;

[0199] Get the attribute value of the newly added attribute of the new SDK object;

[0200] The rendering engine interface is called according to the attribute value to render the new SDK object to obtain a rendering result.

[0201] Optionally, the compatible rendering device includes a deletion module: configured to obtain a new SDK object in response to a deletion operation on an SDK object attribute;

[0202] According to the attributes of the new SDK object after deletion, the interface of the rendering engine is called to render the new SDK object to obtain a rendering result.

[0203] Optionally, the compatible rendering device includes a state calling module: configured to add an object calling state attribute to the SDK object, wherein the default state of the object calling state attribute is a call end state;

[0204] When calling the rendering engine to render the SDK object, the state of the object call state attribute is set to the calling state;

[0205] When the rendering engine is called to complete rendering of the SDK object, the state of the object call state attribute is modified to the call end state.

[0206] The compatible rendering device provided in this application, utilizing the compatible rendering method described in the aforementioned embodiments, can address the technical issue of high processing costs associated with supporting multiple rendering engines. Compared to the prior art, the beneficial effects of the compatible rendering device provided in this application are the same as those of the compatible rendering method described in the aforementioned embodiments. Other technical features of the compatible rendering device are the same as those disclosed in the aforementioned embodiments and are not further elaborated here.

[0207] The present application provides a compatible rendering device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the compatible rendering method in the first embodiment described above.

[0208] Reference below Figure 7, which shows a schematic diagram of the structure of a compatible rendering device suitable for implementing the embodiments of the present application. The compatible rendering device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The compatible rendering device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0209] like Figure 7 As shown, a compatible rendering device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 1002 or programs loaded from a storage device 1003 into a random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the compatible rendering device. Processing device 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage device 1003 including, for example, a magnetic tape or hard disk; and communication devices 1009. Communication device 1009 can allow a compatible rendering device to communicate with other devices wirelessly or wired to exchange data. Although the figures show a compatible rendering device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or have alternatively.

[0210] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0211] The compatible rendering device provided in this application, utilizing the compatible rendering method described in the aforementioned embodiment, can address the technical issue of high processing costs associated with supporting multiple rendering engines. Compared to the prior art, the beneficial effects of the compatible rendering device provided in this application are identical to those of the compatible rendering method described in the aforementioned embodiment. Other technical features of the compatible rendering device are identical to those disclosed in the aforementioned embodiment and are not further elaborated upon here.

[0212] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0213] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0214] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, wherein the computer-readable program instructions are used to execute the compatible rendering method in the above-mentioned embodiment.

[0215] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0216] The computer-readable storage medium may be included in a compatible rendering device, or may exist independently without being incorporated into a compatible rendering device.

[0217] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by a compatible rendering device, the compatible rendering device: obtains a new SDK object in response to an adjustment operation on the SDK object, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object; allocates a rendering engine to the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and other rendering engines; renders the new SDK object by calling the interface of the allocated rendering engine to obtain a rendering result.

[0218] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0219] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0220] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0221] The computer-readable storage medium provided in this application stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned compatible rendering method. This computer-readable storage medium can address the technical issue of high processing costs associated with supporting multiple rendering engines. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are similar to those of the compatible rendering method provided in the aforementioned embodiments and are not further elaborated here.

[0222] The present application also provides a computer program product, comprising a computer program, which implements the steps of the compatible rendering method described above when executed by a processor.

[0223] The computer program product provided in this application can solve the technical problem of high processing costs when supporting multiple rendering engines. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the compatible rendering method provided in the above embodiment, and will not be repeated here.

[0224] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A compatible rendering method, characterized in that: The compatible rendering method includes: In response to an adjustment operation on an SDK object, a new SDK object is obtained, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object; the step of obtaining the new SDK object in response to the adjustment operation on the SDK object comprises: when the adjustment operation is an edit operation, in response to the edit operation on the SDK object attribute, obtaining a diff object according to the changed attribute and attribute value of the SDK object; parsing the diff object according to the rendering engine type, restoring the diff object to obtain a new SDK object corresponding to the edit operation; when the adjustment operation is a new operation, in response to the new operation on the SDK object attribute, obtaining a new SDK object corresponding to the new operation; when the adjustment operation is a delete operation, in response to the delete operation on the SDK object attribute, obtaining a new SDK object corresponding to the delete operation; Allocate a rendering engine for the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and other rendering engines, and multiple rendering engines are integrated into a set of SDKs; By calling the interface of the assigned rendering engine, the new SDK object is rendered to obtain a rendering result, wherein the function of calling the APIs of multiple rendering engines is realized by calling the API of the SDK object once to perform the rendering task.

2. The compatible rendering method according to claim 1, wherein: The step of parsing the diff objects respectively according to the rendering engine type includes: The cloud rendering engine parses the diff object according to the cloud rendering logic through the cloud rendering object to obtain a first parsing result, and allocates the cloud rendering engine according to the first parsing result; The end rendering engine parses the diff object according to the end rendering logic through the end rendering object to obtain a second parsing result, and allocates the end rendering engine according to the second parsing result; For other rendering engines, the diff object is parsed according to preset parsing rules through other rendering objects to obtain a third parsing result, and other rendering engines are allocated according to the third parsing result.

3. The compatible rendering method according to claim 1, wherein: The adjustment operation is a new operation, and the compatible rendering method includes: Get the attribute value of the new attribute of the new SDK object corresponding to the new operation; The rendering engine interface is called according to the attribute value to render the new SDK object to obtain a rendering result.

4. The compatible rendering method according to claim 1, wherein: The adjustment operation is a deletion operation, and the compatible rendering method includes: According to the attributes of the new SDK object after deletion corresponding to the deletion operation, the interface of the rendering engine is called to render the new SDK object to obtain a rendering result.

5. The method according to claim 1, wherein The method comprises: Add an object call state attribute to the SDK object, wherein the default state of the object call state attribute is the call end state; When calling the rendering engine to render the SDK object, the state of the object call state attribute is set to the calling state; When the rendering engine is called to complete rendering of the SDK object, the state of the object call state attribute is modified to the call end state.

6. A compatible rendering device, characterized in that: The compatible rendering device includes: An adjustment module is configured to obtain a new SDK object in response to an adjustment operation on an SDK object, wherein the SDK object includes a scene object, a light object, a geometry object, and a model object; the adjustment module is further configured to, when the adjustment operation is an edit operation, obtain a diff object based on the changed attributes and attribute values of the SDK object in response to an edit operation on an SDK object attribute; parse the diff objects according to the rendering engine type, and restore the diff objects to obtain a new SDK object corresponding to the edit operation; when the adjustment operation is a new operation, obtain a new SDK object corresponding to the new operation in response to an add operation on an SDK object attribute; and when the adjustment operation is a delete operation, obtain a new SDK object corresponding to the delete operation in response to an delete operation on an SDK object attribute. An allocation module, configured to allocate a rendering engine to the new SDK object, wherein the rendering engine includes a cloud rendering engine, an end rendering engine, and other rendering engines, and multiple rendering engines are integrated into a set of SDKs; The rendering module is used to render the new SDK object by calling the interface of the assigned rendering engine to obtain the rendering result, wherein the function of calling the API of multiple rendering engines is realized by calling the API of the SDK object once to perform the rendering task.

7. A compatible rendering device, characterized in that The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the compatible rendering method according to any one of claims 1 to 5.

8. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the compatible rendering method according to any one of claims 1 to 5 are implemented.

9. A computer program product, characterized in that The computer program product comprises a computer program, which implements the steps of the compatible rendering method according to any one of claims 1 to 5 when executed by a processor.

Images