Debugging Method, Device, Storage Medium and Electronic Device

Abstract

The present disclosure relates to a debugging method, apparatus, storage medium, and electronic device to solve problems existing in the related art. The method includes: in response to a debugging operation of a user on a three-dimensional digital asset in an application to be debugged, obtaining debugging information; wherein, the debugging operation is performed by the user when it is determined that the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet a preset effect, and the application software to be debugged refers to the application software after the application to be debugged is packaged and installed; generating a debugging request according to the debugging information; and sending the debugging request to the application software to be debugged, so that the application software to be debugged debugs a target three-dimensional digital asset in the application software to be debugged based on the debugging information.

Description

Technical Field

[0001] The present disclosure relates to the field of computer network technologies, and in particular, to a debugging method, apparatus, storage medium, and electronic device. Background Art

[0002] Developing a 3D application software involves producing 3D digital assets in a digital content production tool and importing the 3D digital assets into a 3D engine, where the digital assets are produced and adjusted. In this process, developers can preview the performance effects of the digital assets in the 3D engine and readjust the digital assets when the preview effects do not meet the preset effects until the performance effects of the digital assets meet the preset effects. Then, the digital assets and the logic program are packaged and installed on the user device to become an application software. However, after the application software is installed on the user device, the effects presented by the digital assets in the application software on the user device may still be inconsistent with the preset effects. In this case, developers need to remanufacture, adjust, preview, package the digital assets in the 3D engine and install the packaged digital assets on the user device. Summary of the Invention

[0003] The purpose of the present disclosure is to provide a debugging method, apparatus, storage medium, and electronic device to solve the problems existing in the related technologies.

[0004] To achieve the above purpose, according to the first aspect of the embodiments of the present disclosure, a debugging method is provided. The method includes:

[0005] In response to a debugging operation of a user on a 3D digital asset in a to-be-debugged application program, obtain debugging information;

[0006] wherein the debugging operation is performed by the user when it is determined that the rendering effect of the 3D digital asset in the to-be-debugged application software does not meet the preset effect, and the to-be-debugged application software refers to the application software after the to-be-debugged application program is packaged and installed;

[0007] Generate a debugging request according to the debugging information;

[0008] Send the debugging request to the to-be-debugged application software so that the to-be-debugged application software debugs the target 3D digital asset in the to-be-debugged application software based on the debugging information.

[0009] Optionally, the debugging information includes a debugging type, and the method further includes:

[0010] When the debugging type represents deleting a 3D digital asset, the debugging request is used to instruct the to-be-debugged application software to delete the target 3D digital asset.

[0011] Optionally, the debugging information includes a debugging type and a debugging value, and the method further includes:

[0012] When the debugging type represents a change to a 3D digital asset, the debugging request is used to instruct the application software to be debugged to update the target 3D digital asset according to the debugging value.

[0013] Optionally, the debugging information includes a debugging type, the target 3D digital asset, and location information of the target 3D digital asset, where the location information includes the 3D coordinates and rotation angle of the target 3D digital asset, and the method further includes:

[0014] When the debugging type represents adding a 3D digital asset, the debugging request is used to instruct the application software to be debugged to save the target 3D digital asset and add the target 3D digital asset to the application software to be debugged based on the 3D coordinates and rotation angle.

[0015] Optionally, the obtaining the debugging information in response to a user's debugging operation on a 3D digital asset in an application software to be debugged includes:

[0016] In response to a user's debugging operation on a 3D digital asset in the application software to be debugged, checking whether the 3D digital asset in the application software to be debugged is consistent with the 3D digital asset in the application software to be debugged;

[0017] When the 3D digital asset in the application software to be debugged is consistent with the 3D digital asset in the application software to be debugged, obtaining the debugging information.

[0018] Optionally, the method further includes:

[0019] When the 3D digital asset in the application software to be debugged is inconsistent with the 3D digital asset in the application software to be debugged, synchronizing the 3D digital asset in the application software to be debugged;

[0020] Prompting the user to perform the debugging operation on the 3D digital asset in the application software to be debugged again to obtain the debugging information.

[0021] Optionally, the debugging request includes the ID of the application software to be debugged, and the sending the debugging request to the application software to be debugged includes:

[0022] Sending the debugging request to a server so that the server forwards the debugging request to the application software to be debugged corresponding to the ID.

[0023] According to a second aspect of the embodiments of the present disclosure, there is provided a debugging device, and the device includes:

[0024] An acquisition module, configured to acquire debugging information in response to a debugging operation of a user on a three-dimensional digital asset in an application to be debugged;

