A special effect making method, device, equipment and storage medium

Abstract

Embodiments of the present disclosure provide a special effect production method, device, equipment and storage medium. The method comprises: displaying a special effect production interface; receiving a component adding operation, the component adding operation being selecting component tag information of a first target component in a presented component menu list; determining a first sub-navigation level table to which the first target component belongs, and presenting the component tag information under a target level node of the first sub-navigation level table; wherein the first sub-navigation level table is pre-displayed in a special effect component navigation view according to a first rendering order. By using the method, in the process of special effect production, after receiving the component adding operation of the special effect component, automatic classification and division of the special effect component can be directly realized, and automatic sorting between the sub-navigation level tables in the special effect component navigation view is equivalent to automatically realizing configuration of the rendering order of the special effect component. The method simplifies the special effect production process and reduces the development understanding cost of the designer.

Description

Technical Field

[0001] This disclosure relates to the field of computer application technology, and in particular to a method, apparatus, device and storage medium for creating special effects. Background Technology

[0002] With the development of computer technology, many special effects scenes based on technologies such as virtual reality have emerged. Currently, special effects scenes can be created using 3D scene creation tools.

[0003] When drawing special effects components for a special effects scene using the 3D scene creation tool, the object information (such as component label information) of the drawn special effects components will be displayed in the navigation view.

[0004] Existing creation tools simply display the object information of drawn special effects components in the navigation view. Categorizing these components requires experienced designers to manually categorize their object information. Furthermore, during the special effects rendering phase, the rendering order of different components must be configured beforehand to ensure optimal rendering results. This configuration process is relatively cumbersome. All of these methods increase the learning and understanding costs for designers and do not guarantee the accuracy and effectiveness of the drawn special effects components. Summary of the Invention

[0005] This disclosure provides a method, apparatus, device, and storage medium for creating special effects, thereby enabling the effective creation of special effects.

[0006] In a first aspect, embodiments of this disclosure provide a method for creating special effects, the method comprising:

[0007] The special effects creation interface is displayed, which includes: a special effects component navigation view;

[0008] Receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list;

[0009] The first sub-navigation hierarchy table to which the first target component belongs is determined, and the component tag information is presented under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0010] Secondly, this disclosure also provides a special effects rendering method, which includes:

[0011] Obtain the target effect rendering file for the target effect to be rendered;

[0012] Extract the target rendering sort and corresponding target component data of each target component from the target special effects rendering file. The target rendering sort is determined based on the special effects production method described in the first aspect embodiment above.

[0013] Using the data of each target component, render each target component according to the target rendering sort to generate target effects.

[0014] Thirdly, this disclosure also provides a special effects production apparatus, the special effects production method comprising:

[0015] The first display module is used to display the special effects creation interface, which includes: a special effects component navigation view;

[0016] The first receiving module is used to receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list;

[0017] The second display module is used to determine the first sub-navigation hierarchy table to which the first target component belongs, and to present the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0018] Fourthly, this disclosure also provides a special effects rendering apparatus, which includes:

[0019] The acquisition module is used to acquire the target effect rendering file of the target effect to be rendered;

[0020] The extraction module is used to extract the target rendering order and corresponding target component data of each target component in the target special effects rendering file. The target rendering order is determined based on the special effects production method described in the first aspect embodiment above.

[0021] The rendering module is used to render each of the target components according to the target rendering sort based on the data of each target component, and generate target effects.

[0022] Fifthly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0023] One or more processors;

[0024] Storage device for storing one or more programs.

[0025] When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any embodiment of this disclosure.

[0026] Sixthly, embodiments of this disclosure also provide a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the methods described in any embodiment of this disclosure.

[0027] The technical solution of this disclosure embodiment can display a special effects creation interface, which includes: a special effects component navigation view; receiving a component addition operation, wherein the component addition operation is to select the component tag information of a first target component in the presented component menu list; determining the first sub-navigation hierarchy table to which the first target component belongs, and presenting the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to a first rendering sort. Unlike existing technologies that require manual categorization of component tags and manual configuration of rendering order for special effects components, the above-mentioned technical solution, during the special effects production process, can directly determine which sub-scene a special effects component belongs to and its level within that sub-scene after receiving a component addition operation. This allows the component tag information (such as the component name) of the added special effects component to be presented in the sub-navigation hierarchy table of its respective sub-scene. Simultaneously, this sub-navigation hierarchy table can be presented in a specific rendering order in the special effects component navigation view, enabling designers to quickly understand the rendering order of added special effects components. This embodiment of the above-mentioned technical solution achieves automatic categorization of added special effects components to their respective sub-scenes during special effects production. Furthermore, the automatic sorting of the sub-navigation hierarchy tables in the special effects component navigation view is equivalent to automatically configuring the rendering order of special effects components. In addition, it also achieves the effect of visually demonstrating the rendering order of special effects components to designers. The above technical solutions simplify the special effects production process, reduce the development and understanding costs for designers, and thus improve the accuracy and effectiveness of special effects component drawing. Attached Figure Description

[0028] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0029] Figure 1 A flowchart illustrating a special effects production method provided in an embodiment of this disclosure is given;

[0030] Figure 1a Example diagrams of the special effects creation interface during the execution of the special effects creation method provided in this embodiment are given;

[0031] Figure 1bAn example diagram is provided showing the execution of the first drag operation in the special effects component navigation view during the execution of the special effects production method provided in this embodiment;

[0032] Figure 1c An example diagram showing the effect of the navigation view of the special effects component after the first drag operation is performed in the navigation view of the special effects component during the execution of the special effects production method provided in this embodiment is given.

[0033] Figure 1d An example image of the effect rendering preview panel before the first drag operation is performed in the special effects component navigation view during the execution of the special effects production method provided in this embodiment is given;

[0034] Figure 1e An example image is provided showing the effect displayed in the special effects rendering preview panel after the first drag operation is performed in the special effects component navigation view during the execution of the special effects production method provided in this embodiment;

[0035] Figure 1f An example diagram showing the presentation of the special effects component navigation view during the execution of the special effects production method provided in this embodiment is given;

[0036] Figure 1g An example diagram showing the presentation after receiving the item expansion / contraction operation during the execution of the special effects production method provided in this embodiment is given;

[0037] Figure 1h An example image of the rendering effect after receiving the rendering and hiding operation during the execution of the special effects production method provided in this embodiment is given;

[0038] Figure 2 A flowchart illustrating a special effects rendering method provided in an embodiment of this disclosure is given;

[0039] Figure 3 A schematic diagram of the structure of a special effects production apparatus provided in an embodiment of this disclosure is given;

[0040] Figure 4 A schematic diagram of the structure of a special effects rendering device provided in an embodiment of this disclosure is given;

[0041] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure is given. Detailed Implementation

[0042] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0043] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0044] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0045] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0046] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0047] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0048] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0049] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0050] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0051] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0052] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0053] Special effects creation has diverse applications, including virtual reality, augmented reality, and the application of filters, distortions, and beautification to captured or uploaded images. Special effects creation methods are used to achieve specific effects on screen. For example, effects such as stickers, distortions, filters, virtual object settings, and virtual object implementations in videos require pre-production based on special effects creation methods. The function of special effects creation methods can be understood as creating one or more prop packs and sending them to the application. When a specific effect is needed, the application can invoke the prop pack and apply it to the relevant target object. Using special effects creation methods is equivalent to using special effects creation tools. For example, when adding effects to a video, the effect can be created based on special effects creation methods. The process of creating special effects is equivalent to continuously adding information about the special effects components, which will be drawn and presented in a corresponding order on the drawing panel.

[0054] It should be noted that the rendering order of special effects components in the drawing panel is related to the rendering order of objects within the view list and the camera rendering order within that layer. For example, based on the camera rendering order, the first camera to be rendered will be found, and the corresponding special effects components will be drawn and rendered sequentially based on the rendering order of objects within that camera, and then executed in that order.

[0055] Generally, in the process of creating special effects scenes, when it is necessary to adjust the rendering order of two special effects components, especially when adjusting the rendering order of two special effects components that are not in the same camera, designers often need to manually perform relatively complex camera parameter adjustments. The lack of visually intuitive adjustment interaction means also increases the learning and understanding cost for designers in creating special effects. In addition, when creating complex special effects scenes, the current method of manually recording the rendering order of special effects components cannot guarantee the accuracy and validity of the recorded information.

[0056] Based on this, this embodiment provides a method for creating special effects. Figure 1 A flowchart illustrating a special effects production method provided in this disclosure is given. This disclosure is applicable to situations involving the production of special effects. The method can be executed by a special effects production method. The device can be implemented in the form of software and / or hardware, and optionally, in the form of electronic equipment.

[0057] like Figure 1 As shown, the special effects production method provided in this embodiment may specifically include:

[0058] S110. Display the special effects creation interface, which includes a special effects component navigation view.

[0059] It is understandable that when creating special effects, it is necessary to add the desired special effects components, and then render each special effects component to achieve the special effects effect. Special effects components can be understood as the elements contained in the special effects to be created. From the user's perspective, when a user wants to create special effects, they can trigger the special effects creation function to open the special effects creation interface. After receiving the special effects creation function trigger operation, this execution entity can display the special effects creation interface. For example, the special effects creation method in this embodiment can be implemented by a special effects creation tool in an electronic device. When a user needs to create special effects, they need to launch the special effects creation tool, so that the electronic device can display the special effects creation interface.

[0060] In this embodiment, the special effects creation interface can be specifically understood as an interface provided to users for creating special effects. The specific layout of the special effects creation interface can be designed during the development phase, and the interface includes a special effects component navigation view by default. The special effects creation interface can contain relevant information or buttons related to special effects creation. When creating special effects, the interface receives user-related operations regarding special effects creation to achieve the desired effect. The special effects component navigation view can include special effects components added during the special effects creation process, and these components are displayed in the special effects component navigation map as component tag information. The special effects component navigation map not only includes the added special effects components but also presents the hierarchical relationship between them. In this embodiment, there are no specific limitations on the display format of the special effects component navigation map. For example, the sub-navigation hierarchy table can be a tree structure component, and the sub-navigation hierarchy table can contain multiple nodes arranged hierarchically. For example, the first entry in the sub-navigation hierarchy table is used as the root node in the tree structure; the root node has sub-nodes or leaf nodes, and the component label information of the special effects component is used as a row entry in the sub-navigation hierarchy table.

[0061] S120. Receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list.

[0062] Clearly, when a user wants to create special effects, they must first select the desired special effects components and add them to the special effects component navigation view. In this embodiment, the component menu list can display the component tag information of each special effects component available for user selection. The component tag information of which special effects components are included in the component menu list and the presentation format of the menu list can be set according to actual needs. Component tag information is information that can characterize a special effects component and is bound to the special effects component; for example, the name of the special effects component can be used as the component tag information.

[0063] As described above, the component menu list can either be displayed continuously in a list format on the effects creation interface, or it can be in a collapsed state by default, requiring the user to retrieve and display the component menu list before adding a component. For example, clicking the component menu list control will display the menu list upon receiving a click action.

[0064] From the user's perspective, when a user wants to add a special effects component, they can perform a component addition operation. The component addition operation involves selecting the component tag information of a specific special effects component from the presented component menu list. In this embodiment, the special effects component corresponding to the selected component tag information is recorded as the first target component. From the perspective of this execution entity, this execution entity can receive the component addition operation performed by the user.

[0065] It is understandable that the user's action of selecting the component label information of the first target component in the presented component menu list through the control signal input device can be determined by the relevant hardware or software of this execution entity in cooperation with each other. Furthermore, by analyzing the relevant data information of the action of selecting the component label information of the first target component, it can be determined what operation the user performed on the special effects production interface, thereby receiving the component addition operation triggered by the user.

