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: Boolean Union operation to preserve holes from both tools
Hello Herb. After the transforms, create a sketch on either exposed face of the two parts, a parallel plane or a mate connector. Using the Use tool, capture all the holes you need. After the Boolean, use the sketch to extrude (remove) the holes in the part created by the Boolean. - Scotty
Why I Like Designing on Onshape Mobile
Hello everyone,
Based on my experience with various apps, the most challenging part of designing on a tablet is undoubtedly sketching. Drawing lines and aligning them can be frustrating compared to a PC.
Here is how Onshape by PTC handles these specific challenges:
🔹 Right Tap: It works just like a "Right-Click" on your computer. You simply tap with two fingers to see context menus (like 'View Normal To' or creating a new sketch) without searching for buttons.
🔹 Position Selector: This feature solves the precision issue. By tapping and dragging your pen, a cursor appears that lets you easily snap to the origin or align with other objects. It makes the hardest part of tablet CAD much easier.
🔹 Selection Box: If you have used other CAD tools, you are familiar with this standard: Dragging Left-to-Right creates a Blue box that selects only items fully inside. Dragging Right-to-Left creates a Yellow box that selects anything it touches. Onshape keeps this logic on the tablet. You just press and hold with two fingers to activate it, then drag to choose your selection style.
I showed all of this in the video. You can access my blog post where I share my experiences via the link below.
Re: STL-Export: Missing certain faces
Yepp! These creatures are in fact Hattifnattar in their region of origin. But I guess they are known as Hattifatteners in those places where Mumin is known as Moomin. They are strange creatures, no question about that, but that's no good reason not to be printable, right? ;0)
I played around a bit, and it appears that I get results when I lower the resolution settings. I have no clue why that is, though. Maybe because a thunderstorm is coming up soon, or so. I'll try printing a few.
BTW.: The model is at least partly parametric, though probably not very robust. The spine can be wiggled and resized, and the eyes may be moved around to make different looking Hattifnattarna. Eventually, the intention is to print and put LEDs in them to make them glow at night, while they hide between the potted flowers.
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
@Derek_Van_Allen_BD That's kind of you to say. I hope that if you start using Report you won't need to scrape it out — you'll be able to leave (at least some of) it in, and just disable it for your users, while re-enabling it when you have to fix something weird that they've done ;)
There are a few other niceties, for example, viz() only adds visualizations, dbg() only writes to the console. The standard library sometimes does both, a behavior I do not care for.
Anyhow, give it a whirl. I use it constantly now in my own code (first step is always "import Report"). I'm curious if others will find it to be as useful as I do. @GregBrown and I were using it to debug some code he's working on, and I think he saw the value of being able to write all the debug he wanted and being able to selectively enable/disable/reenable as he went.
jnewth
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
@jnewth thanks so much for creating and sharing this. It is proving invaluable in a current project I'm working on (as you know!) which otherwise was full of numerous messy debug and println's…
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
My surface tweening feature is over 2000 lines of code but most of it is diagnostics as I build the core logic.
I wonder how much of that I could scrape out of there using this.
Re: Use Report, viz(), and dbg() for conditional println and debug visualizations
I literally just stumbled upon the other video this morning! Great work!
ry_gb
Re: FRC CAM Studio Feedback Thread
I don't like how the Toolpath setup choices forget your last selection.
Re: Where are all the places to discovery feature scripts?
There currently isn't a good place to store custom features for easy visibility.
But we could change that if enough people vote on this: Feature Store (Improvement Request)
Here is a list of all the different places you can find custom features:
- by @MBartlett21
- by @dave_cowden
- by @MaxWestwater
- by @Caden_Armstrong
- by @Keith_Rice
- by @EvanReese
- Custom Features Collection PDF by @legandras
- by @MichaelPascoe
- by @onshape
- by @joshtargo
.