[0025] Wherein, the debugging operation is performed by the user when it is determined that the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet the preset effect, and the application software to be debugged refers to the application software after packaging and installing the application to be debugged;

[0026] A generation module, configured to generate a debugging request according to the debugging information;

[0027] A sending module, configured to send the debugging request to the application software to be debugged, so that the application software to be debugged debugs the target three-dimensional digital asset in the application software to be debugged based on the debugging information.

[0028] According to a third aspect of the embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the method described in any one of the first aspects above are implemented.

[0029] According to a fourth aspect of the embodiments of the present disclosure, there is provided an electronic device, including:

[0030] A memory, on which a computer program is stored;

[0031] A processor, configured to execute the computer program in the memory to implement the steps of the method described in any one of the first aspects above.

[0032] Adopting the above technical solutions, at least the following technical effects can be achieved:

[0033] By responding to a user's debugging operation on a 3D digital asset in an application to be debugged, corresponding debugging information is obtained. Herein, the debugging operation is performed by the user when the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after packaging and installation of the application to be debugged. A corresponding debugging request is generated according to the debugging information, and the debugging request is sent to the application software to be debugged, so that when the application software to be debugged receives the debugging request, it can debug the target 3D digital asset in the application software based on the debugging information. By adopting the method of the present disclosure, when the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect, a debugging operation can be performed on the 3D digital asset in the application to be debugged corresponding to the application software to be debugged, and the debugging information is sent to the application software to be debugged to modify the corresponding digital asset in the application software to be debugged, so that the rendering effect of the debugged digital asset in the application software to be debugged meets the preset effect. Compared with the related art, when the rendering effect of the digital asset in the application software is inconsistent with the preview effect, the developer needs to remanufacture, adjust, preview and package the 3D digital asset in the 3D engine, and then update the application software according to the new 3D digital asset package. The method of the present disclosure does not need to re-execute the process of previewing and packaging the 3D digital asset in the 3D engine and installing the packaged 3D digital asset into the application software. Therefore, the method of the present disclosure can improve the debugging efficiency of the 3D digital asset.

[0034] Other features and advantages of the present disclosure will be described in detail in the following specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The drawings are used to provide a further understanding of the present disclosure, and constitute a part of the specification, and are used to explain the present disclosure together with the following specific implementation, but do not constitute a limitation to the present disclosure. In the drawings:

[0036] Figure 1 is a flowchart of a debugging method shown in an exemplary embodiment of the present disclosure.

[0037] Figure 2 is a block diagram of a debugging device shown in an exemplary embodiment of the present disclosure.

[0038] Figure 3 is a block diagram of an electronic device shown in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] The following will describe in detail the specific implementation of the present disclosure with reference to the drawings. It should be understood that the specific implementation described herein is only for explaining and understanding the present disclosure, and is not used to limit the present disclosure.

[0040] The following provides a detailed description of the debugging method, device, storage medium, and electronic device provided by the embodiments of the present disclosure.

[0041] Figure 1 is a flowchart of a debugging method shown according to an exemplary embodiment of the present disclosure. As Figure 1 shown, the method includes:

[0042] S101. In response to a user's debugging operation on a three-dimensional digital asset in an application to be debugged, obtain debugging information.

[0043] S102. Generate a debugging request according to the debugging information.

[0044] Among them, the debugging operation is performed by the user when it is determined that the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after packaging and installation of the application to be debugged, and the application software to be debugged and the application to be debugged have the same three-dimensional digital assets.

[0045] The technical solution provided by the embodiments of the present disclosure can be applied to the process of real-time development and debugging of three-dimensional application software. For example, when the application software developed through a three-dimensional engine runs on a terminal device, the user can debug the application program of the application software according to the actual rendering effect of the three-dimensional digital asset on the terminal device. When debugging the application program, corresponding debugging information can be generated according to the user's debugging operation, and a debugging request can be generated according to the debugging information. The debugging request can be used to adjust the three-dimensional digital asset in the application software in the running state. In some embodiments, the debugging operation performed by the user is performed when it is determined that the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet the preset effect, and the preset effect can be the preview effect of the three-dimensional digital asset in the application to be debugged.

[0046] It should be noted that by packaging the application program developed in the 3D engine and then installing the program package into the terminal device, the application software corresponding to the application program can be obtained, and the 3D digital assets in the application program and the application software are the same. If the rendering effect of the 3D digital assets in the application software does not meet the preset effect, the user can debug the 3D digital assets so that the rendering effect of the 3D digital assets in the application software meets the preset effect. The debugging methods include modifying, deleting, and adding 3D digital assets. The 3D digital assets can be static or dynamic. The 3D digital assets can include, but are not limited to, meshes, shaders, lights, material textures, and audio and video in the 3D scene. Different types of 3D digital assets can have different parameters. For example, the parameters of a mesh include vertex data, index data, and normal data, etc. The parameters of a light include radiation distance, attenuation exponent, and color, etc. The 3D digital assets can also include entity objects composed of 3D digital assets such as meshes, such as chairs, tables, and houses, etc.