[0066] In this embodiment, the specific implementation of the execution entity determining that the user has performed a component addition operation in the special effects creation interface can be described as follows: The special effects creation interface configured in the electronic device can respond to the selection signal generated by the input device controlling the cursor to click on the special effects creation interface. This obtains the click information generated when the input device controls the cursor to click and feeds it back to the upper-level processing module. The processing module can determine whether the user has performed a selection operation on the special effects creation interface, and what component label information was selected. Based on the selected component label information, the processing module can determine that the user has manipulated the input device to select the component label information of the first target component in the presented component menu list on the special effects creation interface.

[0067] At this point, the executing entity can consider the user to have interacted with the special effects creation interface by adding components. The format of the component label information for selecting the first target component from the component menu list presented on the special effects creation interface can be varied, depending on user needs or operating habits. For example, it can be selected by left-clicking, right-clicking, or double-clicking the mouse.

[0068] S130. Determine the first sub-navigation hierarchy table to which the first target component belongs, and present the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0069] In this embodiment, when creating special effects, the relevant special effects components need to be added to the special effects component navigation view. This allows users to add desired special effects components to the navigation view through component addition operations. The hierarchical relationship between the added special effects components is displayed in the navigation view. This step, responding to the component addition operation described above, visually presents a sub-navigation hierarchy table in the special effects component navigation view. Each sub-navigation hierarchy table contains one or more nodes, and the tag information of the target component is displayed under each node.

[0070] Unlike existing technologies that cannot automatically categorize added special effects components, this embodiment treats each sub-navigation hierarchy table as a whole component, with each sub-navigation hierarchy table being decoupled and relatively independent. All content associated with this hierarchy table is recorded and displayed under its respective hierarchy node, effectively managing the sub-navigation hierarchy table as a whole. Therefore, when a component addition operation is received, the tag information corresponding to the first target component needs to be added to the corresponding hierarchy node in its respective sub-navigation hierarchy table.

[0071] In this embodiment, each sub-navigation hierarchy table is managed as a whole. The sub-navigation hierarchy table to which the target component belongs is designated as the first sub-navigation hierarchy table, and the hierarchy nodes to be added to the first sub-navigation hierarchy table are designated as target hierarchy nodes. It is understood that before presenting the component tag information under the target hierarchy node of the first sub-navigation hierarchy table, it is necessary to first determine the first sub-navigation hierarchy table to which the first target component belongs, and to determine whether the first sub-navigation hierarchy table exists in the target component navigation graph. If it does, the component tag information can be presented under the target hierarchy node of the target hierarchy table of the first sub-navigation hierarchy table. If it does not exist, the first sub-navigation hierarchy table needs to be created in the effects component navigation view first, and then the component tag information is presented under the target hierarchy node of the first sub-navigation hierarchy table.

[0072] In existing technologies, subsequent adjustments to components require parameter configuration on the target component's parameter panel. The relationships between various effect components are established through parameter configuration and are not directly visible in the navigation view. Dragging only affects the display of the effect component navigation view; after cross-level adjustments, manual configuration of the parameters corresponding to the sub-navigation hierarchy table is needed to reflect the changes in the rendering effect. In other words, existing technologies only visually display relationships when dragging the sub-navigation hierarchy table, without establishing a connection with the rendering screen. This embodiment establishes a connection between the effect component navigation view and the rendering order, allowing adjustments to the order of the sub-navigation hierarchy table in the effect component navigation view to correspondingly adjust the rendering effect.

[0073] In this embodiment, the special effects components needed for special effects production and their categories can be pre-stored in the device, and the rendering order of each category can be pre-set. That is, the default rendering order between the categories corresponding to the special effects components is pre-stored in the device, denoted as the first rendering order. When the first sub-navigation hierarchy table is displayed in the special effects component navigation view, it can be displayed in the special effects component navigation view according to the first rendering order.

[0074] As described above, when an effect component is added, it will not only appear in the effect component navigation view, but will also be categorized and assigned to a specific sub-navigation hierarchy. When multiple sub-navigation hierarchies are to be displayed, they will be shown according to the default first rendering order.

[0075] For example, the rendering order of the corresponding special effects components is followed, and the sub-navigation hierarchy is presented in a tree structure in the special effects component navigation view, arranged in rendering order. A default categorization for each special effects component within a specific sub-navigation hierarchy is pre-set. For example, assuming commonly used special effects components can be categorized as follows: 2D foreground effects, 2D background effects, face effects, etc. (These are just examples and not listed individually), the default rendering order for these three types of special effects components can be set as: 2D background effects before face effects before 2D foreground effects. If these three types of effects are added to the special effects component navigation view, the top-to-bottom order in the navigation view will also be: 2D background effects, face effects, 2D foreground effects. Each type can be set with a baseline value. For example, filter, beauty, and shape each correspond to a baseline value (500, 2500, 3000), which represents the order of the types. From this baseline value, it can be seen that the rendering order is filter before beauty before shape.

[0076] Furthermore, when a new child-level node is added, the baseline value needs to be recalculated based on the current layout. Assuming this type of child-level node is appearing for the first time, if the current baseline value is less than the node's default baseline value, then the node's default baseline value is used as its baseline value; if it is greater than the node's default baseline value, then the current baseline value plus one is used as its baseline value, and so on down the hierarchy. If it is not appearing for the first time, then the current baseline value plus one is used as its baseline value.

[0077] In this embodiment, the presentation order of the sub-navigation hierarchy tables in the special effects component navigation view is consistent with the rendering order. The rendering order determines the rendering level to which the special effects component belongs in the rendered effect. Components rendered earlier are presented at a lower rendering level, and vice versa. The rendering order corresponds to the drawing order of the special effects components. This ensures that the presentation order of the sub-navigation hierarchy tables in the special effects component navigation view is consistent with the rendering order of their corresponding special effects components.

[0078] For example, Figure 1a Example diagrams of the special effects creation interface during the execution of the special effects creation method provided in this embodiment are given, such as... Figure 1aAs shown, the special effects creation interface 1 includes a special effects component navigation view 11, which displays the added special effects components. The navigation view 11 also presents the added sub-navigation hierarchy, with each sub-navigation hierarchy forming a tree structure component. The first entry in each sub-navigation hierarchy serves as the root node in the tree structure; the component tag information of the contained special effects components serves as a row entry in the sub-navigation hierarchy, constituting a child node or leaf node under the root node. The diagram shows two sub-navigation hierarchy tables. Sub-navigation hierarchy table 1 contains child node 11 and child node 12. Child node 11 includes leaf nodes 111 and 112. Child node 12 includes the next-level child node 121, which includes leaf nodes 1211 and 1212. Similarly, sub-navigation hierarchy table 2 includes child node 21, which includes leaf node 211. When a user adds a component, the tag information of the added effect component will be displayed under the corresponding node in the corresponding sub-navigation hierarchy table.

[0079] Following the example above, when a component addition operation to add a new special effects component is received, this execution entity first needs to determine the sub-navigation hierarchy table to which the special effects component to be added belongs, and then determine whether the sub-navigation hierarchy table to which it belongs is sub-navigation hierarchy table 1 or sub-navigation hierarchy table 2. Assuming that the special effects component to be added belongs to sub-navigation hierarchy table 2, the component tag information of the special effects component to be added can be added to the corresponding sub-level node in sub-navigation hierarchy table 2 presented in the special effects component navigation view. If the special effects component to be added does not belong to sub-navigation hierarchy table 1 or sub-navigation hierarchy table 2, then it is necessary to construct the sub-navigation hierarchy table to which the special effects component belongs, and query the default rendering sort. Based on the default rendering sort, the rendering order of the special effects components involved in sub-navigation hierarchy table 1, sub-navigation hierarchy table 2, and the sub-navigation hierarchy table to be added is determined. The determined rendering order determines the sorting of sub-navigation hierarchy table 1, sub-navigation hierarchy table 2, and the sub-navigation hierarchy table to be added, and presents them in the special effects component navigation view.

[0080] This disclosure provides a special effects production method that differs from existing technologies where component tag information of target components needs to be manually categorized and rendering order needs to be manually configured. In the special effects production process, after receiving a component addition operation, the method directly determines which sub-scene the added special effects component belongs to and its level within that sub-scene. This allows the component tag information (such as the name of the special effects component) to be presented in the sub-navigation hierarchy table of its respective sub-scene. Simultaneously, this sub-navigation hierarchy table can be presented in a specific rendering order in the special effects component navigation view, enabling designers to quickly determine the rendering order of the added special effects components. This embodiment achieves automatic classification of added special effects components to their respective sub-scenes during special effects production. Furthermore, the automated sorting of sub-navigation hierarchy tables in the special effects component navigation view effectively automates the configuration of the special effects component rendering order, and also visually demonstrates the rendering order of the special effects components to designers. The above technical solutions simplify the special effects production process, reduce the development and understanding costs for designers, and thus improve the accuracy and effectiveness of special effects component drawing.

[0081] As a first optional embodiment of this disclosure, based on the above embodiments, this first optional embodiment can further optimize the above-mentioned special effects production method. Specifically, determining the first sub-navigation hierarchy table to which the first target component belongs may include the following execution steps:

[0082] a1) If at least one sub-navigation hierarchy table has been displayed in the special effects component navigation view, determine whether the first target component belongs to the displayed sub-navigation hierarchy table.

[0083] In this optional embodiment, the sub-navigation hierarchy table is treated as a whole as a component. Before displaying the component tag information of the added special effects component, it is necessary to determine to which category the first target component belongs, that is, which sub-navigation hierarchy table the first target component belongs to. Further, it is determined whether the sub-navigation hierarchy table to which the first target component belongs is already displayed in the special effects component navigation view. The result of this step may be that the first target component belongs to a sub-navigation hierarchy table already displayed in the special effects component navigation view, or it may be that the first target component does not belong to a sub-navigation hierarchy table already displayed in the target component object navigation view.

[0084] b1) If so, the sub-navigation hierarchy table to which the first target component belongs is recorded as the first sub-navigation hierarchy table, wherein the first rendering order is the current rendering order of at least one displayed sub-navigation hierarchy table presented in the special effects component navigation view.

[0085] Specifically, if the first target component belongs to a sub-navigation hierarchy table already displayed in the effects component navigation view—that is, the sub-navigation hierarchy table to which the desired effects component belongs is already shown in the effects component navigation view—then the sub-navigation hierarchy table to which it belongs is recorded as the first sub-navigation hierarchy table. The subsequent step is to insert the component tag information of the first target component into the corresponding level node of the first sub-navigation hierarchy table.

[0086] It is important to understand that in this embodiment, a sub-navigation hierarchy table is treated as a whole as a component. If there is already a sub-navigation hierarchy table to which the first target component to be added belongs in the special effects component navigation view, then it is only necessary to insert the component tag information of the special effects component into the sub-navigation hierarchy table, and it is not necessary to build the sub-navigation hierarchy table to which the first target component belongs.

[0087] Specifically, rendering order refers to the order in which special effects components are rendered, which determines the presentation hierarchy of the rendered special effects components. Special effects components rendered earlier are presented later, and special effects components rendered later are presented earlier. Rendering order corresponds to the drawing order when special effects components are drawn.

[0088] In this optional embodiment, the electronic device may pre-store special effects rendering files. These files may contain various special effects categories, the corresponding special effects components within each category, and the default rendering order between categories. This can also be understood as pre-setting the rendering order of each sub-navigation hierarchy table, and recording it as the default rendering order. The order of the sub-navigation hierarchy tables displayed in the special effects component navigation view intuitively represents the rendering order of the special effects components. Since adding the component tag information of the first target component to the sub-navigation hierarchy tables already displayed in the special effects component navigation view does not change the order of the sub-navigation hierarchy tables in the special effects component navigation view, the rendering order remains unchanged. Therefore, the current rendering order of each sub-navigation hierarchy table in the special effects component navigation view is recorded as the first rendering order.

