The CheckMate submission process has been significantly updated for all new content.  Only some existing content will continue through this process.

One thing that we have been finding that artist’s have been having issues with is cancelling a submission. When a submission is cancelled, the entire job is closed. There is no going back to it. Resubmitting the product will create a brand new job/submission that will then be treated by our system as a new submission. This will cause the wait time to be longer than usual as the product is considered as a brand new inspection.

However, updating the product will update the current job that is open.

First, everyone should know how to access their task ticket. It is important to remember that you must be using the new dashboard within squid.io. If you are still using the classic dashboard, then you should see a link at the top that is referring to the new dashboard as shown below:

Please note that you cannot access your notes through the classic dashboard. You need to migrate to the new dashboard. You can currently refer back to the classic dashboard at any given time.

Once you are in the new dashboard, you will see many sections to choose from. Notifications are located at the very top of the page, while current artist news and forum posts are displayed to the right. If you scroll down, you will find information regarding your online products as well as any of your PixelSquid submissions. Last but not least, your current CheckMate Queue can be seen in this example (right).

The CheckMate Queue will list any products that you have submitted to CheckMate. You can click on any link that states Waiting, or Requires Action. Those links will bring you to the product job where you can see the status of your model, communicate with a TurboSquid inspector and update your native/non-native products when needed.

Here’s what each status within the CheckMate Queue means:

• Waiting – A TurboSquid inspector is actively checking your product
• Requires Action – The inspection has been completed and requires fixes on the artist’s end
• Queued – the inspection has not begun just yet

Next, let’s take a quick look at the CheckMate jobs themselves.

When you click on a job from your dashboard, you’ll see a screen similar to the one below.

1. The name of the product you submitted for CheckMate inspection.
2. Information pertaining to your artist status including current SquidGuild Level and how many products you have already certified (both Pro and Lite).
3. This section shows you the status of your job and what task an inspector is currently reviewing on your behalf. Please keep in mind that there are three different task levels and this is the order in which we perform them.
   1. Native File Format – This is the first stage of a CheckMate inspection. At this point, the inspector looks at your main 3D file. The inspector will open and review your model using our inspection tools to ensure there are no technical glitches in your work that could cost you money on a return. This phase must be passed as well to be certified.
   2. Certify Product Preview – In this stage we are looking at your product imagery to ensure your published imagery matches CM requirements. This stage must pass in order for your product to move onto the next phase. Any changes within the product preview page must be made within the publisher.
   3. Non-native File Format – Once your native file passes inspection, all of your submitted non-native file formats begin the inspection process. If you do not have any non-native files, then your inspection is completed. Please note that you will not be able to make any changes until all non-native files have been checked.
4. This section shows you a list of all files that you submitted for CheckMate inspection. The file furthest to your left l is the native file format. The other files are your non-native files.
5. This section identifies the actual model file that will be inspected for the current task (indicated by the underlined section above).
6. This area shows you the current status of your product. There are three different types of statuses.
   1. Submitted – The product is currently in the inspection process.
   2. Approved – This phase of the inspection has passed.
   3. Failed – This phase of the inspection has failed and needs changes.
   4. Broken – The file does not open appropriately and cannot be certified. This option will only appear for Pro non-native files.
7. This section of your job is where you can view the history of the product inspection. It will show you which inspector is checking your product as well as display comments made on the product by that inspector. You can also make comments as well if you wish to speak to the inspector or ask them a question in regards to the product or their feedback.

How To Resubmit a Failed Product

If your product has failed in any phase of the inspection process and you wish to resubmit the product, there are two different ways to do so.

If your product has failed in the product preview phase, then you must go back to the publisher on Turbosquid.com (found in your drop-down menu). The failures can be any of the following: thumbnail images, description, product name, pricing, or keywords.

The native and non-native files are similar when re-submitting. Resubmitting should take place within the existing job ticket itself. In order to re-submit the file, you need to click on Update File (shown right) if your product has failed in the native file phase for both CheckMate Pro and CheckMate Lite. As highlighted, click “Update File.”

Here is how the job ticket will look if your product has failed in the non-native phase for CheckMate Pro.

As you can see, there are three non-natives. The 3ds Max and Maya files have passed, showcasing a green checkmark by each tab. The Cinema 4D has a red X, showing that the non-native has failed.

When a non-native file fails, you are given two options:

1. Update File – You can update the file with the corrections needed.

2. Do not certify file – As this is the non-native file, this is not required to pass CheckMate. Simply hitting this button will confirm that your native and other non-natives that have passed will be CheckMate certified, but will remove the failed non-native file from certified formats when published.

There may also be a time where you find a red X circled, meaning that the file itself is broken and cannot be placed on this product, whether the other files are certified or not. This may be in regards to textures not being included to having major errors in the file, or to the file not opening at all.

Due to this, the option to not certify for CheckMate will not be included, which brings us to another option.

3. Remove file from product – This removes the non-native file completely from the product. All other products that have been certified will receive it’s badge unless other products need checking.

For CheckMate Lite, non-natives are treated differently as it is required that either all CheckMate submitted file types meet the CheckMate Lite standards as well. So if any non-native Lite products do not meet the criteria, you must either update the file, or remove the file from the product as shown.

Once the new upload is complete, be sure to scroll down to the bottom of the page and click on “Submit for Approval”.

That is the overall process for our system. If there are any questions in regards to the process, please feel free to get in touch with your CheckMate Inspector and ask for help.