Plane model processing method and system

Abstract

The present application discloses a method for processing a plane model, which includes: drawing multiple sets of plane model texture constraint maps and determining the texture replacement range between components; making a set of standard plane models and exporting corresponding driver files; sorting out the composition logic of the standard plane model, formulating a component hierarchical structure diagram and a standard component level ID identification table; splitting and reorganizing the multiple sets of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram and the standard component level ID identification table, generating multiple reorganized plane models, and driving the reorganized plane models with the driver file. The present application also discloses a plane model processing system, an electronic device and a computer-readable storage medium. In this way, the rendering freedom of the plane model can be improved and the production cost and cycle can be reduced.

Description

Technical Field

[0001] The present application relates to the field of image processing technology, and in particular to a plane model processing method, system, electronic device and computer-readable storage medium. Background Art

[0002] 2D (flat) model design and rendering is a very popular image processing method in the market, widely used in games, virtual characters, film and television production, and other fields. 2D models can effectively present artistic effects, preserve artistic styles, and realize the designer's original concept.

[0003] However, due to its 2D presentation and technical limitations, while stylizing the original artwork, it loses some freedom in model rendering. Furthermore, 2D model design is very expensive, and in most cases, a separate model must be created for each design. This makes it difficult to render multiple models while switching between internal modules without model overlap. Summary of the Invention

[0004] The main purpose of this application is to propose a plane model processing method, system, electronic device and computer-readable storage medium, aiming to solve the problem of how to improve the freedom of plane model rendering and reduce costs.

[0005] To achieve the above objectives, an embodiment of the present application provides a plane model processing method, the method comprising:

[0006] Drawing multiple sets of plane model texture constraint maps, and determining texture replacement ranges between components in the multiple sets of plane model texture constraint maps;

[0007] Make a set of standard plane models and export the corresponding driver files;

[0008] Sorting out the composition logic of the standard plane model, formulating a component hierarchical structure diagram and a standard component grade code identification table;

[0009] According to the composition logic, the component hierarchical structure diagram and the standard component grade code identification table, the multiple sets of plane model texture constraint diagrams are split and reorganized to generate multiple reorganized plane models, and the driver file is used to drive the reorganized plane models.

[0010] Optionally, the method further includes:

[0011] A user's texture modification requirement for the generated plane model is received, and according to the requirement, the texture modification of the corresponding component is performed within the constraint range of the corresponding texture constraint map.

[0012] Optionally, drawing multiple sets of plane model texture constraint graphs includes:

[0013] Draw M sets of plane models, summarize the commonalities of the image contours of each component in the M sets of plane models by superposition, and form N sets of plane model texture constraint maps, where M and N are positive integers and N <M。

[0014] Optionally, the drive file includes a dynamic drive file and an expression drive file.

[0015] Optionally, the step of combing the composition logic of the standard plane model and formulating a component hierarchical structure diagram and a standard component grade code identification table includes:

[0016] Disassemble each module in the standard plane model and sort out the composition logic of the standard plane model;

[0017] Develop a component hierarchical structure diagram based on the structured logic;

[0018] A standard component grade coding identification table is formulated based on the component grade structure diagram.

[0019] Optionally, combing the composition logic of the standard plane model includes combing component composition structure, front and back texture occlusion relationship, categories to which each component belongs, and ranges of mutually replaceable textures.

[0020] Optionally, the formulating a component hierarchical structure diagram includes:

[0021] The components required in each module of the standard plane model are coded and integrated, including unifying the coding prefixes of the same components, and then hierarchically marking the module intervals to which the components belong and the sub-components within the module intervals to which the components belong.

[0022] Optionally, the formulation of the standard component grade code identification table includes:

[0023] The rendering level is marked with a number at the end of each component code to indicate the rendering order of different components.

[0024] Optionally, the splitting and reorganizing the plurality of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram, and the standard component grade code identification table to generate a plurality of reorganized plane models includes:

[0025] The plurality of plane model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram, and the split modules or components are reorganized and the driver file is embedded;