[0089] c1) If not, construct a first sub-navigation hierarchy table to which the first target component belongs, wherein the first rendering order is determined based on the current rendering order, and the first sub-navigation hierarchy table is inserted into the corresponding position in the special effects component navigation view according to the first rendering order.

[0090] Specifically, if the first target component does not belong to any of the sub-navigation hierarchy tables already displayed in the effects component navigation view—that is, the sub-navigation hierarchy table to which the desired effects component belongs is not shown in the effects component navigation view—then it is necessary to construct the sub-navigation hierarchy table to which the first target component belongs and record it as the first sub-navigation hierarchy table. First, construct the first sub-navigation hierarchy table in the effects component navigation view. Then, insert the component tag information of the first target component into the corresponding level node of the first sub-navigation hierarchy table.

[0091] When adding the first target component, the system first checks if the first child target component exists in the effects rendering file. If it does, it determines which hierarchy the first child scene belongs to. Simultaneously, the rendering order of the first child navigation hierarchy table can be determined based on the default rendering order in the effects rendering file. The rendering order after adding the first child navigation hierarchy table is used as the first rendering order, and the first child scene hierarchy is inserted into the effects component navigation view according to this first rendering order. It's important to note that when adding effects components, constructing their corresponding child navigation hierarchy tables, and displaying them in the effects component navigation view, the sorting and display are based on the default rendering order in the effects rendering file. The newly constructed child navigation hierarchy tables should be inserted into the corresponding positions in the effects component navigation view according to the default rendering order.

[0092] Correspondingly, if the special effects component navigation view is empty, a first sub-navigation hierarchy table to which the first target component belongs is constructed, and the first sub-navigation hierarchy table is directly added to the special effects component navigation view as the first sub-navigation hierarchy table in the special effects component navigation view, and placed at the beginning of the special effects component navigation view.

[0093] This first optional embodiment further optimizes how to determine the sub-navigation hierarchy to which the added special effects component belongs and how to determine the first rendering order before presenting the component tag information of the added special effects component. This technology ensures that the sorting of the sub-navigation hierarchy in the special effects component navigation view is consistent with the rendering order, and can more intuitively display the rendering relationship between the special effects component navigation view and the special effects component.

[0094] As a second optional embodiment of this disclosure, based on the above embodiments, this second optional embodiment can further optimize the above-mentioned special effects production method. Specifically, when the special effects component navigation view displays at least two sub-navigation hierarchy tables, the method may further include the following execution steps:

[0095] a2) Receive a first drag operation, the first drag operation being applied to a row entry in the sub-navigation hierarchy table displayed in the navigation view of the special effects component.

[0096] The above steps describe the characteristics of the special effects component navigation view and how to add special effects components to construct it. This optional embodiment mainly describes how drag-and-drop operations can be performed to adjust the hierarchical relationship presented in the special effects component navigation view when there are at least two sub-navigation hierarchy tables. This drag-and-drop operation is denoted as the first drag-and-drop operation. When there are at least two sub-navigation hierarchy tables in the special effects component navigation view, one possible operation is drag-and-drop. Each row displayed under a sub-navigation hierarchy table can be understood as a row entry in the sub-navigation hierarchy table. For example, the first row entry can represent the naming information of the sub-hierarchy table, and the row entries corresponding to sub-hierarchy nodes or leaf nodes can be the component tag information of the added special effects component.

[0097] This step is used to receive the first drag operation, which is specifically characterized by the user controlling the cursor to move the target object in the special effects component navigation view through signal input devices such as a mouse or touch screen.

[0098] The specific implementation of this execution entity's analysis determining that the user performed the first drag operation in the special effects creation interface can be described as follows: The special effects creation interface configured on the device can respond to drag signals generated by the input device controlling the cursor's click on the interface. This obtains the click information generated when the input device controls the cursor to click and feeds it back to the upper-level processing module. The processing module can determine whether the user performed the first drag operation on the special effects creation interface, and which row item was dragged, by analyzing the click information. Through the drag row item information, the processing module can determine that the user manipulated the input device to perform the first drag operation on the special effects creation interface. It is understandable that the user's first drag behavior, controlled by the input device, can also be determined by the relevant hardware or software of this system working together. Furthermore, by analyzing the data related to the first drag behavior, the system can determine what operation the user performed on the special effects creation interface, thus enabling it to receive the user-triggered first drag operation.

[0099] Preferably, the target of the first drag operation includes at least one of the following:

[0100] The first row entry of any sub-navigation hierarchy table in the special effects component navigation view, or any other row entry in the sub-navigation hierarchy table excluding the first row entry; the first row entry of any sub-navigation hierarchy table and at least one other row entry in at least one other sub-navigation hierarchy table excluding the first row entry in the special effects component navigation view; the first row entries of at least two sub-navigation hierarchy tables in the special effects component navigation view; at least one other row entry in at least two sub-navigation hierarchy tables excluding the first row entry in the special effects component navigation view.

[0101] The first drag behavior of the first drag operation includes at least one of the following:

[0102] In the special effects component navigation view, drag the target object downwards into the blank space; in the special effects component navigation view, drag the target object to the middle of two adjacent sub-navigation levels; in the special effects component navigation view, drag the target object to any row in any sub-navigation level; in the special effects component navigation view, drag the target object to the middle of two adjacent rows in any sub-navigation level.

[0103] Understandably, when an object is selected, only the selected item in that row will be displayed. To perform related operations, further actions are required. For example, dragging will only trigger a drag response, and renaming an item in a row requires a double-click to enter edit mode.

[0104] The technical features described above in this embodiment specify the objects that can be used during drag-and-drop interactions on the special effects production interface, and also provide a detailed description of the drag-and-drop behaviors involved. Furthermore, different drag-and-drop responses can be provided for different drag-and-drop behaviors performed on different objects. This embodiment, through these technical features, better demonstrates the diversity of interactive operations available to designers, thus expanding the applicability of the special effects production tool.

[0105] b2) When the first drag operation satisfies the drag response condition of the second sub-navigation hierarchy table, determine the second rendering order according to the first drag operation, and adjust the display position of the second sub-navigation hierarchy table in the special effects component navigation view according to the second rendering order.

[0106] Specifically, the second sub-navigation hierarchy table can be understood as the sub-navigation hierarchy table affected by the first drag operation. The drag response condition can be understood as the existence of at least two sub-navigation hierarchy tables in the special effects component navigation view, and the target and behavior of the drag operation meeting the set requirements. This step responds to receiving the first drag operation, determining whether the first drag operation meets the drag response condition of the second sub-navigation hierarchy table. When the drag response condition is met, the display position of the second sub-navigation hierarchy table in the special effects component navigation view is adjusted.

[0107] For example, dragging downwards into a blank area means dragging the selected content to a blank, empty area and releasing the mouse. Dragging between two adjacent sub-navigation levels means dragging the selected content to the middle area between the two sub-navigation levels; this middle area will become active and insertable, and moving the mouse over any active area will trigger a corresponding display, such as displaying a blue active line. Dragging onto any row in any sub-navigation level means dragging the selected content onto the target component in that sub-navigation level. Dragging between two adjacent rows in any sub-navigation level means dragging the selected content between special effects components in the sub-navigation level; the length of the active line displayed depends on the special effects component above the dragged position.

[0108] If you select a row entry of an effect component and drag it to the bottom blank space, it has no effect; dragging it between two sub-navigation levels also has no effect; dragging it into the sub-navigation level will, if the active area is between two effect components, insert the selected effect component and its child effect components between the effect components; if the active area is an effect component, insert the selected effect component and its child effect components below the selected effect component.

[0109] If you select the first item of a sub-navigation hierarchy (i.e., select a sub-navigation hierarchy), and drag it to the bottom blank space, you can insert that sub-navigation hierarchy at the bottom of all sub-navigation hierarchy tables in the effects component navigation view; dragging it between two sub-navigation hierarchy tables will insert it into both sub-navigation hierarchy tables; dragging it into a sub-navigation hierarchy table will have no effect.

[0110] If multiple effect component rows are selected across sub-navigation levels, dragging them to the bottom blank space will have no effect; dragging them between two sub-navigation levels will also have no effect; dragging them into the sub-navigation level will, if the active area is between two effect components, insert the selected effect component and its child effect components between the effect components; if the active area is a specific effect component, the selected effect component and its child effect components will be incorporated into the child elements below the selected effect component.

[0111] If you select multiple target components' row entries and sub-navigation hierarchy tables, dragging them to the bottom blank space has no effect; dragging them between two sub-navigation hierarchy tables has no effect; dragging them into the sub-navigation hierarchy table has no effect.

[0112] If you select multiple sub-navigation hierarchy tables and drag them to the bottom blank space, you can insert the sub-navigation hierarchy table at the bottom of all sub-navigation hierarchy tables in the effects component navigation view; dragging it between two sub-navigation hierarchy tables will insert it into two sub-navigation hierarchy tables; dragging it into a sub-navigation hierarchy table will have no effect.

[0113] It's important to know that when you manipulate the sub-navigation hierarchy and effects components in the effects component navigation view, the changes in their appearance in the navigation view will also be reflected in the effects rendering preview panel. For example, if an effects component is dragged into a sub-navigation hierarchy node that doesn't match its usual order, the rendering effect might not be guaranteed to be correct with the built-in filters. Users should use the preview function to identify this issue.

[0114] For example, Figure 1b An example diagram is provided showing the execution of the first drag operation in the special effects component navigation view during the execution of the special effects production method provided in this embodiment, such as... Figure 1b As shown, select the first entry of the sub-navigation hierarchy table 1 and drag it to the blank space below as the first drag operation. Figure 1c An example diagram is provided showing the effect of the special effects component navigation view after the first drag operation is performed in the special effects component navigation view during the execution of the special effects production method provided in this embodiment. For example... Figure 1c As shown, in response to the first drag operation, the rendering order was adjusted, and the corresponding display position in the special effects component navigation view was also adjusted. The display from top to bottom was changed from Sub-navigation Hierarchy Table 1, Sub-navigation Hierarchy Table 2 to Sub-navigation Hierarchy Table 2, Sub-navigation Hierarchy Table 1.

[0115] This second optional embodiment further enhances the functionality of the special effects production method. Based on the above method implementation, it specifically adds the ability to adjust the order of sub-scene row entries by dragging and dropping row entries in the sub-navigation hierarchy table, providing support for adjusting the rendering order of special effects components. Since the order of the sub-navigation hierarchy table in the special effects component navigation view corresponds to its rendering order, adjusting the rendering order of special effects components is more convenient and efficient.

[0116] Furthermore, the special effects creation interface also includes a special effects rendering preview panel, and the method may further include the following execution steps:

[0117] a3) While presenting the component tag information under the target level node of the first sub-navigation level table, render the first target component according to the first rendering sort, and present the first special effect of the first target component on the first rendering layer of the special effect rendering preview panel.

[0118] In this embodiment, the special effects creation interface includes not only a special effects component navigation view but also a special effects rendering preview panel. The special effects rendering preview panel is primarily used to display the rendered effect of the special effects components. The rendering effects of the special effects components displayed on the special effects rendering preview panel are consistent with the special effects components already added in the special effects component navigation view.

