Octane never did that, did it? Did that work in the past?Jaberwocky wrote:Sorry i meant the component names do not appear on the render vewport using the material eyedropper.
They do if you hover the cursor over the scene node pins , just not if you hover the materials eye dropper over the viewport.
well it did for me in the last Beta unless i'm going crazyabstrax wrote:Octane never did that, did it? Did that work in the past?Jaberwocky wrote:Sorry i meant the component names do not appear on the render vewport using the material eyedropper.
They do if you hover the cursor over the scene node pins , just not if you hover the materials eye dropper over the viewport.
Thanks,
Marcus
Your screen capture says 728MB. Was that made in beta 2.48b or beta 2.48c?Jaberwocky wrote:Also one other thing i have noticed.
My available GPU ram seems to have dropped in this version to 578 MB available from the previous version that registered around 750 MB (see previous screen grab). Are the new calcs correct? i seemed to have lost around a quarter of my memory compared to the last beta.
What was the speed you got in beta 2.48b? What happens if you reduce the glossy depth to 8 and/or the specular depth to 8?Elvissuperstar007 wrote:Direct light is very slow, this has not been slow
Hmm, one thing we have changed is that the free memory is checked now every time we display a new result. The main reason we for this is to detect situations where we loose more and more memory due to some leak or some other problem. In the past we would not detect those issues until Octane gets killed...Jaberwocky wrote:your right.Its changed again.Same scene.Somethings up.Not sure if the maths adds up on the preferances screen.