[0026] The reorganized component level codes are identified by calling the standard component level code identification table to obtain the rendering levels of the reorganized modules or components, thereby rendering all the reorganized plane models.

[0027] In addition, to achieve the above-mentioned purpose, an embodiment of the present application further provides a plane model processing system, the system comprising:

[0028] A drawing module, configured to draw multiple sets of plane model texture constraint maps and determine texture replacement ranges between components in the multiple sets of plane model texture constraint maps;

[0029] Production module, used to produce a set of standard plane models and export corresponding driver files;

[0030] A combing module is used to comb the composition logic of the standard plane model and formulate a component hierarchical structure diagram and a standard component grade code identification table;

[0031] A reorganization module is used to split and reorganize the multiple sets of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram and the standard component grade code identification table, generate multiple reorganized plane models, and drive the reorganized plane models with the driving file.

[0032] To achieve the above-mentioned purpose, an embodiment of the present application also provides an electronic device, which includes: a memory, a processor, and a plane model processing program stored in the memory and runnable on the processor, and when the plane model processing program is executed by the processor, it implements the plane model processing method as described above.

[0033] To achieve the above objectives, an embodiment of the present application further provides a computer-readable storage medium, on which a plane model processing program is stored. When the plane model processing program is executed by a processor, the plane model processing method as described above is implemented.

[0034] The plane model processing method, system, electronic device and computer-readable storage medium proposed in the embodiments of the present application provide a method for high-freedom combination, module replacement, and efficient large-scale derivation of plane models. It can split and reorganize multiple sets of plane model texture constraint maps according to the sorted composition logic, component hierarchical structure diagram and standard component level coding identification table to obtain multiple plane models, greatly reducing the dynamic production cost of plane models, shortening the model production cycle, and improving the editability and rendering freedom of plane model images. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 An application environment architecture diagram for implementing various embodiments of the present application;

[0036] Figure 2 This is a flow chart of a plane model processing method proposed in the first embodiment of the present application;

[0037] Figure 3 for Figure 2 Detailed flow chart of step S204;

[0038] Figure 4 A schematic diagram of the logic of constructing a standard 2D model in this application;

[0039] Figure 5 A schematic diagram of a component hierarchical structure diagram in this application;

[0040] Figure 6 A schematic diagram of another component hierarchical structure diagram in this application;

[0041] Figure 7 This is a schematic diagram of a standard component grade ID identification table in this application;

[0042] Figure 8 A schematic diagram of a model reorganization in this application;

[0043] Figure 9 This is a flow chart of a plane model processing method proposed in the second embodiment of the present application;

[0044] Figure 10 A schematic diagram of the hardware architecture of an electronic device proposed in the third embodiment of the present application;

[0045] Figure 11 This is a module diagram of a plane model processing system proposed in the fourth embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this application more clear, the present application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0047] It should be noted that the descriptions of "first", "second", etc. in the embodiments of the present application are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0048] See also Figure 1 , Figure 1This is a diagram of an application environment architecture for implementing various embodiments of the present application. The present application can be applied to an application environment including, but not limited to, a client 2, a server 4, and a network 6.

[0049] The client 2 is used to upload model materials, display model rendering results to users, and receive user operations such as modification and replacement of parts in the model. The client 2 can be a terminal device such as a PC (Personal Computer), mobile phone, tablet computer, portable computer, wearable device, etc.

[0050] The server 4 is used to provide data and technical support to the client 2. For example, it can draw multiple sets of 2D model texture constraint maps, create 2D models with unified animation standards, and export dynamic driver files and expression driver files; organize the 2D model construction logic, develop a hierarchical structure diagram of 2D model components, and develop a standard component level ID identification table; and split and reassemble the multiple sets of 2D model image constraint maps to generate multiple reassembled 2D models. The server 4 can be a computing device such as a rack server, blade server, tower server, or cabinet server. It can be a standalone server or a server cluster consisting of multiple servers.

