Overview

Below you will find guidelines for product submission, packaging, quality control, and other guidelines for products in the Renderosity Marketplace.

What can you sell?

The Renderosity Marketplace welcomes products of all types, including but not limited to models, textures, props, morph targets animations, pose sets for existing models, software, and much more. We have products in the marketplace for a variety of different software programs including Vue, ZBrush, and of course Poser and DAZ Studio, and more, plus products for 2D programs as well. If you are not sure if what you have created is right for the marketplace, simply email us at vendors@renderosity.com with images of your product and a brief description.

Not Allowed!

Renderosity does not accept the following type of content:

• Poses or activity where any person (regardless of age) appears that they "could" be engaged in sexual activity.
• Items that appear "sexual in nature" or are intended for "adult audiences" (example: bondage gear).
• Products that display child or teen nudity.
• Re-distribution of a 3D product in 2D form whereas there is direct competition with the 3D product.

  Renderosity also reserves the right to decline content at our discretion.

Submitting Products

 Copyright Policies

Renderosity adheres to the Digital Millennium Copyright Act (DMCA). We take copyright and trademark violations very seriously. Please make sure you take some time to review our sites copyright policy.

There are many resources available in the marketplace for vendors to use in creating their own original products. On the product upload page, a space is provided to enter the names of the resources used, if any, to create your product. If you obtained resources from somewhere other than Renderosity, you will also need to submit a copy of the license or written permission from the copyright holder to Renderosity by email, fax or regular mail to Bondware, Inc in order to use the resources. This information will be filed in your vendor's file.

Although vendors are allowed to use other resources when they have purchased the rights to redistribute them and use them in their own commercial projects, Renderosity strongly encourages vendors to only sell items that are 100% their own. This will help to limit, and protect everyone from, copyright disputes.

 Product Testing

All products must be thoroughly beta-tested before being submitted to the Marketplace queue.

Once a product has been submitted, the product will be reviewed by our Quality Control Staff to determine whether it meets the standards of quality we have set for the Marketplace. Once accepted, your product will be thoroughly tested by our team, and if there are too many technical issues it will be failed, as determined by our Testers.

• Renderosity allows each artist to upload their store items. If you have any difficulty uploading please submit a support ticket at Renderosity Support for assistance.
• Each vendor may have a maximum of five (5) products uploaded to Review/Pending queue at one time.
• The product may be placed in a maximum of four(4) marketplace departments. Please target your department choices as precisely as you can. If someone would not buy the item for the flip flops you've included with the beachwear, please don't choose footwear. These must be relevant to the product. Any item listing found to be in unrelated departments will be corrected by the marketplace staff.
• The "Product Description", is a text-only area that is required for every product. In addition to whatever information you feel is necessary, a brief, yet complete and detailed description of your product should be entered here, and must also include the following specific information:
  • Complete contents of your package.
  • Product name and URL for any required products.
  • The software and specific versions required to use your product.
  • A full list of morphs included in your product, if applicable.

  If your files have problems or do not follow the submission guidelines, we will delete your submission and the testing results will be placed on the Product Communications Page.

 Failed Product Process

If your product is tested and failures are found, you will be contacted by the tester via the Product Communications Page with the information regarding the failures.

Should an item fail, when the vendor has corrected the issues and replaced the files, they must contact the tester via the Product Communications Page. 

If the product is tested and fails a second time, you will be contacted again regarding the failures.

If your product is re-tested a third time and it fails, you will be notified and the product will be deleted from the testing queue. The product will be eligible for consideration again after thirty (30) days, and the names of two (2) beta testers along with their testing reports must be submitted to us before we will accept it again.

If a Marketplace Tester, Admin, or Review Staff personnel contacts you for any reason regarding one of your products, and you do not reply after seven (7) days time, the product will be deleted from the testing queue.

Product Packaging

 Acceptable File Formats

All files should adhere to the proper file structure for the software it is intended to be used in. Poser products should follow the path :Runtime: ..., etc..

• PC Only: Files may be submitted as a .ZIP. - in some cases (software, video tutorials), a .rar file is acceptable.

