VStitcher is a leader in 3D fashion design, helping designers model their garments via a wide range of features including photorealistic 3D renders. This focus on quality, however, can lead to large file sizes and long load times. VNTANA’s optimization process can drastically cut down on the file size of VStitcher export without sacrificing the visual quality that VStitcher produces. The VNTANA Plugin for VStitcher is designed to simplify the garment design pipeline for VNTANA Clients by handling the export process from VStitcher and automatically uploading the asset to the VTANA Platform for optimizaiton.
The plugin currently requires a manual installation and instructions have been provided within the download. Should you have any questions about the installation process, or usage of the plugin you can reach out to our support team at firstname.lastname@example.org.
Using the Plugin
The VNTANA VStitcher Plugin allows you to easily export your garments from VStitcher using our recommended export settings and have them directly uploaded to the VNTANA Platform for optimization. The plugin can be used either on an individual garment as a final step in your design workflow, or on a batch of garments.
A set of installation instructions are included in the download. At this time, the plugin requires a manual installation and must be placed within the install directory of your VStitcher installation.
To make use of the plugin you must first authenticate with the VNTANA Platform using either a valid Authentication Token (see below for instructions on generating this) or email and password. Once you’ve logged in once with a valid Authentication Token the plugin will attempt to log you in automatically each time the plugin is launched. There is no option for automatic authentication with an email and password.
Folder Select Page
The first screen you are brought to upon successful authentication is the Folder Select page. This is where you will indicate the Organization and Folder on the VNTANA Platform you wish the garment(s) to be uploaded to, as well as whether the plugin is to be executed on your ‘Current Project’ or a batch.
For the ‘Current Project’ option, the .bw file has to already be opened within VStitcher before the export and upload processes start. The directory that is selected is used to indicate to the plugin where .bw files are to import in the case of a batch run, or simply to indicate where to export the ‘Current Project’ if selected.
You cannot progress in the plugin until a directory is set.
The second screen covers the various settings we’ve opened up for adjustment. For the Browzwear VStitcher settings, we only open up inclusion of avatars and colorways. We use our recommended export settings and do not allow these to be altered through the plugin as they are catered to our Browzwear optimization pipeline on the VNTANA Platform. Additionally, if you are running the plugin on a batch of files you will only be able to export ‘All’ colorways, however when handling the currently loaded project you will be able to select to export only the colorway that is currently open in VStitcher.
The VNTANA settings refer to the same settings you can adjust when uploading an asset to a product on the VNTANA Platform. By default, our recommended settings for use with Browzwear files are populated, however should you choose to change any and land on a set of settings you feel give your assets the best outcome, the plugin automatically stores the settings from the latest session and defaults to those instead so you don’t have to adjust them every time.
Tags and Attributes
The final screen gives you the option of adding Tags and / or Attributes to the products created by the plugin. This is optional and is applied broadly to all products created in that run of the plugin, so if there are any garment specific Tags or Attributes these will have to be created manually on the Platform.
This page is accessed via the dropdown menu by your username. This page contains a brief FAQ regarding the plugin and how or why it produces the outcome it does. The same information is available on this page.
Plugin Operations and Possible Issues
Regardless of whether the plugin is being run on the current project or a batch, it determines the export by pulling the latest snapshot that was created, not latest updated. If the outcome doesn’t look the way you expect, this may be the reason and you should verify within Browzwear that the snapshot the plugin will use is correct.
When running the plugin on a batch of files, it is important to understand what the plugin is doing to pull the files it will process. The directory that is set gets scanned for any .bw file, but the plugin has no way of knowing whether a .bw file is ready to be exported or not, other than in cases where there is no snapshot in which case it’ll just move on and not upload it. The most likely outcome of loading unintended files is just that they will be uploaded to the Platform, but it would result in more work after having to remove these files.
The scanning process is recursive, meaning it will search all subdirectories as well. We recommend placing files that are ready to be processed in one folder to avoid issues with processing unintended assets.
The option to update existing products instead of always creating a new product is available through the plugin. We understand the process can entail constant minor reworks as well as exploration into the best settings for your assets, and as such having the ability to push an edit through to an existing product without needing to then delete the old product while still being able to create multiple of one asset with various settings to compare is important.
When importing a garment into VStitcher, a pop-up message can display for a number of reasons. These cannot be handled by the plugin and if left unresolved can cause the plugin to timeout or crash. These tend to relate to garments that have been designed on multiple workstations resulting in different versions for certain components such as avatars.
Re-Installing a Plugin
VStitcher has a tendency to crash when re-installing a plugin. This isn’t an indication of an issue with the plugin, but it can cause some confusion. Generally, just reopening VStitcher shows everything is fine, the newly updated plugin can be accessed from the plugin menu. Sometimes, however, when it crashes the ‘Plugins’ option will be removed from the top navigation bar despite the plugin still being loaded. When this happens, it can require a complete restart of your computer to get that menu option back.
An Authentication Token can be generated on the VNTANA Platform to allow secure authentication through the VStitcher and Clo plugins. Once used, this token will allow automatic authentication upon launching either plugin so long as the token isn’t revoked or regenerated, in which case you would simply need to login again through the plugins with a new token to resume automatic authentication.
To generate an Authentication Token, login to the VNTANA Platform and navigate to your profile settings by clicking ‘My Profile’ in the dropdown accessed via your profile picture.
From your profile settings, click on the “Authentication Key” tab, located towards the upper left of the webpage, to access the key generation screen.
The first time you visit this tab you will simply see a button labeled “Generate”, clicking this will generate the Authentication Token for your user account. You can click the copy icon on the right of the generated token to copy it to your clipboard or manually copy it.
As a security measure, you will only be able to copy the token for the first 30 seconds after it is generated. After this time you will have to regenerate a new token the same way should the need arise. Additionally, while a token is active you have the option to revoke it without generating a new one from the same screen.
- VStitcher 2021.3
- Windows, MacOS