[0051] The network 6 can be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth, or Wi-Fi. The server 4 and one or more clients 2 are connected to each other via the network 6 for data transmission and interaction.

[0052] Example 1

[0053] like Figure 2 FIG. 1 is a flow chart of a planar model processing method according to the first embodiment of the present application. It should be understood that the flow chart in this method embodiment is not intended to limit the order in which the steps are executed. Some steps in the flow chart may be added or deleted as needed. The method will be described below using the server 4 as the execution subject.

[0054] The method comprises the following steps:

[0055] S200, drawing multiple sets of 2D model texture constraint graphs and determining the texture replacement range between components.

[0056] Due to the limitations of their texture cutting properties, 2D dynamic models cannot be reused on a large scale, similar to the dynamic reuse of 3D models through rigging and weight adjustment. In this embodiment, this problem can be solved by overlaying multiple 2D dynamic models, unifying the texture constraint ranges and animation standards between them.

[0057] First, draw several sets of 2D models, and by superimposing them, summarize the commonalities of the image contours of each component to form multiple sets of 2D model texture constraint maps. In this way, a set of texture constraint map templates can be widely used in the modeling and animation production of several sets of 2D models. For example, M sets of 2D models are drawn in advance, and each set of models includes multiple components such as head, body, hands, legs, tops, pants, shoes, etc. For the top component, the geometric shapes of several top contours are relatively similar, and can be summarized into a geometric contour. The model containing this geometric contour can be applied to multiple top components. For example, a long-sleeved T-shirt and a short-sleeved T-shirt have similar contours, and only the sleeve length is different. Then the long-sleeved T-shirt and the short-sleeved T-shirt can share the model containing the geometric contour of the long-sleeved T-shirt. By summarizing in this way, N sets of 2D model texture constraint maps can be formed. Among them, M and N are positive integers and N <M。

[0058] Then, we developed texture drawing specifications for future models. This meant defining the scope of texture replacement between parts. For example, for a top part, if there was some overlap in texture between a short-sleeved T-shirt and a long-sleeved T-shirt with the same geometric outline (the short-sleeved T-shirt part), this could be replaced.

[0059] S202: Create a set of standard 2D models and export corresponding driver files.

[0060] Specifically, a set of 2D dynamic models with a unified animation standard is created, which can be applied to the multiple sets of 2D model texture constraint graphs, and a set of basic standard dynamic driver files and expression driver files are refined to uniformly drive all 2D models. In other words, the multiple sets of 2D model texture constraint graphs can be applied to the standard 2D model, and the dynamic driver files and expression driver files can be used to drive all 2D models generated according to the multiple sets of 2D model texture constraint graphs and the standard 2D model.

[0061] S204 , sorting out the composition logic of the standard 2D model, and formulating a component hierarchical structure diagram and a standard component level ID identification table.

[0062] Due to layer restrictions, traditional 2D dynamic models cannot switch between mutually occluding components at will, otherwise model penetration (model intersection) will occur, and components belonging to the same position cannot change levels. The level is similar to the Z-axis front-to-back spatial volume relationship of a 3D dynamic model. For example, a T-shirt is a top, but the styles are divided into tucked-in and untucked styles. Tops and pants have different front-to-back occlusion relationships. Traditional 2D models cannot meet both styles at the same time and can only create new textures for rendering. This embodiment can solve the above two problems by sorting out the 2D model composition logic, formulating a hierarchical structure diagram of 2D model components, and formulating a standard component level ID identification table.

[0063] For more details, see Figure 3 , is a detailed flowchart of step S204. It is understood that this flowchart is not intended to limit the order in which the steps are performed. As needed, some steps in the flowchart may be added or deleted. In this embodiment, step S204 specifically includes:

[0064] S2040: Disassemble each module in the standard 2D model and sort out the composition logic of the standard 2D model.

[0065] The composition logic includes the component composition structure, the front and back texture occlusion relationship, the category to which each component belongs, the range of mutually replaceable textures, etc.

