Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Assembly Tri Count/Primitives
Jonathan_Hutchinson
Member Posts: 93 PRO
I'm trying to understand how to make an assembly a little more performant. I've stumbled upon the mesh coarseness display settings in appearances (beside the point, not a good place I feel). Are those coarseness settings, and mesh densities of parts, carried downstream into the assemblies those parts are inserted into? So following the logic that If I Reduce part appearance coarseness then the subsequent assemblies should display/Regen a bit better too?
This is a little bit painful as I would then, for certain part studios, need to create a version and update assemblies so as to insert the 'coarsened' appearance setting. This feels like kinda a lot of effort to me, when the mesh coarseness setting could be set at an assembly level? i.e. : please insert coarse meshes of these solid parts. There seem to be a few other places to dial in tesselation settings as well, such as the auto-tesselate/best-tesselate and high quality tesselate from the other lil menu thingy (that I only really used for named views and changing to perspective camera).
Comments
Leaving things on Auto should normally be fine. When you say you want it to be more performant, do you mean loading, spinning, or assembly motion?
How does your system look on https://cad.onshape.com/check ?
What does the performance button say about your assembly tab?
Looking at the auto, most things are tessellated finely (by default? document property maybe?). The mate solve time is for sure the thing that needs to be improved in the Assy in question, but also the tri Count was around 20mil. My system is very bad for sure, just a Chromebook, but I also experience the same on decent workstations.
Another thought was whether standard content tessellation settings is considered as well? I'm pretty sure these are things people will have already asked at some point, though.
What did your stats look like for the check? Depending on your Chromebook, the graphics performance could be a big bottleneck. Also just your basic internet speed is pretty important.
You still haven't really explained which issue is bothering you - loading time, spinning lag, or assembly motion. These can be somewhat separate things.