Ideal Poly Count / Vertex Count / Quad vs Tris for Verge3D

GLiFTeK wrote:

Also, I am wondering whether the verge3d engine prefers tris vs quads.
I say this because some other engines prefer tris, others quads.

If you plan to bake a normal map, so you need to use only trys on your mesh. If you plan to create a middle-poly mesh for yor product so batter choice is polugons.

GLiFTeK wrote:

Also, I had issues with transparency sorting, (backfaces showing through “wireframe textured see-through” materials) and those (BAD) artifacts were solved by making quads to tris.

Yes, it’s a problem of transperency and triangulation (in fact if n-gons exist in).

GLiFTeK wrote:

I think this info would be very important in the User Manual for beginners.

We prepearing a big article (and video lecture) about difficulties in making of a web-application, it will come in two weeks.

Branden Coker wrote:

What are good limits for vertex count and item count?

We recomend to stop between 300,000-500,000 tris per scene.

Branden Coker wrote:

How does animation affect file size/load times?

It will encrease size of the bin files, exporting and loading time if you especially have long animations.

Branden Coker wrote:

Best practices for texture sizes and count.

Use compressed JPG instead PNG, use png only for normal maps. Try avoid alpha channel, especially if it’s not used. Sometimes different softwares produce png images with empty alpha channel and that increase size of the image. Try to keep all maps under 1024×1024. Small tilable maps for noizes and repeated patterns instead of baking them for the whole model.

Branden Coker wrote:

How does shader network (nodes) complexity affect file size?

Try to keep it simple as possible, keep your materials under 50-60 nodes each.

Branden Coker wrote:

Two of current WIP applications can be seen here:

Let’s look at your app. On some textures for example.
This image can be replaces with simple noise maximum 256×256 size.

Here you can use simple b/w jpg texture as mask instead of using heavy PNG with alpha.

Here you also can use small tilable texture.

Better to redo your UV-map to make it more compact. You can use for that UVMapPacker or Shortpacker plugins for Blender. This will allow you to use less image size but keep the quality of image for the model.

Also better to bake all shadows and AO to textures instead of using dynamic SSAO and shadows. Also you can use simple studio HDRI light instead of multiple light sources in the scene.
For normal mapping better to use simple tilable textures instead of gray images with bump. It gives better looking result.

Branden Coker wrote:

Hi Mikhail, I’m just wondering if you’ve had a chance to work on the article that you mentioned.

Unfortunally we all busy with the first Verge3D for Maya releas, may be when it will be ready I’ll have some free time.

Hi Mikhail, thanks for taking the time to write this. These are great pointers. We’ll start implementing some of these right away.

Cheers,
Branden