OTOY Forums

The mismatch error went away when I disable my second graphics card completely. This includes going into Octane Device Settings and disabling, Render, Tone, and Denoise. Seems stable at the moment.

It looks like NVlink was the cause of my problems. I disable SLI mode in the Nvidia Control panel and it seem my dual cards are working correctly now. Hopefully, you guys can correct the issue so I can use the NVlink memory pooling in the future. Thanks.

I get this error message alot and the only way to have it go away is to restart 3DS Max.

CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to bind device to current thread
device 0: failed to initialize context
device 0: failed to initialize render thread 0000016A753A9480
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to bind device to current thread
device 1: failed to initialize context
device 1: failed to initialize render thread 0000016A753AA280

Not sure if this information is useful, but changing the GPU headroom from 100MB to 1GB made my GPU run more stable. EVEN NVLink seem to work better. However I still get this error with NVLink.

Started logging on 30.04.20 14:23:36

OctaneRender Enterprise 2020.1 (8010000)

OptiX API error: Unsupported ABI version
Mismatching barriers, 5 and 2

Hallo tcheng00, is everything okay with you?

I've struggled too with these Out-Of-Core related problems, most of the problems are caused by the insufficient memory of the pc.

I recommend you take a look at these topics.

viewtopic.php?f=27&t=74536

viewtopic.php?f=27&t=73903&start=10

were tense months, unfortunately there is not much material, explaining the limitations, known problems and best practices.

OK here's a new one. New to me at least.
Why is the Octane viewport render being so distorted?

Kind of a big problem...
Seems like it's something to do with upsampling.
Gonna make the animation I'm supposed to be cooking today quite stressful

Edit: Ticking use production resolution seems to fix it. What's happening?

Edit Edit: That only worked for a while. Gone screwie again. So made a new Octane camera and that seemed OK. Then made a standard max camera and that was screwed straight away. Could it be a max display/viwport type thing?

Hi! so far i'm not seeing any bug. looks great.

any implementation of a better fog-enviroment thats more similar to the C4D one?
paride? any idea in this regard?

samsue wrote:Hallo tcheng00, is everything okay with you?

I've struggled too with these Out-Of-Core related problems, most of the problems are caused by the insufficient memory of the pc.

I recommend you take a look at these topics.

viewtopic.php?f=27&t=74536

viewtopic.php?f=27&t=73903&start=10

were tense months, unfortunately there is not much material, explaining the limitations, known problems and best practices.

So far, I'm not having too many problems, I get the occasional denoising doesn't have enough memory error, then I check only 1 gpu to do the denoising and the second gpu to do the tone adjustment. Everything seems to be working find again.

Also, to note, the default setting seems not so good for general applications. Please change this ASAP, so you don't get a lot of new user frustrations. Hopefully, there is a dynamic way to automate the technical settings based on hardware and memory requirement so we don't need to deal with these kinda settings in the future.

I recommend changing GPU headroom to a larger amount to get stability (this changes based on memory/scene size, hopefully this will be dynamically automated in the future). I use the max of 1 GB, but I think I can go lower, just don't know the right combination yet. If you have dual GPUs, use one for denoising and the other for Tone. Do not use NVlink for preview while moving the camera around, it gets out of sync and errors out. I think data transfer over nvlink is not faster enough and gets out of sync on a 2070 Super (this is just my guess). You can use NVlink for final render or preview if you don't change the perspective view.

Also, the GI clamp is so high that it produces fireflies. I've set mine to 10 to maintain a bit of dynamic range without creating hot pixels.

Keep in mind, the optimization for lights does not seem to work for Emission lights that well. So if you can avoid using mesh lights, the Vectron geo lights are better and faster.

I'm not exactly an expert in Octane, but that is what I found so far. Please feel free to correct me. I'm still learning

FYI, I reinstalled my drivers again. It seems it didn't install correctly the last time. Anyway, it did help resolve the nvlink crashing when I change the camera by introducing a slight delay. The other problems still remain.

I would like to test the new camera but can't find new values like in the Standalone Announcement thread.

Do I need a special OSL file?