OctaneRender® pre-Beta 2.41 (win x64) [OBSOLETE]

Thu Jan 20, 2011 7:39 pm

I think I've found a bit of a bug in the OBJ/MTL import. If you have a material which has specular setting of 1,0,0 (bright red) when this imports into Octane, the specular is set to 0.5,0,0 (medium red) it appears as if specular values are being halved on import.

Thu Jan 20, 2011 8:00 pm

Have found another issue.
Maybe the ram of the Card isn´t enough.
If I render an image with 8192px x 8192px and switch on the alphachannel, the mesh becomes invisible.
Without the alphachannel, the scene uses 1290MB. With alpha, it should use ~1750MB.

If I save the scene with alphachannel on and want to render a new one with my plugin, Octane starts, load the scene and before the render begins, Octane close...

face

Thu Jan 20, 2011 8:06 pm

I can make a video if it helps...

face

Thu Jan 20, 2011 8:45 pm

Yup, looks like it runs out of memory. Does it work with smaller image sizes? Like 4K square? I don't see a way to "fix" that beside having a better error handling.

Cheers,
Marcus

Thu Jan 20, 2011 8:49 pm

Yes, with smaler images, it works.
But i think, with 2GB it should work with 8192px² too...
The alphachannel should use around 1/3 of the size from a normal image, maybe there can be a warning if the user want to turn on the alpha option and the ram isn´t enough.

face

radiance · Fri Jan 21, 2011 2:23 am

steveps3 wrote:I think I've found a bit of a bug in the OBJ/MTL import. If you have a material which has specular setting of 1,0,0 (bright red) when this imports into Octane, the specular is set to 0.5,0,0 (medium red) it appears as if specular values are being halved on import.

This is intentional as our specular channel on glossy is 2x as powerfull as the 50/50 range values used in most 3d apps.

Radiance

Fri Jan 21, 2011 7:26 am

After some more testing managed 10m tris @ 800x800

BTW vram use for Geometry isnt reported correctly at the bottom. - reported this once before.

For those interested .obj was 444mb and the blend was 498mb.
Took a while to load and used all 8gb and some disk space, but it worked!

Fri Jan 21, 2011 7:28 am

pixelrush wrote:...
BTW vram use for Geometry isnt reported correctly at the bottom. - reported this once before.

Thanks for the info. Noted.

Cheers,
Marcus

Fri Jan 21, 2011 9:42 am

I tried another 10m tri mesh and strangely enough this one takes less vram. 1725mb.
Dont know why that is... In this case it would be possible to squeeze in another 1m tris.
Never the less here attach is a quick render of the Stanford Thai Statue for the first time in Octane.

Issue --> the Node Inspector isnt refreshing properly after changing material type - its just a blank view (in 2.42 that is)

Fri Jan 21, 2011 10:06 am

Hi.
It seems to me that I found two small bugs.

1. I wrote down a job with maximized the preview window.
After opening the file again, I could not get back to normal windows. All windows and bars I had to change manually.

2. In preview window I can not create a vertical image. You can set any size of the preview, but only if it is a horizontal rectangle, or square. With values, which should give a vertical rectangle picture always comes back to the square.

Pozdrawiam Marcin