FILE SIZE IS 300MB, It is causing very slow rendering.
I had Men's suit as below, before seam cut and sew, it was only 20 MB. But after applying all detail of sewing, it showed 300MB.
Checked all progress and pattern pieces by removing one by one, as below, it still shows 300MB. After removing Right side of check pattern, it became 2MB.
Removed the pattern piece only from the original suit, but still 300MB. It looks it is nothing to do with pattern or sewing.
Is there other hidden reason this file gets too big ? Please advise.
-
When you export you can choose to export the stitching as 3D (which exports each stitch you created in CLO3D seam as a 3D mesh object with many polygons) or you can export the stitching baked to the diffuse map as an image only. It depends what you are doing in your next workflow as to which you may prefer.
So if you untick the export top stitch, but include the > save with textures (Zip) file your stitching will only be exported as a baked seam texture image map into the diffuse layer. So two additional steps need to be checked 1) that you make the patterns in the 2D layout sit in the UV map in a reasonably tight packed layout. 2) that you have a pixel scale map resolution that works for the smallest detail (eg: stitching).
settings and some optional items (make map at least 4096 and maybe larger) for human garment size.
Scale your patterns into a good layout that will pack the UV to maximum. (You can resize this - see blue UV grid with handles - below)
Now when I open up my object file (without stitching exported) the main item mesh density is lighter weight as all the stitching is not exported. And the stitching is only in the diffuse map. However I now have no physical stitching high dense mesh in my 3D model to bake down in a texture workflow, which might not be desirable if I need that for texturing as a separate item. So this is very dependent on which you prefer to use in your final export model.
So give it a go and see which you prefer. If I am doing a texture bake for 3D stitching I would typically isolate that object mesh using a unique base color ID in the stitching within CLO3D, and 0mm bleed on that stitch map in my next workflow so I can split that out from the main model in an automated workflow.
Worth mentioning > CLO3D can also export the object nurbs (internal lines) which are lighter weight objects. So in some cases in my next workflow I use these to stroke in stitch instances, which can be more efficient in mesh count, should I need more detailed stitch texturing. There are a number of ways to overcome big datafiles.
1 -
Sorry, I might not be understanding.
I just need to render the suit, Rendering is not working at all for this size. There are no much of stitches, just many pattern, and no layers.
Do I need to Export suit to OBJ? Just for red, adding pattern image.
0 -
sudolisa, looks like you are on the MAC hardware.
You should be able to render inside CLO3d quite easily.
Check your garment scale is correct (human scale) and your mesh density should be in the 5-10mm distance. If you have done that your file should be a reasonable size. And judging from what you previously posted that sounds okay. Also make sure you haven't loaded crazy large texture maps in the fabrics.Assuming that is all kept to normal human scale, I cannot see why your file size is so large. Even with object top stitching the file size can be large BUT it should easily render inside CLO3D.
Did you load your own texture maps? If so how big were they ?
I would suggest saving out the 'garment' (only > not as a project) as a new file (copy) and then try opening that up and see how big the project is.
Try deleting the fabrics and see if the file size comes down. The object mode stitching can make a file size increase, but you can also set topstitches to use a texture instead of an object - see if that reduces file size. Object browser > Topstitch tab > select topstitch > Property editor > Type > change from object to Texture in drop down (arrow).
0 -
I found one of texture file was 300MB, changed it to smaller size, not 34 ZPRJ file. But for some reason, it does not give rendering...as below. Actually, I found other garment had 300 MB because it has same original texture, but it was OK at rendering regardless of size. Only file below is not working for rendering even though I adjusted size of texture.
Please help.
0 -
A single texture file should not be that large. So swap it out for another texture that is smaller. A good tiling texture can be quite small but still work well in render. Less than 16MB.
Hard to say what is causing that - it could be anything from your camera view point being wrong, to you having some hidden object obstructing the view. A lot of people make the mistake of having the lamp panel smack bang in front of their camera, when they render. have you checked for the basic setup issues.
In lighting make sure all lamps are toggled off from camera render view. It could be a simple obstruction in your camera angle, that only shows up at render time.
Go to Lights > And switch off from render view the 3 Rectangle lights and see if that makes a difference to your scene. You could light just using the HDRI (Dome light) and raise the light intensity up to check if that is the problem (a lamp obstruction in the render view frame).
Toggle off the 3 lamps > stop render > restart render to refresh the scene build > and see if that gets rid of that white area.
Also check your camera clipping plane is set to reasonable values. Switch off the Physical camera temporarily to check that it is not some depth of field or exposure value error. So just run a basic render no physical camera and see if that resolves the issue.
0 -
HI Ottoline,
Thanks for trying to help. I tried multiple ways to check Camera angle.. Brought the suit/avatar in different woman project. When the Men's jacket not on project, rendering works.
But when the jacket is on men, rendering not showing, only back ground. File size is total 46MB only.. it seems like my crazy suit causing unusual problem. I hope I can get some good solution, so I don't have same problem later again.
0 -
I would send that garment file to CLO3D and let them check it.
File it under odd behavior. I have never come across that fault in many years, so you may have something obscure in the patterns worth taking a 'closer technical look ' at.
0
Comments