RayTraced freeze Last WIP

Serengeti (Rhino WIP) Rendering WIP
22

AAAH!

had the same problem with the last WIP. so annoying after i just had started using cycles for a project and i was totally happy with it. so i waited for the next wip. just installed the latest WIP from today but cycles/raytraced still freezes.
happens on an nividia/cuda as well as amd/opencl system.
seems cycles only responds again after it has finished the preset sample count. but most of the time it crashes completely. especially if there isn’t a preset sample count like in high quality mode, where it just keeps on sampling.

23

Hopefully you mean that the UI is not responsive until rendering is done. Note that RH-37955 is re-opened. @andy and I are looking into why this happens. The problem doesn’t seem to be Raytraced, but somewhere deeper, all the way down to how Windows messages are pumped and handled. It is a elusive situation. We can’t reproduce on all machines, but we can see something is amiss.

24

ok,
sorry i was a little rude - just hurts when something doesn’t work anymore after you just started to love it :wink:
hope you can solve the problem asap, thumbs up!

system is:
WIN10PRO 64bit, all updates
i5-6500
GTX1060-6GB

25

we hope the same. working hard on it :slight_smile:

26

Hi there,

I think I’ve found the cause and fix to this problem.

Here is the commit I made with the fix. In short it means that the Cycles threads could cause freeze and dialog problems by making it hard for the OS to give low-level message handling proper priority.

So the fix is to tell the threads they aren’t as important as they think they are.

I hope we can get a public WIP out next Tuesday, because it would be great to hear from you all that the freezes and color picker problems are gone.

So, I’m keeping my fingers (and toes crossed) for the next 4-days (:

/Nathan

27

those arrogant threads - who do they think they are !

having cycles usable again next tuesday would be great, you can do this!

28

cycles works fine again since yesterdays wip. on nividia as well as amd.
thank you very much!

29

Good to hear things have improved (:

30

I’ve noted a few things while testing some GH nodes:

  • HDRs are extremely slow: Loading, rotating (7000*3500 px take +10 seconds to load…) Although that’s maybe not part of your work…
  • (GH) shaders often show grey => changing color using color picker updates viewport
  • assigning names to materials, materials to objects is sometimes laggy.
  • And Raytraced (still) doesn’t stop after 200 samples

But other than that Raytraced works nicely again and I think it’s cool.

Is it generally now possible to google any material and we have the same nodes Blender users have and everything for the most part works the same way as in a tutorial for Blender?

31

These are currently baked, so for huge image files it takes time. Eventually this will made better.

Do you mean the GH color picker?

I’ll see if I can reproduce. Is this on scenes where there are lots if materials, and lots of objects?

If you mean changing Render Quality doesn’t change anything you are right. You can change maximum in several places:

  • click on the pass count, set new maximum. This is view specific. Not yet persistent, but we are working on that
  • Use RhinoCycles_ChangeSamples for the active Raytraced view
  • Use RhinoCycles_SetRenderOptions. Changing this sample count will persist between Rhino sessions

Not all Cycles nodes have been wrapped yet.

/Nathan

32

No, while working with one material. But minutes later I had a blue screen and Windows restarted so maybe it was sth. totally different…

Good to know, minimizes disappointment when finding tutorials that look great, but do not work…

Great, didn’t know that, either.

The viewport was just changed from Shaded to Raytracing. But just when I then change the colour in GH Raytraced is updated.

grey.png1265×443 150 KB

33

Thanks, I’ll see if I can reproduce when I go back to material tweaking.

34

Thanks Nathan
In the last WIP Raytrace is OK
Vittorio

35

Good to hear.

/Nathan