MophMuse V 1.0.0.0 (Pre-release)

[rymaeda]

MorphMuse lets you build surface geometries in CamBam by combining one open curve with one closed outline. It automatically  generates a smooth surfaces"
Just for Cambam V1...

Edit: Removed outdated files.

[pixelmaker]

Hello Ricardo,
This is a very helpful plugin. I can think of many possible applications right away. I will test it in the next few days.
Thank you.

[dh42]

Hello

Very nice  !! Thanks for your job !!

This need to play with the CW/CCW direction of the external profile and the start point of the open poly to obtain what we need, but works very well. Using Invert face on the resulting object may be needed depending of the rotation direction used for the external line.

An example for a "plate" in attachment.

++
David

[dh42]

with a more complicated shape and profile.

++
David

[rymaeda]

Ralf and David, thank you for the feedback and encouragement. I've already run into a problem — I tested everything during development using a polyline provided in another conversation by Bubba, but it turns out the dimensions were in inches. Today I tried with a file in millimeters, and the result was an absurdly refined, heavy surface. The internal parameters, tuned for inches, created an impractically large file. I'll fix this soon, but not today — time to sleep. Thanks to both of you.

PS: Thanks a lot for the polyline, Bubba!

[Bubba]

@rymaeda.
No need to thank me. I thank you for taking the time and creating this plugin.

Will test it when time allows..
Cheers..

[rymaeda]

Bug fixes, measurement unit handling, and a new user manual. The x86 version was not tested—sorry for the inconvenience.

Edit: Removed outdated files.

[dh42]

Hello

Just tested the 32 bits version > OK

The fact that we can play with the Units to set a suitable resolution give a way to optimize the result.

Example on the picture, the shape is ~ 33 * 25mm, with unit set in mm, I get a surface = 2564 faces ... not perfect, there is small defects in the sharped edges in the internal shape. Setting units to cm with the same shapes (no scaling) give a surface = 9854 faces and a good result for the internal edges. with the units set to inches, I get a surface = 14565 faces, good result too, but unnecessarily heavy.

Thanks for the job

++
David

[rymaeda]

Hi!

Here's a quick workaround for the resolution issue. Since the resolution is calculated from the diagonal of the bounding box of the closed polyline, there are still some cases where it can be problematic. I think a custom method to generate points along the curve could help fix that. I was a bit hesitant to share this, but coming up with a solid solution might take some time.

Thanks again for your time and the awesome examples!

I'll delete the older versions and keep just the two most recent ones.

Regards!

[dh42]

Hello

I don't know how the mesh is constructed, but Andy falls on the same problem with the conversion of STEP data to mesh depending of both the units and the real size of the object, and He add a STEP resolution property in the options to allow to set the resolution suitable for the job you want to do. Maybe you can use this setting as a way to define a suitable resolution for your mesh, so the user can define what is suitable for is usage ?

CamBam.CamBamConfig.STEPresolution (double)

I use STEP resolution = 0.05 for mm.

PS: STEP resolution is missing in the configuration page of the english doc. It is only described in "what's new - Revision rc-1 changes - 2019-09-11 - [10] STEP File mesh resolution setting

++
David

[rymaeda]

Hey, David

I don't know how the mesh is constructed,

Actually, the idea is quite simple—the hard part is all the apparatus needed to make it work.

but Andy falls on the same problem with the conversion of STEP data to mesh depending of both the units and the real size of the object, and He add a STEP resolution property in the options to allow to set the resolution suitable for the job you want to do. Maybe you can use this setting as a way to define a suitable resolution for your mesh, so the user can define what is suitable for is usage ?

I think this problem is actually simpler than the one Andy faced, because we're in the opposite situation—working with well-defined curves and corners. The vertex must be placed exactly at the corner, and nowhere else.

CamBam.CamBamConfig.STEPresolution (double)

I use STEP resolution = 0.05 for mm.

That sounds like a great solution to the problem. I'm working on automating all of this, but it might turn out to be more complex than expected—and yet users might still want to make manual adjustments.

PS: STEP resolution is missing in the configuration page of the english doc. It is only described in "what's new - Revision rc-1 changes - 2019-09-11 - [10] STEP File mesh resolution setting"

A valuable bit of info that was tucked away in a corner is now finally out in the open—on the forum!

I'm publishing the code on GitHub, but the directory and the code there are a mess, and everything might change drastically at any moment: https://github.com/rymaeda/MorphMuse

Cheers to a new week—let’s make it a good one!

[dh42]

Hello

A valuable bit of info that was tucked away in a corner is now finally out in the open—on the forum!

Unfortunately, I can't update the English doc myself, I can only do it on the French doc.

++
David

[rymaeda]

Don't worry about it, David. Over the eleven years I've been occasionally following this forum, I've developed a good sense of how things work — and how they don't. The collaboration here is fantastic and ends up making up for the lack of documentation (that's what I was referring to).

[rymaeda]

Hi!

-Customized CreatePointListFromPolyline().
-Adopted the use of the STEP resolution configuration item (David's idea). 

Code: [Select]

// C#
double stepResolution = CamBamConfig.Defaults.STEPResolution;

-Plus some additional internal improvements.

[GeoffreyGRoy]

Just a couple of minor points - nice plugin.

(1) When an incorrect selection is made (say not a single closed polyline and a single open polyline) a message is provided, then a blank widow appears - that either should contain some useful information, or is not necessary.
(2) In the dll file, the "Product Version" for File version  1.3.80.0 is incorrect - I use this to update my installed plugins - to get the latest.
(3) It might be useful to consider, converting the selected items within the plugin (i.e. one closed polyline and one open polyline) to polylines as it is common that these may be constructed from circles, arcs, polyrectangles and  splines, rather that detecting the error and then asking the user to do so.

good work,
Geoff