Hi, I encountered a very weird behaviour with pre 2.3 v5 :
Very often, Octane stops rendering after 13, 17 or 19 samples per pixel...
The GUI remains partially active, but rendering doesn't work and can't be reset or enabled again. Then I have to close it and start it again, but Octane freezes when attempting to close it, instead of exiting.
This happens on heavy and simple scenes as well. I have absolutely no clue about the reason.
Octane stops rendering after 13 or 17 samples per pixel...
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Hi ROUBAL,
have you enlarged the octane window on the second monitor as you said in another post?
doing this I have found a problem very similar with your but I discovered that in reality octane continuing rendering but the window didn't refresh
so I stopped to enlarge the window and all works smoothly
ciao beppe
have you enlarged the octane window on the second monitor as you said in another post?
doing this I have found a problem very similar with your but I discovered that in reality octane continuing rendering but the window didn't refresh
so I stopped to enlarge the window and all works smoothly
ciao beppe
In the "Mesh Preview Kernel" try changing rayepsilon to 0.0020 or more.
http://www.OctanePowerTools.com
Octane Render Power Tools, Animation Tools for Octane Render
facebook | YouTube
Intel Core i7 920 @ 2.67GHz - RAM 12.0 GB
Asus P6T7 WS SuperComputer GTX 480
Octane Render Power Tools, Animation Tools for Octane Render
facebook | YouTube
Intel Core i7 920 @ 2.67GHz - RAM 12.0 GB
Asus P6T7 WS SuperComputer GTX 480
I have two 4/3 monitors, but I used only one with Octane when it happened. I had an other software opened on the right screen : Acdsee displaying reference images.
I will try the rayepsilon trick...
Thank you !
EDIT : I have tried with the rayepsilon at 0.002 and 0.02 with no more success.
Render stops at 13 or 17 spx...
I will try the rayepsilon trick...
Thank you !
EDIT : I have tried with the rayepsilon at 0.002 and 0.02 with no more success.
Render stops at 13 or 17 spx...
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Well, 3 weeks later and no response or advice at all from Refractive...
I really hope that this bug will be solved in 2.3 v6, because I can't use Octane for 3 weeks now !
I really hope that this bug will be solved in 2.3 v6, because I can't use Octane for 3 weeks now !
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
-
enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
Hi Roubal,
I encounter this problem several times and it was due to bad scale, I accidently selected the miles unit instead of meter in the Blender script.
Duno if this may help
I encounter this problem several times and it was due to bad scale, I accidently selected the miles unit instead of meter in the Blender script.
Duno if this may help
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
Does the problem occur only in a particular scene or with all scenes?
Which graphics driver are you using?
Your problem doesn't sound like it's related to the GPU timeout, but just to be sure, could you please reinstall version 1.022b using the installer? This way the GPU timeout gets disabled. The 2.3 versions only come without an installer and the registry fix is not applied.
Cheers,
Marcus
Which graphics driver are you using?
Your problem doesn't sound like it's related to the GPU timeout, but just to be sure, could you please reinstall version 1.022b using the installer? This way the GPU timeout gets disabled. The 2.3 versions only come without an installer and the registry fix is not applied.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Thank you Enrico and Abstrax,
The trouble occurs as well on light and heavy scenes.
I use NVidia Driver version : 8.17.12.5896
I have unistalled 2.2 and reinstalled it.
I have reloaded a 400MB scene and rendered it correctly. So, at least at first glance, the problem of rendering stopped at frame 13 17 or 19 has disappeared.
Now, I fall again in an other bug that I already submitted that prevents me to go forward on my project :
When I relink an obj with more geometry, Octane 2.3 v5 stops rendering during voxelizing and freezes... I encounter the same trouble in 2.2. Seems to happen only on big scenes, but I have used only 1/3 of my 1.5GB, so It doesn't look like a memory limit.
When loaded separately, the relinked obj loads correctly, so it is not an export error with unauthorized settings or Empty objects in the file.
I'm damned! I love Octane , but I can't use it !
These past 3 days, I have reinstalled from scratch all my Win 7 Pro x64 system on a bigger hard disk. As I was working on a cloned system (as I had few time and wanted also to take some safety measure when Octane has required Internet, I cloned my system) I suspected that most softwares crashes were due to an unstable clone, but I notice unfortunately that even with a very clean new install, Octane, Blender and some other softwares (particle Illusion) that had never crashed under Win XP 32 bits are not stable under Win 7 Pro x64. I switched to Win7 64bits to get benefit of more memory, but I really hate my new OS !
I have downloaded from ASUS site a patch supposed to improve compatibility between the P35 chipset and the OS (Win 7 x64supported). I have installed it, but I notice no change.
The two GPU used for rendering fall down to 0% after some voxelizing time and Octane freezes...
The trouble occurs as well on light and heavy scenes.
I use NVidia Driver version : 8.17.12.5896
I have unistalled 2.2 and reinstalled it.
I have reloaded a 400MB scene and rendered it correctly. So, at least at first glance, the problem of rendering stopped at frame 13 17 or 19 has disappeared.
Now, I fall again in an other bug that I already submitted that prevents me to go forward on my project :
When I relink an obj with more geometry, Octane 2.3 v5 stops rendering during voxelizing and freezes... I encounter the same trouble in 2.2. Seems to happen only on big scenes, but I have used only 1/3 of my 1.5GB, so It doesn't look like a memory limit.
When loaded separately, the relinked obj loads correctly, so it is not an export error with unauthorized settings or Empty objects in the file.
I'm damned! I love Octane , but I can't use it !
These past 3 days, I have reinstalled from scratch all my Win 7 Pro x64 system on a bigger hard disk. As I was working on a cloned system (as I had few time and wanted also to take some safety measure when Octane has required Internet, I cloned my system) I suspected that most softwares crashes were due to an unstable clone, but I notice unfortunately that even with a very clean new install, Octane, Blender and some other softwares (particle Illusion) that had never crashed under Win XP 32 bits are not stable under Win 7 Pro x64. I switched to Win7 64bits to get benefit of more memory, but I really hate my new OS !
I have downloaded from ASUS site a patch supposed to improve compatibility between the P35 chipset and the OS (Win 7 x64supported). I have installed it, but I notice no change.
The two GPU used for rendering fall down to 0% after some voxelizing time and Octane freezes...
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
The relinking problem might be fixed now. The relinking fixes will become available with the upcoming release 1.023 v5b, which will be mainly a bug-fix release. Also please update your nVidia driver to 260.99 (the latest release version). To be sure, that there is no other problem, could you please send me the scene scene via mail (I will send you the address via PM).
Cheers,
Marcus
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra