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.
Comments
First off: Thanks for the reply and the suggestions. If you're willing to delve into this I'm all for it. It could get to be a long thread though, so maybe we should take it to a new topic?
My confusion with Branching begins at :34 in that video. Why does the new yellow branch come out of the space in between the "Revision A" spot and the open white circle? Looking closer, I think maybe the branch is intended to have a swoopy curvy beginning, but that swoopy curvy section is getting lost. It's blended in with the main branch, maybe? Some branches appear to be stemming from a revision spot, while others appear to be coming from an ambiguous part of a trunk. Here's an example from one of my documents:
The open "0" on both the main and the rev A branch means that if you go to either branch you are working with the latest revision. Make sense?
If not, send me an email at jmceleney <at> onshape <dot> com
John
I second what you are saying. Branches & versions are confusing. Its embarrassing to admit, but I do not understand branches and versions, therefore I do not use them.
I am sure this a very powerful feature. I have watched the video and webinar recording....still don't understand completely; I get lost in the cluster.
Versions & branches are not for engineering change control but rather data version.
If someone accidentally creates a version....how do you delete it?
I suspect people do not use branches, versions and merging like onshape had thought we would.
It is a new concept.
https://forum.onshape.com/discussion/3656/how-do-you-personally-use-branching-merging-and-versions
I think things will be more clear (or total chaos) after we get configurations/variants in. Now we have to use document versions (or copies) for creating another configuration of model.
With Alibre file system if I had to test something out of existing assembly without braking the original, my workflow was:
1. Create copy of assembly
2. Create new configurations of parts and edit as needed
3. Edit assembly copy to use those new configurations
4. Do same for all sub-assemblies..
With Onshape same situation:
1. Create version to keep original model unchanged
2. Make changes as needed
3. Edit linked docs and create version after edit
4. Update links in main assembly
ps. You can't delete a version at the moment but Onshape is fully aware that we need to do so every now and then.
Another thread for that version graph would be good, offline discussion can only benefit the participants.
Linked[in]
Linked[in]
It'd be nice if there were an automatic "take a stab at making this parametric" option. OK complicated things may fall outside the scope of this but say for an adapter plate with some holes in it it'd be nice to have a true solid built for the user. We could then add some dimensions to move features etc.
I'm sure it'll often be easier to reverse engineer using the mesh just for reference.
Owen S.
HWM-Water Ltd