This article contains the full specification for CheckMate Pro, TurboSquid’s highest quality standard for 3D models. To see the condensed CheckMate Pro Checklist, you can go HERE.
July 15th, 2019
Limitations on CheckMate Pro Certification
Limitations on CheckMate Pro Certification
1.1 Quality – The 3D model must have a high level of aesthetic appeal as well as workability. If the model is intended to represent a real-world object, it must accurately represent that object. Quads and triangles must be intelligently distributed for good edge flow and clean topology.
1.2.1 Product pricing must conform to the CheckMate pricing matrix.
- 3ds Max (.max) (Renderers Supported: Scanline / V-Ray / Corona / Arnold / IRay / Mental Ray)
- Maya (.ma / .mb) (Renderers Supported: Software / Hardware / Mental Ray / V-Ray / Arnold)
- CINEMA 4D (.c4d) (Renderers Supported: Advanced / Physical / Arnold / V-Ray)
- Lightwave (.lws) (Renderers Supported: Default)
- Blender (.blend) (Renderers Supported: Standard / Cycles/ Eevee)
1.3.3 CheckMate Pro certification is awarded on a per-format basis. The native file format must pass CheckMate Pro certification in order to get the Pro badge, but if another certifiable non-native file format fails inspection, the native format (and product) will still be marked as CheckMate Pro certified. The non-native file must, as a minimum, pass the requirements for CheckMate Lite inspection in that it must open and render without errors.
- Collections that contain all CheckMate Pro models can be submitted for Pro certification.
- Collections that contain all CheckMate Lite models can be submitted for Lite certification.
- Collections that contain both CheckMate Lite and Pro models can be submitted for Lite certification.
Standards for 3D Model Inspection
Standards for 3D Model Inspection
2.1.1 No isolated vertices
2.1.2 No coincident vertices
2.1.3 No coincident/coplanar faces
2.1.6 Geometry must not have open edges or borders that cause see-through cracks in the model when rendered. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.
2.2.2 Mostly quads – The model must use quads as much as possible. A range of up to 20% triangles is acceptable for most models, but you should actively endeavor to minimize their usage in your work. Models are inspected manually to ensure excessive triangles aren’t present.
Note that realtime models will often have a much higher percentage of triangles to meet the requirement of minimum geometry possible to form the object.
2.2.3 Clean edge flow – Model must have the best possible edge flow, with sufficient geometry to meet these requirements without superfluous geometry. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.
184.108.40.206 Poles with more than 5 edges on the model are highly discouraged as it can indicate sloppy topology to a customer. If poles are included in your model, you must add the following note to your Product Description.
“NOTE: This model contains poles (more than 5 edges that converge to a single vertex.)”
220.127.116.11.1 Exception for very small, insignificant objects within the model/scene: Such objects do not have to meet the criteria above. Objects such as screws, bolts, rivets, wires, and other objects which are very small in comparison to the overall model size, do not have to follow the Clean Edge Flow rules.
18.104.22.168.2 Exception for one-sided objects with opacity map: Objects that represent a thin real-life object as a one-sided object, where the shape of the object is depicted via an opacity map, do not have to follow the Clean Edge Flow rules.
Examples of this exception are leaves, petals, decals, paper, cloth. This exception does not apply to fully three-dimensional objects such as thin boxes.
22.214.171.124.3 Exception for realtime models – Models intended for game engines, realtime display, or background elements must have the lowest number of polygons possible while still retaining the model’s shape, but do not have to conform to the subdivision points above. For such models, a high percentage of triangles is allowable, provided they are necessary to make the model shape with the lowest number of polygons possible.
2.2.4 Crease value – Value of the Crease or Open SubDiv function within your 3D application must be 0 for all edges. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.
This requirement ensures that a subdividable model, when converted to other formats, will retain the same shape when subdivided. If the model is a realtime model (not subdividable), there is no reason to have a Crease value other than 0.
2.3.1 Real-world scale within 1-3% – Model can use any units to achieve real-world scale. If the model does not have an exact real-world counterpart (such as a human character or an unbranded car), the model must use the size/scale of comparable objects in real life.
2.3.2 Exception for exceedingly large/small models – Models of objects that have a real-world scale at a microscopic or astronomical level, such as amoebas and solar systems, are excepted from having real-world scale.
2.4.3 The model should be oriented to World up-axis – The obvious “up” side of the model must be pointing toward the World up axis. In other words, the model can’t be lying on its side or upside-down when the file is opened. For objects that can be oriented in multiple ways (e.g. books, pencils, etc.), the artist is free to choose the up-axis, but this must be reflected in the presentation images so a customer’s expectations are matched by what is shown.
2.4.4 The native model file must be in the same position and framing as the Search image. Additional non-native file formats that are published simply need to open so the full model is visible in the viewport with no hidden parts but do not have to match pose and framing of the native file.
2.6.1 Descriptive and unique object names – Default object names are not acceptable. They should be changed to be descriptive of the object and easy-to-understand when reviewed by a customer.
2.6.3 Model includes a grouping or hierarchy for moving all objects in model together.
2.6.4 All geometry is contained in a single layer structure, with the layer having the same name as the product. Note: Only models inspected after June 15, 2013 are guaranteed to meet this point of the specification.
- 3ds Max – Layers
- Maya – Display Layers
- CINEMA 4D – Layers
- Lightwave – Include the .LWS with the model and organize using a null object
- Blender – All elements of the model on a single layer
2.7.1 At least one material must be applied to each object to represent real-world object surfaces. The customer should be able to render the model upon purchase and get quality surface representation.
2.7.3 Materials and Bitmap texture files named descriptively. Bitmap filenames Image, Pic or Picture plus a number are not acceptable. Likewise, material filenames 01-Default, Blinn01, Mat are not acceptable.
A model with mapped textures must meet these requirements:
2.9.4 Custom rig must include instructions – A Readme, PDF document, or other documentation on how to use the rig. Rigs that use Biped or CAT are not required to have a readme unless there are custom controls.
Standards for Product Presentation
Standards for Product Presentation
126.96.36.199 Search image should show the entire model inside the image boundaries. Exceptions can be made for closeups of characters and other vertically oriented models like skyscrapers, street lights, etc.
188.8.131.52 This set of rendered imagery shows off the model’s quality, detail and aesthetic appeal from a variety of angles and positions. This is where you get to show off your skill to potential customers, so spend time on these.
184.108.40.206.2 Although highly recommended, the first Product Shot does not need to match the same pose and composition as the Search image. However, it should be displayed as it exists when the file is opened.
220.127.116.11.3 Other spec requirements for Search Image also apply (no text, logos or borders.). Watermarks can be used only as described and subject to inspector discretion. Turntables are not allowed as the Search image or your first Product Shot.
It is usually necessary to include at least 3-4 closeups of various parts of the geometry to fully show the topology. On a complex model, more wireframes might be required to give a potential customer the visual information they need to make a buying decision.
18.104.22.168 The wireframe should be generated over a colored (non-textured) version of the model. There must be a sufficient contrast between the background/object and wire colors to make the topology visually understandable. Neutral tones are highly recommended, but are not required. The background and object do not have to share the same tone or color.
22.214.171.124 Subdividable model wireframe recommendations: When creating models intended for subdivision, it is recommended (not required) that you provide at least two (2) additional wireframes with these attributes:
126.96.36.199.1 One wireframe that shows entire model’s base geometry (no subdivision) with a text label stating such. Text label must be in a color that contrasts the image background, and should not overlap the model unless overlapping is unavoidable. Label must be one of the following, including punctuation, capitalization, and spelling:
- Subdivision Level 0
- Subdivision Level: 0
- Subdivision: None
- No Subdivision
Do not use names of tools or modifiers within your native software in the text label, as these names might not be familiar to customers using other software.
- Subdivision Level [number]
- Subdivision Level: [number]
- Subdivision: [number]
A Photoshop PSD file with suitable Subdivision Level text is available for download on the CheckMate Tools page. It is recommended (but not required) that you use this PSD file to set the text on these wireframe images.
188.8.131.52 All wireframe images must clearly show the model’s geometry as a solid, neutral color with contrasting colored wires showing the construction of the model. Screen captures and see-through renders are not allowed for wireframe images.
184.108.40.206 A minimum sequence of 12 frames that displays a rotation of the static object. Animation should start at the front of the model, have an equal number of degrees between frames, and should loop seamlessly without slowing down.
3.1.5 Unwrapped UV Image Requirements: At least one (1) image of the unwrapped UVs of your model if one of the following options is selected for the model’s Unwrapped UVs attribute within the publisher interface:
- Yes, overlapping
- Yes, non-overlapping
If no texture is applied to the object, background color on thumbnail should match the material color applied to the object. The image should show the main texture, pattern, or color on the object, not secondary textures such as bump or specular maps.
3.1.6 Optional Images: Beyond the required imagery explained above (Search, Product Shots, Wireframes, Unwrapped UVs, Turntables), you are encouraged to use your creativity to showcase your talent with additional product shots, turntables, and more. Although recommended, these images do not need to adhere to the image size minimums or aspect ratios listed in the required imagery above. However, they must follow TurboSquid’s Product Imagery and Presentation Standards.
3.2.1 Includes at least one certifiable file format (See 1.3 File Formats).
3.2.4 All required files archived with product file in one of the following three ways:
- All bitmap textures are archived with each certifiable model file in a flat file structure.
- All bitmap textures are archived with each certifiable model file in a single subfolder beneath the main product file.
- All bitmap textures required are placed into a single, named ZIP file and uploaded once as a Textures Supporting Items product in the TurboSquid publisher. Certifiable model files are each placed into their own named ZIP files and uploaded on their own. See Bitmap Texture Pathing.
3.3.4 All words in the Product Name except articles, conjunctions and prepositions must have initial capital letter. Words that represent acronyms can be all caps, but product Name should not be all caps.
3.4.1 Polygon Count value matches poly count in native file format. If you’ve applied subdivision to the native file format which is removable (as with a TurboSmooth modifier in 3ds Max or an editable history in Maya) you must enter the polygon count without subdivision.
3.4.2 Vertex Count value matches vertex count in native file format before subdivision.
3.4.3 In the Geometry field within the publisher, one of these two choices is selected:
- Polygonal Quads/Tris
- Polygonal Quads only
3.5.3 Third-party plug-ins or renderers used or referenced in model explicitly specified in your description. If the renderer in the model file is set to a non-default renderer, or if materials are those from a non-default renderer, state this in Description.
The CheckMate Specifications, CheckMate names, including “CheckMate Pro” and “CheckMate Lite,” and all related branding and logos, whether registered or not, are the property of TurboSquid. TurboSquid retains all ownership of these trademarks and copyrighted material. They are protected by intellectual property laws of the U.S. or in some instances, foreign laws and international treaties. Unauthorized use may violate copyright, trademark and other laws.
CheckMate Specifications may be reused and republished by third parties with permission, with the exception of third parties that sell or distribute 3D content as part of a stock 3D business. In no case may models distributed or sold anywhere other than at turbosquid.com (or its affiliates including the SquidGuild Network) be referred to as “CheckMate,” “CheckMate Certified,” “CheckMate Pro,” “CheckMate Lite” or any by similar name referencing CheckMate.
Participants in the CheckMate program who have received certification and would like to use CheckMate branding to promote their own models may do so on other sites, so long as such models are not sold on those other sites.
For any questions or to request permission to republish CheckMate Specifications, please contact firstname.lastname@example.org.