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.
Options
Comments
A lot of those "really smart people" among others of course came from building Solidworks back in 1995 (and later years)
What's interesting is back in 1995, SW UI and workflows echoed the Windows UI that most everyone was already accustomed to then as Windows was becoming mainstream upon release.
Now fast forward 20+ years of experience building today's most popular design tool and DS shoving an ecosystem and experience that nobody knows what it is or even wants.
Just a few short years into Onshape development another similar theme that made SW successful back in 95 is happening again now, but with Onshape. "Everyone" knows how to use an internet browser - EVERYONE. The "Browser" represents the new "Windows" paradigm today in that people are familiar with the "Tabbed" workflows and added the mostly transparent "Cloud" of Amazon servers behind the scenes. Take that a new generation of young people who are familiar with "Google Docs" workflows and ice the cake with collaborative design - wow. An engineering manager with any forward thinking should be able to start to see how to leverage this and scale people where needed.
For example, right now a project is almost done by an individual, but the drawings need to be completed and released to manufacturing; prints are needed yesterday. Another person(s) can start detailing the parts and this is where it gets interesting. You could have potentially X number of people to start producing drawings from anywhere on the globe and scale as needed depending on how big the job is. You have 100 components you need drawings for? You could have 2,5,10 or 100 people creating drawings of different parts at the same time to shorten that time-to-completion linearly or even exponentially. I see this collaborative drawings effort in larger companies really showcase Onshape aside from collaborative design as Onshape becomes more widespread as it obviously matures.
It's a beautiful thing to watch evolve and be a part of again 20+ years later!
As far as the smooth transitions go, I believe this is revolutionary that Onshape users just take for granted. Gaming systems have to wait to download and install updates even today; they're not even caught up yet this generation.
This SW thread in my opinon aside from many other aspects of course is why Onshape will become king.
https://forum.solidworks.com/thread/223031
Now it's just:
(1) did my computer turn on? YES!
(2) does chrome still work like it did the day before? YES!
(3) is Onshape ready to go? YES, you know it is!
HWM-Water Ltd
A drawing is simple and vividly clear about everything someone needs to know about a specific part with very little training.
I cannot see drawings going away any time soon. At least until all the old soft headed people who have a hard time keeping up with future tech die off from an asteroid strike... We will need drawings as they are still in charge, and will not even attempt learning new skills.
Most (all but 2) of my customers only have 2D cad, and require at least a plan view of everything. And it is painful to not have blocks available through export, because all lines are just dumb lines, and when you have an engine block with 1,000 radius and contours sitting in your machine and you need to select every line and change it to "Red" "Phantom 2". It means there is still work that needs to be done in Onshape's drawings to be ready to slow down progress in that area.
So until then, I (and many others) require drawings to have as much dedication to the code as the 3D side.
Have you tried reducing the tessellation quality on parts that don't require it?
Can you simplify some parts in your assembly?
Have you used the feedback tool to ask for help from the support team?
How good is your internet?
IR for AS/NZS 1100
Would be helpful to have some information like this. Will try and split up work into different documents. I have a lot of tabs but, how can you get around that?
You can create a version of the document and then tell your top level sub-assemblies to be set to that version. I can attest to the increase in performance. Last fall I was working on a large project, top level assembly was about 65 feet long, it had very long load times and by versioning the top level assembly it drastically reduced load times and click performance.
If you are importing engine models, it may be worth the time to create those subassemblies. You can also version individual parts in those assemblies. It seems to help with Onshape loading times when you give a version for it to point to
Loading Studio Data
It just keeps on spinning for ten minutes with virtually no network activity.
This means I am even more excited about a future that includes folders in the feature tree! Given that we really need keyboard control of the rollback bar, what keys would work for <up>, <down>, <top of tree>, <end of tree>, <over closed folder>, <into closed folder>? Or do we forget the last two and use the mouse to open and close folders as needed?
HWM-Water Ltd
I'd also rather use Page Up/Down for navigating the feature tree
IR for AS/NZS 1100
sequence.
Twitter: @onshapetricks & @babart1977
Another longtime wish for assemblies is a tree search tool.
Twitter: @onshapetricks & @babart1977
Suggestion: Please start the thread with a clear description of what the issues are that precipitated folders being suggested as a solution. I think I know what the issues are, but I would like to see some clear consensus from the masses.
Given my understanding of what the issues are I do not see folders as an optimal solution. I would like to know more.
I've been slowly but surely going through all of the Learning Path Center training and tutorials etc... Below is another example of using the Mate Connector as an origin definition for In-Context creation of new Part Studio.