[0066] In this embodiment, the composition logic of the standard 2D model can be sorted out according to the currently commonly used 2D model disassembly and component composition methods. Figure 4 As shown in FIG, it is a schematic diagram of the logic of the standard 2D model. Figure 4 In the 2D model, the standard 2D model is broken down into many modules, including the body (including face, left and right hands, left and right legs, etc.), clothes, hair, headwear, facing, trousers, shoes, etc. A module is a layer and may include multiple components. Figure 4 From left to right in the figure are the frontmost module to the backmost module of the standard 2D model, and the front (left) module can block the back (right) module.

[0067] S2042: Develop a component hierarchical structure diagram based on the sorted composition logic.

[0068] Integrate the components required in each module in the model into IDs. The same component ID prefix is ​​unified, such as A_. The secondary ID can mark the module interval (position) to which the component belongs. For example, when the component belongs to the left side of the model, it is marked A_L_. The tertiary ID can mark the sub-component of the module interval to which the component belongs, such as A_L_1, and so on.

[0069] like Figure 5 The figure shows a schematic diagram of the hierarchical structure of the components. Figure 5 In the model, taking the hands module as an example, the component ID prefix is ​​unified as hands. When there are multiple parts for the hands, they are distinguished as hands_A, hands_B, etc., and then each part is marked as L or R according to whether it belongs to the left hand or the right hand. Each part is further distinguished according to which part of the hand it belongs to, and finally marked as hands_A_L_TS, hands_A_L_TS_patch, etc.

[0070] like Figure 6 As shown in FIG, it is a schematic diagram of another component hierarchical structure diagram. Figure 6 In this example, let's take the model's top module as an example. Assuming the top module includes components such as sleeves and clothes, the component ID prefixes are sleeve, clothes, etc. Then, for components like sleeves, different postures are distinguished by annotations such as CX (hanging down), CY (arms on hips), and TS (hands raised). For components like clothes, letters A to Z are used to distinguish identical components in the same position with different front-to-back occlusion relationships, for example, A for a turtleneck windbreaker, B for a polo shirt, and C for a round-neck T-shirt. Components are then distinguished by annotations such as LD (lower left), RD (lower right), LU (upper left), and RU (upper right).

[0071] In the component hierarchy diagram, the subordinate relationship of each part in the model is: model-module-component-texture, driver file, description file (see Figure 6 ), wherein the driving file includes a dynamic driving file and an expression driving file.

[0072] S2044: Develop a standard component grade ID identification table based on the component grade structure diagram.

[0073] In this embodiment, component IDs are digitally graded, with the rendering level indicated by a specific number at the end of the component ID, such as A_L_1_1020. This allows the model rendering process to understand the rendering order of different components, allowing for overlapping rendering of modules. In other words, by identifying the number at the end of the component ID, the component is automatically mapped to the corresponding model level during rendering. The higher the level, the higher the rendering level.

[0074] like Figure 7 The figure shows a schematic diagram of the standard component grade ID identification table. Figure 7 In the figure, some component level IDs (numbers in the first column) are shown. In the subsequent rendering process, the rendering order of each component can be obtained by identifying the component level ID of each component.

[0075] In addition, when the module is rendered, multiple component resource packages will be included in the module, including but not limited to textures, dynamic driver files, expression driver files, and model description files.

[0076] Back to Figure 2 , S206, according to the composition logic, the component hierarchical structure diagram and the standard component level ID identification table, the multiple sets of 2D model texture constraint diagrams are split and reorganized to generate multiple reorganized 2D models, and the reorganized 2D models are driven by the driver file.

[0077] First, the multiple sets of 2D model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram. The split modules or components are then reassembled, and the dynamic driver file and expression driver file are embedded. Then, by retrieving and identifying the component level ID of the reassembled module, the overlapping rendering level of the reassembled 2D models of different modules or components is obtained, and all reassembled 2D models are rendered. Finally, all reassembled 2D models are uniformly driven according to the dynamic driver file and the expression driver file.

