Kepler test build 2.58e Standalone (for GTX 6xx cards)

[marcio_max]

buy now 680 4 GB. tested ....... I'm shocked it's slower 470.
I'm waiting for you to optimize for Kepler.

I buy GTX 670. Only worth it because it has 4gb. This helps a lot!

[vladislav]

buy now 680 4 GB. tested ....... I'm shocked it's slower 470.
I'm waiting for you to optimize for Kepler.

I buy GTX 670. Only worth it because it has 4gb. This helps a lot!

and I had to remove the 670 and 470 to finish the project on the cards at 92 degrees celsius - very unpleasant.
I hope that soon finalize Octane Kepler developers and I can enjoy it fully.

[justix]

It has been doubled so if we finish kepler card support we can allow double the amount of textures on those cards.

--
Roeland

what's the progress about cracking the kepler pandora's box?

[MattRM]

Hi all,

Do you planed to released a Kepler version that support the instances and also found some solutions to speed up Kepler card ?

Thanks,

[kavorka]

I do believe they have stated that they are waiting for CUDA 5.0 to be released because that will help the kepler cards.

[PeterCGS]

I got a very strange bug when rendering animations. It quits randomly if I let it sit as just a icon on the taskbar (minimized/no interaction)

If I instead click on Octane after it had parsed the .obj so I see the rendering take place, everything seems to work fine. It render out everything, closes down and starts on the next frame. But its frustrating when doing a 200 frame animation to have to do it every time.

I got this problem with 2.58d aswell, but then was only happening not so often, but now it happens on almost every frame It makes no sense at all. I also have had the problem lately that sometimes my .png files arent saved out 100%. They are interrupted while writing them, so at the bottom of the pngs its a white empty row (everything from 33% of the whole image down to 5% of the last part). I dont know if this is the step that terminates Octane or not :/

It might have to do with the reason I've updated my Nvidia drivers after putting in a GTX670 card in my machine (I run win7 x64 btw)

[PeterCGS]

I removed the GTX480 today, and inserted two more GTX670 cards (3xEVGA 670 SC). Im very pleased with the total amount of VRAM I can play with, and even with three cards Im very satisfied with the speed. Now however after a frame is saved down, Octane crashes on closing

Problem signature:
Problem Event Name: APPCRASH
Application Name: octane.exe
Application Version: 0.0.0.0
Application Timestamp: 4fe15600
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec4aa8e
Exception Code: c0000005
Exception Offset: 000000000004e4b4
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1053
Additional Information 1: dff8
Additional Information 2: dff8503142ed15b11a3d74fada54227c
Additional Information 3: 2f1c
Additional Information 4: 2f1cec07fa5431b2dfefff3594f99e48

[PeterCGS]

Oh man.. I did a dirty solution now Im using mouse recorder to close the Octane crash window for every frame, repeat it for the full animation haha.

/Regards Peter K

[FooZe]

Hi Peter,

Does this still happen even with a single card?
Is multi-GPU disabled in nvidia control panel?
Also what is the rest of the configuration? A recently new motherboard and CPU?

EDIT: this actually looks like it's a base operating system problem - not necessarily octane itself. ntddl.dll is part of the OS. Are you having similar crashes with anything else like internet explorer?

Cheers
Chris.

[PeterCGS]

Hi Chris, no I dont have any other crashes.

The CPU is a i7 hexacore 980 with 24GB ram. Don't remeber the exakt model of the mobo but its a Gigabyte and has been running flawless the last two years.

I've ran 2x480GTX cards without any problem. For this project Im doing now the VRAM wasnt enough, so I tested replacing one of the 480 cards with a 670 running this build. Everything worked fine, so I decided to get two more 670 cards. As soon as I put more than one 670 card into my system the crashes began. I dont have any multi GPU enabled, so Im little puzzled :/ The crash happens exactly when Octane closes down.