[0047] Specifically, in response to the user's debugging operation on the 3D digital assets in the application program to be debugged, debugging information is obtained, and a debugging request is generated according to the debugging information. Among them, the user's debugging operation can be deleting the target 3D digital asset, adding the target 3D digital asset, and changing the target 3D digital asset, etc. For example, if the user's debugging operation is to delete the target 3D digital asset, then the debugging information can include at least one of the unique identifier (UID, Unique Identifier) or the universally unique identifier (UUID, Universally Unique Identifier) of the target 3D digital asset, the UID / UUID of the entity object to which the target 3D digital asset belongs, and the index data of the target 3D digital asset under the entity object. If the user's debugging operation is to add the target 3D digital asset, then the debugging information can include the target 3D digital asset and the position information of the target 3D digital asset. This position information is used to represent the display position of the target 3D digital asset in the 3D scene presented by the application software to be debugged.

[0048] In some implementation manners, the debugging request can be encapsulated according to the debugging information, and the debugging request can be sent to the application software to be debugged.

[0049] S103. Send the debugging request to the application software to be debugged, so that the application software to be debugged debugs the target 3D digital assets in the application software to be debugged based on the debugging information.

[0050] Among them, a module for receiving requests is set in the application software to be debugged, and this module is used to listen for debug requests. After receiving a debug request, the application software to be debugged can debug the target three-dimensional digital asset according to the debug information in the debug request. In some embodiments, under the Java framework, a listener can be set to listen for debug requests, and response operations corresponding to different types of debug requests can be set in the listener to perform corresponding response operations according to the debug information in different types of debug requests, so as to debug the target three-dimensional digital asset.

[0051] It should be noted that the technical solution provided by the embodiments of the present disclosure can be implemented on one terminal device or on multiple terminal devices. When implemented on one terminal device, in response to a user's debug operation on the three-dimensional digital asset in the application program to be debugged, a debug request can be generated according to the obtained debug information and sent to the application software to be debugged in the local machine, so that the application software to be debugged performs corresponding debugging based on the debug information. When implemented on multiple terminal devices, the application program to be debugged can run on the first terminal device, and the application software to be debugged can run on the second terminal device. The first terminal device generates a debug request according to the obtained debug information in response to a user's debug operation on the three-dimensional digital asset in the application program to be debugged and sends it to the second terminal device, so that the application software to be debugged on the second terminal device performs corresponding debugging based on the debug information.

[0052] In addition, it should be noted that the above debug method of the present disclosure is applicable to real-time debug scenarios.

[0053] By adopting the above method, corresponding debugging information is obtained in response to a user's debugging operation on a 3D digital asset in an application to be debugged. Among them, the debugging operation is performed by the user when the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after packaging and installing the application to be debugged. A corresponding debugging request is generated according to the debugging information, and the debugging request is sent to the application software to be debugged, so that when the application software to be debugged receives the debugging request, it can debug the target 3D digital asset in the application software based on the debugging information. By adopting this method of the present disclosure, when the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect, a debugging operation can be performed on the 3D digital asset in the application to be debugged corresponding to the application software to be debugged, and the debugging information is sent to the application software to be debugged to modify the corresponding digital asset in the application software to be debugged, so that the rendering effect of the debugged digital asset in the application software to be debugged meets the preset effect. Compared with the related art, when the rendering effect of the digital asset in the application software is inconsistent with the preview effect, the developer needs to remake, adjust, preview and package the 3D digital asset in the 3D engine, and then update the application software according to the new 3D digital asset package. The method of the present disclosure does not need to re-execute the process of previewing and packaging the 3D digital asset in the 3D engine and installing the packaged 3D digital asset into the application software. Therefore, this method of the present disclosure can improve the debugging efficiency of the 3D digital asset.

[0054] To make the technical solution provided by the present disclosure easier to understand for those of ordinary skill in the art, the above steps will be described in detail with examples below.

[0055] It can be understood that the debugging information may include a debugging type, which is used to characterize the type of the user's debugging operation on the 3D digital asset in the application to be debugged. Among them, for different types of debugging operations, the obtained debugging information may include the following situations:

