Hi Michael

In the process of following your suggestions about the honeycomb I have discovered a few things.

1. MOI fails "silently". I decided to give MOI a whole night (6-8 hours) to attempt the boolean. In the morning. MOI was still in "Calculating..."/hourglass mode plus the MOICommandProcessor entities were not consuming cycles and there were no memory deltas. Instead of purging, I clicked the MOI close button. It promptly asked me of I wanted to save my model (I didn't), then closed cleanly. Obviously the boolean had failed without a message. There should be a message of some kind and MOI returned to user control.

2. I rescaled (as you suggested) and tried the same boolean, but this time there was a crash popup with the button to email the crash report. This dialog was unresponsive and I had to purge MOI.

3. I then attempted a simpler boolean (an open instead of closed curve for the cutting object) on a subset of honeycomb. That boolean completed successfully!

But...!!!!

The number of "mouse-over" display artifacts that I reported here: http://www.moi3d.com/forum/?webtag=MOI&msg=645.1 in this new model is many! I have attached some images. As you can see, they appear simply in response to moving the mouse around the viewports. IMHO there appears to be a correlation between using the boolean difference on an object and the display artifacts... almost as if MOI calculates extraneous points and sends them to the display engine intermittently. As I said in that other thread, Rhino used to have these things (prior to V1). I was running on a different video card back then, but it was ATI, also.

I have 1Gb of RAM and 8Gb of swap on two drives.

This model is just for fun and for learning MOI, therefore not important to me to complete. But do you want me to continue to report these kinds of issues?

> But do you want me to continue to report these kinds of issues?

Certainly, the more information about problems the better!

The display artifact one seems to be a tough problem though, I took another look at your old version in some detail and I just can't repeat any similar problems over here. Also I haven't had any reports of this type of behavior other than yours.

The part that is especially odd is that when you mouse over, the screen will redraw but MoI sends the exact same mesh data to the video card as before the mouseover, just updating one color value... So it is difficult to think of what is going wrong there...


re: #1 - normally when there is a failure it should exit the "Calculating..." stage as well. It seems like in this case there is some bug that is preventing that from happening. Could you possibly post your model here (maybe with just one of those hexagons to keep file size low, I can make an array of them over here). If I can reproduce your problem over here it would help to figure it out and solve it.

re: #2, crash - well, that isn't better! Can you please take a look in the MoI folder in c:\Program Files and see if there was a file created there called moi_report1.zip ? When MoI crashes it tries to write some information in a crash dump file. If that was generated, please e-mail it to me at moi@moi3d.com, and that might also help me in tracking down the bug.

Thanks,

- Michael

I've attached a 3dm with one honeycomb cell and the closed path.

Naturally it does not exhibit the rendering artifact, even after a boolean difference.

Just a little try With the Array Line
Honey comb = Polygon 2 Units, thick 0.1 Unit, hight 10 Units
one Honey comb in volume (without the construction lines) * 100
I re take these 100 resultant Honey combs
and re apply the Array Line so 100 * 100 = 10 000
but during this last action the button "Cancel" is not working (in reasonnable time(?) :(
And stop the program with Alt +Ctrl + Del very hard to apply!
Is that normal?
There is not an internal process for stop the calculating during this function?

No problem for 10 * 10 = 100 :)

Hi Pilou, you probably ran out of memory. Once that happens things will go very very slowly as memory is swapped back and forth to the disk. That's probably why Ctrl+Alt+Delete was even very slow.

Array line does not currently have any cancel mechanism built into it, for the time being you should generally try to avoid making very large numbers of objects with it.

- Michael

< very large numbers of objects with it
Seems more reasonable indeed :)