This disclosure relates to computer-generated imagery (CGI) and computer-aided animation. More specifically, this disclosure relates to an interactive multi-mesh modeling system and associated techniques for use in CGI and computer-aided animation.
With the wide-spread availability of computers, computer graphics artists and animators can rely upon computers to assist in production process for creating animations and computer-generated imagery (CGI). This may include using computers to have physical models be represented by virtual models in computer memory. Typically, two-dimensional (2D) or three-dimensional (3D) computer-aided animation combines 2D/3D models of objects and programmed movement of one or more of the models. In 3D computer animation, the first step is typically the object modeling process. Objects can be sculpted much like real clay or plaster, working from general forms to specific details, for example, with various sculpting tools. Models may then be constructed, for example, out of geometrical vertices, faces, and edges in a 3D coordinate system to represent the objects. These virtual models can then be manipulated using computers to, for example, simulate physics, design aesthetic actions such as poses or other deformations, crate lighting, coloring and paint, or the like, of characters or other elements of a computer animation display.
Pixar is one of the pioneering companies in the computer-generated imagery (CGI) and computer-aided animation industry. Pixar is more widely known as Pixar Animation Studios, the creators of animated features such as “Toy Story” (1995) and “Toy Story 2” (1999), “A Bugs Life” (1998), “Monsters, Inc.” (2001), “Finding Nemo” (2003), “The Incredibles” (2004), “Cars” (2006), “Ratatouille” (2007), and others. In addition to creating animated features, Pixar develops computing platforms and tools specially designed for computer-aided animation and CGI. One such example is now known as PhotoRealistic RenderMan, or PRMan for short. PRMan is a photorealistic RenderMan-compliant rendering software system based on the RenderMan Interface Specification (RISpec) which is Pixar's technical specification for a standard communications protocol (or interface) between 3D computer graphics programs and rendering programs. PRMan is produced by Pixar and used to render their in-house 3D animated movie productions. It is also available as a commercial product licensed to third parties, sold as part of a bundle called RenderMan Pro Server, a RenderMan-compliant rendering software system developed by Pixar based on their own interface specification. Other examples include tools and plug-ins for programs such as the AUTODESK MAYA high-end 3D computer graphics software package from AutoDesk, Inc. of San Rafael, Calif.
One core functional aspect of PRMan can include the use of a “rendering engine” to convert geometric and/or mathematical descriptions of objects into images. This process is known in the industry as “rendering.” For movies, other animated features, shorts, and special effects, a user (e.g., a skilled computer graphics artist) can specify the geometric or mathematical description of objects to be used in the rendered image or animation sequence, such as characters, props, background, or the like. In some instances, the geometric description of the objects may include a number of animation control variables (avars) and values for the avars. An animator may also pose the objects within the image or sequence and specify motions and positions of the objects over time to create an animation.
As such, the production of CGI and computer-aided animation may involve the extensive use of various computer graphics techniques to produce a visually appealing image from the geometric description of an object that may be used to convey an essential element of a story or provide a desired special effect. One of the challenges in creating these visually appealing images is the can be the balancing of a desire for a highly-detailed image of a character or other object with the practical issues involved in allocating the resources (both human and computational) required to produce those visually appealing images.
Therefore, one issue with the production process is the time and effort involved when a user undertakes to model the geometric description of an object. One practice in computer animation can be to use multiple versions of the same geometric model according to a specific task. One might, for example, create and render a model for final display, but prefer to use a somewhat simplified model for other purposes, such as creating animation or performing simulation. However, it may take several hours to several days for a user to design, create, rig, pose, paint, or otherwise prepare a model that can be used to produce the visually desired look for one task. This involvement in time and effort can limit that ability of the user to create enough variants of the model for use in different stages of the production process or in a single scene to covey particular element of the story or to provide the desired visual effect. Additionally, artistic control over the look of a model or its visual effect when placed in a scene may also be lost by some attempts at reducing the time and effect in preparing a model that rely too much on automated procedural creation of models.
Accordingly, what is desired is to solve one or more of the problems relating to creating objects for use in CGI and computer-aided animation, some of which may be discussed herein. Additionally, what is desired is to reduce some of the drawbacks relating to creating objects for use in CGI and computer-aided animation, some of which may be discussed herein.
This disclosure relates to computer-generated imagery (CGI) and computer-aided animation. More specifically, this disclosure relates to an interactive multi-mesh modeling system and associated techniques for use in CGI and computer-aided animation.
In various embodiments, an interactive multi-mesh modeling system may allow users to employ a variety of modeling techniques (e.g., solid modeling or shell/boundary modeling) to interactively create one or more computer-generated representations of objects (e.g., animated characters, static props, and objects whose motions are determined by computer simulations) for a variety of different tasks or tools associated with phases of modeling, layout and animation, and rendering. Some of these different tasks or tools can have requirements for the computer-generated representations of objects on which they operate. These requirements may differ from how some computer-generated representations were originally created (e.g., 3D solid objects output using solid modeling techniques vs. 2D flat “panel constructed” objects required for some computer simulations). Thus, the interactive multi-mesh modeling system may further employ a variety of techniques for taking a source computer-generated representation of an object and providing the automatic creation, management, and maintenance of instances or versions of the source, and any information defined thereon or associated therewith, that are suitable for several different tasks.
Accordingly, in one aspect, an interactive multi-mesh modeling system may automatically create and/or maintain one or more computer-generated representations of an object designated for each of a plurality of different tasks based on a source computer-generated representation of the object which may not be suitable to the requirements of some of the tasks. In another aspect, in maintaining each of the one or more computer-generated representations of the object designated for each of the plurality of different tasks, the interactive multi-mesh modeling system may automatically create and maintain correspondences between the source computer-generated representation of the object and any of the computer-generated representations of the object designated for the different tasks such that information defined on or otherwise associated with the source computer-generated representation of the object can be shared with or transferred to any of the other computer-generated representations of the object, and vice versa. In a further aspect, in maintaining each of the one or more computer-generated representations of the object designated for each of the plurality of different tasks, the interactive multi-mesh modeling system may automatically create and maintain correspondences between versions or iterations of computer-generated representations of the object that may be generated for the same task such that information defined on or otherwise associated with one computer-generated representation of the object used for the task can be shared with or transferred to any other computer-generated representation of the object for the same task, and vice versa. In a still further aspect, in maintaining each of the one or more computer-generated representations of the object designated for each of the plurality of different tasks, the interactive multi-mesh modeling system may automatically create and maintain correspondences between one of the computer-generated representations of the object designated for a first task and another computer-generated representations of the object designated for a second task such that information defined on or otherwise associated with one computer-generated representation of the object for one task can be shared with or transferred to another computer-generated representation of the object for another different task, and vice versa.
In one embodiment, a method for facilitating creation of computer graphics can include receiving a first mesh. A mesh generation specification may also be received for each task in a plurality of different tasks. A mesh generation specification corresponding to a particular task in the plurality of different tasks can define criteria, instructions, requirements, or the like, of meshes for the particular task. One or more meshes can be automatically created or generated for each task in the plurality of different tasks based on the first mesh and the mesh generation specifications for the task. A first correspondence between the first mesh and each one of the automatically generated meshes can be automatically generated specifying transfer of information between the first mesh and each automatically generated mesh. A second correspondence between a first one of the automatically generated meshes suitable for a first task in the plurality of different tasks and a second one of the automatically generated meshes suitable for a second task in the plurality of different tasks can also be automatically generated. The second correspondence can specify the transfer of information between the first automatically generated mesh of the first task and the second automatically generated mesh of the second task.
In further embodiments, generating the one or more meshes automatically for each task in the plurality of different tasks can include generating at least one mesh to have a geometrically regular structure different than the first mesh and a first resolution that is greater than a second resolution associated with the first mesh. In another aspect, generating the one or more meshes automatically for each task in the plurality of different tasks can include generating at least one mesh suitable for a rendering task in the plurality of different tasks and at least one mesh suitable for at least one of a simulation task and animation task in the plurality of different tasks. In a further aspect, generating the one or more meshes automatically for each task in the plurality of different tasks can include generating at least one mesh for a first task in the plurality of different tasks based on removal information identifying one or more features of the first mesh that are not suitable for meshes on which the first task operates.
In various embodiments, information may be automatically transferred between the first mesh and at least one of the automatically generated meshes based on the first correspondence between the first mesh and each one of the automatically generated meshes. The information may include any data defined on or otherwise associated with the input meshes and/or task data defined on or otherwise associated with any of the automatically generated meshes. In one aspect, information may be automatically transferred between the first automatically generated mesh of the first task and the second automatically generated mesh of the second task based on the second correspondence between the first automatically generated mesh of the first task and the second automatically generated mesh of the second task.
In further embodiments, one or more of the automatically generated meshes may be automatically regenerated based on a modification to the first mesh or a modification to the mesh generation specification corresponding to at least one task in the plurality of different tasks defining the criteria for the one or more of the automatically generated meshes on which the at least one task operates. A third correspondence between each automatically regenerated mesh and the one or more of the automatically generated meshes may be automatically generated specifying transfer of information between each automatically regenerated mesh and the one or more of the automatically generated meshes. Information may be automatically transferred between each automatically regenerated mesh and the one or more of the automatically generated meshes.
In some embodiments, generating either the first correspondence or the second correspondence may include generating a correspondence between a plurality of manifolds based on a disambiguation using a combination of different metrics defined on each of the plurality of manifolds and an embedding space. In another aspect, generating either the first correspondence or the second correspondence may include generating a spatial correspondence specifying transfer of animation or simulation data between meshes. In yet another aspect, generating either the first correspondence or the second correspondence may include generating a spatial correspondence specifying transfer of lighting or shader data between meshes.
In one embodiment, a non-transitory computer-readable medium stores computer-executable code for creating computer graphics. The computer-readable medium can include code for generating a first correspondence between a first mesh and each one of one or more meshes designated for each task in a plurality of different tasks, the first correspondence between the first mesh and each one of one or more meshes designated for each task in the plurality of different tasks specifying transfer of information between the first mesh and each mesh, and code for generating a second correspondence between a second mesh being one of the one or more meshes designated for each task in the plurality of different tasks and a third mesh one of the one or more meshes designated for each task in the plurality of different tasks, the second correspondence between the second mesh and the third mesh specifying transfer of information between the second mesh and the third mesh.
In another embodiment, an interactive multi-mesh modeling system may include one or more computer systems, each having at least one processor and a memory in communication with the processor and configured to store a set of instructions which when executed by the processor cause the processor to generate a user interface having first functionality that enables a user to interact with a first task in a plurality of different tasks to model an object to create a first mesh associated with the object, second functionality that enables the user to interact a second task in the plurality of different tasks to animate or simulate motion of a second mesh associated with the object modeled via the first tasks, and third functionality that enables the user to interact with a third task in the plurality of different tasks to render a third mesh associated with the object modeled via the first task and any associated motion of the second mesh animated or simulated via the second task, maintain a plurality of correspondences specifying transfer of information between meshes, at least one correspondence in the plurality of correspondences being between the first mesh associated with the object and each of the second mesh and the third mesh, and at least one correspondence in the plurality of correspondences being between the second mesh and the third mesh, transfer information defined on or otherwise associated with the first mesh to at least one of the second mesh and the third mesh based on the at least one correspondence in the plurality of correspondences being between the first mesh associated with the object and each of the second mesh and the third mesh, and transfer information defined on or otherwise associated with at least one of the second mesh and the third mesh to the other based on the at least one correspondence in the plurality of correspondences being between the second mesh and the third mesh.
A further understanding of the nature of and equivalents to the subject matter of this disclosure (as wells as any inherent or express advantages and improvements provided) should be realized by reference to the remaining portions of this disclosure, any accompanying drawings, and the claims in addition to the above section.
In order to reasonably describe and illustrate those innovations, embodiments, and/or examples found within this disclosure, reference may be made to one or more accompanying drawings. The additional details or examples used to describe the one or more accompanying drawings should not be considered as limitations to the scope of any of the claimed inventions, any of the presently described embodiments and/or examples, or the presently understood best mode of any innovations presented within this disclosure.
This disclosure relates to computer-generated imagery (CGI) and computer-aided animation. More specifically, this disclosure relates to an interactive multi-mesh modeling system and associated techniques for use in CGI and computer-aided animation.
In various embodiments, an interactive multi-mesh modeling system may allow users to employ a variety of modeling techniques (e.g., solid modeling or shell/boundary modeling) to interactively create one or more computer-generated representations of objects (e.g., animated characters, static props, and objects whose motions are determined by computer simulations) for a variety of different tasks or tools associated with phases of modeling, layout and animation, and rendering. Some of these different tasks or tools can have requirements for the computer-generated representations of objects on which they operate. These requirements may differ from how some computer-generated representations were originally created (e.g., 3D solid objects output using solid modeling techniques vs. 2D flat “panel constructed” objects required for some computer simulations). Thus, the interactive multi-mesh modeling system may further employ a variety of techniques for taking a source computer-generated representation of an object and providing the automatic creation, management, and maintenance of instances or versions of the source, and any information defined thereon or associated therewith, that are suitable for several different tasks.
Introduction
The one or more design computers 110 can include hardware and software elements configured for designing one or more computer-generated objects used in CGI and assisting with computer-aided animation. Each of the one or more design computers 110 may be embodied as a single computing device or a set of one or more computing devices. Some examples of computing devices are PCs, laptops, workstations, mainframes, cluster computing system, grid computing systems, cloud computing systems, embedded devices, computer graphics devices, gaming devices and consoles, consumer electronic devices having programmable processors, or the like. The one or more design computers 110 may be used at various stages of a production process (e.g., pre-production, designing, creating, editing, simulating, animating, rendering, post-production, etc.) to produce models of objects, computer-generated scenes, images, image sequences, animations, motion pictures, video, audio, or associated effects related to CGI and animation by employing one or more of object libraries 120 and/or systems 130-170 via various tools or interfaces.
The one or more object libraries 120 can include hardware and/or software elements configured for storing and accessing information related to one or more computer-generated objects. The information may be accessed by the one or more design computers 110 and/or systems 130-170 during various stages of a production process to produce CGI and animation. Some examples of the one or more object libraries 120 can include one or more file, one or more databases, or other storage devices and mechanisms. The one or more object libraries 120 may be locally accessible to the one or more design computers 110 and/or system 130-170 or hosted by one or more computer systems or storage devices externally accessible to the one or more design computers 110 and/or system 130-170.
Some examples of information stored in the one or more object libraries 120 can include information representing an object itself, metadata, object geometry, object topology, rigging, control data, animation data, animation cues, simulation data, texture data, lighting data, shader code, or the like. An object stored in the one or more object libraries 120 can include any entity that has an n-dimensional (e.g., 1D, 2D, or 3D) surface geometry. The shape of an object can include a set of points or locations in space (e.g., object space) that make up the object's surface. Topology of an object can include the connectivity of the surface of the object (e.g., the genus or number of holes in an object) or the vertex/edge/face connectivity of an object.
The one or more object modeling systems 130 can include hardware and/or software elements configured for modeling one or more computer-generated objects. The one or more object modeling systems 130 can be embodied as the one or more design computers 110 and/or software programs hosted by one or more computer systems. The one or more object modeling systems 130 may be invoked by or used directly by a user of the one or more design computers 110 and/or automatically invoked by or used by one or more processes associated with the one or more design computers 110. Some examples of software programs embodied as the one or more object modeling systems 130 can include commercially available high-end 3D computer graphics and 3D modeling software packages, such as 3D STUDIO MAX and AUTODESK MAYA produced by Autodesk, Inc. of San Rafael, Calif.
Modeling can include the creating, sculpting, and editing of an object. In various embodiments, the one or more object modeling systems 130 may be configured to generated a model to include a description of the shape of an object. The one or more object modeling systems 130 can be configured to facilitate the creation and/or editing of features, such as non-uniform rational B-splines or NURBS, polygons and subdivision surfaces (or SubDivs), that may be used to describe the shape of an object. In general, polygons are a widely used model medium due to their relative stability and functionality. Polygons can also act as the bridge between NURBS and SubDivs. NURBS are used mainly for their ready-smooth appearance and generally respond well to deformations. SubDivs are a combination of both NURBS and polygons representing a smooth surface via the specification of a coarser piecewise linear polygon mesh. A single object may have several different models that describe its shape.
The one or more object modeling systems 130 may further generate model data (e.g., 2D and 3D model data) for use by other elements of system 100 or that can be stored in the one or more object libraries 120. The one or more object modeling systems 130 may be configured to allow a user to associate additional information, metadata, color, lighting, rigging, controls, or the like, with all or a portion of the generated model data.
The one or more object articulation systems 140 can include hardware and/or software elements configured to articulating one or more computer-generated objects. The one or more object articulation systems 140 can be embodied as the one or more design computers 110 and/or software programs hosted by one or more computer systems. The one or more object articulation systems 140 may be invoked by or used directly by a user of the one or more design computers 110 and/or automatically invoked by or used by one or more processes associated with the one or more design computers 110. Some examples of software programs embodied as the one or more object articulation systems 140 can include commercially available high-end 3D computer graphics and 3D modeling software packages, such as 3D STUDIO MAX and AUTODESK MAYA produced by Autodesk, Inc. of San Rafael, Calif.
Articulation can include the building or creation of rigs, the rigging of an object, and the editing of rigging. In various embodiments, the one or more articulation systems 140 be configured to enable the specification of rigging for an object, such as for internal skeletal structures or eternal features, and to define how input motion deforms the object. One technique is called “skeletal animation,” in which a character can be represented in at least two parts: a surface representation used to draw the character (called the skin) and a hierarchical set of bones used for animation (called the skeleton). Another technique involves the use of deformers in which a surface representation used to draw the character is deformed in response to one or more control structures that enclose the surface representation and whose manipulations drive the deformers.
The one or more object articulation systems 140 may further generate articulation data (e.g., data associated with controls or animations variables) for use by other elements of system 100 or that can be stored in the one or more object libraries 120. The one or more object articulation systems 140 may be configured to allow a user to associate additional information, metadata, color, lighting, rigging, controls, or the like, with all or a portion of the generated articulation data.
The one or more object animation systems 150 can include hardware and/or software elements configured for animating one or more computer-generated objects. The one or more object animation systems 150 can be embodied as the one or more design computers 110 and/or as software programs hosted by one or more computer systems. The one or more object animation systems 150 may be invoked by or used directly by a user of the one or more design computers 110 and/or automatically invoked by or used by one or more processes associated with the one or more design computers 110. Some examples of software programs embodied as the one or more object animation systems 150 can include commercially available high-end 3D computer graphics and 3D modeling software packages, such as 3D STUDIO MAX and AUTODESK MAYA produced by Autodesk, Inc. of San Rafael, Calif.
Animation can include the specification of motion and position of an object over time. In various embodiments, the one or more animation systems 150 may be configured to enable users to manipulate controls or animation variables or utilized character rigging to specify poses of object for one or more key frames of an animation sequence. The one or more animation systems 150 generate intermediary frames based on the one or more key frames. In some embodiments, the one or more animation systems 150 may be configured to enable users to specify animation cues, paths, or the like according to one or more predefined sequences. The one or more animation systems 150 generate frames of the animation based on the animation cues or paths. In further embodiments, the one or more animation systems 150 may be configured to enable users to define animations using one or more animation languages, morphs, deformations, or the like.
The one or more object animations systems 150 may further generate animation data (e.g., inputs associated with controls or animations variables) for use by other elements of system 100 or that can be stored in the one or more object libraries 120. The one or more object animations systems 150 may be configured to allow a user to associate additional information, metadata, color, lighting, rigging, controls, or the like, with all or a portion of the generated animation data.
The one or more object simulation systems 160 can include hardware and/or software elements configured for simulating one or more computer-generated objects. The one or more object simulation systems 160 can be embodied as the one or more design computers 110 and/or as software programs hosted by one or more computer systems. The one or more object simulation systems 160 may be invoked by or used directly by a user of the one or more design computers 110 and/or automatically invoked by or used by one or more processes associated with the one or more design computers 110. Some examples of software programs embodied as the one or more object simulation systems 160 can include physically-based numerical engines and commercially available high-end 3D computer graphics and 3D modeling software packages, such as 3D STUDIO MAX and AUTODESK MAYA produced by Autodesk, Inc. of San Rafael, Calif.
Simulation can include determining behavior, such as motion/position/collisions, of an object in response to one or more simulated forces, conditions, or other objects. In various embodiments, the one or more object simulation systems 160 may be configured to enable users to create, define, edit, or configure simulation engines, such as a physics engine or physics processing unit (PPU/GPGPU) using one or more physically-based numerical techniques. In general, a physics engine can include a computer program that simulates one or more physics models (e.g., a Newtonian physics model), using variables such as mass, velocity, friction, wind resistance, or the like. The physics engine may simulate and predict effects under different conditions that would approximate what happens to an object according to the physics model. The one or more object simulation systems 160 may be used to simulate the behavior of objects, such as hair, fur, and cloth, in response to a physics model and/or animation of one or more characters and objects within a computer-generated scene.
The one or more object simulation systems 160 may further generate simulation data (e.g., motion and position of an object over time) for use by other elements of system 100 or that can be stored in the one or more object libraries 120. The generated simulation data may be combined with or used in addition to data generated by the systems 130-150. The one or more object simulation systems 160 may be configured to allow a user to associate additional information, metadata, color, lighting, rigging, controls, or the like, with all or a portion of the generated simulation data.
The one or more object rendering systems 170 can include hardware and/or software element configured for “rendering” or generating one or more images of one or more computer-generated objects. The one or more object rendering systems 170 can be embodied as the one or more design computers 110 and/or software programs hosted by one or more computer systems. The one or more object rendering systems 170 may be invoked by or used directly by a user of the one or more design computers 110 and/or automatically invoked by or used by one or more processes associated with the one or more design computers 110. One example of a software program embodied as the one or more object rendering systems 170 can include PhotoRealistic RenderMan, or PRMan, produced by Pixar Animations Studios of Emeryville, Calif.
“Rendering” can include generating an image from a model based on information such as geometry, viewpoint, texture, lighting, and shading information. In various embodiments, the one or more object rendering systems 170 can be configured to render one or more objects to produce one or more computer-generated images or a set of images over time that provide an animation. The one or more object rendering systems 170 may generate digital images or raster graphics images.
In various embodiments, a rendered image can be understood in terms of a number of visible features. Some examples of visible features that may be considered by the one or more object rendering systems 170 may include shading (e.g., techniques relating to how the color and brightness of a surface varies with lighting), texture-mapping (e.g., techniques relating to applying detail information to surfaces or objects using maps), bump-mapping (e.g., techniques relating to simulating small-scale bumpiness on surfaces), fogging/participating medium (e.g., techniques relating to how light dims when passing through non-clear atmosphere or air; shadows (e.g., techniques relating to effects of obstructing light), soft shadows (e.g., techniques relating to varying darkness caused by partially obscured light sources), reflection (e.g., techniques relating to mirror-like or highly glossy reflection), transparency or opacity (e.g., techniques relating to sharp transmissions of light through solid objects), translucency (e.g., techniques relating to highly scattered transmissions of light through solid objects), refraction (e.g., techniques relating to bending of light associated with transparency, diffraction (e.g., techniques relating to bending, spreading and interference of light passing by an object or aperture that disrupts the ray), indirect illumination (e.g., techniques relating to surfaces illuminated by light reflected off other surfaces, rather than directly from a light source, also known as global illumination), caustics (e.g., a form of indirect illumination with techniques relating to reflections of light off a shiny object, or focusing of light through a transparent object, to produce bright highlights on another object), depth of field (e.g., techniques relating to how objects appear blurry or out of focus when too far in front of or behind the object in focus), motion blur (e.g., techniques relating to how objects appear blurry due to high-speed motion, or the motion of the camera), non-photorealistic rendering (e.g., techniques relating to rendering of scenes in an artistic style, intended to look like a painting or drawing), or the like.
The one or more object rendering systems 170 may further render images (e.g., motion and position of an object over time) for use by other elements of system 100 or that can be stored in the one or more object libraries 120. The one or more object rendering systems 170 may be configured to allow a user to associate additional information or metadata with all or a portion of the rendered image. The one or more object rendering systems 170 may output information that can be encoded in various image and video formats, such as those related to JPG, PNG, MPG, MOV, H.264, or the like.
Interactive Multi-Mesh Modeling System
In various embodiments, system 100 may include one or more hardware elements and/or software elements, components, tools, or processes, embodied as the one or more design computers 110, object library 120, the one or more object modeler systems 130, the one or more object articulation systems 140, the one or more object animation systems 150, the one or more object simulation systems 160, and/or the one or more object rendering systems 170 that provide one or more tools for an interactive multi-mesh modeling system. In some aspects, a 3D model may be the sole authored data from which system 100 automatically creates and maintains other versions or representation of the 3D model suitable for a variety of specific tasks or task related tools, such as animation, simulation, and rendering. In further aspects, system 100 may automatically create and maintain correspondences (e.g., correspondence functions) between the 3D model and these other versions or representation of the 3D model facilitating the uni-directional or bi-directional transfer of information between meshes. In still further aspects, system 100 may automatically create and maintain correspondences between some of these other versions or representation of the 3D model facilitating the uni-directional or bi-directional transfer of information between meshes used for the same tasks and/or the transfer of information between meshes used in different tasks.
In various embodiments, input mesh 210 may be associated with any model. Input mesh 210 may have any predetermined geometry, topology, complexity, resolution, or the like. Input mesh 210 further may be represented by any structures typically used to create computer-generated objects. Input mesh 210 may be associated with a model created using one or more 2D sketches that are swept along a path to become 3D. These may be cuts or extrusions for example. In another example, input mesh 210 may be associated with a model have one or more surfaces defined, trimmed, merged, or filled to make a solid object. In another example, input mesh 210 may include sufficient resolution to maintain a desired shape. In a further example, input mesh 210 may be associated with data, such as modeling, animation, simulation, or rendering data. Such data may be defined on input mesh 210 or otherwise associated with input mesh 210.
At its current resolution or level of detail, model 300 may be use for display purposes or for rendering plausible images and animations. However, model 300 may not be directly suitable for other computer-generated graphics phases and tasks, such as simulation or photorealistic rendering. Traditionally, a modeler may have to manually create and maintain multiple versions of model 300 that may be used according to one or more different tasks. This can lead to several problems. For example, one problem with utilizing multiple versions of the same geometric model for different tasks is that during the design and authoring phase (i.e. when the model is initially being created and modified), it is unwieldy to force a modeler to build and maintain both a full model and the additional models needed to different tasks at the same time. This essentially compounds the amount of work required for every change to the full model that must be propagated to the different versions. In another example, garment models representing cloth traditionally have been modeling using flat panels that are stitched together. The skill set required to model cloth in this manner, however, may be different than the skill set of a typical 3D modeler or solid object modeler due to unfamiliarity with the requirements of computer simulations that rely on flat panel construction or varying user interfaces of different tool sets.
Accordingly, in various embodiments, interactive multi-mesh modeling system 200 may automatically create and maintain multiple instances or versions of input mesh 210 that may be used according to one or more different tasks. These automatically generated instances or versions may be completely independent of input mesh 210. Referring again to
For example, interactive multi-mesh modeling system 200 may provide one or more user interfaces and tools that enable a user having a background in solid modeling to create any number of solid models that represent cloth or other garment objects. From these, interactive multi-mesh modeling system 200 can automatically create and maintain variant meshes each adapted for and suitable to a different task/tool of tasks/tools 230. Some examples of the different tasks tools can include modeling tasks, layout and animation tasks, simulation tasks, and rendering tasks. Variation can also exist within a task/tool, such as different types of rendering tasks. These variant meshes can have a higher or lower resolution than the original, have more or less geometry than the original, have different topologies, be of different topological types, or the like. There can be many reasons for that the original solid models may not be suitable for these particular task, one being that there may be extra geometric complexity of a final solid model that can interfere in some manner with the animation process or introduce additional processing time. Thus, interactive multi-mesh modeling system 200 can automatically create and maintain separate meshes each adapted for and suitable to their different tasks.
Accordingly, interactive multi-mesh modeling system 200 may on demand and/or automatically generate and maintain output mesh 220A and enable output mesh 220A to be utilized in or by task 230A, which may including one or more rendering tasks or tools. Output mesh 220A may be automatically created to include or not include one or more user-specified or procedurally determined enhancements or features in geometry, topology, resolution, detail, or the like, that make output mesh 220A more suitable for task 230A. Interactive multi-mesh modeling system 200 may automatically create and maintain a correspondence (e.g., one or more correspondence functions) specifying the transfer of information defined on or otherwise associated with input mesh 210 to automatically generated output mesh 220A. Accordingly, in one aspect, interactive multi-mesh modeling system 200 may automatically create and maintain a more complex, higher resolution model from an original model of a garment object to be rendered for final display.
In various embodiments, interactive multi-mesh modeling system 200 may on demand and/or automatically generate and maintain output mesh 220B and enable output mesh 220B to be utilized in or by task 230B, which may include one or more animation tasks or tools. Output mesh 220B may be automatically created to include or not include one or more user-specified or procedurally determined enhancements or features in geometry, topology, resolution, detail, or the like, that make output mesh 220B more suitable for task 230B. Interactive multi-mesh modeling system 200 may automatically create and maintain a correspondence (e.g., one or more correspondence functions) specifying the transfer of information defined on or otherwise associated with input mesh 210 to automatically generated output mesh 220B. Accordingly, in another aspect, interactive multi-mesh modeling system 200 may automatically create and maintain a somewhat geometrically simplified model from the original model of a garment object to be used for creating animation data.
In various embodiments, interactive multi-mesh modeling system 200 may on demand and/or automatically generate and maintain output mesh 220C and enable output mesh 220C to be utilized in or by task 230C, which may include one or more simulation tasks or tools. Output mesh 220C may be automatically created to include or not include one or more user-specified or procedurally determined enhancements or features in geometry, topology, resolution, detail, or the like, that make output mesh 220C more suitable for task 230C. Interactive multi-mesh modeling system 200 may automatically create and maintain a correspondence (e.g., one or more correspondence functions) specifying the transfer of information defined on or otherwise associated with input mesh 210 to automatically generated output mesh 220C. Accordingly, in another aspect, interactive multi-mesh modeling system 200 may automatically create and maintain a model from the original model of a garment object to be used for creating simulation data.
As discussed above, interactive multi-mesh modeling system 200 may impart animation data, simulation data, rendering data, or other information defined on or otherwise associated with input mesh 210 to each of the automatically generated output meshes 220. As such, changes to input mesh 210 by a modeler (e.g., geometric changes) or modifications to information defined on or otherwise associated with input mesh 210 can be automatically utilized in selected ones of tasks 230 as interactive multi-mesh modeling system 200 reflects such changes in the automatically generated output meshes 220.
In further embodiments, interactive multi-mesh modeling system 200 may impart animation data, simulation data, rendering data, or other information defined on or otherwise associated with one of the automatically generated output meshes 220 to another one of the automatically generated output meshes 220. For example, interactive multi-mesh modeling system 200 may transfer task data defined on a first model automatically created and maintained for use in a particular task to a second model subsequently used in the particular task as a replacement for first model due to changes to input mesh 210. Therefore, existing task data may be preserved from one version of a model to another used in the same tasks. In another example, may transfer task data defined one automatically created and maintained model used in a first task to another automatically created and maintained model used in a second task. Therefore, the results of first task may be transferred to the model used in the second tasks.
Output mesh 220A can be represented by a solid polygonal mesh having a second resolution (represented by a second predetermined number of edges, vertices, and faces in
Output mesh 220C can be represented by 2D polygonal mesh or flat panel having a third resolution (represented by a third predetermined number of edges, vertices, and faces in
In various embodiments, input mesh 210 or other meshes utilized by interactive multi-mesh modeling system 200 may not necessarily be triangular or have a specific geometric regularity. Input mesh 210 may have one or more faces varying considerably in size. Additionally, input mesh 210 may not be in a proper form suitable, for example, for a garment simulation system or for a final rendering process. At least one process provided by interactive multi-mesh modeling system 200 for automatically producing or generating one or more meshes from an input mesh may include “retesselation.” Retesselation refers to one or more techniques that produce a new mesh that closely approximates the shape of an original mesh. In various embodiments, interactive multi-mesh modeling system 200 may provide that the structure of the retesselated mesh is to be more regular.
For example, in retesselation phase 610, interactive multi-mesh modeling system 200 may prepare input mesh 210 for one or more rendering tasks by generating shirt model 620. Shirt model 610 can be represented by a higher resolution mesh than input mesh 210 with a specific geometric regularity that is more suitable for rendering. In retesselation phase 610, interactive multi-mesh modeling system 200 may implement one or more techniques for taking input mesh 210 (e.g., having a 3D polygonal mesh) that may not necessarily be triangular and possibly having faces varying considerably in size, and producing a new triangular mesh that closely approximates the shape of the original. Interactive multi-mesh modeling system 200 may also prepare other models during retesselation phase 610 for other tasks, such as animation or simulation, by automatically generating meshes that are suitable to a task's particular requirements.
In various embodiments, input mesh 210 and other meshes utilized by interactive multi-mesh modeling system 200 may include extra geometric complexity that can interfere in some manner with one or more of tasks 230. At least one process provided by interactive multi-mesh modeling system 200 for automatically producing or generating one or more meshes from an input mesh may include “decimation.” Decimation refers to one or more techniques that simplify or reduce the geometry and/or topology of a model. In other words, one or more geometric or topological simplifications may be made to a model to prepare the model in a format suitable for a particular task. For example, in decimation phase 630, interactive multi-mesh modeling system 200 may implement geometric, topological, or other changes resulting from adding, removing, or modifying vertices, faces, or edges of input mesh 210) to create another model (e.g., shirt model 640). For example, a flat “panel constructed” garment suitable for simulations may be generated based on input mesh 210.
In various embodiments, interactive multi-mesh modeling system 200 may be guided in decimation phase 630 using user input or automated feature determining techniques. For example, how input mesh 210 is to be decimated by interactive multi-mesh modeling system 200 may be specified using tags, annotations, or other metadata. In one example, one or more annotations may be defined by a user directly on input mesh 210 and/or added directly to the model. Interactive multi-mesh modeling system 200 may utilize existing techniques that differentiate features or elements of a mesh, such as coloring, as a source of one or more annotations used to decimate input mesh 210.
In further embodiments, input mesh 210 and other meshes utilized by interactive multi-mesh modeling system 200 may not be in an appropriate form for a particular tasks. At least one process provided by interactive multi-mesh modeling system 200 for automatically producing or generating one or more mesh from an input mesh may include the generation of “fracture texture coordinates.” As discussed above, some computer simulations may assume a flat “panel constructed” garment input. The simulation systems may need to know the rest shape of an object to be simulated to determine how a model will react when it finds itself in a shape other than its rest shape. In some cases, including the simulation of cloth-like behavior, simulation results may use force response algorithms that require a two-dimensional parameterization of the surface with very particular characteristics. However, these 2D parameterizations may loose some important pieces of information from the 3D model. Accordingly, in various embodiments, in fractured texture coordinates phase 660, interactive multi-mesh modeling system 200 may transform a UV mapping associated with input mesh 210 to determine gradients of U and V each polygon in the UV mapping that are substantially orthogonal and of uniform magnitude and that approximate the original gradients of U and V for the polygon. In fractured texture coordinates phase 660, interactive multi-mesh modeling system 200 may reshape individual polygons in the UV mapping based on the 3D representation of input mesh 210. Interactive multi-mesh modeling system 200 may also ensure that the measurement directions between neighboring polygons are consistent.
In further embodiments, interactive multi-mesh modeling system 200 automatically maintains correspondences between input mesh 210 and other mesh utilized or created by interactive multi-mesh modeling system 200 and between the mesh utilized or created by interactive multi-mesh modeling system 200 themselves. At least one process provided by interactive multi-mesh modeling system 200 for automatically producing or generating one or more mesh from an input mesh and the maintenance of correspondences may include a disambiguation. Interactive multi-mesh modeling system 200 may resolve ambiguities in one or more associations or correspondences between objects, such between input mesh 210 and shirt model 620, between instances or version of shirt model 620, and between shirt model 620 and shirt model 650 providing that animation/simulation of shirt model 650 produces similar animation/simulation results of shirt model 620 in rendering phase 690.
For example, in disambiguation phase 680, interactive multi-mesh modeling system 200 may determine one or more correspondences or correspondence functions that specify the transfer of information between two meshes. Interactive multi-mesh modeling system 200 may implement one or more techniques that take any produced animation/simulation data for one model (e.g., shirt model 650 provided by simulation phase 670), and correlated it to model 620 such that shirt model 620 is placed in the same position, pose, etc. or otherwise exhibits that same behavior for rendering phase 690. In the absence of any predetermined correspondence between shirt model 620 and shirt model 650 as a reference model, one most common way of assigning each driven region to a reference region to follow is using what is known as spatial correspondence where one puts both the driven and the reference model in some default or “neutral pose” which are known to correspond, and then associates regions of the driven mesh with the region of the reference mesh they are closest to. However, most simple correspondence techniques fail when the driven model is fairly complex compared to the reference model. Accordingly, in various embodiments, in disambiguation phase 680, interactive multi-mesh modeling system 200 may implement one or more techniques for determining a spatial correspondence using a combination of metrics defined on the two meshes and a metric define on an embedding space. Some examples of metrics are Euclidean distance, geodesic distance, and topological distance.
In further embodiments, interactive multi-mesh modeling system 200 may enable the rendering of input mesh 210 or any of automatically generated output meshes 230 and associated task data in at least one rendering process provided by interactive multi-mesh modeling system 200 or connected to interactive multi-mesh modeling system 200. Interactive multi-mesh modeling system 200 may automatically generate shirt model 620 suitable for rendering and using one or more automatically generated associations or correspondences, transfer any modeling/animation/simulation or other task data from any one of input mesh 210 or other automatically generated shirt models to shirt model 620 in rendering phase 690.
Accordingly, in aspects of various embodiments, interactive multi-mesh modeling system 200 allows for interactive creation and design of a single 3D solid cloth model, for the authoring of animation data, simulation data (e.g., material characteristics), rendering data (e.g., shading/texture data), or the like, on the model or on one of multiple automatically generated version of the model that are suitable for a specific task, and for the automatic management and transferring of all or part of the authored data and results of these various tasks from the original model and between any automatically generated versions of the original model.
Mesh Generation Specifications
In step 720, an input mesh is received. For example, a user of interactive multi-mesh modeling system 200 may utilize one or more commercially available tools to create or sculpt a 3D model having a polygonal mesh. In another example, information defining the input mesh may be loaded from one or more files or libraries.
In step 730, a mesh generation specification is received for each of a plurality of different tasks. For example, criteria specifying one or more instructions or requirements may be received for each task in tasks 230. An instruction or requirement may include a data source type, a data repository, an input specification or format, an output specification or format, data transformations required, mesh attributes or features, mesh resolution, constraints, preservation information, removal information, or the like. An instruction or requirement may be specified directly by a user or administrator of interactive multi-mesh modeling system 200. In other embodiments, a set of instructions or requirements may be automatically determined by interactive multi-mesh modeling system 200 through a programming interface or API associated with a system that provides a particular task or set of tasks. Interactive multi-mesh modeling system 200 may receive, modify, or update a mesh generation specification for a task manually in response to user input or dynamically when it is recognized that interactive multi-mesh modeling system 200 has access to the task or the task has been added to one or more workflows implemented by interactive multi-mesh modeling system 200.
In step 740, a plurality of task meshes and associated correspondences between the input mesh and the tasks meshes are maintained. In various embodiments, interactive multi-mesh modeling system 200 may automatically generate at least one task mesh and associated correspondences for each of tasks 230 based on input mesh 210 and a mesh generation specification for each of tasks 230. For example, based on an input mesh, interactive multi-mesh modeling system 200 may automatically generate an output mesh having a higher resolution than the input mesh and approximating the shape of the input mesh that is suitable for rendering and any associated correspondences specifying transfer of information defined on or otherwise associated with the input mesh to the automatically generated mesh or transfer of information defined on or otherwise associated with another automatically generated mesh (such as those suitable for animation or simulation) to the automatically generated mesh designated for rendering purposes.
A correspondence for a meshes can define how position information of one mesh (be it the input mesh or a mesh managed automatically by interactive multi-mesh modeling system 200) corresponds to position information of another mesh (e.g., any of the meshes managed automatically by interactive multi-mesh modeling system 200). A correspondence may define an association between data found at a point on one mesh and data to be located at a point on another mesh. A correspondence may include information representing one or more subdiv maps. A correspondence may further define information representing a determined spatial disambiguation between at least two meshes.
In step 750, one or more selected correspondences between task meshes are maintained. For example, interactive multi-mesh modeling system 200 may automatically generate one output mesh for one particular task and another output mesh for another particular task. Interactive multi-mesh modeling system 200 may generate and maintain any associated correspondences (or correspondence functions) specifying transfer of information defined on or otherwise associated with the one output mesh for the one particular task to the another output mesh for the another particular tasks and transfer of information defined on or otherwise associated with the meshes between the meshes. In another example, in response to a modification to the input mesh or to a modification to a mesh generation specification of a particular task, interactive multi-mesh modeling system 200 may automatically regenerate an output mesh for that particular task and any associated correspondences (or correspondence functions) specifying transfer of information defined on or otherwise associated with the input mesh to the automatically generated mesh, transfer of information defined on or otherwise associated with another automatically generated mesh (such as those suitable for animation or simulation) to the automatically generated mesh designated for the particular task, and transfer of information defined on or otherwise associated with the previously automatically generated mesh designated or the tasks to the newly regenerated mesh.
In step 760, data transfer is maintained between the input mesh and the tasks meshes and the selected task meshes based on their associated correspondences. In one example, interactive multi-mesh modeling system 200 may transfer animation data defined on or otherwise associated with the input mesh to an automatically generated output mesh. In another example, interactive multi-mesh modeling system 200 may transfer results of a computer simulation of one of the automatically generated meshes to another automatically generated mesh designated for rendering. In yet another example, interactive multi-mesh modeling system 200 may transfer task data created for one automatically generated mesh for a particular onto an automatically regenerated mesh for the particular tasks. Other properties of the input mesh or other data associated with any of the automatically generated meshes, such as material properties, lighting, shader code, rigging, control structures, animation variables, or the like, can be automatically transferred to and from an input mesh, between meshes for different tasks, and between versions or instances of meshes for the same task.
Accordingly, in aspects of various embodiments, interactive multi-mesh modeling system 200 allows for creating and designing a single 3D solid cloth model and authoring animation data, simulation data, and rendering data for any one of the input meshes and/or automatically created meshes. In further aspects, interactive multi-mesh modeling system 200 allows for transferring of all or part of input data associated with the input meshes and/or the results of various tasks (e.g., task data) between any of the input meshes and/or the output meshes (or versions thereof).
Area 820 can include elements (e.g., GUI widgets or controls) configured for enabling a user to create and display a model, such as input mesh 210 or output meshes 220. Area 820 may further be configured for enabling a user to interact with input mesh 210 or output meshes 220, such as for the purposes of editing, modifying, annotating, attaching data, or the like. For example, area 820 may display output mesh 220C with specific geometric regularity, suitable for animating or simulating, that has been generated by interactive multi-mesh modeling system 200 from input mesh 210. Area 820 may display output mesh 220C with one or more geometric and/or topological simplifications as compared to output mesh 220A displayed in area 810.
Area 830 can include elements (e.g., GUI widgets or controls) configured for displaying information or receiving selections made by users for options associated with tasks 230. Area 830 may further be configured with one or more user interface elements configured for enabling interactions with the models displayed in areas 810 and 820 or invoking specific tasks with the models displayed in areas 810 and 820.
Area 930 can include elements (e.g., GUI widgets or controls) configured for displaying information or receiving selections made by users for options associated with tasks 230. Area 930 may further be configured with one or more user interface elements configured for enabling interactions with the models displayed in areas 910 and 920 or invoking specific tasks with the models displayed in areas 910 and 920.
Computer system 1000 can include hardware and/or software elements configured for performing logic operations and calculations, input/output operations, machine communications, or the like. Computer system 1000 may include familiar computer components, such as one or more one or more data processors or central processing units (CPUs) 1005, one or more graphics processors or graphical processing units (GPUs) 1010, memory subsystem 1015, storage subsystem 1020, one or more input/output (I/O) interfaces 1025, communications interface 1030, or the like. Computer system 1000 can include system bus 1035 interconnecting the above components and providing functionality, such connectivity and inter-device communication. Computer system 1000 may be embodied as a computing device, such as a personal computer (PC), a workstation, a mini-computer, a mainframe, a cluster or farm of computing devices, a laptop, a notebook, a netbook, a PDA, a smartphone, a consumer electronic device, a gaming console, or the like.
The one or more data processors or central processing units (CPUs) 1005 can include hardware and/or software elements configured for executing logic or program code or for providing application-specific functionality. Some examples of CPU(s) 1005 can include one or more microprocessors (e.g., single core and multi-core) or micro-controllers, such as PENTIUM, ITANIUM, or CORE 2 processors from Intel of Santa Clara, Calif. and ATHLON, ATHLON XP, and OPTERON processors from Advanced Micro Devices of Sunnyvale, Calif. CPU(s) 1005 may also include one or more field-gate programmable arrays (FPGAs), application-specific integrated circuits (ASICs), or other microcontrollers. The one or more data processors or central processing units (CPUs) 1005 may include any number of registers, logic units, arithmetic units, caches, memory interfaces, or the like. The one or more data processors or central processing units (CPUs) 1005 may further be integrated, irremovably or moveably, into one or more motherboards or daughter boards.
The one or more graphics processor or graphical processing units (GPUs) 1010 can include hardware and/or software elements configured for executing logic or program code associated with graphics or for providing graphics-specific functionality. GPUs 1010 may include any conventional graphics processing unit, such as those provided by conventional video cards. Some examples of GPUs are commercially available from NVIDIA, ATI, and other vendors. In various embodiments, GPUs 1010 may include one or more vector or parallel processing units. These GPUs may be user programmable, and include hardware elements for encoding/decoding specific types of data (e.g., video data) or for accelerating 2D or 3D drawing operations, texturing operations, shading operations, or the like. The one or more graphics processors or graphical processing units (GPUs) 1010 may include any number of registers, logic units, arithmetic units, caches, memory interfaces, or the like. The one or more data processors or central processing units (CPUs) 1005 may further be integrated, irremovably or moveably, into one or more motherboards or daughter boards that include dedicated video memories, frame buffers, or the like.
Memory subsystem 1015 can include hardware and/or software elements configured for storing information. Memory subsystem 1015 may store information using machine-readable articles, information storage devices, or computer-readable storage media. Some examples of these articles used by memory subsystem 1070 can include random access memories (RAM), read-only-memories (ROMS), volatile memories, non-volatile memories, and other semiconductor memories. In various embodiments, memory subsystem 1015 can include direct 3D multi-resolution garment modeling data and program code 1040.
Storage subsystem 1020 can include hardware and/or software elements configured for storing information. Storage subsystem 1020 may store information using machine-readable articles, information storage devices, or computer-readable storage media. Storage subsystem 1020 may store information using storage media 1045. Some examples of storage media 1045 used by storage subsystem 1020 can include floppy disks, hard disks, optical storage media such as CD-ROMS, DVDs and bar codes, removable storage devices, networked storage devices, or the like. In some embodiments, all or part of direct 3D multi-resolution garment modeling data and program code 1040 may be stored using storage subsystem 1020.
In various embodiments, computer system 1000 may include one or more hypervisors or operating systems, such as WINDOWS, WINDOWS NT, WINDOWS XP, VISTA, or the like from Microsoft or Redmond, Wash., SOLARIS from Sun Microsystems, LINUX, UNIX, and UNIX-based operating system. Computer system 1000 may also include one or more applications configured to executed, perform, or otherwise implement techniques disclosed herein. These applications may be embodied as direct 3D multi-resolution garment modeling data and program code 1040. Additionally, computer programs, executable computer code, human-readable source code, shader code, rendering engines, or the like, and data, such as image files, models including geometrical descriptions of objects, ordered geometric descriptions of objects, procedural descriptions of models, scene descriptor files, or the like, may be stored in memory subsystem 1015 and/or storage subsystem 1020.
The one or more input/output (I/O) interfaces 1025 can include hardware and/or software elements configured for performing I/O operations. One or more input devices 1050 and/or one or more output devices 1055 may be communicatively coupled to the one or more I/O interfaces 1025.
The one or more input devices 1050 can include hardware and/or software elements configured for receiving information from one or more sources for computer system 1000. Some examples of the one or more input devices 1050 may include a computer mouse, a trackball, a track pad, a joystick, a wireless remote, a drawing tablet, a voice command system, an eye tracking system, external storage systems, a monitor appropriately configured as a touch screen, a communications interface appropriately configured as a transceiver, or the like. In various embodiments, the one or more input devices 1050 may allow a user of computer system 1000 to interact with one or more non-graphical or graphical user interfaces to enter a comment, select objects, icons, text, user interface widgets, or other user interface elements that appear on a monitor/display device via a command, a click of a button, or the like.
The one or more output devices 1055 can include hardware and/or software elements configured for outputting information to one or more destinations for computer system 1000. Some examples of the one or more output devices 1055 can include a printer, a fax, a feedback device for a mouse or joystick, external storage systems, a monitor or other display device, a communications interface appropriately configured as a transceiver, or the like. The one or more output devices 1055 may allow a user of computer system 1000 to view objects, icons, text, user interface widgets, or other user interface elements.
A display device or monitor may be used with computer system 1000 and can include hardware and/or software elements configured for displaying information. Some examples include familiar display devices, such as a television monitor, a cathode ray tube (CRT), a liquid crystal display (LCD), or the like.
Communications interface 1030 can include hardware and/or software elements configured for performing communications operations, including sending and receiving data. Some examples of communications interface 1030 may include a network communications interface, an external bus interface, an Ethernet card, a modem (telephone, satellite, cable, ISDN), (asynchronous) digital subscriber line (DSL) unit, FireWire interface, USB interface, or the like. For example, communications interface 1030 may be coupled to communications network/external bus 1080, such as a computer network, to a FireWire bus, a USB hub, or the like. In other embodiments, communications interface 1030 may be physically integrated as hardware on a motherboard or daughter board of computer system 1000, may be implemented as a software program, or the like, or may be implemented as a combination thereof.
In various embodiments, computer system 1000 may include software that enables communications over a network, such as a local area network or the Internet, using one or more communications protocols, such as the HTTP, TCP/IP, RTP/RTSP protocols, or the like. In some embodiments, other communications software and/or transfer protocols may also be used, for example IPX, UDP or the like, for communicating with hosts over the network or with a device directly connected to computer system 1000.
As suggested,
Various embodiments of any of one or more inventions whose teachings may be presented within this disclosure can be implemented in the form of logic in software, firmware, hardware, or a combination thereof. The logic may be stored in or on a machine-accessible memory, a machine-readable article, a tangible computer-readable medium, a computer-readable storage medium, or other computer/machine-readable media as a set of instructions adapted to direct a central processing unit (CPU or processor) of a logic machine to perform a set of steps that may be disclosed in various embodiments of an invention presented within this disclosure. The logic may form part of a software program or computer program product as code modules become operational with a processor of a computer system or an information-processing device when executed to perform a method or process in various embodiments of an invention presented within this disclosure. Based on this disclosure and the teachings provided herein, a person of ordinary skill in the art will appreciate other ways, variations, modifications, alternatives, and/or methods for implementing in software, firmware, hardware, or combinations thereof any of the disclosed operations or functionalities of various embodiments of one or more of the presented inventions.
The disclosed examples, implementations, and various embodiments of any one of those inventions whose teachings may be presented within this disclosure are merely illustrative to convey with reasonable clarity to those skilled in the art the teachings of this disclosure. As these implementations and embodiments may be described with reference to exemplary illustrations or specific figures, various modifications or adaptations of the methods and/or specific structures described can become apparent to those skilled in the art. All such modifications, adaptations, or variations that rely upon this disclosure and these teachings found herein, and through which the teachings have advanced the art, are to be considered within the scope of the one or more inventions whose teachings may be presented within this disclosure. Hence, the present descriptions and drawings should not be considered in a limiting sense, as it is understood that an invention presented within a disclosure is in no way limited to those embodiments specifically illustrated.
Accordingly, the above description and any accompanying drawings, illustrations, and figures are intended to be illustrative but not restrictive. The scope of any invention presented within this disclosure should, therefore, be determined not with simple reference to the above description and those embodiments shown in the figures, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
This Applicants claims priority to and the benefit of U.S. Patent Application No. 61/248,050, filed Oct. 2, 2009 and entitled “Direct 3D Multiresolution Garment Modeling System,” which is hereby incorporated by reference for all purposes. This application is related to the following commonly owned and co-pending applications: U.S. patent application Ser. No. 12/893,319, filed Sep. 29, 2010 and entitled “Annotation-Based Mesh Modification” which claims priority to U.S. Provisional Patent Application No. 61/248,042, filed Oct. 2, 2009 and entitled “Automatic Annotation-Based Mesh Modification,” both of which are hereby incorporated by reference for all purposes. U.S. patent application Ser. No. 12/893,353, filed Sep. 29, 2010 and entitled “Structured Polygonal Mesh Retesselation” which claims priority to U.S. Provisional Patent Application No. 61/248,045, filed Oct. 2, 2009 and entitled “Structured Polygonal Mesh Retesselation,” both of which are hereby incorporated by reference for all purposes. U.S. patent application Ser. No. 12/893,395, filed Sep. 29, 2010 and entitled “Automatic Spatial Correspondence Disambiguation” which claims priority to U.S. Provisional Patent Application No. 61/248,046, filed Oct. 2, 2009 and entitled “Automatic Spatial Correspondence Disambiguation,” both of which are hereby incorporated by reference for all purposes. U.S. patent application Ser. No. 12/893,460, filed Sep. 29, 2010 and entitled “Fractured Texture Coordinates” which claims priority to U.S. Provisional Patent Application No. 61/248,051, filed Oct. 2, 2009 and entitled “Fractured Texture Coordinates,” both of which are hereby incorporated by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
6940505 | Savine et al. | Sep 2005 | B1 |
7138999 | Alliez et al. | Nov 2006 | B2 |
7283134 | Hoppe | Oct 2007 | B2 |
7538769 | Hoppe | May 2009 | B2 |
7899241 | Baxes et al. | Mar 2011 | B2 |
8237710 | Marketsmueller | Aug 2012 | B1 |
8405655 | Onodera et al. | Mar 2013 | B2 |
Entry |
---|
Alliez et al, Recent Advances in Remeshing of Surfaces, Aug. 31, 2009, pp. 1-31. |
Desbrun et al, Instrinsic Parameterizations of Surface meshes. EUROGRAPHICS 2002, vol. 21, No. 2, 2002, pp. 1-10. |
Nguyen et al., “Geometry completion and detail generation by texture synthesis,” The Visual Computer 21, 8-10 (2005): 669-678. |
Schall et al., “Controlled filed generation for quad-meshing,” Proceeding of the 2008 ACM Symposium on Solid and Physical Molding, ACM 2008. |
Xu et al., Technical Section: Dynamic harmonic fields for surface processing, Computers and Graphics, Jun. 2009, vol. 33, No. 3, pp. 391-398. |
Dong et al., Spectral Surface Quadrangulation, SIGGRAPH 06, ACM, Jul. 2006, pp. 1057-1066. |
Sifri et al., Geodesic-based surface remeshing, Proceedings, 12th International Meshing Roundtable, Sandia National Laboratories, pp. 189-199, Sep. 2003. |
Yan et al., Isotropic Remeshing with Fast and Exact Computation of Restricted Voronoi Diagram, Eurographics Symposium on Geometry Procession, 2009, pp. 1445-1454. |
Number | Date | Country | |
---|---|---|---|
61248050 | Oct 2009 | US |