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: Regarding storage capacity, user limits, and PLM integration
- Storage is cheap these days. Onshape's cloud storage and compute is all based on AWS. You'll find that documents that haven't been touched in a while will take longer to load. Documents that were last touched by someone on your team halfway around the world may also take longer to load. I don't know the details, but I can infer that there are different levels of storage at the various Onshape AWS sites, and that when something has been active on a different server, it may take a moment to sync the changes around the world. Having managed Solidworks PDM Pro between the US and China (and trying to keep the syncing working smoothly), and spent a lot of time with my then CIO on server costs etc, I really don't want to waste my life on those details ever again.
- The free version of Onshape is for non-commercial work only. I doubt anyone is paying for windchill for their hobbies. I have no clue about Onshape/Windchill integrations. Arena (also owned by PTC) has a first party integration which is supposed to work well.
S1mon
Re: Emojis within feature notifications 😀☠️💣
Love doing that. It also support unicode, so you can name your features in style with a unicode text converter.
Re: Improvements to Onshape - September 19th, 2025
Correct, that's why Onshape gave us a way to make our own library
https://cad.onshape.com/help/Content/frame.htm#creating-profile-library
Re: Improvements to Onshape - September 19th, 2025
This is the only reason I have my own pipe size frame profile is so I can list the actual dimensions of the pipe and the DIN equivalent name for the same exact product so I can delete conversations from my life about how 2" pipe has no dimensions on it that measure 2" and yes, that European cartridge filter will definitely fit it because it was designed to.
The number of times someone has told me confidently and incorrectly that pipe was measured by ID is staggering.
Re: Improvements to Onshape - September 19th, 2025
yep, thats what I mean. It is misleading
The metric one might be better labelled as 38x89 cls in parenthesis, for example. Because that's a size that everyone knows over here (which is 1.5"x3.5"). I've not measured the section sizes of the frame it builds, sorry. I just looked at the metric options and though that I can't actually buy those sizes with out getting them custom planed from larger stock.
Re: Improvements to Onshape - September 19th, 2025
The 2"x 4" is actually 1.5"x3.5" if that's what your referring to. It is a bit misleading to have it labeled the way it is. It should be labeled 2x4 without the inch marks. and/or have the actual size in parenthesis.
MDesign
Re: New features for measurement: Relative Measure, Euler to MC, and MC to Euler
@Derek_Van_Allen_BD Onshape std library is generally written in terms of matrixes. You could certainly write a quat library for your own work, but (imo) the usual reasons for quats (performance, interpolation, and fewer matrix multiplys) don't make much improvement in Onshape. That said: if you write it I will read it!
For avoiding gimbal lock and such: I'd recommend just using the rotation matrix transforms. Onshape has some utilities builtin to make this type of code a little simpler to write but it's still pretty error-prone. In fact: The blog post will mostly be a recitation of the many (many) numerical and programmatic mistakes one person can make when trying to implement euler angle tools!
@eric_pesty Strong agreement. I think @GregBrown identified a core pain point that needs addressing which is why he wanted to write these tools. Onshape dev team has a lot of stuff on their plate so who knows the timing? But they are aware of the need.
jnewth