Dear JimStar.
I have a scene in which all geometry is grouped by layers. The day before and all worked fine. Today the scene when rendering fails. By turning off all layers and then adding each of them I figured out which layer is causing the error. Such error occurs a second time with different layers. Here Is The Error Log:
Started logging on 15.05.15 08:23:19
OctaneRender 2.23.1 (2230001)
CUDA error 700 on device 1: Error code unknown.
-> kernel execution failed (dl)
device 1: direct lighting failed
CUDA error 700 on device 1: Error code unknown.
-> failed to deallocate device memory
CUDA error 700 on device 1: Error code unknown.
-> could not get memory info
device 1: failed to upload data texture 4 of context 0
CUDA error 700 on device 1: Error code unknown.
-> failed to allocated device memory
device 1: failed to upload data texture 4 of context 0
CUDA error 700 on device 1: Error code unknown.
-> failed to allocated device memory
device 1: failed to upload data texture 4 of context 0
Octane 2.31.1-1.6
Scene stopped to render
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)
-
AlexMakhov
- Posts: 21
- Joined: Thu Feb 12, 2015 12:22 pm
After update to 1.8 i have same error. Error Log:
Started logging on 15.05.15 09:31:13
OctaneRender 2.23.2 (2230002)
CUDA error 700 on device 1: Error code unknown.
-> kernel execution failed (pt)
device 1: path tracing failed
CUDA error 700 on device 1: Error code unknown.
-> failed to clear linear 2D device memory
CUDA error 700 on device 1: Error code unknown.
-> failed to load symbol data to the device (kernel data)
device 1: direct lighting failed
Started logging on 15.05.15 09:31:13
OctaneRender 2.23.2 (2230002)
CUDA error 700 on device 1: Error code unknown.
-> kernel execution failed (pt)
device 1: path tracing failed
CUDA error 700 on device 1: Error code unknown.
-> failed to clear linear 2D device memory
CUDA error 700 on device 1: Error code unknown.
-> failed to load symbol data to the device (kernel data)
device 1: direct lighting failed
-
AlexMakhov
- Posts: 21
- Joined: Thu Feb 12, 2015 12:22 pm
Reboot does not help. To the device 1 was not a question. This Titan z which has worked perfectly. Driver the latest version.JimStar wrote:AlexMakhov
This error happens on level lower than the plugin. Looks like some problems with GPU or driver...
Have you tried the machine reboot? Are you sure the GPU (device 1) is OK?..
-
AlexMakhov
- Posts: 21
- Joined: Thu Feb 12, 2015 12:22 pm
This layer is frozen and has not been edited for a long time.JimStar wrote:If this happens only with one layer in one scene - then try to find what have you changed there since it was working.
Maybe just added some heavy meshes or textures that exceed the GPU memory...
I tried to open backup file of the previous day when everything worked, but it gave no results.
-
AlexMakhov
- Posts: 21
- Joined: Thu Feb 12, 2015 12:22 pm
All layers off except the one that causes the error.
- Attachments
-
AlexMakhov
Then just try to think logically:
- Your scene was working yesterday with 1.6 plugin.
- You did not touch anything in the scene.
- You did not change the plugin version 1.6. So, the plugin code was not changed, it is still the same plugin that worked on the untouched scene yesterday.
- Today your untouched scene does not render with the same untouched 1.6 plugin.
Basing on this logic - it's not a plugin issue. This is still the same version with the same code that it had yesterday. And it is given to render the same untouched scene.
If you are absolutely sure nothing in the scene was changed - then it is not the scene issue...
What's left?
So, either check the GPU (e.g. overheating on some stage of rendering), or search what was changed in the scene... I see the big amount of mesh nodes, so you may have exceeded the nodes amount limit after adding something to the scene...
Then just try to think logically:
- Your scene was working yesterday with 1.6 plugin.
- You did not touch anything in the scene.
- You did not change the plugin version 1.6. So, the plugin code was not changed, it is still the same plugin that worked on the untouched scene yesterday.
- Today your untouched scene does not render with the same untouched 1.6 plugin.
Basing on this logic - it's not a plugin issue. This is still the same version with the same code that it had yesterday. And it is given to render the same untouched scene.
If you are absolutely sure nothing in the scene was changed - then it is not the scene issue...
What's left?
So, either check the GPU (e.g. overheating on some stage of rendering), or search what was changed in the scene... I see the big amount of mesh nodes, so you may have exceeded the nodes amount limit after adding something to the scene...
-
AlexMakhov
- Posts: 21
- Joined: Thu Feb 12, 2015 12:22 pm
Device 0 and 1 is Titan Z. the Device 2 is Titan Black. In the settings include only Black and everything works fine.
AlexMakhov wrote:Device 0 and 1 is Titan Z. the Device 2 is Titan Black. In the settings include only Black and everything works fine.
So, looks like it is still a question...AlexMakhov wrote:To the device 1 was not a question. This Titan z which has worked perfectly.