[0056] In the first case, when the debugging operation of the user represents the deletion of a certain 3D digital asset, the debugging type in the debugging information represents the deletion of the 3D digital asset. In addition, the debugging information may further include at least one of the unique identifier (UID, Unique Identifier) or the universally unique identifier (UUID, Universally Unique Identifier) of the target 3D digital asset, the UID / UUID of the entity object to which the target 3D digital asset belongs, and the index data of the target 3D digital asset under the entity object. Each 3D digital asset constituting the entity object has corresponding index data, and the index data is used to point to the 3D digital asset under the entity object. It can be understood that the debugging request generated according to the debugging information can be used to instruct the application software to be debugged to delete the target 3D digital asset.

[0057] In some embodiments, the debugging information includes the UID / UUID of the target 3D digital asset. In this case, the UID / UUID can point to a 3D digital asset such as a mesh, or can point to an entity object composed of 3D digital assets such as a mesh. After receiving the debugging information, when the debugging type represents the deletion of a 3D digital asset, the application software to be debugged can determine the target 3D digital asset according to the UID / UUID, and thus delete the target 3D digital asset.

[0058] In other embodiments, the debugging information includes the UID / UUID of the entity object to which the target 3D digital asset belongs, and the index data of the target 3D digital asset under the entity object. In this case, the UID / UUID can point to an entity object composed of 3D digital assets such as a mesh, and the index data is used to point to the target 3D digital asset under the entity object. An entity object can be composed of multiple 3D digital assets. After receiving the debugging information, when the debugging type represents the deletion of a 3D digital asset, the application software to be debugged can determine the entity object according to the UID / UUID, and then determine the target 3D digital asset under the entity object according to the index data, and thus delete the target 3D digital asset.

[0059] In the second case, when the debugging operation characterized by the user represents modifying a 3D digital asset, the debugging type in the debugging information is used to characterize the change of the 3D digital asset. In addition, the debugging information may further include the UID / UUID of the target 3D digital asset and the debugging value, or include the UID / UUID of the entity object to which the target 3D digital asset belongs, the index data of the target 3D digital asset under the entity object, and the debugging value. Among them, the debugging value may be the difference between the parameter value after debugging and the parameter value before debugging, or may be the parameter value after debugging. Different 3D digital assets may correspond to different debugging values. For example, if the 3D digital asset is a shader, the debugging value may be the RGB value representing the color. If the 3D digital asset is light, the debugging value may be the value representing the radiation distance, and may also be the value representing the attenuation exponent. If the 3D digital asset is an entity object, the debugging value may be the position information of the entity object, etc. It can be understood that the debugging request generated according to the debugging information can be used to instruct the application software to be debugged to update the target 3D digital asset according to the debugging value.

[0060] In specific implementation, the process of determining the target 3D digital asset in the application software to be debugged is similar to the first case. After receiving the debugging information, when the debugging type represents changing the 3D digital asset, the target 3D digital asset is first determined. After determining the target 3D digital asset, the parameter value to be debugged in the target 3D digital asset is updated according to the debugging value.

[0061] In the third case, when the debugging operation represents adding a 3D digital asset, the debugging type in the debugging information represents adding a 3D digital asset. In addition, the debugging information may further include the target 3D digital asset and the position information of the target 3D digital asset. It should be noted that the 3D digital asset corresponds to position information, which represents the display position of the 3D digital asset in the 3D scene presented by the application software. The position information includes the 3D coordinates and rotation angle of the target 3D digital asset. It can be understood that the debugging request generated according to the debugging information can be used to instruct the application software to be debugged to save the target 3D digital asset and add the target 3D digital asset to the application software to be debugged based on the 3D coordinates and rotation angle.

[0062] In specific implementation, after receiving the debugging information, when the debugging type represents adding a 3D digital asset, the application software to be debugged determines the display position of the target 3D digital asset in the 3D scene presented by the application software to be debugged according to the 3D coordinates and rotation angle, and adds the target 3D digital asset to the display position.

[0063] It should be understood that the application to be debugged has a variety of 3D digital assets, and the application software to be debugged corresponding to the application to be debugged also has a variety of 3D data assets. Each 3D digital asset in the application to be debugged is usually in one-to-one correspondence with each 3D digital asset in the application software to be debugged. However, new 3D digital assets can also be obtained from the 3D engine in the application to be debugged, and these new 3D digital assets are not pre-stored in the configuration file of the application software to be debugged. Therefore, if the target 3D digital asset added by the user in the application to be debugged is not a new 3D digital asset obtained from the 3D engine, it can be determined that the target 3D digital asset has been pre-stored in the configuration file of the application software to be debugged. In this case, the debugging information may not include the target 3D digital asset. That is to say, after receiving the debugging information, the application software to be debugged can directly obtain the target 3D digital asset from the local storage according to the UID / UUID of the target 3D digital asset.