If your product is intended for 2 or more different programs you must upload a complete product zip for each software the product is intended to work in/for. For example if your product is for Poser and Daz Studio you will need to upload a product zip for each program. These should be full product files. This way if a buyer uses Poser only, they can download the Poser files only. If your product is for Daz Studio the buyer will need to download only the Daz Studio Files.

All zip names should be titled "PRODUCTNAME.zip" If your item contains multiple zips, they should be named accordingly such as "ProductName_01.zip", "ProductName_02.zip", OR "ProductNamePart1.zip", "ProductNamePart2.zip"

  Products that do not adhere to the above standard will fail.

  For additional information on Paths please see our Creating File Paths for Poser Products Tutorial.

 Required Files

Each product zip file must contain the following:

• A ReadMe File
• Product name, copyright statement & date
• Vendor name (email addresses are not permitted within the online readme file)
• Product description
• System requirements (PC, MAC, or PC/MAC and compatible software versions)
• Needed files: Any 3rd party files needed for the product to function. Product/products name. A direct link is not required in readme file.
• Installation instructions
• Usage tips/limitations
• Complete list of morphs (if product contains morphs)
• Files list (Exact folder and file name listing) This listing should include the required Documentation folder and the files required in that folder. i.e. Readme file and Renderosity License files as show: Documentation(productname)readme.txt and renderositylicense.txt
• Product files
• All files required to make the product functional should be included.
• Nested files are not allowed for DAZ Studio or Poser Content. We must see Documentation, Data, People, Runtime, etc when we open the zip file. We do not use Content or My Library for DAZ Studio Products.
• Readme and License must be contained within a Documentation folder. The Documentation folder should be in the root of the zip (not within the Runtime: path)….. The Readme file must be named "ProductName_Readme" to avoid Readme files overwriting other Readme's.
• License file

 Important In order to ensure that future updates to our licenses are in force and effective immediately when any changes may have to be made, the license file should contain ALL of the following text.

VISIT THE LINK BELOW AND READ THE RENDEROSITY END USER LICENSE AGREEMENT (EULA)FOR THIS PRODUCT.

http://www.renderosity.com/renderosity-licenses-cms-17254

Renderosity has two license options, and it is very important to make sure you read and understand the correct license before using our products. All Renderosity products use this STANDARD LICENSE as of April 1, 2014 regardless of when purchased, unless products specifically have "EXTENDED LICENSE" in the title. If you have any questions, or do not agree to the terms of our license, please email license@renderosity.com.

  Most applications other than Poser don't require files to be distributed to sub-folders. For non-Poser-based packages we do not require the ZIP file paths to adhere to the Poser standard listed above.

Quality Standards

General

• All models will contain either tri's or quad's (3-or 4-sided polygons). Ngons (5 sides polygons) do not behave well in Poser or in Daz Studio. This will be evident when testing the product … the mesh or model will have polygons that are visibly different from those surrounding it, be lighter or darker in appearance when they should not be, etc. More times than not, this may not cause a problem in Poser that needs to be addressed but will show up in Daz Studio.
• All Poser models should be in .obj format. DAZ Studio models use .duf
• All products must include texture templates for the models included in the product if applicable. Templates are to be included in a separate zip file.
• Poser files (.cr2s, pz3s, etc) should never include mesh data (embedded geometry/object). Objects should be stored in the geometry folder, and should be pointed to with the proper path within the file.
• UV Mapping should be optimal for models. In other words, there should be little-to-no distortion or stretching when applied to the model, and no seams should be visible except where they are intended.
• All thumbnails in Poser must be uniform in appearance, and appropriately sized and have a graphical representation of the item (figure, prop, mat pose, pose, camera, light, etc...)
• Checkered .jpg must be applied to all models to check for UV stretching and distortions
• Any files that aren't needed for the product to function are not to be included in the product zip, such as thumbs.db, .ini, etc….
• For any product containing more than one zip, the only file that is acceptable be duplicated in each of the zips is the Readme file. Duplicating product files between zips is not acceptable.
• All file names such as .obj's, pp2's and all texture names must be distinct in naming. Using your vendor initials or part of the product name in the naming of these files will avoid issues in testing and distribution. Generic file naming such as 1.jpg or back.jpg or hat.obj is not acceptable.

Clothing

