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: HELP!!!!!!
Another great reason to why the industry will transition away from file based workflow. ha.
MDesign
Re: Rethinking SolidWorks
Do they know that Fusion 360 will only let you be off line for so long. I had a chuckle when a friend wanted to demonstrate for a group how he could work without a connection. Then the program insisted that he sign in because he had been offline too long. There was no Wfi in the building. LOL
Re: [Chatbot Copilot] - We Built a FeatureScript AI Assistant That Outperforms ChatGPT
Congrats! Video demonstration?
The standard rate for integrated AI is around 10 to 15 USD / month. This is the cost of git copilot for visual studio which is a must have for quick questions and repetitive work or code clean up.
Assuming it is as useful as git copilot, I would pay 15 to 30 USD / month for a tool like this. It would need to be an integrated app in the Onshape app side panel, I wouldn't want to have to go to gpt's website for every question. Not sure Onshape allows apps for feature studios though, so it might need to be a web extension that can read the featurescript on the current page then insert or replace code.
Re: Optimizing Infill Space for a CADet
Model the lower part as a solid and then use a shell.
Re: EDITING TOOLS IN ONSHAPE DRAWINGS
Short answer is that these tools don't exist in the drawing environment, but there is a work around.
You can do it as sketches in a part studio and export to DXF and import into the drawing. It felt a bit dumb initially but it's actually quite flexible, I have setup a part studio with several sketches containing things like borders in one, a simple title block in another one, and more complete title block, etc…
The key to get the different ones to be placed correctly was to place a diagonal construction line matching the paper size in each sketch to import (bottom left to top right) and this way it will just come in centered on the page (and you just delete the one line).
Export Rules for parts in an assembly?
I've created export rules so that a part would be exported with ${partNumber} ${description}, but it does not seem to work if you export the tab of an assembly. It only applies to the top level of the assembly, not the parts themselves.
If someone outside of the company downloads a specific file, the export rules also don't work.
Am I doing something wrong here? Or are export rules that limited?
My usecase is this:
I've made an assembly, I've configured all of the meta data, I would like my purchasing team to share said assembly's publication to a vendor where they can download either specific parts or the entire assembly. I would prefer to not have to put all of the meta-data in the display name in onshape. Example: I have a part called a Dog House, it is part number 001, it has a description "Compartment Dog House". In the Bomb it displays correctly, however, in the exported file it's simple "Dog House", with no way to export the PN or description. Do I need to put them back in the name like I did with Solidworks?
Further, if that is the case, surely there is a way to create display names from the parts metadata, no?
Edit: Solved part of this, you are able to force export rules in the settings of a publication. (imo, this should be an opt out feature but w/e) There is still the issue that parts inside an assembly or part studios do not have rules applied.
This would be less of an issue if we could insert individual parts from part studios and assemblies, but since we can't, export rules don't seem to serve a purpose.
