OctaneRender™ Standalone 3.03.3 Tweet

[coilbook]

Hi coilbook,
could you share an example scene that shows the issue?
ciao beppe

Hi Unfortunately scene is like 5 GB with textures and 70 Gb of VDB smoke but i attached log with all kinds of errors hopefully it will help

[andw]

The undock feature of tool panes (outliner, inspector, node editor and so on) is great in v.3 , but it has a small disadvantage: when I minimize main window (with render viewport), all undocked panes are still left in the same places, cluttering desktop and (in case of two or more Octane instances running) making hard to select desired pane of proper application instance.
Probably it would be better to hide them when main window is minimized?

[abstrax]

Lots of slave errors and main PC errors (pc BSOD, 3ds max crashes, render stops at the end of the frame, etc) during animation rendering especially if VDBs are used or Medium in the Sun. I remember when you released 2.2 version you eliminated all cuda errors somehow but with version 3 they are all back. (so it is not temperature related)

If you create a complex scene with motion blur objects and VDBs and render for 10 hours I think you should be able to recreate all the errors.

We have fixed all issues we could reproduce somehow. The next release will have two fixes: One for an infinite loop in displacement mapping (causing the OS to eventually kill the graphics driver, which will invalidate the CUDA context, resulting in CUDA errors). The other one is an infinite loop in the direct light calculation, which would not result in CUDA errors but would render threads to hang anyway.

If you've got any scenes that render fine in v2 but not in v3 or any scenes that cause issues in v3, we are happy to have an in-depth look and fix anything we can find. Without any reproducible errors it's practically impossible to improve the stability.

[coilbook]

Lots of slave errors and main PC errors (pc BSOD, 3ds max crashes, render stops at the end of the frame, etc) during animation rendering especially if VDBs are used or Medium in the Sun. I remember when you released 2.2 version you eliminated all cuda errors somehow but with version 3 they are all back. (so it is not temperature related)

If you create a complex scene with motion blur objects and VDBs and render for 10 hours I think you should be able to recreate all the errors.

We have fixed all issues we could reproduce somehow. The next release will have two fixes: One for an infinite loop in displacement mapping (causing the OS to eventually kill the graphics driver, which will invalidate the CUDA context, resulting in CUDA errors). The other one is an infinite loop in the direct light calculation, which would not result in CUDA errors but would render threads to hang anyway.

If you've got any scenes that render fine in v2 but not in v3 or any scenes that cause issues in v3, we are happy to have an in-depth look and fix anything we can find. Without any reproducible errors it's practically impossible to improve the stability.

I will try to email the scene but it is so big.
I attached images of all the errors we have maybe they can help you also master log errors are attached. Pictures are slave errors. It would render for 50-80 frames and freeze up when frame is almost done. The whole 3ds max must be restarted or slaves would not work. Sometimes computer.

Also a lot of the times when slave fails computer must be restarted because if you look at EVGA precision you can see it is half way but not at full speed. Not exactly for sure what happens.

All those freezings are similar to version 2 we had but then you fixed them all but they are back with version 3.

[abstrax]

I will try to email the scene but it is so big.
I attached images of all the errors we have maybe they can help you also master log errors are attached. Pictures are slave errors. It would render for 50-80 frames and freeze up when frame is almost done. The whole 3ds max must be restarted or slaves would not work. Sometimes computer.

Thanks for sending the logs. Unfortunately I can't see any good hint at what might be the cause. Maybe wait until 3.03.4 is out (planned for release today) and check if the problem persists. I assume it will persist, in which case it would be tremendously helpful if you could somehow get the scene to us (or any scene that shows the problem). If you have the chance maybe try to test without volume rendering or try to reduce the scene complexity and see if the issue goes away. I assume the scene would then become much smaller. Maybe you can find an indication what part of the scene is causing the problems.

But again, I think it's best to wait until 3.03.4 is out.

Also a lot of the times when slave fails computer must be restarted because if you look at EVGA precision you can see it is half way but not at full speed. Not exactly for sure what happens.

Yes, that's weird. Never seen that before. Which driver version are you using?

All those freezings are similar to version 2 we had but then you fixed them all but they are back with version 3.

Kernel issues always look similar because it's all happening in CUDA land, which is more or less like a black box during runtime.

Thanks a lot for your help.

[FrankPooleFloating]

Marcus, glad you guys are okay. Did you awaken to the house shaking this morning, rather than the alarm clock?

[abstrax]

Marcus, glad you guys are okay. Did you awaken to the house shaking this morning, rather than the alarm clock?

Fortunately, the earth quake was quite far away from Auckland so we didn't notice anything and the Tsunami didn't happen: https://www.geonet.org.nz/quakes/region ... 016p661332

But thanks for asking.

[coilbook]

I will try to email the scene but it is so big.
I attached images of all the errors we have maybe they can help you also master log errors are attached. Pictures are slave errors. It would render for 50-80 frames and freeze up when frame is almost done. The whole 3ds max must be restarted or slaves would not work. Sometimes computer.

Thanks for sending the logs. Unfortunately I can't see any good hint at what might be the cause. Maybe wait until 3.03.4 is out (planned for release today) and check if the problem persists. I assume it will persist, in which case it would be tremendously helpful if you could somehow get the scene to us (or any scene that shows the problem). If you have the chance maybe try to test without volume rendering or try to reduce the scene complexity and see if the issue goes away. I assume the scene would then become much smaller. Maybe you can find an indication what part of the scene is causing the problems.

But again, I think it's best to wait until 3.03.4 is out.

Also a lot of the times when slave fails computer must be restarted because if you look at EVGA precision you can see it is half way but not at full speed. Not exactly for sure what happens.

Yes, that's weird. Never seen that before. Which driver version are you using?

All those freezings are similar to version 2 we had but then you fixed them all but they are back with version 3.

Kernel issues always look similar because it's all happening in CUDA land, which is more or less like a black box during runtime.

Thanks a lot for your help.

Ok Sounds good I will try to email it to you because of copyrighted stuff in it i cannot attach here. This scene did not have any VDB nor volume light. Also I noticed more errors happened when we added 1080 and new titan x pascals. That slave have the newest 372 drivers to support pascal. MAster and other slaves have one year old 362 drivers due to issues we had with BSOD they only have maxwell and kepler GPUs. I guess I should match all drivers on all machines

[frankjrmi]

Just got a new Mac Pro (late 2013). Installed new macOS Sierra. Can't get Octane standalone to run. Error box says:

Octane Render 3.03.3 cannot be opened because of a problem. Check with the developer to make sure OctaneRender 3.03.3 works with this version of macOS. You may need to reinstall the application. Be sure to install any available updates for the application and macOS.

I've tried reinstalling several times, no luck.

Any ideas?

[bepeg4d]

Hi frankjrmi,
have a look at this other discussion in the Apple MacOs section:
viewtopic.php?f=14&t=56333
ciao beppe