There is definitely some improvement going on as far as performance is concerned. We are heading in the right direction.
Thank you Dan and Steve for taking this seriously.
And we just now published a new RhinoBETA with Steve’s transparency fix. Please give it a try. I see a major improvement here on my machine with all things transparent (Ghosted, etc).
Hello Dan,
I confirm a significant improvement also on my iMac.
-Simon
There are still some performance issues when
- importing dwg files
- working on 2d drawings in wireframe mode
- switching between different named views
- changing screen mode / full screen and 4 screen
but I can confirm that performance has gotten better.
I do feel that performance has slightly improved too, especially in ghosted mode.
With regards to the delay in switching between named views, I have discovered a specific repeatable instance where I get a large delay when switching views:
Upon opening a file with a large pdf ‘picture’ placed (an architectural plan), I get a large delay when switching from a single view to the multi view the first time that I change only. Once I have done it once, subsequent changes of view are roughly the normal speed.
How do I do that in raytraced screen mode I have the same light situation as in rendered mode?
Since it is way slower in raytraced I would like that I can fix the light in rendered mode and then display it in raytraced (better quality) or render the image.
Important would be that the light between theese doesn’t change every time.
Raytraced and Rendered mode are regarding lighting two completely different approaches. I don’t see Rendered mode do similar lighting any time soon.
Thx for the info.
If I want to do a High Quality Render in Rhino v6, should I set up the lighting in “Rendered” Mode or in “Raytraced” mode? In which one do I have the better preview for the actual rendering?
@OXII Use raytrace for both, then it is exactly the same
i had to use a ghosted view quite a bit today…
it’s great… not ‘better’… more like butter…
well done @stevebaer
Thank you. I messed a bit around with the v6 render settings and I find it complicated.
It is also not entirely true that raytraced is the preview for render, since I see lighst in the final render which in raytraced I don’t see.
It also opens a huge render window which you have to reduce in size all the time.
If you use -viewcapturetofile, you can get high res images out of the raytrace engine. I also believe there is a way using a beta render dialogue. Basically the ‘raytrace’ engine is going to be the new render engine in due course. In the meantime you can still use it both in viewport and output images.
@nathanletwory can advise further!
Confirmed as well. Opened heaviest current model have. Most all good including Ghosted! This model used to suck wind (nearly unusable) in v5. v6 MAJOR improvement!
Raytraced - another story; sucks wind terribly. Rumor has it I don’t have the ‘right’ hardware. Tried a few different boxes. To be fair, I’ve only played with Raytraced very briefly, so I could be doing something ‘wrong’…Hoping sorted eventually. Huge potential. (back to Keyshot for productivity, though)
Has anyone found Blender 2.8 render performing noticeably better on an array of Mac hardware? I haven’t yet experimented.
Blender 2.8 in Cycles kills it. A magnificent piece of software.
Big advantage: in cycles preview I can organize my scene lights and materials and when I do the actual render it stays the same, so I don’t have to worry that things look different when I hit render.
A huge downturn in Rhino mac v6:
Rendered screen mode, Raytraced screen mode and an actual render gives you three different results. So how the heck should you be able to set up materials and your scene without losing huge amounts of time? What is the point for that?
I my opinion things should be simple, easy and fast. That is what is required in the professional world.
But why things look different in Rendered, Raytraced and the actual render?
I understand, that are three different techniques…
But isn’t that very confusing for someone who wants an easy and smooth workflow?
Looks to me this is a matter of gamma settings. The first seems to be gamma corrected. Not at a computer so cannot check.
I think you’ve either not understood my previous post or you’re ignoring it for the sake of getting worked up.
I’m no expert but they all calculate the image using different algorithms. The output is going to be inevitably and irrevocably different.
The best thing to do is pick one and make it look good. If you want a ‘quick’ (ish) live preview and the best output, then go with Raytrace in the viewport and use viewcapturetofile to output high res images. Or the rendernext plugin although I’ve not tried that yet and not entirely sure how you go about it.
You can read more about it here: Cycles render engine in RM - #94 by nathanletwory
Thank you, I will try further with Raytraced mode and also try to make it work for our office.
I was just a bit surprised why we do need 3 different modes of rendering in Rhino v6. It is confusing.