[0078] Since all the modules or components can be reassembled, the number of 2D models obtained after reassembly can be extremely large. In this embodiment, the number of reassembled 2D models can be randomly generated according to the number of models required by the user.

[0079] like Figure 8 The figure shows a schematic diagram of the matching of a model reorganization. Figure 8 In the figure, the two 2D models above are split and reorganized, that is, some modules or components are exchanged, and the following two 2D models can be obtained.

[0080] Traditional 2D models are typically created and rendered as a complete set. Changing texture styles requires rebuilding and animation for each new set. Furthermore, after a traditional 2D model is split, only the individual modules can be rendered as a whole. For example, if a module in a model requires parts A, B, and C, the components of the remaining modules cannot be added to the rendering between parts A, B, and C.

[0081] This embodiment, by summarizing the texture constraint graph drawn from the image contour, allows a set of templates to be widely applicable to multiple sets of 2D model building and animation production. Furthermore, the individual modules and components of the model can be split and then reassembled into several complete models of different shapes.

[0082] Furthermore, through the established component hierarchy diagram and component level ID identification table, component IDs can be re-read to achieve overlapping rendering between modules. For example, other module components, such as components @ and &, can be added between components A, B, and C to implement the logic of A+@+B+&+C.

[0083] Since each component has been digitally graded by ID, when reorganizing the model between interchangeable modules, calling the component ID for identification and rendering can avoid component texture conflicts, mold penetration, etc., and realize the free combination of multiple modules to obtain a variety of combined models.

[0084] Example 2

[0085] like Figure 9 FIG. 1 is a flowchart of a plane model processing method according to a second embodiment of the present application. In the second embodiment, the plane model processing method further includes step S308 based on the first embodiment described above. It should be understood that the flowchart in this method embodiment is not intended to limit the order in which the steps are executed. Some steps in the flowchart may be added or deleted as needed.

[0086] The method comprises the following steps:

[0087] S300: Draw multiple sets of 2D model texture constraint graphs and determine the texture replacement range between components.

[0088] First, we draw several sets of 2D models and, by overlaying them, summarize the commonalities of the image outlines of each component to form multiple sets of 2D model texture constraint maps. This allows a single texture constraint map template to be widely applicable to the modeling and animation of multiple sets of 2D models. Next, we develop texture drawing specifications for future newly added models, specifically defining the range of texture replacement between components.

[0089] S302: Create a set of standard 2D models and export corresponding driver files.

[0090] Specifically, a set of 2D dynamic models with a unified animation standard is created, which can be applied to the multiple sets of 2D model texture constraint graphs, and a set of basic standard dynamic driver files and expression driver files are refined to uniformly drive all 2D models. In other words, the multiple sets of 2D model texture constraint graphs can be applied to the standard 2D model, and the dynamic driver files and expression driver files can be used to drive all 2D models generated according to the multiple sets of 2D model texture constraint graphs and the standard 2D model.

[0091] S304 , sorting out the composition logic of the standard 2D model, and formulating a component hierarchical structure diagram and a standard component level ID identification table.

[0092] First, the modules of the standard 2D model are disassembled to clarify the model's construction logic. This construction logic includes component structure, the relationship between front and back texture occlusion, the categories of each component, and the range of interchangeable textures. In this embodiment, the standard 2D model's construction logic can be clarified using commonly used 2D model disassembly and component assembly methods.

[0093] Then, based on the structured logic, a component hierarchy diagram is developed. The components required for each module in the model are consolidated into IDs. Identical components have a unified ID prefix, such as A_. Secondary IDs can indicate the module to which the component belongs. For example, if the component belongs to the left side of the model, it is marked A_L_. Tertiary IDs can indicate the subcomponents within the module to which the component belongs, such as A_L_1, and so on.

[0094] A standard component level ID identification table is then developed based on the component hierarchy diagram. In this embodiment, component IDs are digitally graded, with the rendering level indicated by a specific number at the end of the component ID, such as A_L_1_1020. This allows the rendering order of different components to be understood during model rendering, allowing for overlapping rendering between modules. In other words, by identifying the number at the end of the component ID, components are automatically mapped to the corresponding model level during rendering. The higher the level, the higher the level of the rendered display.

