Octane Render Testing Pre-Release Pre23_3 [obsolete]

[grimm]

Sure no problem, although it is going to have to wait until I get home. My copy of octane is registered to my home computer and I'm at work right now.

[livuxman]

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

In my previous post I mentioned that with the GTX260 works well, but it fails with the gtx470. The problem started to me (on the 470) with the 2.2 ubuntu build published some time ago.

For my part there is no hurry, take all the time.

Cheers

[radiance]

has any linux user managed to get an image with a fermi card (eg GTX400 series) even if it's unstable or crashes ?
eg, not the launch failure.

that will probably nail the issue and we'll be able to give a fix tomorrow early.

Radiance

[derjens]

when i use only my 8800 Ultra as active instead ma GTX 460 all is fine.
It seems that the problem is only on GTX400 based cards.

[radiance]

ok, i think we were a bit too exhausted and did'nt notice the fermi option was not enabled on our linux build machine when we made the builds.
i'll post the download link of the non-fermi version here for now, expect a fully fermi compatible release tomorrow early

Only for users of GTX200 or older cards for today:
http://www.refractivesoftware.com/rcdow ... ux_x64.zip

Yours,
Radiance

[imensah]

not sure if this is fixed yet but
there is no light transmission through glass and still some anomalies related to the smooth bool. no light through glas eally sucks. I've noticed some achieve this in some gallery images and im not sure how they are doing it

[pixelrush]

ok issue time... a few to start off with anyway..

1. Fstop doesnt seem to be giving more depth of field - sure it darkens which you can compensate with exposure but no actual change?? seems a very narrow depth? not sure autofocus is working. see pics - slight exp difference caused my me

2. Request: can we have a portrait mode button for the image resolution please
and when you change to 'custom' could it default to what you have presently while you change it - goes to zero presently.

3. Film size in vram seems to be additive of the initial amount used, on each change - something is not quite right yet sorry guys.

4. Still have issue with a scene with polys maxing use of vram not being visible when rendering. Found this is related to image size.
1024x512 was black and going 37msps. Making it 700x500 it worked ok at right speed. This was the max size I could get even though I apparently had enough vram space for larger. When I used an 800x400hdr from the demo scenes for lighting I needed to cut back the size to 600x400 again else it was black. In some res cases the image gradually became darker over time and others the view would brighten momentarily from black only with mouse action in the viewport but it would not rotate the view etc.
Seems to need some empty (undocumented) space for workings?
I still had 83 or os mb unused with the initial 1024x512 load that wouldnt display.
After changing to 700x500 it was showing 84mb free. ie 1mb diff but seemingly needing the extra space.
Issue 3 was not helping but perhaps something about the vram space is not reported correctly?
I admit being this full is an extreme case but I just mention the behaviour.

5.Previously reported bug with specular colour being lost to white on material type change is still present

6.Reset camera view to default with material ball doesnt reset to a useful position

[DayVids]

ok issue time... a few to start off with anyway..

1. Fstop doesnt seem to be giving more depth of field - sure it darkens which you can compensate with exposure but no actual change?? seems a very narrow depth? not sure autofocus is working. see pics - slight exp difference caused my me

Aperature is used to adjust DOF separately from f-stop ( always has been ).

Threw me for a loop first time in too .

[mib2berlin]

The latest linux version still crashes if i change materials in every file i test.
Sometimes earlier, sometimes later but within a few minutes.
Tested with 256.35/44/53 with cuda toolkit 3.0 and 3.1.

Cheers mib

[pixelrush]

@DayVids
Well I've never noticed it before probably why it hasnt worked for me very well in the past

so Fstop doesnt actually do anything? other than be a sort of anti exposure?

I dont know, isnt it sort of counter intuitive to not set dof by the camera Fstop setting?

Shouldnt the actual effect of Fstop and aperture as they are be the other way around?

I would have thought changing the aperture would reduce the light entering the lens and exposure is about the film, whereas Fstop is intended to limit the focus..dunno..

Edit: btw another issue is that I think the filtersize could be 1.25 default and range be 1-3