Cycles and Lands Design plants bug

rhino

#1

Hi @nathanletwory Can you check this out?
I installed Lands Design to test out the plants, but this is what happens if I turn on Raytraced:

BUT… If i use the Rhino Render Next and starts a render, then Lands pops up a statusbar and suddenly Raytraced starts over and renders the plant correctly at the SAME TIME as Rhino Render Next: (Waste of time + strange that it works)

UNTIL it reaches the destination value (170 in this case) then Raytraced decides to recalculate once more, but now with the “white bush” again.


(Nathan 'jesterKing' Letwory) #2

I don’t have Lands, but could you save the tree and send it to me via PM?


#3

I uninstalled it again. It was too unresponsive when I had as little as 8 trees in the scene.
But the beta is free and available here: http://www.lands-design.com/
(I wish I got paid for bugtracking because then I could play with that stuff all day, so I have to leave that fun part up to you guys :wink: )


(Nathan 'jesterKing' Letwory) #4

Right, I might do that later this week then - currently busy preparing for


#5

Hi,
it was too unresponsive in Raytraced mode or in any display mode?


#6

Raytraced mode fails to manage Lands plants because they are quite complex objects. We need to do something to fix this.

However, when you use the Rhino Render Next, plants objects are replaced by much more detailed plants. In this case they are standard textured meshes that Rhino manages perfectly.


(jesterKing) #7

Rhino Render Next = Raytraced. In both cases the geometry, materials and textures are received through the changequeue system. There should be no difference.


#8

In any, I added a few conifers and in an empty scene and I got a few delays where Rhino froze for 30 something seconds. I tried to move 5 trees and then it started thinking again (very unlike your videos). This was in rendered mode and I have a GeForce 970 on this machine, so it has enough power.


#9

No, but when turing on Raytraced it looks like above, but when Rhino Next is started then a Lands Dialog box with a status bar appears before the rendering starts and then both the viewport and nxt starts rendering as I showed in the images above.


(Nathan 'jesterKing' Letwory) #10

Does this mean you are using a conduit to draw in the viewport?

I think for Raytraced at least the correct way is to use the CRM, which is also what would be used in a production render. If you need to discuss this in more detail you can write directly to me with questions at nathan@mcneel.com.


#11

Yes, that is.

Custom Render Meshes sounds good, I guess one day we are going to implement them.


#13

I’m pretty sure that the problem was caused by a plugin named “Displacement”. We have some sort of conflict with this plugin so that when Lands updates its objects Displacement plugin starts to do a lot of recursive calls that cause these delays.

Disabling the Displacement plugin should solve the problem. The new Lands version, recently published, tries to minimize this problem when Displacement is present, but the best solution is to disable it, unless you really need it.


(Nathan 'jesterKing' Letwory) #14

Are you saying that just having the plug-in enabled causes this?

@andy, @Jussi_Aaltonen do you have any idea if that is even possible?


(Jussi Aaltonen) #15

Hi @albert, I could not repeat the issue just by adding a bunch of trees into an empty document. I tried with Lands Design Beta version 4.9.9.5273. Can you help me how to see the delays? Which Rhino 6 version are you running on?


#16

Hi Jussi,
the problem happened mostly on Rendered mode and having Forests with a large number of trees. Forests are single Rhino objects that contain a lot of geometry. When they was modified and redrawn, the delays was incredibly annoying and this is how the call stack looked like:

In the latest Lands Design Beta, the one you have tested, released few days ago, we have changed the implementation of “HasSubObjectMaterials” function so that it always returns false. This way, it looks like RDK (and Displacement) ignores our objects in many of its procedures, and since they are custom objects drawn by us, it’s not a problem at all.

Hope this help to figure out the problem. If you need an older version of Lands Design, let me know and I’ll provide you it.


(Jussi Aaltonen) #17

Thanks for the call stack @albert! We now know what this is. RDK is preparing to show own material for each sub object. At the moment best solution is what you’ve already done: to return false from HasSubObjectMaterials.

We will probably improve this for Rhino WIP.


#18

Wow, great result!