Octane Render Testing Pre-Release Pre23_3 [obsolete]

Fri Sep 10, 2010 7:48 pm

Will you ever get a 'Bug' Reporter, so's which to analyze from? or is it not needed?

Fri Sep 10, 2010 7:50 pm

have the same crashes like matej

Cuda error in file 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx : unspecified launch failure

for system information see signature

Fri Sep 10, 2010 7:51 pm

radiance wrote:Can you try installing the latest linux drivers from the nvidia home page ?

Still no luck... I installed 256.53 drivers.

Fri Sep 10, 2010 7:59 pm

It happens the same problem I reported in 2.2 with the ubuntu build of nostromo, not failed the previous radiance build.
Cuda error in file 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx : unspecified launch failure.

The problem only occurs if you use the gtx 470. With the GTX 260 works perfectly.

I tried to update the drivers as indicated radiance to cuda 3.1, but the problem remains the same.

Cheers

radiance · Fri Sep 10, 2010 8:05 pm

DayVids wrote:new aa replacement seems to just make my edges blurry and make everything look out of focus.

Product shots of DVD's now have a blurry look to them if I run them at the desired final res. and just filter them to be less steppy.

perhaps I am still going to be looking at scaling down but not as much with the new filter?

Do you have a good workflow for this? or am I possibly doing something wrong?

Can you have a look and let me know your thoughts as to what I'm seeing/what I'm doing?

It's a new filter, and maybe we put the default filter width a bit too high.
just make it a bit less in the 'filter width' option float parameter on your directlighting or pathtracing render kernel settings.

If you find a good default, feel free to post it here and we'll make it the default, but we'll probably finetune it next week if you don't have time for it

Radiance

radiance · Fri Sep 10, 2010 8:08 pm

to all linux users

I'm pulling this release (for linux) for today, it's obvious we forgot something in our tired state as we released after a 12 hour coding day.
We'll make new build and post it tomorrow.

If anyone of you has a dual boot with windows, use the windows version for tonight.

It's 10 past 10pm here, so i'm not heading to the office to make the build tonight...

Radiance

Fri Sep 10, 2010 8:15 pm

Ok, same here with 256.53.
Maybe this helps:
7ffff4bc8000-7ffff5111000 rwxp 0128e000 08:01 132207 /usr/lib64/libnvidia-glcore.so.256.53
7ffff5111000-7ffff5127000 rwxp 00000000 00:00 0
7ffff5127000-7ffff5128000 r-xp 00000000 08:01 418334 /usr/lib64/tls/libnvidia-tls.so.256.53
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe92b9710 (LWP 29566)]
0x00007ffff5cc59e5 in raise () from /lib64/libc.so.6
(gdb)

See ya, mib

Fri Sep 10, 2010 8:16 pm

There's no need to try to solve this problem tonight, we can wait. Take a rest.

Fri Sep 10, 2010 9:12 pm

Hmm interesting, I did a quick test of the linux build on my box and it worked great, none of the problems posted here. I'm using the 256.35 version of the driver, but I don't remember which version of the tool kit I have installed (it must be 3.1 ?). This version started up much faster then the previous versions and during the time I was using it, it was very responsive (even on my 220). I will do some more in-depth testing when I get home tonight. I'm really excited about the mesh lights so I will definitely test them.

Has a new version of the test scene ocs file been posted? I tried to load the one I had but I got a version error. The only problems that I encountered was mostly cosmetic. My display is small so now with the livedb window the text at the bottom of the render window gets overlayed and becomes unreadable. The other problem I had was when I dragged a material out of the livedb window and in to the node window it moved really slow. It was kind of like the mouse was moving through molasses. Other then that I had no crashes or other problems. This was on Fedora 12 linux if it helps any. This is strange as it's usually me that is having all the problems.

radiance · Fri Sep 10, 2010 9:15 pm

grimm wrote:Hmm interesting, I did a quick test of the linux build on my box and it worked great, none of the problems posted here. I'm using the 256.35 version of the driver, but I don't remember which version of the tool kit I have installed (it must be 3.1 ?). This version started up much faster then the previous versions and during the time I was using it, it was very responsive (even on my 220). I will do some more in-depth testing when I get home tonight. I'm really excited about the mesh lights so I will definitely test them. Has a new version of the test scene ocs file been posted? I tried to load the one I had but I got a version error. The only problems that I encountered was mostly cosmetic. My display is small so now with the livedb window the text at the bottom of the render window gets overlayed and becomes unreadable. The other problem I had was when I dragged a material out of the livedb window and in to the node window it moved really slow. It was kind of like the mouse was moving through molasses. Other then that I had no crashes or other problems. This was on Fedora 12 linux if it helps any. This is strange as it's usually me that is having all the problems.

hmmm,

could it be a fermi issue ? (eg GTX400 cards don't work ?)
can linux users confirm this ?

grimm -> can you post the exact versions of the toolkit/drivers you used in detail (and possibly download links) ?

Radiance