[0064] In addition, in the third case, the debugging information may also include the scale of the target 3D digital asset. The scale is used to specify the size of the 3D digital asset. The parameter of the scale can be the scaling factor, which is used to represent the scaling factors of the 3D digital asset in the three axis directions of the 3D space. For example, (1, 1, 1) means that the 3D digital asset has no scaling. (2, 1, 1) means that the 3D digital asset is scaled 2 times in the X-axis direction and has no scaling in the Y-axis and Z-axis directions.

[0065] Optionally, the above step S101 may include:

[0066] In response to the user's debugging operation on the 3D digital asset in the application to be debugged, check whether the 3D digital asset in the application to be debugged is consistent with the 3D digital asset in the application software to be debugged;

[0067] When the 3D digital asset in the application to be debugged is consistent with the 3D digital asset in the application software to be debugged, obtain the debugging information.

[0068] It should be noted that in response to the user's operation, the state of the 3D digital asset in the 3D scene presented by the application software to be debugged can be updated, and the updated state of the 3D digital asset may not be consistent with the default state of the 3D digital asset in the application to be debugged. Therefore, in order to prevent the default state of the 3D digital asset debugged by the user in the application to be debugged from being inconsistent with the actual state of the 3D digital asset in the application software to be debugged and affecting the debugging effect, the consistency of the two states can be checked when it is detected that the user performs a debugging operation.

[0069] For example, the application software to be debugged updates the material of a chair asset in a three-dimensional scene in response to a user operation, resulting in the actual state of the chair asset being inconsistent with the default state. In such a case, if the material of the chair asset is not updated in a timely manner in the application program to be debugged according to the actual state of the chair in the application software to be debugged, it is possible that the user may change the chair asset or other three-dimensional digital assets in the default state based on the rendering effect of the actual state of the chair asset, which will inevitably lead to the final rendering effect being inconsistent with the preset effect. To avoid this situation, in a specific implementation, in response to a debugging operation by the user on a three-dimensional digital asset in the application program to be debugged, it is checked whether the three-dimensional digital asset in the application program to be debugged is consistent with the state of the three-dimensional digital asset in the application software to be debugged. Only when the three-dimensional digital asset in the application program to be debugged is consistent with the state of the three-dimensional digital asset in the application software to be debugged, the debugging information is obtained.

[0070] Optionally, the method provided by the embodiments of the present disclosure may further include:

[0071] When the three-dimensional digital asset in the application program to be debugged is inconsistent with the three-dimensional digital asset in the application software to be debugged, synchronize the three-dimensional digital asset in the application software to be debugged;

[0072] Prompt the user to re-perform the debugging operation on the three-dimensional digital asset in the application program to be debugged to obtain the debugging information.

[0073] It can be understood that when the three-dimensional digital asset in the application program to be debugged is inconsistent with the state of the three-dimensional digital asset in the application software to be debugged, synchronize the three-dimensional digital asset in the application software to be debugged, and prompt the user to re-perform the debugging operation on the three-dimensional digital asset in the application program to be debugged to obtain the debugging information.

[0074] In a possible implementation, in response to a user's debugging operation on a 3D digital asset in an application to be debugged, the target 3D digital asset to be debugged by the user is determined, and it is checked whether the status of the target 3D digital asset in the application to be debugged is consistent with the status of the target 3D digital asset in the application software to be debugged. Among them, the synchronization information can be obtained from the application software to be debugged, and based on this synchronization information, it is determined whether the status of the target 3D digital asset in the application software to be debugged is consistent with its status in the application to be debugged. Moreover, when it is checked that the statuses of the two are inconsistent, the target 3D digital asset in the application software to be debugged can be synchronized according to this synchronization information. It can be understood that after synchronizing the target 3D digital asset, the user can be prompted to re-perform the debugging operation on the 3D digital asset in the application to be debugged, and the corresponding debugging information can be obtained according to the debugging operation re-performed by the user. Among them, the synchronization information can be used to synchronize the 3D digital assets in the application software to be debugged in the application to be debugged.

[0075] It should be noted that the running priority of the module that receives requests in the application software to be debugged can be lower than the priority of the application software to be debugged for updating the status of 3D digital assets in response to user operations. That is to say, when the user runs the application software to be debugged and performs corresponding operations, the application software to be debugged preferentially responds to the user's operations to update the status of 3D digital assets, and then listens for whether a debugging request is received. In this way, the technical solution provided by the embodiments of the present disclosure can ensure that the application software to be debugged preferentially meets the user's usage requirements during operation, and when no user operation is received, the application software to be debugged is debugged according to the debugging request.