[0095] In addition, when the module is rendered, multiple component resource packages will be included in the module, including but not limited to textures, dynamic driver files, expression driver files, and model description files.

[0096] S306, splitting and reorganizing the multiple sets of 2D model texture constraint maps according to the composition logic, the component hierarchical structure diagram and the standard component level ID identification table, generating multiple reorganized 2D models, and driving the reorganized 2D models with the driver file.

[0097] First, the multiple sets of 2D model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram. The split modules or components are then reassembled, and the dynamic driver file and expression driver file are embedded. Then, by retrieving and identifying the component level ID of the reassembled module, the overlapping rendering level of the reassembled 2D models of different modules or components is obtained, and all reassembled 2D models are rendered. Finally, all reassembled 2D models are uniformly driven according to the dynamic driver file and the expression driver file.

[0098] S308: Receive a user's texture modification requirement for the generated 2D model, and perform texture modification on corresponding components according to the requirement and the corresponding texture constraint map.

[0099] In this embodiment, because the 2D model texture constraint map is standardized, every component within the texture constraints can be freely modified. Upon receiving a user's texture modification request, the 2D model texture constraint map corresponding to the component to be modified is found. The texture of the component is modified within the constraints of the 2D model texture constraint map, and a new 2D model is rendered. It is worth noting that if texture modifications are performed outside the constraints of the 2D model texture constraint map, image information outside the constraints will be lost.

[0100] Therefore, the plane model processing method proposed in this embodiment can realize the free modification of each component within the texture constraint and perform model reuse, thereby improving the editability and rendering freedom of the 2D model image.

[0101] Example 3

[0102] like Figure 10 FIG3 is a schematic diagram of the hardware architecture of an electronic device 20 according to the third embodiment of the present application. In this embodiment, the electronic device 20 may include, but is not limited to, a memory 21, a processor 22, and a network interface 23 that can be interconnected via a system bus. It should be noted that Figure 10 Only the electronic device 20 having components 21 - 23 is shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead. In this embodiment, the electronic device 20 may be the server 4 .

[0103] The memory 21 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 21 can be an internal storage unit of the electronic device 20, such as the hard disk or memory of the electronic device 20. In other embodiments, the memory 21 can also be an external storage device of the electronic device 20, such as a plug-in hard disk equipped on the electronic device 20, a smart memory card (SMC), a secure digital (SD) card, a flash card, etc. Of course, the memory 21 can also include both the internal storage unit of the electronic device 20 and its external storage device. In this embodiment, the memory 21 is generally used to store the operating system and various application software installed on the electronic device 20, such as the program code of the plane model processing system 60. In addition, the memory 21 can also be used to temporarily store various types of data that have been output or are to be output.

[0104] In some embodiments, the processor 22 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 22 is generally used to control the overall operation of the electronic device 20. In this embodiment, the processor 22 is used to execute program code stored in the memory 21 or process data, such as executing the plane model processing system 60.

[0105] The network interface 23 may include a wireless network interface or a wired network interface. The network interface 23 is generally used to establish a communication connection between the electronic device 20 and other electronic devices.

[0106] Example 4

[0107] like Figure 11 FIG2 is a block diagram of a plane model processing system 60 according to a fourth embodiment of the present application. The plane model processing system 60 can be divided into one or more program modules, one or more of which are stored in a storage medium and executed by one or more processors to implement the embodiment of the present application. The program modules referred to in the embodiment of the present application refer to a series of computer program instruction segments that can perform specific functions. The following description will specifically introduce the functions of each program module in this embodiment.

[0108] In this embodiment, the plane model processing system 60 includes:

[0109] The drawing module 600 is used to draw multiple sets of 2D model texture constraint graphs and determine the texture replacement range between components.