[0119] This step is equivalent to adding information to the special effects component navigation view and also adding rendering effects to the special effects rendering preview panel when adding special effects components. Specifically, while presenting the component tag information under the target level node of the first sub-navigation hierarchy table, the added special effects component is rendered and presented on the special effects rendering preview panel. The rendering of the added special effects component needs to be performed according to the first rendering order determined in the above steps. The rendering order determines the presentation level of the rendered special effects component. Special effects components rendered earlier are presented at a lower level, and target components rendered later are presented at a higher level. The rendering order corresponds to the drawing order when drawing special effects components. After rendering the first target component according to the first rendering order, the first target component will be presented on the rendering layer corresponding to the rendering order on the special effects rendering preview panel, which is denoted as the first rendering layer in this embodiment.

[0120] b3) While adjusting the display position of the second sub-navigation hierarchy table in the special effects component navigation view, render the second target component involved in the second sub-navigation hierarchy table according to the second rendering order, and present the second special effects of the second target component on the second rendering layer of the special effects rendering preview panel.

[0121] In this step, the sub-navigation hierarchy table that is dragged and adjusted is recorded as the second sub-navigation hierarchy table, the special effects components involved in the dragged and adjusted sub-navigation hierarchy table are recorded as the second target components, and the rendering layer where the special effects components are rendered after dragging and adjustment is recorded as the second rendering layer.

[0122] This step is equivalent to adjusting the display order of the effects components in the effects component navigation view and also adjusting the rendering effect in the effects rendering preview panel during the first drag operation. Specifically, while adjusting the display position of the second sub-navigation hierarchy in the effects component navigation view, i.e., reordering the sub-navigation hierarchy by dragging, the purpose is to adjust the rendering layers in real-time rendering. The adjusted rendering order is recorded as the second rendering order. When adjusting the display position of the second sub-navigation hierarchy in the effects component navigation view, the rendering order of the effects components rendered in the effects rendering preview panel will also be adjusted, and the rendering layers they occupy will be adjusted accordingly.

[0123] Clearly, adjusting the rendering effect involves adjusting the rendering layer itself. Unlike existing technologies that require complex parameter configurations, the method provided in this embodiment is visual and easily operable by the user. Adjustments to the rendering layer can be made simply by dragging and dropping, making the operation more convenient for the user.

[0124] It's important to know that each effect component has an automatic sorting switch, which users can control to turn on or off. When automatic sorting is enabled, dragging objects up or down within the same layer of nodes will automatically change the rendering order, which manifests as a change in their presentation position. The presentation position of the effect component will also change. If automatic sorting is disabled, dragging can be considered as only adjusting the presentation position and will not affect the rendering order of the corresponding components.

[0125] For example, Figure 1d The following is an example image showing the effect preview panel before the first drag operation is performed in the special effects component navigation view during the execution of the special effects production method provided in this embodiment, such as... Figure 1d As shown, this example describes the adjustments made to the rendering preview panel before the first drag operation in the previous example. To distinguish between the special effects components involved in sub-navigation hierarchy table 1 and sub-navigation hierarchy table 2, which belong to two different rendering layers after rendering, this example represents the rendering layer of special effects components involved in sub-navigation hierarchy table 1 as rendering effect 1, and the rendering layer of special effects components involved in sub-navigation hierarchy table 2 as rendering effect 2. It can be seen that when the special effects components in the navigation view are ordered from top to bottom as sub-navigation hierarchy table 1 and sub-navigation hierarchy table 2, the special effects components involved in sub-navigation hierarchy table 1 will be rendered first, followed by the special effects components involved in sub-navigation hierarchy table 2. The hierarchy presented in the special effects rendering preview panel is that rendering effect 1 is lower, and rendering effect 2 is higher.

[0126] Figure 1e An example image is provided showing the effect displayed in the special effects rendering preview panel after a first drag operation is performed in the special effects component navigation view during the execution of the special effects production method provided in this embodiment. After the first drag operation, from a visual perspective, in addition to adjusting the display position of the sub-navigation hierarchy table in the special effects component navigation view, the special effects components involved in the sub-navigation hierarchy table are rendered in the rendering order and presented on the corresponding rendering layers of the special effects rendering preview panel. Corresponding to the adjustment of the display position of the sub-navigation hierarchy table in the special effects component navigation view, the hierarchical relationship presented on the special effects rendering preview panel is also adjusted, with rendering effect 2 at the bottom and rendering effect 1 at the top.

[0127] This technical solution further adds a special effects rendering preview panel to the special effects creation interface. When a scene addition or drag-and-drop operation is received, the rendering effect of the special effects components in the special effects rendering preview panel will change accordingly while the presentation in the special effects component navigation view is adjusted. The rendering effect presented in the special effects rendering preview panel is consistent with the effect presented in the special effects component navigation view. By establishing a connection between the special effects component navigation view and the special effects rendering preview panel through rendering order, users can more intuitively perceive the rendering order reflected in the special effects component navigation view and the special effects rendering preview panel. By simply adjusting the special effects component navigation view, the rendering effect of the special effects rendering preview panel can be adjusted, simplifying the operation process, reducing the user's learning and understanding cost, and improving the convenience and efficiency of operation.

[0128] As a third optional embodiment of this disclosure, based on the above embodiments, this third optional embodiment can further optimize the above-mentioned special effects production method. Specifically, this third optional embodiment can optimize the sub-navigation hierarchy table as follows: the sub-navigation hierarchy table is a tree structure component, the first row of the sub-navigation hierarchy table is used as the root level node in the tree structure; the component tag information of the added target component is used as a row entry in the sub-navigation hierarchy table, constituting a sub-level node or leaf node under the root level node; a collapsible control is displayed on the row entry corresponding to the root level node and the sub-level node.

[0129] For example, Figure 1f An example diagram showing the presentation of the special effects component navigation view during the execution of the special effects production method provided in this embodiment is given, such as... Figure 1f As shown, the special effects component navigation view includes sub-navigation hierarchy table 1, sub-navigation hierarchy table 2, and sub-navigation hierarchy table 4. Each sub-navigation hierarchy table is treated as a tree structure component. Taking sub-navigation hierarchy table 1 as an example, sub-navigation hierarchy table 1 is the root level node, and a collapsible control is displayed on the corresponding row item; sub-level nodes 11, 12, and 121 are sub-level nodes under the root level node, and a collapsible control is displayed on the corresponding row item; leaf nodes 111, 112, 1211, and 1212 correspond to the component label information of different special effects components.

[0130] This embodiment defines the sub-navigation hierarchy table. The sub-navigation hierarchy table is equivalent to a tree structure, and the sub-level nodes or child nodes contained within it can be considered categories within the sub-navigation hierarchy table. The sub-navigation hierarchy table can have a root node, under which there can be one or more child nodes of the same level, and further under these child nodes can be child nodes or leaf nodes, extending to a structure composed entirely of leaf nodes. All sub-navigation hierarchy tables are tree structure components. Special effects components can function as either child nodes or leaf nodes. Collapsible / expandable controls are used to collapse or expand the corresponding row entries of a hierarchy node. Users can collapse or expand row entries by clicking the collapsible / expandable control. For example, the collapsible / expandable control can be located at the far left of the row entries corresponding to the root node and its child nodes. Clicking the collapsible / expandable control can be done by left-clicking the collapsible / expandable area. The row entries corresponding to the root-level node display a collapsible control. Clicking this control will collapse or expand all row entries under that root-level node. The row entries corresponding to child-level nodes display a collapsible control. Clicking this control will collapse or expand all row entries under that child-level node.

[0131] This optional embodiment adds a description of the sub-navigation hierarchy table. By treating the entire sub-navigation hierarchy table as a tree structure component, special effects components can be added to the corresponding level nodes of the sub-navigation hierarchy table when adding them. Unlike existing technologies that require manual movement of added special effects components to their corresponding level nodes, this optional embodiment can automatically add them to the correct position. Furthermore, during drag-and-drop operations, each sub-navigation hierarchy table can be moved as a whole, making the operation more convenient.

[0132] Furthermore, based on the third optional embodiment described above, the method may further include the following execution steps:

[0133] a4) Receive an item collapse / expansion operation, wherein the item collapse / expansion operation is triggered by triggering the collapse / expansion control corresponding to the target level node; or, the item collapse / expansion operation is selected by selecting the row item where the target level node is located.

[0134] This embodiment specifically describes how to expand or collapse row entries by receiving entry expansion / collapse operations. The target level node can be understood as the selected level node for which the entry expansion / collapse operation is performed. The expandable / collapse control is used to implement the function of collapsing or expanding the row entry corresponding to the level node. The entry expansion / collapse operation is triggered by the expandable / collapse control corresponding to the target level node, or by selecting the row entry at the target level. Users can expand / collapse row entries or select the row entry at the target level to be expanded / collapsed by clicking the expandable / collapse control. The underlying technical implementation of receiving entry expansion / collapse operations can refer to the technical implementation of adding operations to the receiving component in the above steps, and will not be described in detail here.

[0135] b4) If the item expansion operation is an item expansion operation, then the row items contained under the target level node are expanded and displayed.

[0136] If the item expansion operation is an item expansion operation, this step is used to respond to the above steps to receive the item expansion operation, which can be specifically manifested as expanding and presenting the row items contained under the target level node.

[0137] c4) If the item collapse operation is an item collapse operation, then collapse the row items under the target level node.

[0138] If the item collapse operation is an item collapse operation, this step is used to respond to the received item collapse operation in the above steps. Specifically, this can be manifested as expanding and displaying the row items contained under the target level node; or collapsing the row items under the target level node. The underlying technical implementation of the response can refer to the technical implementation of adding operation responses to the receiving component in the above steps, and will not be described in detail here.

[0139] For example, the collapsible control can be positioned at the far left of the row entries corresponding to the root-level node and its child-level nodes. Clicking the collapsible control can be done by left-clicking it. A collapsible control is displayed for the row entries corresponding to the root-level node. Clicking this control or the row entry corresponding to the root-level node will collapse or expand all row entries under that root-level node. A collapsible control is also displayed for the row entries corresponding to child-level nodes. Clicking this control or the row entry corresponding to that child-level node will collapse or expand all row entries under that child-level node.

[0140] For example, continue to refer to Figure 1f The root-level node and the corresponding row entries of the child-level nodes all display collapsible controls 10. To receive the collapsible operation, the collapsible controls on the 121st row of the child-level node and the 4th row of the sub-navigation table were clicked. Figure 1gAn example diagram is provided showing the presentation after receiving the item expansion / contraction operation during the execution of the special effects production method provided in this embodiment, such as... Figure 1g As shown, after receiving the collapse operation of the sub-level node 121 row entry, the content under the sub-level node 121 is collapsed; after receiving the collapse operation of the sub-navigation level table 4 row entry, the content under the sub-navigation level table 4 is collapsed.

[0141] This optional embodiment further enhances the functionality of the special effects creation method. Building upon the aforementioned method, it specifically adds the ability to expand and collapse row items via item expansion / collapse operations. This technology enables better management and presentation of the special effects component navigation view to the user.

[0142] Furthermore, based on the third optional embodiment described above, the method may further include the following execution steps:

[0143] a5) Receive the entry naming operation for the first target row entry.

[0144] This embodiment specifically describes the function of renaming row entries by receiving an entry naming operation. The row entry to be renamed is denoted as the first target row entry. The entry naming operation of the first target row entry can be performed by clicking the first target row entry through an external signal input device, such as by double-clicking the first target row entry with a mouse. The specific implementation of the entry naming operation is not limited here.

[0145] b5) Control the first target row entry to be in an editable state and obtain the editing information edited in the first target row entry.

[0146] This step responds to the aforementioned entry naming operation for receiving the first target row entry and can control whether the selected first row entry is in an editable state. When the first row entry is in an editable state, the user can enter a new row entry name into the edit box. This executing entity obtains the editing information edited in the first target row entry.

