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.
Best Of
Re: Vendor/Customer Sharing
@S1mon and @jonathan_b List views has more room to run and structure view will be like the other side of that coin (working on it) where related drawings are shown. Structure view will present your latest released products in a much more natural and intuitive way - where you will be able to navigate the levels of your product and browse to find what you are looking for. Recursive views (views looking within all subfolders) are a natural fit for both list and structure views and still remains on us to deliver. Where used is not meant as an easy consumption type view - it's meant to be used as a part of impact analysis when considering ramifications of changes to your products.
I wouldn't expect Arena to be the answer here either.
We'll have more to do in list and structure views than what's mentioned here - but this is really the start of component based views that make more sense and are document agnostic. Non-cad consumers of the information would expect to see and interact with views like this as opposed to only monolithic documents.
I wouldn't expect Arena to be the answer here either.
We'll have more to do in list and structure views than what's mentioned here - but this is really the start of component based views that make more sense and are document agnostic. Non-cad consumers of the information would expect to see and interact with views like this as opposed to only monolithic documents.
Re: Whats the correct workflow for modular parts from seperate models
Any parts reusable across assemblies can be in their own 'document' to make them easy to keep track of and clean. Also study "CONFIGURATIONS" to make things like bearing assemblies and handles.
Individual mountain bike designs would want to be in separate documents.
Iterations of the same design with different sizes can be contained in one document using configurations.
Individual mountain bike designs would want to be in separate documents.
Iterations of the same design with different sizes can be contained in one document using configurations.
Re: Improvements to Onshape - July 19th, 2024
Is sheet metal planned for conical surfaces?
Re: Improvements to Onshape - July 19th, 2024
Don't know if it's something to do with my browser.... Dark mode won't stay on after I log out. I have changed in preferences and saved, but when I log back in, its white screen again. Anybody else get this?
Re: Forum Code Block's Broken
Not wanting to throw @lougallo under the bus, but I’m throwing him under the bus here.
Re: Hatching surface + GD&T surface leader
@Connor_LeCLaire I've created a ticket for your issue on hatching. We can discuss on that support ticket.
Regarding the need to attach datums directly to faces of parts in views - we don't support that yet, but it's something on our shorter term list to get to. You should see GDT supported next. We recently added support for surface finish and notes.
Regarding the need to attach datums directly to faces of parts in views - we don't support that yet, but it's something on our shorter term list to get to. You should see GDT supported next. We recently added support for surface finish and notes.