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: Improvements to Onshape - September 20th, 2024

@NeilCooke I have plenty of instances where the console output becomes difficult to parse due to volume. We import in a lot of configured Part Studios and sometimes we intentionally break features in those Part Studios to create correct information (or lack of information). This can cause a large amount of overflow error messages which can make it tricky when debugging. And good luck if I accidentally left a debug or println in a custom feature used in that imported part studio, because those will carry over too.

I've had some challenges in identifying where a debug or println is coming from. I didn't think about using the feature id, that will be helpful for now. But I really like your idea about showing messages from features being edited. I think it would also be nice to see what features are generating what FS console output, since sometimes they do not directly come from the feature being edited, like when using Derive. I could see that getting tricky though, because you might care about which feature is generating the output but you also might care about which feature studio the output is sent from, especially in cases where a feature studio is importing a library of function from another feature studio.

chadstoltzfus

Re: Drawing Revision Table does not reflect part.

@Jonathan_Hockaday The revision table is pulling metadata and history information for the drawing tab. Most companies use it and want it this way. We do have an improvement request to make tables that refer to the metadata for the reference(s) contained within the drawing. Keep in mind you can also release drawings separately from their references, so that might provide a challenge if the table was connecting to different release events versus the drawing itself.

The revision description in your image above is a property of the drawing tab itself. You can edit this directly in the table for the next not released revision entry, AND you can also edit this in the properties dialog for the drawing tab. Additionally, you can visit the drawing tab in the version of the document where this drawing was released, and edit the revision description there. Anywhere this revision shows, is then edited in all versions or workspaces where the drawing lives. Company admins can restrict the ability to edit metadata for released components to just admins, but it is handy to correct things like spelling mistakes if this does not violate your company practices.

The table itself has template controls under company Release Management settings as seen here:

You can add/remove different columns that are mapped to different metadata.

I'd suggest submitting support tickets if you have more needs or questions here.

PeteYodis

Re: Maneuvering in the 3d Space

While a WASD free-flying mode actually would be cool, in my personal opinion, there's a meaningful difference between game navigation and design software navigation (which is very standard - it's not unique to CAD). In a game, you're the pivot. You're moving yourself. In CAD, you're moving relative to whatever you're working on, so it's more in line with the paradigm to prefer controls that make that easier, rather than free-form movement.

Besides, even in standard video game controls, there's a lot of variation. Inverted pitch controls, different names and conventions for buttons, etc.

It surprises me that kids get turned off design software primarily because of the controls. I'd assume it would be because of the learning curve. How much have you seen this happen?

_anton

Re: upper level assemblies are not updating automatically when lower level sub-assemblies are updated

I had a similar issue. billy2's response is insightful. OnShape only pushes changes from sub-assemblies to a higher level if they are made by a mate connector. If you simply move something around without the positioning being defined by a mate connector, it won't be pushed to the higher level.

rokerson

Re: How to mate a bracket to an extrusion

I was going to say you should practice with editing the mate connector themselves, using re-align and offsets (instead of just using offset in the mate feature itself).
For these I just use the hole in the center as the reference on the profile side (and offset by 1/2 the profile width).
You could also define an explicit mate connector on the bracket that is 1/2 the profile width away to save time (only really helps if you don't use the bracket on different size channels).

There's an example here:
https://forum.onshape.com/discussion/comment/87424#Comment_87424

eric_pesty

Re: How to mate a bracket to an extrusion

It might be better to add a mate connector to the flat face and then use the move option to rotate it 90 degrees. Unless you are in control of the draft on the bracket, adding 5 degrees in the mate connector definition is dangerous if the draft changes.