[0147] c5) In response to the naming information saving operation, the edited information is used as the new entry name of the first target row entry and saved.

[0148] As described above, after editing the new name of a row entry, the user can save the name information. This saving operation can be performed by clicking a "Save Name" button, or by clicking a blank area. Specifically, this step, in response to the saving operation, saves the edited information as the new entry name for the first target row entry.

[0149] This technical solution further enhances the functionality of the special effects production method. Based on the above method implementation, it specifically adds the ability to rename row entries by receiving the entry naming operation. This technology enables better management of the special effects component navigation view.

[0150] Furthermore, based on the third optional embodiment described above, the method may further include the following execution steps:

[0151] a6) Receive the entry deletion operation for the second target row entry.

[0152] This embodiment specifically describes how to implement the deletion function of row entries by receiving an entry deletion operation. The row entry to be deleted is denoted as the second target row entry. The entry deletion operation of the second target row entry can be performed by selecting the second target row entry through an external signal input device and clicking the delete option. For example, it can be performed by left-clicking the second target row entry and then right-clicking to select the delete option from the operation menu list. The specific implementation of the entry deletion operation is not limited here.

[0153] b6) If the second target row entry is a root level node, delete the third sub-navigation level table to which the second target row entry belongs from the special effects component navigation view, and withdraw the special effects rendering of the target components involved in the third target sub-navigation level table on the special effects rendering preview panel of the special effects production interface.

[0154] This step responds to the entry deletion operation in the previous steps. In this embodiment, the sub-navigation hierarchy to which the second target row entry belongs is denoted as the third sub-navigation hierarchy. It is understood that different row entries are located at different hierarchy levels, and the deletion scenarios differ. If the second target row entry is a root-level node, receiving the entry deletion operation is equivalent to deleting the entire sub-navigation hierarchy. The rendering file information related to the target component involved in this sub-navigation hierarchy is essentially gone. Similarly, the rendering information related to it will disappear from the effects rendering preview panel, which is equivalent to revoking the effects rendering of the target component involved in the third target sub-navigation hierarchy in the effects rendering preview panel of the effects creation interface.

[0155] c6) If the second target row entry is a sub-level node, delete all row entries contained under the sub-level node and undo the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel.

[0156] Specifically, the second target row entry is a child-level node, which means deleting the content under the child-level node, specifically all row entries contained within it. Simultaneously, the file information under the child-level node is also deleted; the file information related to the rendering of the target component under that child-level node is essentially gone. Similarly, the rendering information related to it will disappear from the effects rendering preview panel, effectively reversing the effects rendering of the target component under the child-level node in the effects rendering preview panel.

[0157] d6) If the second target row entry is a leaf node, delete the second target row entry and undo the effect rendering of the target component involved in the second target row entry in the effect rendering preview panel.

[0158] Specifically, the second target row entry is a leaf node, meaning the content under that leaf node is deleted; that is, the row entry corresponding to that leaf node is deleted. Simultaneously, the file information corresponding to that leaf node is also deleted; the file information related to the rendering of the target component involved in this leaf node is essentially gone. Similarly, the rendering information related to it will disappear from the effects rendering preview panel, which is equivalent to reverting the effects rendering of the effects component involved in the second target row entry in the effects rendering preview panel.

[0159] This technical solution further enhances the functionality of the special effects creation method. Building upon the aforementioned method, it specifically adds the ability to delete row entries by receiving deletion operations, simultaneously reverting the rendering of the involved special effects components on the special effects rendering preview panel within the special effects creation interface. The rendering effect displayed on the special effects rendering preview panel is consistent with the effect displayed in the special effects component navigation view. By establishing a connection between the special effects component navigation view and the special effects rendering preview panel through rendering order, users can more intuitively perceive the rendering order reflected in both views. Simple adjustments to the special effects component navigation view allow for the display of the rendering effect in the special effects rendering preview panel, reducing the user's learning and understanding costs and improving operational convenience and efficiency.

[0160] Furthermore, after responding to the entry deletion operation of the second target row entry, the method may further include the following execution steps: if the content of the third sub-navigation level table to which the second target row entry belongs is empty, then delete the third sub-navigation level table from the special effects component navigation view.

[0161] In this step, after responding to the entry deletion operation of the second target row entry, if the content of the third sub-navigation level table to which the second target row entry belongs is empty, that is, for the deleted row entry is the root level node, only the root node remains after the deletion operation, which is equivalent to an empty sub-navigation level table, then the third sub-navigation level table is deleted from the special effects component navigation view, which is equivalent to deleting the entire table.

[0162] This optional embodiment specifies that when the entry deletion operation is performed on the root node, after deleting the entry of the response row entry, the empty sub-navigation hierarchy table to which the row entry belongs can also be deleted, thereby realizing the management of the special effects component navigation view and ensuring that only valid information is retained in the target component navigation graph.

[0163] Furthermore, each row of entries in the sub-navigation hierarchy table displays a rendering / hiding control; the method may also specifically include the following execution steps:

[0164] a7) Receive rendering hide operation, wherein the rendering hide operation is to trigger the rendering hide control presented on the third target row entry.

[0165] This embodiment specifically describes how to implement the function of rendering or hiding by receiving a rendering / hiding operation. Rendering / hiding is used to determine whether the rendering of the target component involved in the effect is shown or hidden on the effect rendering preview panel of the effect creation interface. In this embodiment, the row entry requiring rendering / hiding operation is denoted as the third target row entry. The rendering / hiding operation triggers the rendering / hiding control displayed on the third target row entry. Users can determine whether the effect component involved in the row entry is shown or hidden on the effect rendering preview panel of the effect creation interface by clicking the rendering / hiding control. The underlying technical implementation of receiving the rendering / hiding operation can refer to the technical implementation of adding operations to the receiving component in the above steps, and will not be described in detail here.

[0166] b7) If the third target row entry is a root level node, determine the fourth sub-navigation level table to which the third target row entry belongs, and use rendering to show or hide the special effects rendering of the target components involved in the fourth sub-navigation level table on the special effects rendering preview panel of the special effects production interface.

[0167] This step responds to the rendering / hiding operation in the steps described above. In this embodiment, the sub-navigation hierarchy to which the third target row entry belongs is denoted as the fourth sub-navigation hierarchy. It is understood that different row entries are located at different hierarchy levels, and their visibility / hiding behavior differs. If the third target row entry is a root-level node, receiving the rendering / hiding operation is equivalent to showing or hiding the rendering of all target components corresponding to the entire fourth sub-navigation hierarchy, i.e., showing / hiding the special effects rendering of the target components involved in the fourth sub-navigation hierarchy in the special effects rendering preview panel of the special effects creation interface. In this embodiment, when a row entry is selected, the row entry in the special effects component navigation view can be grayed out.

[0168] c7) When the third target row entry is a sub-level node, the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel is presented or hidden by rendering concealment operation.

[0169] This step responds to the rendering / showing operation described above. If the third target row entry is a child-level node, receiving the rendering / showing operation is equivalent to showing or hiding the rendering of the corresponding special effects components under the child-level node, that is, showing / showing the special effects rendering of the target components involved under the child-level node in the special effects rendering preview panel of the special effects creation interface. In this embodiment, when a row entry is selected, the row entry in the special effects component navigation view can be grayed out.

[0170] d7) When the third target row entry is a leaf node, the special effects rendering of the target component involved in the third target row entry in the special effects rendering preview panel is presented or hidden by rendering a hidden operation.

[0171] This step responds to the rendering / hide operation in the steps described above. If the third target row entry is a leaf node, receiving the rendering / hide operation is equivalent to showing or hiding all the special effects components corresponding to that leaf node, that is, showing / hide the rendering of the target components involved in that leaf node in the special effects rendering preview panel of the special effects creation interface. In this embodiment, when a row entry is selected, the row entry in the special effects component navigation view can be grayed out.

[0172] For example, Figure 1h Example images of the rendering effect during the execution of the special effects production method provided in this embodiment, including the receiving, rendering, and hiding operations, are shown. Figure 1h As shown, the root level node, child level nodes, and leaf node corresponding row entries all display the rendering hide / hide control 20. When a rendering hide operation is received on the sub-navigation hierarchy table 1, it is equivalent to hiding the rendering of all target components involved in the sub-navigation hierarchy table 1, thus hiding rendering effect 1 in the effects rendering preview panel. This can be compared... Figure 1d and Figure 1h The effects rendered in the preview panel have changed, and rendering effect 1 is now hidden.

[0173] This optional embodiment further enhances the functionality of the special effects production method. Based on the above method implementation, it specifically adds the ability to present or hide the rendering of the relevant special effects components in the special effects rendering preview panel through rendering and hiding operations. This realizes the need to achieve changes in the special effects rendering effect by adjusting the special effects production, and provides convenience for user operation.

[0174] As a fourth optional embodiment of this example, based on the above embodiments, the special effects creation interface can be further optimized to include: a special effects model resource panel. The method may also specifically include the following execution steps:

[0175] a8) Receive a second drag operation, the second drag operation being applied to the special effects model displayed in the special effects model resource panel.

[0176] In this embodiment, the special effects creation interface includes a special effects component navigation view, a special effects rendering preview panel, and a special effects model resource panel. The special effects model resource panel contains special effects models that can be used for special effects creation. When a special effects model needs to be added, it can be added to the special effects component navigation view via a drag-and-drop operation, referred to in this embodiment as the second drag-and-drop operation. The second drag-and-drop operation is applied to the special effects models displayed in the special effects model resource panel. The special effects model resource panel can be directly displayed in the special effects creation panel, or it can be invoked and displayed via a touch. Once displayed, models can be dragged and dropped onto the special effects component navigation view. For example, the resource model can be a 3D model.

[0177] b8) Analyze the second drag behavior of the second drag operation, and add the effect model that matches the second drag behavior to the effect component navigation view.

[0178] This execution entity analyzes the second drag-and-drop behavior to determine which special effects model was selected and what operations were performed on it. After analyzing the second drag-and-drop behavior, the selected special effects model can be added to the special effects component navigation view. For example, if the second drag-and-drop operation drags a resource model to an empty space in the special effects component navigation view, the resource model can be automatically added to the bottommost sub-navigation level table. If the second drag-and-drop operation drags a resource model to a sub-navigation level table in the special effects component navigation tree, the resource model is inserted into that sub-navigation level table.

[0179] This optional embodiment further enhances the functionality of the special effects production method. Based on the above method implementation, a special effects model resource panel is added to the special effects production interface. By dragging and dropping, resource templates in the special effects model resource panel can be added to the special effects component navigation view, enriching the functionality of special effects production and improving the convenience of user operation.

[0180] Furthermore, the method also includes:

[0181] a9) Receive model instance creation operation, wherein the model instance creation operation is to trigger the instance creation option on the special effects model resource panel.

[0182] This embodiment also provides a model instance creation function. The model instance creation function is implemented by receiving a model instance creation operation, which is triggered by selecting the instance creation option on the special effects model resource panel. When a user wants to perform a model instance creation operation, they can click the instance creation option on the special effects model resource panel.

[0183] b9) Create a model instance and display the instance tag information of the model instance under the target level node of the fifth sub-navigation level table, which is displayed after the special effects component navigation view has already included the sub-navigation level table.

[0184] This step responds to the model instance creation operation, creates a model instance, and displays the instance tag information of the newly created model instance under the hierarchy node of the scene hierarchy table. For example, right-clicking will display many instances to create; clicking the selected instance will automatically add it to the hierarchy node. In this embodiment, by default, the newly created model instance will belong to the effects component navigation view after the effects component navigation view already contains a sub-navigation hierarchy table, denoted as the fifth sub-navigation hierarchy table. The model instance will be presented under the target hierarchy node of this sub-navigation hierarchy table. It is understood that the affiliation of model instances can be pre-set during the development phase.

