Hello ALL
我做了一个简易骰子，出了问题。（I made a simple dice. Something went wrong.）


Boolen→Isect

额外出现了粘连面，如何才能删除或分离这些面，而不是使用好面阵列的方式进行修补？(How can we remove or separate the additional adhesive surfaces instead of repairing them using a good array of surfaces?)

Hi SUIYAN, can you please post the .3dm model file with your object in it?

If you want to work with surfaces you can use Edit > Separate to break your model up into separate unjoined surfaces.

It may be possible that the problem in this case is a display bug and your actual surface is ok. Does it look ok if you export to .obj format?

- Michael

Also attached here is a fixed dice object that you can use.

- Michael

HI Michael
.3dm file

MOI做的模型到Rhino中打开是正常的，然后以rhino保存，到MOI中打开仍然模型不正确。（It is normal to open the model made by MOI in Rhino,
Then save it in Rhino and open it in MOI, but the model is still incorrect.）

Hi SUIYAN, it does seem to be a display bug, if you export out the exported data looks ok.

If you want to fix it so it displays ok, you can select the weird looking faces:


Use Delete to remove them leaving a hole there:


Select one of the other faces that are ok:


Use Transform > Mirror and then Edit > Join:


- Michael

谢谢 Michael，我一直是这么做的阵列或者镜像。仍然希望修复这个BUG，因为BUG也可能出现在没有相同曲面的模型上。（Thank you Michael, I have always done arrays or mirrors this way. I still hope to fix this bug, as it may also occur on models without the same surface.）

Hi SUIYAN,

re:
> I still hope to fix this bug, as it may also occur on models without the same surface.

If you have other cases that seem similar but with other surfaces please send the .3dm file containing those to me also.

You can e-mail me at moi@moi3d.com .

Thanks, - Michael

OK，先看看这个(Let's take a look at this first)


仅在v5中出现。stp显示BUG，对比不连接面的情况影响似乎更严重一些。（Only appears in V5. STP shows a bug, and compared to the situation where there is no connection, the impact seems to be more severe.）


在V4以及Plasticity中显示均正确。（It is displayed correctly in both V4 and Plasticity.）

其余模型在交流群中出现时，我将发邮件给您。（I will email you once the remaining models are present in the communication group.）

Hi SUIYAN, that's a much different bug than the other one, they are not related.

This one is from the STEP importer having some difficulty with splitting edges that cross over the "seam" of a closed surface.

It's not just a display mesh problem like the other one.

You can still send them to me, at some point I will probably try to write a new split at seams function and it is good to have more test cases.

- Michael