[0076] Optionally, the debugging request includes the ID of the application software to be debugged, and the above step S103 may include:

[0077] Sending the debugging request to the server so that the server forwards the debugging request to the application software to be debugged corresponding to the ID.

[0078] It can be understood that the communication between the application to be debugged and the application software to be debugged can be forwarded by the server.

[0079] In some embodiments, each application software to be debugged running on the terminal device has an ID that can identify the terminal device. Therefore, different real-time debugging can be performed on the application software to be debugged running on different terminal devices according to the ID of the terminal device. Specifically, the debugging request is sent to the server so that the server forwards the debugging request to the application software to be debugged on the terminal device corresponding to the ID. Among them, only one application software to be debugged can run on one terminal device.

[0080] In some other embodiments, the ID of the application software to be debugged is used to identify the application software to be debugged. Therefore, different real-time debugging can be performed for different application software to be debugged according to the ID of the application software to be debugged. Specifically, a debugging request is sent to the server so that the server sends the debugging request to the application software to be debugged corresponding to the ID. Among them, multiple application software to be debugged can run on one terminal device.

[0081] By adopting the above method, corresponding debugging information is obtained in response to a user's debugging operation on a three-dimensional digital asset in an application program to be debugged. Among them, the debugging operation is performed by the user when the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after the application program to be debugged is packaged and installed. A corresponding debugging request is generated according to the debugging information, and the debugging request is sent to the application software to be debugged, so that the application software to be debugged can, when receiving the debugging request, debug the target three-dimensional digital asset in the application software based on the debugging information. By adopting the method of the present disclosure, when the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet the preset effect, a debugging operation can be performed on the three-dimensional digital asset in the application program to be debugged corresponding to the application software to be debugged, and the debugging information is sent to the application software to be debugged to modify the corresponding digital asset in the application software to be debugged, so that the rendering effect of the debugged digital asset in the application software to be debugged meets the preset effect. Compared with the related art in which when the rendering effect of a digital asset in an application software is inconsistent with the preview effect, the developer needs to remanufacture, adjust, preview, and package the three-dimensional digital asset in a three-dimensional engine, and then update the application software according to the new three-dimensional digital asset package, the method of the present disclosure does not need to re-execute the process of previewing and packaging the three-dimensional digital asset in the three-dimensional engine and installing the packaged three-dimensional digital asset into the application software. Therefore, the method of the present disclosure can improve the debugging efficiency of the three-dimensional digital asset.

[0082] Based on the same inventive concept, the present disclosure further provides a debugging device. Refer to Figure 2 , Figure 2 FIG. is a block diagram of a debugging device shown according to an exemplary embodiment of the present disclosure. As Figure 2 shown, the debugging device 100 includes:

[0083] An acquisition module 101, configured to obtain debugging information in response to a user's debugging operation on a three-dimensional digital asset in an application program to be debugged;

[0084] Among them, the debugging operation is performed by the user when it is determined that the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after the application program to be debugged is packaged and installed.

[0085] A generation module 102, configured to generate a debugging request according to the debugging information;

[0086] A sending module 103, configured to send the debugging request to the application software to be debugged, so that the application software to be debugged debugs the target 3D digital asset in the application software to be debugged based on the debugging information.

[0087] By using the above device, corresponding debugging information is obtained by responding to the user's debugging operation on the 3D digital asset in the application program to be debugged. Among them, this debugging operation is performed by the user when the rendering effect of this 3D digital asset in the application software to be debugged does not meet the preset effect. The application software to be debugged refers to the application software after the application program to be debugged is packaged and installed. A corresponding debugging request is generated according to this debugging information, and the debugging request is sent to the application software to be debugged, so that when the application software to be debugged receives this debugging request, it can debug the target 3D digital asset in the application software based on the debugging information. By using the device of the present disclosure, when the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect, a debugging operation can be performed on the 3D digital asset in the application program to be debugged corresponding to the application software to be debugged, and the debugging information is sent to the application software to be debugged to modify the corresponding digital asset in the application software to be debugged, so that the rendering effect of the debugged digital asset in the application software to be debugged meets the preset effect. Compared with the related technology, when the rendering effect of the digital asset in the application software is inconsistent with the preview effect, the developer needs to remanufacture, adjust, preview and package the 3D digital asset in the 3D engine, and then update the application software according to the new 3D digital asset package. The device of the present disclosure does not need to re-execute the process of previewing and packaging the 3D digital asset in the 3D engine and installing the packaged 3D digital asset into the application software. Therefore, the device of the present disclosure can improve the debugging efficiency of the 3D digital asset.