[0185] This optional embodiment further enhances the functionality of the special effects production method. Based on the above method implementation, it adds another way to create model instances. Through the model instance creation operation, model instances in the special effects model resource panel can be added to the special effects component navigation view, enriching the functionality of special effects production and improving the convenience of user operation.

[0186] Furthermore, the special effects creation interface also includes an operation undo control, and the method may further include the following execution steps:

[0187] a10) receives a rollback operation, wherein the rollback operation is triggered by the operation undo control.

[0188] This embodiment specifically describes how to implement the rollback function for a deletion operation by receiving a rollback operation. An operation rollback control can implement the rollback function, and the rollback operation is triggered by clicking the operation rollback control. For example, this can be achieved through a signal input device, such as a mouse, by clicking the operation rollback control.

[0189] b10) Return to the display state corresponding to the previous operation node in the special effects creation interface.

[0190] This step responds to the received rollback operation and can revert the special effects creation interface to the display state corresponding to the previous operation node. In this embodiment, there is no limit to the number of times the operation can be undone; for example, one rollback can be achieved by clicking the operation rollback control once. Alternatively, the rollback can be achieved by clicking the rollback control multiple times. In addition, the special effects creation method provided in this embodiment also includes copy and paste functions.

[0191] This optional embodiment further enhances the functionality of the special effects production method. Based on the above method implementation, it specifically adds the ability to revert the display state of the special effects production interface by receiving a rollback operation. This technology enables better management of the navigation view of special effects components.

[0192] As a fifth optional embodiment of this disclosure, based on the above embodiments, this fifth optional embodiment can further optimize the above-mentioned special effects production method. Specifically, the method may further include the following execution steps:

[0193] a11) Obtain the final target rendering sort of the sub-navigation hierarchy table displayed in the navigation view of the special effects component.

[0194] The above is only a description of special effects production; here we introduce a description of special effects rendering. Specifically, we obtain the final rendering order of the sub-navigation hierarchy table displayed in the special effects component navigation view. This rendering order can be the order after the user adds or drags and drops to adjust it according to their needs. This rendering order is recorded as the target rendering order.

[0195] b11) Integrate the target component data of the target components in the sub-navigation hierarchy table according to the target rendering sort to form the special effects rendering file of the created special effects.

[0196] In this context, the target component can be understood as the component involved in creating the special effects, and the special effects component data can be understood as the parameters required for rendering the target component. The special effects rendering file can be understood as various information required for rendering the special effects. In this embodiment, a special effects rendering file is required for rendering the special effects. The special effects component data of the special effects components in each sub-navigation hierarchy table, sorted according to the target rendering, is obtained to form the special effects rendering file of the created special effects.

[0197] This optional embodiment describes the process from the perspective of special effects rendering. Based on the special effects production, a special effects rendering file is generated. The special effects rendering file is used for special effects rendering, thereby establishing a connection between special effects production and special effects rendering. This realizes that the hierarchical order of each sub-navigation table in the special effects component navigation view corresponds to the rendering order, providing support for adjusting the rendering order in the rendering effect through simple operations on the special effects component navigation view.

[0198] Figure 2 A flowchart illustrating a special effects rendering method provided in this disclosure is given. This disclosure is applicable to situations involving special effects rendering. The method can be executed by a special effects rendering device, which can be implemented in software and / or hardware, and optionally, by an electronic device.

[0199] like Figure 2 As shown, the special effects rendering method of this disclosure embodiment may specifically include:

[0200] S210. Obtain the target effect rendering file for the target effect to be rendered.

[0201] This embodiment primarily describes how to implement special effects rendering. The target special effect can be understood as the desired special effect, and the target special effects rendering file can be understood as the special effects rendering file required to achieve the target special effect. The target special effects rendering file contains various information required for special effects rendering. For example, the target special effects rendering file contains target component data that integrates the target components from each sub-navigation hierarchy table according to the target rendering sort.

[0202] S220. Extract the target rendering sort and corresponding target component data of each target component in the target special effects rendering file. The target rendering sort is determined based on the special effects production method described in the embodiments of this disclosure.

[0203] The target effect rendering file contains the rendering order of each target component in the target effect, denoted in this embodiment as the target rendering order and the target component data corresponding to each target component. The target rendering order of each target component in the target effect is extracted from the target effect rendering file, and its corresponding target component data can also be extracted. It should be noted that in this embodiment, the target rendering order is determined based on the effect production method provided in this disclosure.

[0204] It is understandable that the order of the sub-navigation hierarchy in the special effects component navigation view during special effects production is consistent with the target rendering order. At the same time, the rendering order of each target component during special effects rendering is based on the target rendering order. Therefore, the display order of the sub-navigation hierarchy in the special effects component navigation view during special effects production is consistent with the rendering order of the target components during special effects rendering.

[0205] S230. Using the data of each target component, render each target component according to the target rendering sort to generate target effects.

[0206] Specifically, target component data can be understood as the various parameter information of the target component. By using this data and rendering each target component according to the target rendering order, the target effect is generated. Because of the target rendering order, the rendering order of each target component varies, resulting in differences in the rendering layers of each target component within the target effect. The rendering order determines the rendering layer of the target component. Target components rendered earlier have a lower rendering layer, and vice versa. The rendering order corresponds to the drawing order during the drawing of the target components.

[0207] This disclosure provides a special effects rendering method, which involves obtaining a target special effects rendering file for a target special effects to be rendered; extracting the target rendering order and corresponding target component data of each target component in the target special effects rendering file, wherein the target rendering order is determined based on the special effects production method described in this disclosure; and rendering each target component according to the target rendering order using the target component data to generate the target special effects. In this embodiment, the special effects rendering file determined by the above-mentioned special effects production method can more effectively ensure the correctness and effectiveness of the special effects rendering. Unlike the special effects rendering files generated by existing production methods, the special effects rendering file generated by the special effects production method provided in this embodiment achieves automatic classification and division of the added special effects components to their respective sub-scenes, and also achieves automatic adjustment of the rendering order of the special effects components. The entire scene drawing process not only simplifies the special effects production process and reduces the development and understanding costs for designers, but also improves the correctness and effectiveness of the special effects component drawing.

[0208] Figure 3 A structural schematic diagram of a special effects production method provided in an embodiment of this disclosure is given, as follows: Figure 3 As shown, the device includes: a first display module 31, a first receiving module 32, and a second display module 33, wherein,

[0209] The first display module 31 is used to display the special effects creation interface, which includes: a special effects component navigation view;

[0210] The first receiving module 32 is used to receive a component adding operation, wherein the component adding operation is to select the component tag information of the first target component in the presented component menu list;

[0211] The second display module 33 is used to determine the first sub-navigation hierarchy table to which the first target component belongs, and to present the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0212] This disclosure provides a special effects production method. During the special effects production process, upon receiving a component addition operation for a target component, it can directly determine which sub-scene the target component belongs to and its level within that sub-scene. This allows the component tag information (such as the target component's name) of the added target component to be presented in the sub-navigation hierarchy table of its respective sub-scene. Simultaneously, this sub-navigation hierarchy table can be presented in a specific rendering order in the special effects component navigation view, enabling designers to quickly understand the rendering order of the added target component. This embodiment achieves automatic classification of added target components to their respective sub-scenes during special effects production. Furthermore, the automated sorting of the sub-navigation hierarchy tables in the special effects component navigation view is equivalent to automatically configuring the rendering order of the target components. It also provides a visual representation of the target component's rendering order to designers. This technical solution simplifies the special effects production process, reduces the development and understanding costs for designers, and improves the accuracy and effectiveness of target component rendering.

[0213] Furthermore, the second display module 33 can be specifically used for:

[0214] If at least one sub-navigation hierarchy table has been displayed in the special effects component navigation view, determine whether the first target component belongs to the at least one displayed sub-navigation hierarchy table;

[0215] If so, the sub-navigation hierarchy table to which the first target component belongs is determined as the first sub-navigation hierarchy table, wherein the first rendering order is the current rendering order of at least one displayed sub-navigation hierarchy table presented in the special effects component navigation view.

[0216] If not, then construct a first sub-navigation hierarchy table to which the first target component belongs, wherein the first rendering sort is determined based on the current rendering sort, and the first sub-navigation hierarchy table is inserted into the corresponding position in the special effects component navigation view according to the first rendering sort.

[0217] Furthermore, when the special effects component navigation view displays at least two sub-navigation hierarchy tables, the device also includes a first drag-and-drop response module, which can be used to:

[0218] Receive a first drag operation, the first drag operation being applied to a row entry in the sub-navigation hierarchy table displayed in the navigation view of the special effects component;

[0219] When the first drag operation satisfies the drag response conditions of the second sub-navigation hierarchy table, the second rendering order is determined according to the first drag operation, and the display position of the second sub-navigation hierarchy table in the special effects component navigation view is adjusted according to the second rendering order.

[0220] Furthermore, the target of the first drag-and-drop operation includes at least one of the following:

[0221] The first row entry of any sub-navigation hierarchy table in the special effects component navigation view, or any other row entry in the sub-navigation hierarchy table except for the first row entry;

[0222] The first row entry of any sub-navigation hierarchy table within the special effects component navigation view, and at least one other row entry in at least one other sub-navigation hierarchy table excluding the first row entry;

[0223] The first row entry of at least two sub-navigation hierarchy tables in the special effects component navigation view;

[0224] The special effects component navigation view contains at least two sub-navigation hierarchy tables with at least one other row entry besides the first row entry;

[0225] The first drag behavior of the first drag operation includes at least one of the following:

[0226] In the special effects component navigation view, drag the target object to the blank space below;

[0227] In the special effects component navigation view, drag the target object to the middle of two adjacent sub-navigation hierarchy tables;

[0228] In the special effects component navigation view, drag the target object to any row of any sub-navigation level table;

[0229] In the special effects component navigation view, drag the target object to the middle of any two adjacent rows in the sub-navigation hierarchy table.

[0230] Furthermore, the special effects creation interface also includes a special effects rendering preview panel, and the device also includes a rendering and presentation module, which can be used for:

[0231] While presenting the component tag information under the target level node of the first sub-navigation hierarchy table, the first target component is rendered according to the first rendering sort, and the first special effect of the first target component is presented on the first rendering layer of the special effect rendering preview panel.

[0232] While adjusting the display position of the second sub-navigation hierarchy table in the special effects component navigation view, the second target component involved in the second sub-navigation hierarchy table is rendered according to the second rendering order, and the second special effects of the second target component are presented on the second rendering layer of the special effects rendering preview panel.

[0233] Furthermore,

[0234] The sub-navigation hierarchy table is a tree structure component as a whole, and the first entry of the sub-navigation hierarchy table serves as the root level node in the tree structure.

[0235] The component tag information of the added target component is used as a row entry in the sub-navigation hierarchy table, forming a sub-hierarchical node or leaf node under the root level node;

[0236] Each row entry corresponding to the root-level node and its child-level nodes displays a collapsible control.

[0237] Furthermore, the device also includes a retraction / expansion response module, which can be used specifically for:

[0238] Receive an item collapse / expansion operation, wherein the item collapse / expansion operation is triggered by triggering the collapse / expansion control corresponding to the target level node; or, the item collapse / expansion operation is selected by selecting the row item where the target level node is located.

[0239] If the item expansion operation is an item expansion operation, then the row items contained under the target level node are expanded and displayed.

[0240] If the item collapse operation is an item collapse operation, then the row items under the target level node are collapsed.

[0241] Furthermore, the device also includes a naming response module, which can be used specifically for:

[0242] Receive the entry naming operation for the first target row entry;

[0243] Control the first target row entry to be in an editable state, and obtain the editing information edited in the first target row entry;

[0244] In response to the naming information save operation, the edited information is used as the new entry name for the first target row entry and saved.

[0245] Furthermore, the device also includes a first deletion response module, which can be used to:

[0246] Receive the entry deletion operation for the second target row entry;

[0247] If the second target row entry is a root level node, delete the third sub-navigation level table to which the second target row entry belongs from the special effects component navigation view, and withdraw the rendering of the target components involved in the third target sub-navigation level table on the special effects rendering preview panel in the special effects production interface.

[0248] If the second target row entry is a sub-level node, delete all row entries contained under the sub-level node, and undo the rendering of the target components involved under the sub-level node in the special effects rendering preview panel;

[0249] If the second target row entry is a leaf node, delete the second target row entry and undo the rendering of the target component involved in the second target row entry in the effects rendering preview panel.

[0250] Furthermore, the device may also include a second deletion response module, which, after responding to the entry deletion operation of the second target row entry, may specifically be used for:

[0251] If the content of the third sub-navigation level table to which the second target row entry belongs is empty, then the third sub-navigation level table is deleted from the special effects component navigation view.

[0252] Furthermore, each row of entries in the sub-navigation hierarchy table displays a rendering visibility control;

[0253] The device may also include a hidden response module, which can be used specifically for:

[0254] Receive a rendering hide operation, wherein the rendering hide operation is to trigger the rendering hide control presented on the third target row entry;

[0255] When the third target row entry is a root level node, determine the fourth sub-navigation level table to which the third target row entry belongs, and use rendering to show or hide the special effects rendering of the target components involved in the fourth sub-navigation level table on the special effects rendering preview panel in the special effects production interface.

[0256] When the third target row entry is a sub-level node, the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel is presented or hidden through rendering concealment operations;

[0257] When the third target row entry is a leaf node, the special effects rendering of the target component involved in the third target row entry in the special effects rendering preview panel is presented or hidden by rendering concealment operation.

[0258] Furthermore, the special effects creation interface also includes: a special effects model resource panel;

[0259] The device also includes a second drag-and-drop response module, which can be used specifically for:

[0260] Receive a second drag operation, which is applied to the special effects model displayed in the special effects model resource panel;

[0261] Analyze the second drag behavior of the second drag operation, and add the special effect model that matches the second drag behavior to the special effect component navigation view.

[0262] Furthermore, the device also includes a creation module, which can be used specifically for:

[0263] Receive a model instance creation operation, wherein the model instance creation operation is to trigger the instance creation option on the special effects model resource panel;

[0264] Create a model instance and display the instance tag information of the model instance under the target level node of the fifth sub-navigation level table, which is displayed after the sub-navigation level table is already included in the special effects component navigation view.

[0265] Furthermore, the special effects creation interface also includes: an operation undo control.

[0266] The device may also include a rollback module, which can be used specifically for:

[0267] Receive rollback operation, wherein the rollback operation is triggered by the operation undo control;

[0268] Return to the display state corresponding to the previous operation node on the special effects creation interface.

[0269] Furthermore, the device also includes a rendering file determination module, which can be used for:

[0270] Obtain the final target rendering sort of the sub-navigation hierarchy table displayed in the navigation view of the special effects component;

[0271] The target component data of each sub-navigation level table is integrated according to the target rendering sort to form the special effects rendering file of the created special effects.

[0272] The special effects production method provided in this disclosure can execute the special effects production method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0273] Figure 4 This is a schematic diagram of the structure of a special effects rendering device provided in an embodiment of the present disclosure, as shown below. Figure 4 As shown, the device includes: a first display module 41, a first receiving module 42, and a second display module 43, wherein,

