Hello,
I've installed OctaneRender™ 4.0 for Houdini™ - beta build 4.00.0.8 XB3, it works well, i've just tried basic things, but when i activate the denoiser, my computer reboot.
Sometimes it works 5 minutes before rebooting, sometimes it reboot as soon as i activate the denoiser.
But when it works, it's very impressive!!! Good work guys!
My setup :
- Win 10, 1803, 17134.112
- geforce 780 3GB for display and 1080Ti 11GB for rendering, driver 398.11
- Houdini indie 16.5.496
- Octane 4.0 for Houdini, subscription license.
Computer Reboot when using denoiser
Moderator: juanjgon
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Hi,
Hmm, I've not seen any problem on this build that could reboot the system. This is weird system level crash. Are you sure that you have your display GPU also disabled for denosing? Be aware that the GPU can be disabled for rendering, but still enabled for denoising. Both options must be disabled in the plugin options panel, GPUs tab.
Thanks,
-Juanjo
Hmm, I've not seen any problem on this build that could reboot the system. This is weird system level crash. Are you sure that you have your display GPU also disabled for denosing? Be aware that the GPU can be disabled for rendering, but still enabled for denoising. Both options must be disabled in the plugin options panel, GPUs tab.
Thanks,
-Juanjo
Hello,
You're right, it was still enabled.
I have disabled the options, but it's still rebooting as soon as i activate the denoiser.
Everything is working good, except the denoiser. I don't understand why, i hope there is no problem with my computer...
You're right, it was still enabled.
I have disabled the options, but it's still rebooting as soon as i activate the denoiser.
Everything is working good, except the denoiser. I don't understand why, i hope there is no problem with my computer...
Hmm, even if you enable the denoising only in the 1080Ti GPU, and with any scene? It is a weird issue, here using 1080 GPUs all seem to work fine.
Can you please enable the plugin log file in "debug" mode in the plugin options panel, debug tab, and attach the log that you get after one of these crashes?
Thanks,
-Juanjo
Can you please enable the plugin log file in "debug" mode in the plugin options panel, debug tab, and attach the log that you get after one of these crashes?
Thanks,
-Juanjo
Hello,
any scene...
Here is the log file.
any scene...
Here is the log file.
- Attachments
-
- octane.log
- (65.98 KiB) Downloaded 196 times
Well, nothing related to CUDA or any other kind of error is reported in the log, so it is hard to know what could be the problem. Here all seems to work fine, and I don't have other reports about a problem like that.
It seems a hard system crash. It could be a drivers issue, perhaps you could try to update them to the latest ones available, or if you have the latest ones downgrade to one a bit older and try again. It could be also a hardware issue, but it is weird that the problem only happens with the denoiser feature enabled. Could you have perhaps your CPU or your GPUs overclocked?
One good test could be to try to render a scene using the Standalone 4.0 XB3 with the denoiser enabled to see if it has the same problem. You can download it here:
viewtopic.php?f=33&t=67790
Thanks,
-Juanjo
It seems a hard system crash. It could be a drivers issue, perhaps you could try to update them to the latest ones available, or if you have the latest ones downgrade to one a bit older and try again. It could be also a hardware issue, but it is weird that the problem only happens with the denoiser feature enabled. Could you have perhaps your CPU or your GPUs overclocked?
One good test could be to try to render a scene using the Standalone 4.0 XB3 with the denoiser enabled to see if it has the same problem. You can download it here:
viewtopic.php?f=33&t=67790
Thanks,
-Juanjo
Hello juanjgon,
i've tried the Standalone 4.0 XB3, it's the same problem, as soon as the denoising process start, the computer reboot.
I 've update my drivers, nothing change, still rebooting.
It's not the "houdini version", so it's probably a hardware issue. But i don't know where. The CPU and GPU are not overclocked.
i've tried the Standalone 4.0 XB3, it's the same problem, as soon as the denoising process start, the computer reboot.
I 've update my drivers, nothing change, still rebooting.
It's not the "houdini version", so it's probably a hardware issue. But i don't know where. The CPU and GPU are not overclocked.
If you can reproduce this problem with the Standalone, perhaps you could post it in the Standalone release post to see if you can help the core devs to fix it. You could also wait for the next release, that probably is around the corner, to see if this problem has been already fixed.
In any case, I don't have other reports about a problem like that, so all sounds to me like a weird hardware or system issue.
Thanks,
-juanjo
In any case, I don't have other reports about a problem like that, so all sounds to me like a weird hardware or system issue.
Thanks,
-juanjo