[BUG] Domains - Adding domain prevents distribution

TheShy

D-W Finally finished the homework, I now checked the solution you said, the problem is still not solved

TheShy

[unknown]

D-W I just downloaded the new version 1.02 and found a new problem

I use Bouding Box to preview, but what I get is a point cloud preview
After spreading the tree, the point cloud previewed by Rhino Nature is all on the reverse side, that is to say, the position of the rendered tree is opposite to the position of the rhino nature preview

TheShy

D-W

test.3dm

242kB

This is the file I used, you can check it, the tree used is the official Vray resource library

D-W

TheShy Thanks for the file it explains a lot. So here we go:

First, your block internal geometries are made out of curves. That's why the only possible representation is the middle point of the object. RN will not make previews for not meshable geometry and lines and curves are not meshable. it has to be a meshable object to get a preview.
Second points are above due to normals of the surface check FAQ
Third your models include roots and the point which is shown is actually a centroid of the bottom base of auto calculated bbox of not meshable objects inside the blocks. Look at this:

Pink points are exactly at the base of the block while your base point of the block is higher (due to roots) that's why those are shown below the picked domain. We could assume that this is not expected and should be fixed but there is a good reason for that as if you will turn on vertical mirroring the point will be flipped exactly as block bottom base (in relation to the base point) while if insertion point would be used it wouldn't show flipping at all.
However, as I understand current behavior is unexpected and confusing? I will mark it to recheck if it does what it should do, but I'm open to discussion on how this could work differently.

TheShy the tree used is the official Vray resource library

You mean Cosmos right? The case here is that V-Ray proxy representation option is Bounding Box pick there something else like Low.

TheShy

D-W I understand, I can solve these problems as long as I change the display effect of the tree to a low-quality display (grid display) on the Vray panel, but the first spreading problem still cannot be solved, as shown in the previous figure, when I add On the fourth surface, the spread of this ecosystem will stop, and we look forward to subsequent repairs.

D-W

TheShy move one of the surfaces slightly up/down (1mm will be enough) then it will work:

IIRC this was a Rhino API issue and it was happening during beta randomly. I will investigate that. It is related only to projected distribution types if you'll pick another for eg. Vertex you'll see it does its job. I've logged this and will definitely check what's going on, as this is a bug without any doubt.

D-W

TheShy now not meshable problem should be solved due to new placeholder preview.

However the "4th" srf case still bothers me. Small "jiggle" solves always the issue though I wondered how those srfs was achieved? Regular cutting by crvs or baked form GH or maybe another way, maybe this rare case is happening due to some kind of malformed geometry.

D-W

@TheShy I reviewed this PR many times and the only explanation for this is inconsistency in Rhino API execution, though still a bug, however, I cannot do here much as this is handled on the Rhino side and seems not much investigated according to the state of their log here. On the other hand, this seems not happening on newer Rhino builds no matter how hard I try to reproduce it with any new geometry in a new file, so I'm closing this ticket (at least for now).

TheShy

D-W I remember when I was doing course design, these faces were cut into parts to plant trees, because some faces might have been accidentally deleted by me at some point, so there were also faces that I generated by extracting the edge lines of the openings and then using the PlanarSrf command

D-W

TheShy Typical cutting or making flat srfs out of crvs shouldn't impact generation at all, I was considering that sometimes baked geometry from GH may be rarely invalid and in such cases, when RN cannot acquire srf mesh it can cause issues.