• All clothing models should include at least one base texture.
• It is recommended but not mandatory that morphs included in clothing that correspond to morphs in the intended figures, should cross talk, and should also include corresponding JCM's.
• All models that incorporate handles should also include mat poses to HIDE or SHOW the handles; handles should not show up in renders.
• Poser clothing should have at least 4 of the full body morphs that come with the base figure for which it is modeled, and it is preferred to also have a reasonable number of the most widely used partial body morphs in order to make the product more marketable. DAZ Studio Users expect all clothing to fit everyone.
• Dials for any extra morphs included in the clothing should be appropriately named so they are easily understood, i.e. Skirt Shorter, TopUp_L, etc., and should function accordingly.
• Textures included with clothing should be realistically scaled and also scaled consistently across groups.
• All clothing and accessories should be modeled to a reasonable standard of fit and quality according to the style of the clothing and the character for which it is intended to be used.
• Adjustment morphs should be included for any problem areas of clothing where poke-thru or fitting problems could occur, or where clothing requires special posing.
• All clothing items need to be tested with each morph included, and posed using each of the character's poses included with the figure…. i.e., each article of clothing must be applied and each pose must be used when testing with and without included morphs in clothing.

Props

• Unless it is parented to another prop, OR all the props in a particular package or library are required to land in a specific position in order to create a multi-prop "scene", all props must load in zero position on the x,y, and z axis, with no rotations applied.
• Props created to be worn by or used by a character (jewelry or a sword), should be smart-propped in the appropriate position. Props that are to be used by a character, if applicable, must include corresponding hand poses for that prop.

Morphs

• "Custom" morphs created for sale and distribution should be completely unique and cannot be derived from morphs included in an existing product as a base for your own product.
• The only exceptions are "injection pose files" which are created to use in character packages that basically use values only on the existing morphs/dials in a specific character, in which case the morphs for that character would be required to have been previously purchased in order to use the injection pose files included in the product, and should be listed as a needed/required product.
• Custom morphs must follow the following path:
  • Runtime:Libraries:Morphs:yourdirectoryname

Poses