[0274] Module 41 is used to obtain the target effect rendering file of the target effect to be rendered;

[0275] Extraction module 42 is used to extract the target rendering order and corresponding target component data of each target component in the target special effects rendering file, wherein the target rendering order is determined based on the special effects production method according to any one of claims 1-15;

[0276] The rendering module 43 is used to render each of the target components according to the target rendering sort based on the data of each target component, and generate target effects.

[0277] The special effects rendering apparatus provided in this disclosure can execute the special effects rendering method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the method execution.

[0278] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0279] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 5 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 5 The diagram below shows the structure of the terminal device or server 500. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0280] like Figure 5 As shown, electronic device 500 may include a processing unit (e.g., central processing unit, graphics processor, etc.) 501, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 502 or a program loaded from storage device 508 into random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. An edit / output (I / O) interface 505 is also connected to bus 504.

[0281] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0282] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined in the methods of embodiments of this disclosure.

[0283] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0284] The electronic device provided in this embodiment belongs to the same inventive concept as the special effects production method or special effects rendering method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0285] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the special effects production method or special effects rendering method provided in the above embodiments.

[0286] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having 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, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0287] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0288] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0289] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: perform material parsing processing on the original material of the business object to obtain the target graphic material of the business object; generate target poster description information based on the target graphic material and the poster generation configuration information of the business object; and generate and display the target poster image of the business object by rendering the target poster description information.

[0290] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can 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 can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0291] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0292] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0293] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0294] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0295] According to one or more embodiments of this disclosure, [Example 1] provides a method for creating special effects, the method comprising:

[0296] The special effects creation interface is displayed, which includes: a special effects component navigation view;

[0297] Receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list;

[0298] The first sub-navigation hierarchy table to which the first target component belongs is determined, and the component tag information is presented under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0299] According to one or more embodiments of this disclosure, [Example 2] provides a special effects production method, wherein determining the first sub-navigation hierarchy table to which the first target component belongs may include:

[0300] If at least one sub-navigation hierarchy table has been displayed in the special effects component navigation view, determine whether the first target component belongs to the at least one displayed sub-navigation hierarchy table;

[0301] If so, the sub-navigation hierarchy table to which the first target component belongs is determined as the first sub-navigation hierarchy table, wherein the first rendering order is the current rendering order of at least one displayed sub-navigation hierarchy table presented in the special effects component navigation view.

[0302] If not, then construct a first sub-navigation hierarchy table to which the first target component belongs, wherein the first rendering sort is determined based on the current rendering sort, and the first sub-navigation hierarchy table is inserted into the corresponding position in the special effects component navigation view according to the first rendering sort.

[0303] According to one or more embodiments of this disclosure, [Example 3] provides a method for creating special effects. When the special effects component navigation view displays at least two sub-navigation hierarchy tables, the method may further include:

[0304] Receive a first drag operation, the first drag operation being applied to a row entry in the sub-navigation hierarchy table displayed in the navigation view of the special effects component;

[0305] When the first drag operation satisfies the drag response conditions of the second sub-navigation hierarchy table, the second rendering order is determined according to the first drag operation, and the display position of the second sub-navigation hierarchy table in the special effects component navigation view is adjusted according to the second rendering order.

[0306] According to one or more embodiments of this disclosure, [Example 4] provides a method for creating special effects.

[0307] The first drag-and-drop operation applies to at least one of the following:

[0308] The first row entry of any sub-navigation hierarchy table in the special effects component navigation view, or any other row entry in the sub-navigation hierarchy table except for the first row entry;

[0309] The first row entry of any sub-navigation hierarchy table within the special effects component navigation view, and at least one other row entry in at least one other sub-navigation hierarchy table excluding the first row entry;

[0310] The first row entry of at least two sub-navigation hierarchy tables in the special effects component navigation view;

[0311] The special effects component navigation view contains at least two sub-navigation hierarchy tables with at least one other row entry besides the first row entry;

[0312] The first drag behavior of the first drag operation includes at least one of the following:

[0313] In the special effects component navigation view, drag the target object to the blank space below;

[0314] In the special effects component navigation view, drag the target object to the middle of two adjacent sub-navigation hierarchy tables;

[0315] In the special effects component navigation view, drag the target object to any row of any sub-navigation level table;

[0316] In the special effects component navigation view, drag the target object to the middle of any two adjacent rows in the sub-navigation hierarchy table.

[0317] According to one or more embodiments of this disclosure, [Example 5] provides a method for creating special effects, wherein the special effects creation interface further includes a special effects rendering preview panel, and the method may further include:

[0318] While presenting the component tag information under the target level node of the first sub-navigation hierarchy table, the first target component is rendered according to the first rendering sort, and the first special effect of the first target component is presented on the first rendering layer of the special effect rendering preview panel.

[0319] While adjusting the display position of the second sub-navigation hierarchy table in the special effects component navigation view, the second target component involved in the second sub-navigation hierarchy table is rendered according to the second rendering order, and the second special effects of the second target component are presented on the second rendering layer of the special effects rendering preview panel.

[0320] According to one or more embodiments of this disclosure, [Example Six] provides a method for creating special effects.

[0321] The sub-navigation hierarchy table is a tree structure component as a whole, and the first entry of the sub-navigation hierarchy table serves as the root level node in the tree structure.

[0322] The component tag information of the added target component is used as a row entry in the sub-navigation hierarchy table, forming a sub-hierarchical node or leaf node under the root level node;

[0323] Each row entry corresponding to the root-level node and its child-level nodes displays a collapsible control.

[0324] According to one or more embodiments of this disclosure, [Example Seven] provides a method for creating special effects, which may further include:

[0325] Receive an item collapse / expansion operation, wherein the item collapse / expansion operation is triggered by triggering the collapse / expansion control corresponding to the target level node; or, the item collapse / expansion operation is selected by selecting the row item where the target level node is located.

[0326] If the item expansion operation is an item expansion operation, then the row items contained under the target level node are expanded and displayed.

[0327] If the item collapse operation is an item collapse operation, then the row items under the target level node are collapsed.

[0328] According to one or more embodiments of this disclosure, [Example Eight] provides a method for creating special effects, which may further include:

[0329] Receive the entry naming operation for the first target row entry;

[0330] Control the first target row entry to be in an editable state, and obtain the editing information edited in the first target row entry;

[0331] In response to the naming information save operation, the edited information is used as the new entry name for the first target row entry and saved.

[0332] According to one or more embodiments of this disclosure, [Example Nine] provides a method for creating special effects, which may further include:

[0333] Receive the entry deletion operation for the second target row entry;

[0334] If the second target row entry is a root level node, delete the third sub-navigation level table to which the second target row entry belongs from the special effects component navigation view, and withdraw the rendering of the target components involved in the third target sub-navigation level table on the special effects rendering preview panel in the special effects production interface.

[0335] If the second target row entry is a sub-level node, delete all row entries contained under the sub-level node, and undo the rendering of the target components involved under the sub-level node in the special effects rendering preview panel;

[0336] If the second target row entry is a leaf node, delete the second target row entry and undo the rendering of the target component involved in the second target row entry in the effects rendering preview panel.

[0337] According to one or more embodiments of this disclosure, [Example 10] provides a special effects creation method, which, after responding to an entry deletion operation of the second target row entry, may further include:

[0338] If the content of the third sub-navigation level table to which the second target row entry belongs is empty, then the third sub-navigation level table is deleted from the special effects component navigation view.

[0339] According to one or more embodiments of this disclosure, [Example 11] provides a method for creating special effects, wherein each row of entries in the sub-navigation hierarchy table displays a rendering / hiding control; the method may further include:

[0340] Receive a rendering hide operation, wherein the rendering hide operation is to trigger the rendering hide control presented on the third target row entry;

[0341] When the third target row entry is a root level node, determine the fourth sub-navigation level table to which the third target row entry belongs, and use rendering to show or hide the special effects rendering of the target components involved in the fourth sub-navigation level table on the special effects rendering preview panel in the special effects production interface.

