Octane Render Commercial v1.02 beta2 Released Tweet

[yijian4515]

Are you chinese,Contact me,[email protected]

i want to with you talk about this render

[lolko7]

Is any chance for octane Render DEMO v1.02 beta for linux ? I don't want create new post therefore i ask here.
Your linux DEMO version 0.8a and 0.81 don't work for me :
/rendertarget.cpp' in line 557 : no CUDA-capable device is available
I think that driver version 195.36.15 not work with this release of Octane Render. I downgrade driver and check it out but DEMO version for last driver with Cuda 3.0 will be great.
Octane render looks amazing but i don't know if he work on my spec. This is very interesting alternative.
Thanks and Greetings for All Octane Team

[radiance]

Hi,

There are currently too much issues on linux that i'd like to wait and provide a demo for linux with the next upcoming beta 2.1 bugfix release.
there are quite a few issues on linux that i'd like to clear up first, before we release another demo for it.

Radiance

[teknofreek]

Hi, have been on the side looking at Octane for a while, currently got the latest demo and as per previous posts found it is locked at a 1024 x 512 res..
What resolution limitations are on the commercial release, if any? That is v1.02 beta2.
I am seriously thinking of getting this product to aid some serious archvis I want to provide to clients, but would need hi res print capable files.
at least 4800 x 4800 ppi (approx 14" x at 300dpi) Hopefully up to 8k. Is this possible at the current level of development? ie If I buy a commercial license?
Also what formats is the prog capable of saving in?
Sorry if this is obvious (somewhere..) but I couldn't find anything on the output capabilities only import.

Thx!
Teknofreek

[radiance]

Hi, have been on the side looking at Octane for a while, currently got the latest demo and as per previous posts found it is locked at a 1024 x 512 res..
What resolution limitations are on the commercial release, if any? That is v1.02 beta2.
I am seriously thinking of getting this product to aid some serious archvis I want to provide to clients, but would need hi res print capable files.
at least 4800 x 4800 ppi (approx 14" x at 300dpi) Hopefully up to 8k. Is this possible at the current level of development? ie If I buy a commercial license?
Also what formats is the prog capable of saving in?
Sorry if this is obvious (somewhere..) but I couldn't find anything on the output capabilities only import.

Thx!
Teknofreek

Hi,

It depends on your GPU. with current cards we're getting practical usage (eg enough room for a decent scene and the HDR film buffer) up to 4000x4000, then it gets tricky.
I think with newer cards like the GTX400 series which have a 48bit memory model and will be offered later this year with more onboard memory, you should be able to go to 8000x8000.

Radiance

[RenderWilli]

@radiance
Perhaps an extra option for outputting high resolution images could be a solution.
Creating an image of the current scene without the whole HDR film on the GPU.
A preview resolution in the viewport and tile rendering for the final HDR film to harddrive.
Could be a perfect solution for archvis.

[teknofreek]

Thanks Radiance, I did think a bit harder later and realised size would be GPU mem based, but good to know a basic limit. I've had a lot of scenes crash, that is load ok but when I click on the mesh to get the ball rolling it takes ages to bring up the materials (sometimes never) and eventually drops out to the W7 desktop. Using W7 64bit home prem. GTX 260 896 mb ddr3.
It's a bit of a weird one as am not sure what does it. The silly thing is I can load a different scene with what I know from my other renderer, are larger, poly and textures wise, and it will be ok. Also from what I think are fairly large files, I am only using no more than 300 or so mb on the gpu. (a crasher file does not get to the position I can check what mem useage it has, or had...) Is the commercial version more stable?
Anyway, I may post further in the demo area regards this issue, but my real interest is getting a commercial ver, so have posted here at present.
I do understand that it is a beta and may still have some stability issues, if there are some workarounds, pls let me know. ( I did see something regards editing the registry for timeouts or whatever, is this a reasonable / ok thing to do?)


Cheers!
TF.

[radiance]

Thanks Radiance, I did think a bit harder later and realised size would be GPU mem based, but good to know a basic limit. I've had a lot of scenes crash, that is load ok but when I click on the mesh to get the ball rolling it takes ages to bring up the materials (sometimes never) and eventually drops out to the W7 desktop. Using W7 64bit home prem. GTX 260 896 mb ddr3.
It's a bit of a weird one as am not sure what does it. The silly thing is I can load a different scene with what I know from my other renderer, are larger, poly and textures wise, and it will be ok. Also from what I think are fairly large files, I am only using no more than 300 or so mb on the gpu. (a crasher file does not get to the position I can check what mem useage it has, or had...) Is the commercial version more stable?
Anyway, I may post further in the demo area regards this issue, but my real interest is getting a commercial ver, so have posted here at present.
I do understand that it is a beta and may still have some stability issues, if there are some workarounds, pls let me know. ( I did see something regards editing the registry for timeouts or whatever, is this a reasonable / ok thing to do?)


Cheers!
TF.

you need to apply the registry tweak for the watchdog timeout of the gpu driver here: viewtopic.php?f=21&t=824

we're including these in our next release as easily installable registry files.

Radiance

[radiance]

@radiance
Perhaps an extra option for outputting high resolution images could be a solution.
Creating an image of the current scene without the whole HDR film on the GPU.
A preview resolution in the viewport and tile rendering for the final HDR film to harddrive.
Could be a perfect solution for archvis.

it's not that easy.
with MLT, the only kernel that can render decent images with no fireflies, you can't render an image in parts,
as you'll get different normalization (eg brightness) for the different tiles.

it's a tough task and i'm sure recent advancements in gpu memory will soon solve this issue. cards with 3GB will soon be available as commodity hardware.

Radiance

[meleseDESIGN]

C4D is able to Render 16K images and unlimited tiles of your scene.
But with Octane, more then 4K makes no sense because of the missing but needed RAM on current gfx cards. 4K is totaly ok, my Sony Alpha 350 wont give me a higher resolution.

Only one question: Why will you get different brightness for tiles with MLT? What about rendering tiles without MLT? Splitt the Camera view in Octane in 9 tiles (or even more), each 3-4K and after rendering you can stitch the outputed tiles together in Photoshop and you have an 9Kx9K/12Kx12K final image.

Like in C4D.

it's not that easy.
with MLT, the only kernel that can render decent images with no fireflies, you can't render an image in parts,
as you'll get different normalization (eg brightness) for the different tiles.

it's a tough task and i'm sure recent advancements in gpu memory will soon solve this issue. cards with 3GB will soon be available as commodity hardware.

Radiance