• Poses should not contain any morph information unless it is specifically created to include them.
• Poses should be created with as much realism as possible, with logical movement and positioning, i.e. feet on the floor in standing positions, butt on the floor or chair when sitting, no hands or fingers poking through hips, and no contortionist positions (unless it's on purpose, and in that case, should be noted in the readme file).
• IK should be turned off for all poses saved.
• The Poser thumbnail must depict the pose that it's actually applying

Textures

• Products that include textures either for an existing product or for models included in the package, should include MAT pose files to apply those textures and/or .mc6 or .mt5 files (whichever are more appropriate to the specific product.
• Texture files should be in .jpg or .png format, unless the product's functionality or intended appearance requires another file format such as .tif, etc.
• Texture files should have distinctive naming. 1.jpg or red.jpg etc are not acceptable naming. The textures should use a part of the product name or first few letters of vendor name/product to be distinct.li>
• Repeated product submissions with multiple looks and similarities will not be accepted. We want unique products in the marketplace.

Pricing

 Pricing

All prices are minimums, anything above this is up to the individual vendor. There is no ceiling on prices you choose to set.

For a breakdown on minimum pricing read the Minimum Pricing Guidelines.

  Prices are subject to change at the discretion of Renderosity Staff. Pricing guidelines are also subject to change.

Product Naming

 Product Naming

When deciding upon a name for your product, we encourage you to search the marketplace for your prospective names in order to find out if a current product carries the same name

As a matter of professional courtesy and ethics among vendors, we discourage you to use names that are already used on current products in the marketplace, and using creativity and originality in your naming process.

If a product enters the MarketPlace with the exact name of an existing product, and a Vendor lodges a complaint to the Store staff the Vendor with the newest product will be asked to rename their product. If the vendor refuses to rename the product it will not be released into the MarketPlace. Renderosity will not search for naming conflict. This should be done by the Vendor prior to submitting a product to the MarketPlace.

Vendors should always try to work this out prior to engaging the Store Staff. If a resolution can't be reached in a professional manner between the vendors, the Store Staff will assist in this process.

If your product name is Trademarked please send the Trademark registration information to copyrights@renderosity.com

Product Promotion

 Promotion

Your product promotions can make the difference between a mediocre seller or a best seller. Potential customers base their buying decisions directly on the images in your product page, so you want to spend a good amount of time and attention on accurately representing your product, while displaying it in the best way possible.

Here are a few things to consider:

• Avoid noisy/busy backgrounds … neutral colors for backgrounds and accents work best.
• Use the highest quality settings for your renders … 3 great renders that take a bit more time are better than 6 quick ones.
• Present your product creatively and according to your vision of how you want it to look.
• Make sure to highlight all of the content and options available with your product.
• Make sure you show your product from all angles and POVs.

 Marketplace Links

Refer to the guidelines below when placing links throughout the marketplace.

 Image Guidelines

Refer to the guidelines below when uploading images for products.

 Important  Additional Requirements

• There must be a minimum of 3 additional/lightbox images on your product page.
• Any image that displays nudity should be marked "yes" on the content advisory directly under the upload buttons.
• You must display a front, back and side view unless not appropriate.
• Promos for clothing and accessories must include images that utilize at least 5 different poses.
• Promos for clothing and accessories must include images of the clothing with at least 3 obviously different morphs (i.e. Voluptuous, Aiko, Thin).
• Promos for clothing textures must also display the front back and sides of the item so folks can clearly see what they are buying.
• Renders for promotional images must be done in the program for which the product is intended. i.e. If your product is under the Poser category and listed as Poser required to use the product you must do the promotional image renders in Poser. If your product states it is also compatible with Daz Studio and Daz Studio is listed as a department for your product then you must provide at least one render that is done in Daz Studio and label that image as being done in said program. (if your product is for poser only it is not necessary to label your images but they are required to be done in poser. Same is true for Daz Studio...if the product is Daz Studio only you are not required to label the images but they are required to be rendered in that program.) If your product is for Vue the same is true and you must provide renders that are done in Vue. Maya, 3D Studio ...etc. At least one render for each program specified is required to show the entire product being sold. So if your product is a character for example, the render must show the entire character both from and back views to show morphs and skin textures being sold in the product. If your product is a props set/scene the same is true. The entire scene and all props must be shown in renders for each program.
• Example images of your product should not be altered with post production render touch-ups intended to alter the appearance of the model. To assist customers with their purchasing decisions, these pictures are intended to be an accurate representation of the product without adjustments.
• Off site links are not allowed within the thumbnail, promotional images, promotional wording or readme.txt file for your MarketPlace product except as outlined in the table above.
• Off site links to products that are required for your product to function must be included in your promotional wording and readme.txt file and the link is required to resolve directly to the main page of the required product.
• The product thumbnail, main image, and the promotional image may not contain any nudity and must follow the nudity guidelines.

Content Guidelines

Nudity

Refer to the guidelines on nudity below when uploading products throughout the marketplace.

• No nudity. This implies no clothes, clothes that are transparent or blurring of nude images.
• Tasteful breast exposure. No areola or nipple exposure, and no transparent fabric. 50 % of the breasts must be covered.
• No exposed buttocks - more exposure than a standard bikini bottom would constitute nudity.
• No suggestive or sexual positioning.
• No child nudity.
• Promotional images should not be sexually suggestive or erotic.
• No Sexually Suggestive Language, images or "Censored" language/images.

Note: Additional Promo Images may contain nudity if applicable to the product, but must be marked as such with a check mark in the Content Advisory box..

 Character and/or Texture packages for the following figures are not allowed to be shown nude in any promotional images in the MarketPlace: Mill Kids and Rosy Cheeks Lina

 If a character/texture package for any other model appears too young for nude exposure by the majority of the Admin Team, you will be advised and asked to provide images containing no nudity.

 Due to the definition of Minor according to United States Law, we will not allow any nude pictures of children in The MarketPlace. This includes products advertised as teens, pre-adolescents, child-like fairies, etc...

 Additionally, any image can be removed at the discretion of staff if it is deemed unsuitable for this community.

Violence

No depictions of injury being caused to any living creature.

Includes, but is not limited to injury from either:

• Piercing or edged weapons/tools
• Projectiles
• Fire or chemical burns
• Blunt force trauma
• Punching, kicking, slapping, strangulation or crushing

Shippables

Reselling opportunities for software development companies are available. Contact vendors@renderosity.com for reseller options.