Hi,

I'm playing around with the heightmap plugin and I create the curves with an png file. so far so good.
When I try to copy or save or what ever... an error message pops up with the following error message in the attachment you can see.
strg+alt+ent. is the only possible solution.



Best regards
Jörg

Hi pixelhouse, do you get that same error anytime you try to save like if you start up a fresh instance of MoI and create a sphere and then save it does that work ok?

Or does it only happen with that particular file? It looks like you've got a massively complex single surface there, maybe that's causing a problem. You could try generating a less dense surface to see if that would help.

- Michael

Hi Michael,

yes, it works with an instance of Moi. But in this case I can't copy objects (landscape) from one to another Moi.
A less density object can't be a solution for me. We need to print this model out to a millling machine. Its just a quick test to see
whats possible with Moi and Max Heightmap-script.

I think, its a "spontaneous" error. Maybe its just a dream to export my landscapes to an step-file :)

Hi pixelhouse, in order to generate that kind of high density surface to a milling machine you'll probably need it to be generated in a polygon mesh modeling program rather than in a CAD modeling program like MoI.

I would guess that you're probably running out of memory and that's causing some side effects like the script processing not working.

The only way I could know for sure if that's the problem is if I could reproduce the error over here, which I can try if you send me the image file and instructions on how you're generating the object. If the image file is particularly large you may need to upload it to a file sharing service like Dropbox, etc... and then e-mail me the link at moi@moi3d.com

- Michael

Hi Pixelhouse,

Here's a bit of info since you mentioned "Maybe its just a dream to export my landscapes to an step-file :)"

High frequency detail as found in nature is poorly represented by nurbs. In fact, if you convert a polygon model or raster data to nurbs you are losing information if your goal is to represent the information as faithfully as possible. So I would ask you to evaluate your need to have a nurbs surface.

It is a common requirement to have nurbs model for milling steel to make an injection mold, particularly for best surface finish. Therefore, it seems to be a misconception that the nurbs model is the best format for everything, while for some applications it may not be.

Many CADCAM programs can accept facetted (triangulated) representations such as STL, so there is no need for a nurbs surface if the end use will be the machined model and/or you are not making tooling for injection molds.

divide and conquer???

Hi Michael,
step files are a lot smaller and easier to manipulate as the polygons. Another advantage is the editor sppeed. I'm using Cinema 4d for my workflow: Plane 1000x1000 subdivisions, convert to polys,
load the image in the displacement-deformer and divide the plane one more time. So I have a nice base to create the mountains.
I need to bool wholes in the surface to place parts of energy like wind, water and so on in to the surface. the bool-operations are strange to create in cinema, and it needs a lot of time.

So I thought the workflow with Moi and step-files are a lot easier and faster. I have learned the Software of the milling machine can't read the step-files.

I will send you the file via Dropbox in the next 2 days.
Thank you for your assessment, Michael!


Hi Chris,
I've learned a lot about milling machines in the last 2 days. The optical impression (hope thats correct) in Moi of my landscape was great, and I thought wow, thats it! Its a perfect way to generate the models we need.
For more detail I use world machine to add details like small stones and errosions and make an B and W image output for cinema 4d.
I go forward to optimize my polygon workflow with many different tools to create the best result for our clients. I've tested a part of the mountains (100x100x100 mm) out to the milling machine and the client are satisfied with the result.

Thanks for your help!
Hope my english is understandable :)

Kind regards
Jörg

Heightmap.v.0.8.2018.02.24(MoI.v4)

Hi Max
have you change something because the mesh size is very tight
Thanks

Hi Finema,

no, I didn't change anything

Today I wrote RasterImage script based on heightmap (inspired by Paper.js examples)

http://moi.maxsm.net/files/scripts/RasterImage.v.0.5.2018.02.25(MoI.v4).zip

Amazing work Max!

By the way, if you squint your eyes while looking at Max's image above you'll be amazed how it comes to life!

Ed Ferguson

Cool!

No possibility to put colors from image ?

French Version of HeightMap ;)
http://moiscript.weebly.com/heightmap.html

Hi Pilou,

a color version for you, as .pdf which you can load into Affinity Designer and then make a big
poster from it. :-)



Regards
Stefan

Cool !

but the PDF has no color inside Moi! ;)

I know, maybe worth to ask for a feature request in v4...

Regards
Stefan

Yes :)

Here a random one! :)

Hello Max,

I hesitate to ask anything of you as you have been so very generous.

However, I continue to wonder if it might be possible to generate Heightmaps from within MOI.
This would augment your wonderful script by allowing z coordinates from existing MOI surfaces to be altered within image processers (i.e. Photoshop) and vice versa.
The ability to iteratively import & export Heightmaps would broaden the range of possibilities exponentially by applying the power of each toolset to the other.

Best regards from your most grateful and ardent fan,
-- Mindset

Hi Mindset, you could use the Transform > Deform > Flow command in MoI to apply a heightmap over an existing surface.

Draw a plane at the z = 0 level of the heightmap, then select the heightmap to be the object to deform, run Transform > Deform > Flow, then when it asks for the base surface select your z = 0 plane, and for the target surface select the existing surface.

There's more information about Flow here:
http://moi3d.com/3.0/docs/moi_command_reference8.htm#flow

- Michael