[0088] Optionally, the debugging information includes a debugging type, and the device 100 further includes:

[0089] A first indication module, configured to, when the debugging type represents deleting a 3D digital asset, the debugging request is used to instruct the application software to be debugged to delete the target 3D digital asset.

[0090] Optionally, the debugging information includes a debugging type and a debugging value, and the device 100 further includes:

[0091] A second indication module, configured to, when the debugging type represents changing a 3D digital asset, the debugging request is used to instruct the application software to be debugged to update the target 3D digital asset according to the debugging value.

[0092] Optionally, the debugging information includes a debugging type, the target 3D digital asset, and location information of the target 3D digital asset. The location information includes 3D coordinates and a rotation angle of the target 3D digital asset. The apparatus 100 further includes:

[0093] A third indication module, configured to, when the debugging type represents adding a 3D digital asset, the debugging request is used to instruct the application software to be debugged to save the target 3D digital asset and add the target 3D digital asset to the application software to be debugged based on the 3D coordinates and the rotation angle.

[0094] Optionally, the obtaining module 101 is further configured to:

[0095] In response to a debugging operation of a user on a 3D digital asset in the application software to be debugged, check whether the 3D digital asset in the application software to be debugged is consistent with the 3D digital asset in the application software to be debugged;

[0096] When the 3D digital asset in the application software to be debugged is consistent with the 3D digital asset in the application software to be debugged, obtain the debugging information.

[0097] Optionally, the apparatus 100 further includes:

[0098] A synchronization module, configured to, when the 3D digital asset in the application software to be debugged is inconsistent with the 3D digital asset in the application software to be debugged, synchronize the 3D digital asset in the application software to be debugged;

[0099] A prompt module, configured to prompt the user to perform the debugging operation on the 3D digital asset in the application software to be debugged again to obtain the debugging information.

[0100] Optionally, the debugging request includes an ID of the application software to be debugged. When sending the debugging request to the application software to be debugged, the sending module 103 is further configured to:

[0101] Send the debugging request to a server, so that the server forwards the debugging request to the application software to be debugged corresponding to the ID.

[0102] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0103] Based on the same inventive concept, an embodiment of the present disclosure further provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the above debugging method are implemented.

[0104] Specifically, the computer-readable storage medium may be a flash memory, a hard disk, a multimedia card, a card-type memory (such as an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, a public cloud server, and so on.

[0105] Regarding the computer-readable storage medium in the above embodiments, the implementation of the steps of the debugging method when the computer program stored thereon is executed has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0106] Based on the same inventive concept, an embodiment of the present disclosure further provides an electronic device, which includes:

[0107] A memory, on which a computer program is stored;

[0108] A processor, configured to execute the computer program in the memory to implement the steps of the above debugging method.

[0109] Figure 3 It is a block diagram of an electronic device 200 shown according to an exemplary embodiment. As Figure 3 shown, the electronic device 200 may include: a processor 201, a memory 202. The electronic device 200 may further include one or more of a multimedia component 203, an input / output (I / O) interface 204, and a communication component 205.

[0110] Among them, the processor 201 is used to control the overall operation of the electronic device 200 to complete all or part of the steps in the above debugging method. The memory 202 is used to store various types of data to support the operation of the electronic device 200. These data may include, for example, instructions for any application or method operating on the electronic device 200, as well as application-related data, such as contact data, received and sent messages, pictures, audio, video, and so on. The memory 202 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disc. The multimedia component 203 may include a screen and an audio component. Among them, the screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 202 or sent through the communication component 205. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 204 provides an interface between the processor 201 and other interface modules. The above other interface modules may be a keyboard, a mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 205 is used for wired or wireless communication between the electronic device 200 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, near field communication (NFC), 2G, 3G, 4G, or 5G, NB-IoT (Narrow Band Internet of Things), or a combination of one or more of them. Accordingly, the communication component 205 may include: a Wi-Fi module, a Bluetooth module, and an NFC module.

[0111] In an exemplary embodiment, the electronic device 200 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components, and is used to execute the above debugging method.

[0112] The preferred embodiments of the present disclosure have been described in detail above in conjunction with the accompanying drawings. However, the present disclosure is not limited to the specific details in the above embodiments. Within the technical concept of the present disclosure, various simple modifications can be made to the technical solutions of the present disclosure, and these simple modifications all fall within the protection scope of the present disclosure.

