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.
Practical limit to model size?
øyvind_kaurstad
Member Posts: 234 ✭✭✭
As I wrote in this thread: https://forum.onshape.com/discussion/2694/after-using-onshape-for-a-few-months, I have spent a lot of time waiting for Onshape while working on this particular model. The worst waiting is (naturally) when going back in history to do some modifications. Everything is then quite slow, and in many cases there are no indication (not even the spinner) to show that Onshape is working. While I had kind of hoped that someone from Onshape would reply to that thread (I feel I raised some valid issues), that hasn't happened (at least not yet).
My experience with that model tells me that it is too large for Onshape to handle with decent speed, so I am wondering how large models other people make with Onshape? I do realize that this is a difficult question, because it largely depends not only of the number of features, but also what kind of features are used. Some are more computational intensive than others, probably causing even more slowdowns than "lighter" features.
Here's a screenshot with model statistics of the model I am talking about:
As you can see, my model has a lot of arcs and splines (and sweeps), which is probably giving Onshape servers some additional work.
Am I asking too much when I want to have a model of this size and complexity in a tool like Onshape?
My experience with that model tells me that it is too large for Onshape to handle with decent speed, so I am wondering how large models other people make with Onshape? I do realize that this is a difficult question, because it largely depends not only of the number of features, but also what kind of features are used. Some are more computational intensive than others, probably causing even more slowdowns than "lighter" features.
Here's a screenshot with model statistics of the model I am talking about:
As you can see, my model has a lot of arcs and splines (and sweeps), which is probably giving Onshape servers some additional work.
Am I asking too much when I want to have a model of this size and complexity in a tool like Onshape?
0
Comments
I may be reaching out to you privately to ask if you would be willing to share this with us so that we may run a performance profile against it (we cannot see anyone's data unless they explicitly share it with us). Thank you.
https://www.youtube.com/watch?v=8waFJVV6c8s
This is the model statistics for a project I am working on, all mechanical, I am starting to feel like we are running out of grunt but hopefully not. I am also trying to think of strategies to improve performance but hoping I don't have to use these.
This is assembly only has half the parts included at this stage, I am about to start filling it out with the rest, will be very interesting to see the result's. There will be also hundreds of bolts and nuts but I don't think I'll be able to include these. Would like to show some pictures but still confidential.
Twitter: @onshapetricks & @babart1977
Would be interested to hear how you get along with working on this model, as I have a feeling that in it's current state, Onshape has some challenges when model sizes starts getting large.
projektowanieproduktow.wordpress.com
projektowanieproduktow.wordpress.com
https://forum.onshape.com/discussion/2583/how-to-model-a-marble-track
I hadn't gone back to see your previous concept in the end of that thread and am absolutely floored at the execution of the concept. How robust is the model? It looked like Michal had made OnShape do some serious tricks to even get the proof of concept to work without 3d sketching tools, so seeing this finished product is amazing. Absolutely amazing work.
I will not incorrectly capitalize Onshape
I will not incorrectly capitalize Onshape
I will not incorrectly capitalize Onshape
I will not incorrectly capitalize Onshape
I will not incorrectly capitalize Onshape
I don't think the model can be called robust, there are way too many workarounds and shady techniques (and I was also a bit too lazy regarding constraints), but the result is still quite good. And Onshape really generates extremely clean STL files. No repairing necessary whatsoever.
@philip_thomas Nudge, Nudge, OnShape, OnShape. :-)
Duly noted, but I guess if I were staying with current capitalization conventions for other modeling packages, I should be spelling it ONSHAPE. Old habits, I guess. I blame the app on my phone for making me want to capitalize the letters.
Sorry for the tangent, just some musings that I had recently that I didn't think warranted its own thread.
For Matthew - yes the physical limit is a cubic kilometer. From my previous life at SolidWorks and my work in Oil and Gas, components are modelled at life size and then for mockups, scaled to 1:10 and assembled for for full sea level to sea floor representations. This would work for mines as well. Don't forget though that pipes (and mine shafts) tend to look very thin at these scales. This technique while it works, is rarely used.
Did you link to this model? Would be interesting to study your way of doing it;) Takk så meget for det;)
HWM-Water Ltd
It is also full of very 'expensive' operations.
My first reactions are;
1) From the feature statistics, what is the total regen time? This number is the total modeling server 'thinking' time - nothing to do with facetization or data transmission. If there are any 'very time consuming' features (more than a few seconds), then we should be looking at those.
2) I suspect that the part resolution is turned up very high. From lowest to highest, there are orders of magnitude more facets being created - that all takes time. Try setting the part resolutions to 'automatic' - chances are that will speed things up.
Happy to look at the model if you chose to share a link. That said, there is no way that this is 'beyond' Onshape
I think it is @øyvind_kaurstad 's model
IR for AS/NZS 1100
HWM-Water Ltd
HWM-Water Ltd
Where can I find such hidden shortcuts?
HWM-Water Ltd