[0110] First, we draw several sets of 2D models and, by overlaying them, summarize the commonalities of the image outlines of each component to form multiple sets of 2D model texture constraint maps. This allows a single texture constraint map template to be widely applicable to the modeling and animation of multiple sets of 2D models. Next, we develop texture drawing specifications for future newly added models, specifically defining the range of texture replacement between components.

[0111] The production module 602 is used to produce a set of standard 2D models and export corresponding driver files.

[0112] Specifically, a set of 2D dynamic models with a unified animation standard is created, which can be applied to the multiple sets of 2D model texture constraint graphs, and a set of basic standard dynamic driver files and expression driver files are refined to uniformly drive all 2D models. In other words, the multiple sets of 2D model texture constraint graphs can be applied to the standard 2D model, and the dynamic driver files and expression driver files can be used to drive all 2D models generated according to the multiple sets of 2D model texture constraint graphs and the standard 2D model.

[0113] The sorting and selecting module 604 is used to sort out the composition logic of the standard 2D model and formulate a component hierarchical structure diagram and a standard component level ID identification table.

[0114] First, the modules of the standard 2D model are disassembled to clarify the model's construction logic. This construction logic includes component structure, the relationship between front and back texture occlusion, the categories of each component, and the range of interchangeable textures. In this embodiment, the standard 2D model's construction logic can be clarified using commonly used 2D model disassembly and component assembly methods.

[0115] Then, based on the structured logic, a component hierarchy diagram is developed. The components required for each module in the model are consolidated into IDs. Identical components have a unified ID prefix, such as A_. Secondary IDs can indicate the module to which the component belongs. For example, if the component belongs to the left side of the model, it is marked A_L_. Tertiary IDs can indicate the sub-components within the module to which the component belongs, such as A_L_1, and so on.

[0116] A standard component level ID identification table is then developed based on the component hierarchy diagram. In this embodiment, component IDs are digitally graded, with the rendering level indicated by a specific number at the end of the component ID, such as A_L_1_1020. This allows the rendering order of different components to be understood during model rendering, allowing for overlapping rendering between modules. In other words, by identifying the number at the end of the component ID, components are automatically mapped to the corresponding model level during rendering. The higher the level, the higher the level of the rendered display.

[0117] In addition, when the module is rendered, multiple component resource packages will be included in the module, including but not limited to textures, dynamic driver files, expression driver files, and model description files.

[0118] The reorganization module 606 is used to split and reorganize the multiple sets of 2D model texture constraint maps according to the composition logic, the component hierarchical structure diagram and the standard component level ID identification table, generate multiple reorganized 2D models, and drive the reorganized 2D models with the driver file.

[0119] First, the multiple sets of 2D model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram. The split modules or components are then reassembled, and the dynamic driver file and expression driver file are embedded. Then, by retrieving and identifying the component level ID of the reassembled module, the overlapping rendering level of the reassembled 2D models of different modules or components is obtained, and all reassembled 2D models are rendered. Finally, all reassembled 2D models are uniformly driven according to the dynamic driver file and the expression driver file.

[0120] The plane model processing system proposed in this embodiment can provide a method of high-freedom combination, module replacement, and efficient large-scale derivation of plane models. It can split and reorganize multiple sets of plane model texture constraint maps according to the sorted composition logic, component hierarchical structure diagram and standard component level ID identification table to obtain multiple plane models, greatly reducing the dynamic production cost of plane models, shortening the model production cycle, and improving the editability and rendering freedom of plane model images.

[0121] Example 5

[0122] The present application also provides another embodiment, namely, providing a computer-readable storage medium, which stores a plane model processing program, and the plane model processing program can be executed by at least one processor to enable the at least one processor to perform the steps of the plane model processing method as described above.

[0123] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0124] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0125] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present application can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented using program code executable by the computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0126] The above are only preferred embodiments of the embodiments of the present application, and do not limit the patent scope of the embodiments of the present application. Any equivalent structure or equivalent process transformation made using the contents of the description and drawings of the embodiments of the present application, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the embodiments of the present application.

Claims