[0342] When the third target row entry is a sub-level node, the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel is presented or hidden through rendering concealment operations;

[0343] When the third target row entry is a leaf node, the special effects rendering of the target component involved in the third target row entry in the special effects rendering preview panel is presented or hidden by rendering concealment operation.

[0344] According to one or more embodiments of this disclosure, [Example Twelve] provides a method for creating special effects, wherein the special effects creation interface further includes: a special effects model resource panel; the method may further include:

[0345] Receive a second drag operation, which is applied to the special effects model displayed in the special effects model resource panel;

[0346] Analyze the second drag behavior of the second drag operation, and add the special effect model that matches the second drag behavior to the special effect component navigation view.

[0347] According to one or more embodiments of this disclosure, [Example Thirteen] provides a method for creating special effects, which may further include:

[0348] Receive a model instance creation operation, wherein the model instance creation operation is to trigger the instance creation option on the special effects model resource panel;

[0349] Create a model instance and display the instance tag information of the model instance under the target level node of the fifth sub-navigation level table, which is displayed after the sub-navigation level table is already included in the special effects component navigation view.

[0350] According to one or more embodiments of this disclosure, [Example Fourteen] provides a method for creating special effects, wherein the special effects creation interface further includes: an operation undo control, and the method may further include:

[0351] Receive rollback operation, wherein the rollback operation is triggered by the operation undo control;

[0352] Return to the display state corresponding to the previous operation node on the special effects creation interface.

[0353] According to one or more embodiments of this disclosure, [Example Fifteen] provides a method for creating special effects, which may further include:

[0354] Obtain the final target rendering sort of each displayed sub-navigation hierarchy table within the navigation view of the special effects component;

[0355] The target component data of each sub-navigation level table is integrated according to the target rendering sort to form the special effects rendering file of the created special effects.

[0356] According to one or more embodiments of this disclosure, [Example Sixteen] provides a special effects rendering method, the method comprising:

[0357] Obtain the target effect rendering file for the target effect to be rendered;

[0358] Extract the target rendering sort and corresponding target component data of each target component from the target special effects rendering file. The target rendering sort is determined based on the special effects production method described in any one of Examples 1 to 15.

[0359] Using the data of each target component, render each target component according to the target rendering sort to generate target effects.

[0360] According to one or more embodiments of this disclosure, [Example Seventeen] provides a method for creating special effects, the apparatus comprising:

[0361] The first display module is used to display the special effects creation interface, which includes: a special effects component navigation view;

[0362] The first receiving module is used to receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list;

[0363] The second display module is used to determine the first sub-navigation hierarchy table to which the first target component belongs, and to present the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort.

[0364] According to one or more embodiments of this disclosure, [Example 18] provides a special effects rendering apparatus, the apparatus comprising:

[0365] The acquisition module is used to acquire the target effect rendering file of the target effect to be rendered;

[0366] An extraction module is used to extract the target rendering order and corresponding target component data of each target component in the target special effects rendering file, wherein the target rendering order is determined based on the special effects production method according to any one of claims 1-15;

[0367] The rendering module is used to render each of the target components according to the target rendering sort based on the data of each target component, and generate target effects.

[0368] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0369] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0370] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for creating special effects, characterized in that, include: The special effects creation interface is displayed, which includes: a special effects component navigation view; Receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list; The first sub-navigation hierarchy table to which the first target component belongs is determined, and the component tag information is presented under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort; Each special effects component is pre-set to belong to a default category in the sub-navigation hierarchy table, which contains one or more hierarchy nodes.

2. The method according to claim 1, characterized in that, The first sub-navigation hierarchy table for determining the affiliation of the first target component includes: If at least one sub-navigation hierarchy table has been displayed in the special effects component navigation view, determine whether the first target component belongs to the at least one displayed sub-navigation hierarchy table; If so, the sub-navigation hierarchy table to which the first target component belongs is determined as the first sub-navigation hierarchy table, wherein the first rendering order is the current rendering order of at least one displayed sub-navigation hierarchy table presented in the special effects component navigation view. If not, a first sub-navigation hierarchy table to which the first target component belongs is constructed, wherein the first rendering order is determined based on the current rendering order, and the first sub-navigation hierarchy table is inserted into the corresponding position in the special effects component navigation view according to the first rendering order.

3. The method according to claim 1, characterized in that, When the special effects component navigation view displays at least two sub-navigation hierarchy tables, the method further includes: Receive a first drag operation, the first drag operation being applied to a row entry in the sub-navigation hierarchy table displayed in the navigation view of the special effects component; When the first drag operation satisfies the drag response conditions of the second sub-navigation hierarchy table, the second rendering order is determined according to the first drag operation, and the display position of the second sub-navigation hierarchy table in the special effects component navigation view is adjusted according to the second rendering order.

4. The method according to claim 3, characterized in that, The first drag-and-drop operation applies to at least one of the following: The first row entry of any sub-navigation hierarchy table in the special effects component navigation view, or any other row entry in the sub-navigation hierarchy table except for the first row entry; The first row entry of any sub-navigation hierarchy table within the special effects component navigation view, and at least one other row entry in at least one other sub-navigation hierarchy table excluding the first row entry; The first row entries of at least two sub-navigation hierarchy tables in the special effects component navigation view; The special effects component navigation view contains at least two sub-navigation hierarchy tables with at least one other row entry besides the first row entry; The first drag behavior of the first drag operation includes at least one of the following: In the special effects component navigation view, drag the target object to the blank space below; In the special effects component navigation view, drag the target object to the middle of two adjacent sub-navigation hierarchy tables; In the special effects component navigation view, drag the target object to any row of any sub-navigation level table; In the special effects component navigation view, drag the target object to the middle of any two adjacent rows in the sub-navigation hierarchy table.

5. The method according to claim 3 or 4, characterized in that, The special effects creation interface also includes a special effects rendering preview panel, and the method further includes: While presenting the component tag information under the target level node of the first sub-navigation hierarchy table, the first target component is rendered according to the first rendering sort, and the first special effect of the first target component is presented on the first rendering layer of the special effect rendering preview panel. While adjusting the display position of the second sub-navigation hierarchy table in the special effects component navigation view, the second target component involved in the second sub-navigation hierarchy table is rendered according to the second rendering sort, and the second special effects of the second target component are presented on the second rendering layer of the special effects rendering preview panel.

6. The method according to claim 1, characterized in that, The sub-navigation hierarchy table is a tree structure component, and the first entry of the sub-navigation hierarchy table serves as the root level node in the tree structure. The component tag information of the added target component is used as a row entry in the sub-navigation hierarchy table, forming a sub-hierarchical node or leaf node under the root level node; Each row entry corresponding to the root-level node and its child-level nodes displays a collapsible control.

7. The method according to claim 6, characterized in that, The method further includes: Receive an item collapse / expansion operation, wherein the item collapse / expansion operation is triggered by triggering the collapse / expansion control corresponding to the target level node; or, the item collapse / expansion operation is selected by selecting the row item where the target level node is located. If the item expansion operation is an item expansion operation, then the row items contained under the target level node are expanded and displayed. If the item collapse operation is an item collapse operation, then the row items under the target level node are collapsed.

8. The method according to claim 6, characterized in that, The method further includes: Receive the entry naming operation for the first target row entry; Control the first target row entry to be in an editable state, and obtain the editing information edited in the first target row entry; In response to the naming information save operation, the edited information is used as the new entry name for the first target row entry and saved.

9. The method according to claim 6, characterized in that, The method further includes: Receive the entry deletion operation for the second target row entry; If the second target row entry is a root level node, delete the third sub-navigation level table to which the second target row entry belongs from the special effects component navigation view, and withdraw the special effects rendering of the target components involved in the third sub-navigation level table on the special effects rendering preview panel in the special effects creation interface. If the second target row entry is a sub-level node, delete all row entries contained under the sub-level node, and retract the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel; If the second target row entry is a leaf node, delete the second target row entry and revert the effect rendering of the target component involved in the second target row entry in the effect rendering preview panel.

10. The method according to claim 9, characterized in that, After responding to the entry deletion operation of the second target row entry, the method further includes: If the content of the third sub-navigation level table to which the second target row entry belongs is empty, then the third sub-navigation level table is deleted from the special effects component navigation view.

11. The method according to claim 6, characterized in that, Each row of entries in the sub-navigation hierarchy table displays a rendering hidden control; The method further includes: Receive a rendering hide operation, wherein the rendering hide operation is to trigger the rendering hide control presented on the third target row entry; When the third target row entry is a root level node, determine the fourth sub-navigation level table to which the third target row entry belongs, and use rendering to show or hide the special effects rendering of the target components involved in the fourth sub-navigation level table on the special effects rendering preview panel in the special effects production interface. When the third target row entry is a sub-level node, the special effects rendering of the target components involved under the sub-level node in the special effects rendering preview panel is presented or hidden through rendering concealment operations; When the third target row entry is a leaf node, the special effects rendering of the target component involved in the third target row entry in the special effects rendering preview panel is presented or hidden by rendering concealment operation.

12. The method according to claim 1, characterized in that, The special effects creation interface also includes: a special effects model resource panel; The method further includes: Receive a second drag operation, which is applied to the special effects model displayed in the special effects model resource panel; Analyze the second drag behavior of the second drag operation, and add the special effect model that matches the second drag behavior to the special effect component navigation view.

13. The method according to claim 12, characterized in that, Also includes: Receive a model instance creation operation, wherein the model instance creation operation is to trigger the instance creation option on the special effects model resource panel; Create a model instance and display the instance tag information of the model instance under the target level node of the fifth sub-navigation level table, which is displayed after the sub-navigation level table is already included in the special effects component navigation view.

14. The method according to any one of claims 6-13, characterized in that, The special effects creation interface also includes: an operation undo control. The method further includes: Receive rollback operation, wherein the rollback operation is triggered by the operation undo control; Return to the display state corresponding to the previous operation node on the special effects creation interface.

15. The method according to claim 1, characterized in that, Also includes: Obtain the final target rendering sort of the sub-navigation hierarchy table displayed in the navigation view of the special effects component; The target component data of the target components in the sub-navigation hierarchy table are integrated according to the target rendering sort to form the special effects rendering file of the created special effects.

16. A special effects rendering method, characterized in that, include: Obtain the target effect rendering file for the target effect to be rendered; Extract the target rendering sort and corresponding target component data of each target component from the target special effects rendering file, wherein the target rendering sort is determined based on the special effects production method according to any one of claims 1-15; Using the data of each target component, render each target component according to the target rendering sort to generate target effects.

17. A special effects production device, characterized in that, include: The first display module is used to display the special effects creation interface, which includes: a special effects component navigation view; The first receiving module is used to receive a component addition operation, wherein the component addition operation is to select the component tag information of the first target component in the presented component menu list; The second display module is used to determine the first sub-navigation hierarchy table to which the first target component belongs, and to present the component tag information under the target hierarchy node of the first sub-navigation hierarchy table; wherein, the first sub-navigation hierarchy table is pre-displayed in the special effects component navigation view according to the first rendering sort; Each special effects component is pre-set to belong to a default category in the sub-navigation hierarchy table, which contains one or more hierarchy nodes.

18. A special effects rendering device, characterized in that, include: The acquisition module is used to acquire the target effect rendering file of the target effect to be rendered; An extraction module is used to extract the target rendering order and corresponding target component data of each target component in the target special effects rendering file, wherein the target rendering order is determined based on the special effects production method according to any one of claims 1-15; The rendering module is used to render each of the target components according to the target rendering sort based on the data of each target component, and generate target effects.

19. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-16.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-16.

Images