Corners like this are always challenging and no matter what result you expect, it requires some logic.
At this point I assume you need panels with 25 mm thickness or so. Miters / 45° cuts on 90° edges are simple but the ‘naked’ edge between the two vertical faces would have to be cut 90°…
In case you need help, it would help if you could explain or illustrate the requirements a little better.
With logic I was referring to what happens at the edges. The panel to panel relation or what angle a ‘naked edge’ should be cut. This is not something a one line script or single component will do for you.
you might have noticed not to ask a single question here. Yes the Rhinocommon command is not best around, and other implementations fail, often because they also rely on it underneath. I think for those people who have worked with other CAD know about Rhinos pros and cons. And solid modelling is not its strength
Why is it failing?
I guess because those “edge-cases” are not as trivial as you might think.
What could the forum do? Probably nothing with adequate effort. I never seen someone implementing those algorithms from scratch, and probably McNeel didn’t do it in couple of hours either
What could McNeel do? Improving it, but I doubt they will finish it until you finished your work. Maybe they never improve.
What’s the solution?
Use a different CAD application or do this manually. There are a bunch of apps out there better performing with this particular task. In the end ‘Offset Brep’ is a shortcut, same those Boolean Intersection commands. You could model it surface-based.
Btw, one more thing. Because I think this is important. All these plugins are made by people without charging any money. Take it as it is. This is usually how those license start with. I personally stopped developing plugins some years ago because of receiving presumptuous emails, predominately from Asia.
Martin is totally right. He wants to pinpoint the problem and help you to find a workaround. Its just not going to work if you refuse the accept that (at least in Rhino) there is no one-click solution to your problem. By answering like this, your tone become quickly presumptuous against people who want to help you. No matter if you use a plugin or if you ask people for help in a forum. People spend their time to help other people in solving problems. And its extremely frustrating if all you do is trying to prove peoples and developers stupidity.
First of all, the reason for me posting this (and others) is to find out if these Offset Brep Failures are due to an existing bug or if others have had similar experiences. It’s possible that the failure occurred because I didn’t do it correctly. In other words, who knows if there is “no one-click solution” to my problem, or if there might be a “one-click solution,” but I simply operated it incorrectly?
Secondly, I would appreciate an explanation as to why and how the assumption that “there is no one-click solution” was made, instead of immediately addressing the purpose and finding workarounds. That’s why I replied and uploaded other similar cases that yielded the same results. The “mesh thicken” is the workaround I’ve tried.
What I noticed being emphasized and get on nerves was the very first sentence, “Please don’t create all these topics.” From my perspective, these posts were created over time but never seemed to be resolved, as if the problem were caused by my own actions, yet no one really confirmed that. I’m still unsure if it really is the case or not.
I have never blamed the plugin makers or Rhino developers or called them wrong or stupid. I have never used such words, have I? Where did this judgment and rabbit hole come from? The images shown above simply express the sentiment of, “Hey, I want to use OffsetBrep, and I’ve already tried these plugins, but they all yield the same result… Oh, they’re all using Brep.CreateOffsetBrep… is that how Brep.CreateOffsetBrep currently works…? Yes? Okay then…Or maybe I did something wrong?”
@TomTom, I don’t know which plugin you created, but that doesn’t affect my appreciation for you guys. I feel sorry for the presumptuous emails you’ve received from Asia, and I can understand to some extent because I’m somewhat in a similar position. All I hope is that these words can clarify things and help dispel any stereotypes.