1. A plane model processing method, characterized in that: The method comprises: Drawing multiple sets of plane model texture constraint maps, and determining texture replacement ranges between components in the multiple sets of plane model texture constraint maps; Make a set of standard plane models and export the corresponding driver files; Sorting out the composition logic of the standard plane model, formulating a component hierarchical structure diagram and a standard component grade code identification table; Splitting and reorganizing the plurality of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram, and the standard component grade code identification table to generate a plurality of reorganized plane models, and driving the reorganized plane models with the driver file; The step of splitting and reorganizing the plurality of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram, and the standard component grade code identification table to generate a plurality of reorganized plane models includes: The plurality of plane model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram, and the split modules or components are reorganized and the driver file is embedded; The reorganized component level codes are identified by calling the standard component level code identification table to obtain the rendering levels of the reorganized modules or components, thereby rendering all the reorganized plane models.

2. The plane model processing method according to claim 1, characterized in that: The method further comprises: A user's texture modification requirement for the generated plane model is received, and according to the requirement, the texture modification of the corresponding component is performed within the constraint range of the corresponding texture constraint map.

3. The plane model processing method according to claim 1 or 2, characterized in that: Drawing multiple sets of plane model texture constraint graphs includes: Draw M sets of plane models, summarize the commonalities of the image contours of each component in the M sets of plane models by superposition, and form N sets of plane model texture constraint maps, where M and N are positive integers and N <M。 4. The plane model processing method according to any one of claims 1 to 2, characterized in that: The drive files include dynamic drive files and expression drive files.

5. The plane model processing method according to any one of claims 1 to 2, characterized in that: The process of sorting out the composition logic of the standard plane model and formulating a component hierarchical structure diagram and a standard component grade code identification table includes: Disassemble each module in the standard plane model and sort out the composition logic of the standard plane model; Develop a component hierarchical structure diagram based on the structured logic; A standard component grade coding identification table is formulated based on the component grade structure diagram.

6. The plane model processing method according to claim 5, characterized in that: The composition logic of combing the standard plane model includes combing the component composition structure, the front and back texture occlusion relationship, the category to which each component belongs, and the range of mutually replaceable textures.

7. The plane model processing method according to claim 6, characterized in that: The component hierarchical structure diagram is formulated as follows: The components required in each module of the standard plane model are coded and integrated, including unifying the coding prefixes of the same components, and then hierarchically marking the module intervals to which the components belong and the sub-components within the module intervals to which the components belong.

8. The plane model processing method according to claim 7, characterized in that: The formulated standard component grade code identification table includes: The rendering level is marked with a number at the end of each component code to indicate the rendering order of different components.

9. A plane model processing system, characterized in that: The system comprises: A drawing module, configured to draw multiple sets of plane model texture constraint maps and determine texture replacement ranges between components in the multiple sets of plane model texture constraint maps; Production module, used to produce a set of standard plane models and export corresponding driver files; A combing module is used to comb the composition logic of the standard plane model and formulate a component hierarchical structure diagram and a standard component grade code identification table; a reorganization module, configured to split and reorganize the plurality of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram, and the standard component grade code identification table, generate a plurality of reorganized plane models, and drive the reorganized plane models using the driver file; The step of splitting and reorganizing the plurality of plane model texture constraint maps according to the composition logic, the component hierarchical structure diagram, and the standard component grade code identification table to generate a plurality of reorganized plane models includes: The plurality of plane model texture constraint graphs are shuffled and split according to the composition logic and the component hierarchical structure diagram, and the split modules or components are reorganized and the driver file is embedded; The reorganized component level codes are identified by calling the standard component level code identification table to obtain the rendering levels of the reorganized modules or components, thereby rendering all the reorganized plane models.

10. An electronic device, characterized in that: The electronic device includes: a memory, a processor, and a plane model processing program stored in the memory and executable on the processor. When the plane model processing program is executed by the processor, the plane model processing method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a plane model processing program, which implements the plane model processing method according to any one of claims 1 to 8 when executed by a processor.

Images