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.
What was the version of the new and the old graphics drivers?Carl S. wrote:I haven't tested this with Octane so ignore this if necessary but I was just having the same exact problem rendering with Iray with the new graphics driver. I reverted back to the old one and all is fine again.
Thanks,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
New:260.99abstrax wrote:What was the version of the new and the old graphics drivers?Carl S. wrote:I haven't tested this with Octane so ignore this if necessary but I was just having the same exact problem rendering with Iray with the new graphics driver. I reverted back to the old one and all is fine again.
Thanks,
Marcus
Older:258.96
Hi Marcus,
I just see the posts here, so I haven't yet downloaded the most recent Nvidia driver, but by a very weird and mysterious side effect, you solved all my problems :
In your Private Message, you asked me to send you the whole scene files.
As it includes numerous heavy file for an amount of 324 Mo, I have copied all the files in a folder, and compressed it in a Zip file of 73MB.
I was going to upload it on my FTP when I had the idea of unzipping the files for verification purpose, and I tested the ocs file from the unzipped folder. The file opened fine and started rendering. Then, I tried to relink the most recent obj file with modified geometry and added character : It worked !!!
I saved a new ocs file, closed Octane, opened it again and loaded the recent ocs : everything is OK. I tested with both 2.2 and 2.3 v5... it works !
I don't understand...
I just see the posts here, so I haven't yet downloaded the most recent Nvidia driver, but by a very weird and mysterious side effect, you solved all my problems :
In your Private Message, you asked me to send you the whole scene files.
As it includes numerous heavy file for an amount of 324 Mo, I have copied all the files in a folder, and compressed it in a Zip file of 73MB.
I was going to upload it on my FTP when I had the idea of unzipping the files for verification purpose, and I tested the ocs file from the unzipped folder. The file opened fine and started rendering. Then, I tried to relink the most recent obj file with modified geometry and added character : It worked !!!
I saved a new ocs file, closed Octane, opened it again and loaded the recent ocs : everything is OK. I tested with both 2.2 and 2.3 v5... it works !
I don't understand...

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.
actually it does, it could have something to do with filepaths, hence when you "dumped" all in a single folder (where octane checks anyway when it can't find a resource anyway) it solved. It's worth checking it out.
I've recently had this crash kind of like the one you where first pointing out, and I'm almost certain it had to do with having coplanar faces in some objects due to a mistake in my modeling process (quite stupid setup up one), it worked fine but after some random samples where processed (from 100 to 2000) octane stopped, not crashed, but it couldn't be closed and when I forced it, it wouldn't start again till I rebooted the OS, I was quite surprised and by chance I tried hmk's rayepsilon trick, it worked, then I found out some "textures" weren't showing, and I found out the freaking coplanar faces, once solved octane started working normally with standard rayepsilon, I have to do some further testing but I don't have much time now, I'll do so later on (also Radiance if you want I can upload you the problematic files).
If I don't make much sense, spare me, I'm on a low sleep diet as of late
I've recently had this crash kind of like the one you where first pointing out, and I'm almost certain it had to do with having coplanar faces in some objects due to a mistake in my modeling process (quite stupid setup up one), it worked fine but after some random samples where processed (from 100 to 2000) octane stopped, not crashed, but it couldn't be closed and when I forced it, it wouldn't start again till I rebooted the OS, I was quite surprised and by chance I tried hmk's rayepsilon trick, it worked, then I found out some "textures" weren't showing, and I found out the freaking coplanar faces, once solved octane started working normally with standard rayepsilon, I have to do some further testing but I don't have much time now, I'll do so later on (also Radiance if you want I can upload you the problematic files).
If I don't make much sense, spare me, I'm on a low sleep diet as of late

windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
Did those objects have alpha maps? We fixed a nasty bug that can make Octane lock up, if a material has an alpha texture that is at least in some places 0.kubo wrote:actually it does, it could have something to do with filepaths, hence when you "dumped" all in a single folder (where octane checks anyway when it can't find a resource anyway) it solved. It's worth checking it out.
I've recently had this crash kind of like the one you where first pointing out, and I'm almost certain it had to do with having coplanar faces in some objects due to a mistake in my modeling process (quite stupid setup up one), it worked fine but after some random samples where processed (from 100 to 2000) octane stopped, not crashed, but it couldn't be closed and when I forced it, it wouldn't start again till I rebooted the OS, I was quite surprised and by chance I tried hmk's rayepsilon trick, it worked, then I found out some "textures" weren't showing, and I found out the freaking coplanar faces, once solved octane started working normally with standard rayepsilon, I have to do some further testing but I don't have much time now, I'll do so later on (also Radiance if you want I can upload you the problematic files).
If I don't make much sense, spare me, I'm on a low sleep diet as of late
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
yeap, actually some of those had alpha maps.
Great to know you found that bug, now kill it with fire!!!
then if I understand it correctly could it be "fixed" in the meantime lowering the texture power under 1.00? that way it shouldn't have a 0 value.
Great to know you found that bug, now kill it with fire!!!

then if I understand it correctly could it be "fixed" in the meantime lowering the texture power under 1.00? that way it shouldn't have a 0 value.
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
With alphamap you mean a opacity map?
A workaroud for a opacity map with value 0 is to use a black texture
That works for me...
face
A workaroud for a opacity map with value 0 is to use a black texture

That works for me...
face
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
Yes I mean the opacity map. And the problem occurs, if at least parts of the opacity texture becomes 0, i.e. black. That means reducing the power or using a black texture doesn't help here. But it doesn't happen always - in the end a few factors play a role, like size of the geometry, ray epsilon and other things.
Anyway this problem is now fixed and the fix will become available with the next release, which I hope is not too far away.
Cheers,
Marcus
Anyway this problem is now fixed and the fix will become available with the next release, which I hope is not too far away.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hm, i haven´t no crashes if i use a black texture on the same scene that makes trouble without a texture...
Ok, maybe the other factors become important.
face
Ok, maybe the other factors become important.
face
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578