OTOY Forums

Hi Paul,

I will go with option 3. The reason I ask for this, is because one display I use for render in my setup.

I will go with option 3. The reason I ask for this, is because one display I use for render in my setup.

I was proposing to do all 3.

Paul

face_off wrote:

I will go with option 3. The reason I ask for this, is because one display I use for render in my setup.

I was proposing to do all 3.

Paul

yeah.. please all 3... having the controls only on the setup tab would be a huge step back.

The thing about the viewport button bar that annoys me is that it's stuck to the top of the viewport. So, unless it can be moved around separately, I like having the option to turn it off completely and have all the controls in one place in the setup bar.

The thing about the viewport button bar that annoys me is that it's stuck to the top of the viewport. So, unless it can be moved around separately, I like having the option to turn it off completely and have all the controls in one place in the setup bar.

It is stuck at the top of the Viewport is partially off the screen. This is a limitation of the Modo API.

Paul

So it looks like my PNY GTX660 ti just died on the cuda cores. The plug in tells me Octane has an error, even the standalone version just comes up red in the info bar. Still seems to work on 2D but sometimes now OGL can go wonky in modo, where parts of geometry will have weird triangles coming off them then they will disappear as you rotate around the object.
I took the card out and installed it in one of my other windows 7 machines and I get the same error so I think it's done.

I was hopping to hold off buying another card until I was sure Octane is going to work for me, I know the 660 ti was not the fastest card but it did ok for testing and converting old objects over. So do I buy a fast card like a 780ti and make better use of my investment in the software?
Has Octane caused cards to fail on the cuda cores? is this common or I'm just lucky

So what is everyone using around here? Suggestions are appreciated.
Thanks Keith

This is the error log file
Started logging on 23.04.14 18:37:30

OctaneRender version 1.50 (1500001)

CUDA error 716 on device 0: Error code unknown.
-> Kernel execution failed (dl)
CUDA device 0: Direct lighting failed
CUDA error 716 on device 0: Error code unknown.
-> Failed to copy memory to device.
CUDA device 0: Failed to load data of data texture 20 of context 0 onto device
CUDA error 716 on device 0: Error code unknown.
-> Failed to deallocate device memory
CUDA error 716 on device 0: Error code unknown.
-> Could not get memory info

So it looks like my PNY GTX660 ti just died on the cuda cores.

I've had a faulty card before....so it happens. The fix for my card was to underclock it by 10%, and it then worked fine. Although I haven't seen Cuda Error 716 because - so it might mean a different hardware issue to the one I was getting. Suggestion researching exactly what 716 is.

Paul

Paul your a genius
I installed msi afterburner and underclocked it and it started to work.
I then put it back to it's default settings and it's still working.
It seems to me that when it crashed it jumbled up the cuda cores somehow and underclocking it got it working again. Now it's fine at full speed.
I'm going to put it back into my main workstation tomorrow and do some testing with it and see if I can get it to fail again.
Thanks
Keith

Keith - my theory is you need to do the first render after turning on your PC with the card underclocked - then you can set it back to normal (if the fault is anything like mine).

Paul

Paul,

I am really enjoying this plugin!

One suggestion... in the modod material, if specular amount is set to 0 and blurry reflection is not checked, the roughness parameter should be interpreted as 0.