[0113] In addition, it should be noted that, among the various specific technical features described in the above specific embodiments, without conflict, they can be combined in any appropriate manner. To avoid unnecessary repetition, the present disclosure will not separately describe various possible combination manners.

[0114] In addition, any combination can be made between various different embodiments of the present disclosure, as long as it does not violate the idea of the present disclosure, and it should also be regarded as the content disclosed by the present disclosure.

Claims

1. A debugging method, characterized in that, The method includes: In response to a debugging operation by a user on a 3D digital asset in an application to be debugged, obtaining debugging information; wherein, the debugging operation is performed by the user when it is determined that the rendering effect of the 3D digital asset in the application software to be debugged does not meet the preset effect, and the application software to be debugged refers to the application software after packaging and installing the application to be debugged; Generating a debugging request according to the debugging information; Sending the debugging request to the application software to be debugged, so that the application software to be debugged debugs the target 3D digital asset in the application software to be debugged based on the debugging information; The obtaining debugging information in response to a debugging operation by a user on a 3D digital asset in an application to be debugged includes: In response to a debugging operation by a user on a 3D digital asset in an application to be debugged, checking whether the 3D digital asset in the application to be debugged is consistent with the 3D digital asset in the application software to be debugged; When the 3D digital asset in the application to be debugged is consistent with the 3D digital asset in the application software to be debugged, obtaining the debugging information; When the 3D digital asset in the application to be debugged is inconsistent with the 3D digital asset in the application software to be debugged, synchronizing the 3D digital asset in the application software to be debugged; Prompting the user to re-perform the debugging operation on the 3D digital asset in the application to be debugged to obtain the debugging information; wherein, the running priority of the module for receiving requests in the application software to be debugged is lower than the priority for the application software to be debugged to update the status of the 3D digital asset in response to a user operation.

2. The method according to claim 1, characterized in that, The debugging information includes a debugging type, and the method further includes: When the debugging type indicates deleting a 3D digital asset, the debugging request is used to instruct the application software to be debugged to delete the target 3D digital asset.

3. The method according to claim 1, characterized in that The debugging information includes a debugging type and a debugging value, and the method further includes: When the debugging type indicates changing a 3D digital asset, the debugging request is used to instruct the application software to be debugged to update the target 3D digital asset according to the debugging value.

4. The method according to claim 1, wherein The debugging information includes a debugging type, the target 3D digital asset, and the position information of the target 3D digital asset, where the position information includes the 3D coordinates and rotation angle of the target 3D digital asset, and the method further includes: When the debugging type indicates adding a 3D digital asset, the debugging request is used to instruct the application software to be debugged to save the target 3D digital asset and add the target 3D digital asset to the application software to be debugged based on the 3D coordinates and rotation angle.

5. The method according to claim 1, wherein The debugging request includes the ID of the application software to be debugged, and the sending the debugging request to the application software to be debugged includes: Sending the debugging request to a server, so that the server forwards the debugging request to the application software to be debugged corresponding to the ID.

6. A debugging device, characterized in that, The device includes: An acquisition module, configured to acquire debugging information in response to a debugging operation of a user on a three-dimensional digital asset in an application to be debugged; wherein, the debugging operation is performed by the user when it is determined that the rendering effect of the three-dimensional digital asset in the application software to be debugged does not meet a preset effect, and the application software to be debugged refers to the application software after packaging and installing the application to be debugged; A generation module, configured to generate a debugging request according to the debugging information; A sending module, configured to send the debugging request to the application software to be debugged, so that the application software to be debugged debugs a target three-dimensional digital asset in the application software to be debugged based on the debugging information; The acquisition module is further configured to: In response to a debugging operation of a user on a three-dimensional digital asset in an application to be debugged, check whether the three-dimensional digital asset in the application to be debugged is consistent with the three-dimensional digital asset in the application software to be debugged; When the three-dimensional digital asset in the application to be debugged is consistent with the three-dimensional digital asset in the application software to be debugged, acquire the debugging information; The device further includes: A synchronization module, configured to synchronize the three-dimensional digital asset in the application software to be debugged when the three-dimensional digital asset in the application to be debugged is inconsistent with the three-dimensional digital asset in the application software to be debugged; A prompt module, configured to prompt the user to re-perform the debugging operation on the three-dimensional digital asset in the application to be debugged to acquire the debugging information; wherein, the running priority of the module for receiving requests in the application software to be debugged is lower than the priority of the application software to be debugged for updating the state of the three-dimensional digital asset in response to a user operation.

7. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the steps of the method according to any one of claims 1-5.

8. An electronic device, characterized in that, including: A memory, on which a computer program is stored; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1-5.

Images