Hello again.
I have a question for BurrMan.
May I ask how did you cut out that sharp corner? I'd like to reproduce steps you've done to accomplish that.

Hi aj,
I went to the side view and drew a square that enclosed the whole area, then did a Boolean diff. Then delete the faces of the 2 pieces facing each other so they are open. I ran a blend on the top and bottom, then did a 2 profile, 2 rail sweep on the sides to be able to join it back into a solid.

If that's not clear, I can make a quick video.

Thank you BurrMan.
I've managed to repeat your steps and learn something new. I didn't know that you can cut solids using curves, even in 3D view. Very useful.

Oh, I forgot.
What if I need to readjust the fillet after it has been created? Is it possible to remove it and recreate it without having to create the object from scratch?

Hi AJ,

> What if I need to readjust the fillet after it has been created? Is it possible to remove it
> and recreate it without having to create the object from scratch?

It is possible to delete the fillet and then do some untrimming and retrimming of the surrounding surfaces. There is a tutorial on those object repair techniques here: http://moi3d.com/forum/index.php?webtag=MOI&msg=446.17 . But it's still a fair amount of work involved so it's generally better to save off an unfilleted version of your object to a separate file so you can go back to it later on.

If you think you're going to need to do a lot of edits like that you may want to use what is called a "parametric history based" CAD program like SolidWorks or Alibre which are focused on keeping a list of actions that can be edited. MoI is more focused on making it as easy as possible to just freely draw and create the initial models.

- Michael

Thank you Michael and I apologise for my late reply.
No, I don't think that I'd require many edits, so keeping hidden backups of non-filleted solids seems to be enough for me. I'm thinking of using MOI to create quick prototypes of hard surface models that I will later use as base models for voxel sculpting and/or retopologise them for subdivision.

Hi Michael, I run into these issues pretty often, and it occurred to me that a really useful feature would be visual feedback indicating the problematic edges. A status/error pane/bar would also be really nice, since stuff seems to fail silently-- additionally, since some actions automatically complete without hitting done, silently failing can be a bit bewildering.

Will

Hi Will, the problem is that it tends to be quite difficult to provide error information that makes any sense to a regular human being as opposed to a mathematician...

It also requires some cooperation from the inner functions of the geometry kernel itself to return back the specific information about what particular edges caused the problem, right now this is not really provided for in an extensive way by the geometry library that MoI uses.


> additionally, since some actions automatically complete without hitting done,
> silently failing can be a bit bewildering.

Do you have an example of one of these situations? It always helps to have a specific example to look at rather than just talking in general terms.

There are many commands that don't have any further options to adjust in them, those generally finish without needing to do a separate additional "Done" stage in order to increase efficiency of operation.


At some point I would like to have a kind of console area where a log of information could be displayed. I have not yet found a good place to put that in the UI without it consuming a lot of space and kind of dominating the UI to a problematic extent though.

- Michael

Hi Michael, I suggested the visual feedback (perhaps highlighting problematic edges in red) to avoid complicated error messages, though if an command fails, it would be nice for the command pane (top left corner) to at least display "command failed" or "union failed" or some such instead of just disappearing.

As far as commands which sometimes do not require pressing "done" go, most recently I ran into a bit of frustration unioning complex solids which I had preselected. I eventually reworked the solids, but the bewildering bit is this: the union takes a long time, and the "done" button still responds to clicks, but does not appear to do anything-- then the command pane disappears and I assumed the union had succeeded. I only discovered that it hadn't after trying to do another boolean operation where one of the failed union pieces was hidden from view. I retried the union a few times before I realized it was not operator error in applying the union, but that my model was broken in some way.

Will

Hi Will,

> though if an command fails, it would be nice for the command pane (top left corner) to at least display
> "command failed" or "union failed" or some such instead of just disappearing.

That's already been added in for the most recent v3 beta. From the release notes:



> As far as commands which sometimes do not require pressing "done" go, most recently I ran into a
> bit of frustration unioning complex solids which I had preselected.

Yeah that happens because it's also possible for Union to work with nothing initially selected in which case it asks you to select things and waits for you to push "Done". That same UI is ending up displaying for the preselection case as well. I guess that could be tuned up by hiding the "Done" button for the case of stuff having been already preselected before running the command.

The new "Calculation failed" UI should be helpful for distinguishing cases where there was not any result generated, although with boolean union there is another complication with failures in that it's not quite the case that nothing is generated from the union but that the same objects are generated out the other end but they did not cut each other up.

- Michael

Ah, I didn't realize the new beta added that. Excellent!

I know the preselection causes automatic command execution for some commands, which is great. It was just baffling when the command pane appeared and suddenly vanished without completion for no apparent reason. Anyway, the new UI you mentioned should help with that.

As a suggestion for the done button, perhaps when the command starts execution, change the text to "Calculating..." and disable the button so it doesn't respond to clicks.

Edit: Actually, an approach more consistent with typical UI would be to immediately change the entire content of the pane to a progress view. Even if a progress bar or percentage is not doable and it just displays "Calculating..." and a cancel button, the content switch makes sense. Usually one expects clicking done or cancel to immediately close the pane or transition to a new content view. Just my $0.02.

Will

Hi Will,

> Edit: Actually, an approach more consistent with typical UI would be to immediately change
> the entire content of the pane to a progress view.

Sounds pretty good, but one complication is that there are also many commands that need to show some kind of an "in progress" indicator (like "Calculating..." does currently) while you're still inside the command, for commands that have options that you can adjust before finishing the command. Like for example the Fillet command lets you enter in a radius and then starts off the calculation, but when the calculation is finished you're still in the fillet command and can change the radius again (and get "Calculating..." again) before you actually finish the command.

That's why the current "Calculating..." mechanism is more like something that gets added in to whatever UI is currently showing rather than only being a final screen.

- Michael