OctaneRender® 1.025 beta 2.50 [OBSOLETE]

[necko77]

certain hdri's slow my system down to a crawl, .19 Msamples/s. And when I change out the hdri I go back up to normal, (which is between 2.5 and 7.5 Msamples/s).

same stuff wtih me...reloading hdri or using sun light system after HDRI map speed up computing and octane responce

[abstrax]

certain hdri's slow my system down to a crawl, .19 Msamples/s. And when I change out the hdri I go back up to normal, (which is between 2.5 and 7.5 Msamples/s).

same stuff wtih me...reloading hdri or using sun light system after HDRI map speed up computing and octane responce

Interesting. Could you send us a scene (incl. textures and HDRI) that creates this problem?

Thanks,
Marcus

[necko77]

i allready overwrite that scene . . . i will try to find files tomorow cos that was test on fly

[Mugga]

Ok, thanks for the info. Could you please test the same scene and resolution in beta 2.46b. I would be surprised, if there is much of a difference, but am curious if for some reason the UI behaves better.

In general, if you render on the same graphics card, that is used for display, the UI feels "sluggish", because during each kernel call, the framebuffer will not be updated. I.e. even though the UI drawing happens, you can't see it. Since beta 2.48b we try now to use smaller work chunks in path tracing and direct lighting, which should improve things a bit, but the general problem is still there and is hard to solve without affecting the performance.

If you really want to work in parallel to rendering, get a cheap display card (any that supports OpenGL 2.1 can be used) and use the GTX headless for Octane rendering only.

Cheers,
Marcus

Hey Marcus,

i have the same problem with very slow ui. But the overall system responsiveness depends on the scene you are rendering. When i render a very heavy scene i can't really use my pc at all. And i already got a onboard graphic. But because i got 3 monitors i have to conntect two to the onboard and one to the display. But it really doesen't matter which display i use.

Isn't there a possibilty to change the priority? Similar to the CPU priority in the windows task manager?

[DayVids]

certain hdri's slow my system down to a crawl, .19 Msamples/s. And when I change out the hdri I go back up to normal, (which is between 2.5 and 7.5 Msamples/s).

same stuff wtih me...reloading hdri or using sun light system after HDRI map speed up computing and octane response

Interesting. Could you send us a scene (incl. textures and HDRI) that creates this problem?

Thanks,
Marcus

Well, it turned out for me, that I had forgotten I had SLI on from testing if it improved some OpenGL performance on some of my video filter plug-ins ( it appears to not actually ).

So when I disabled SLI, then the performance was identical with both HDRI's. I don't know if you're still interested in the project files, but I'll certainly upload them for you if you want me to still.

[GDRS]

Hello there been some time since our last post due to heavy projects.

Some issues we have with 2.50

1) All scenes tested with the exact settings are way slower with 2.50

2) On direct lighting ambient occlusion (3) or diffuse when samples are greater than 4000 and diffuse depth greater than 2 octane crashes the second the render finishes with out letting the user to save the image we can save it at 3999 but never at render finish due to the crash.

3) Some sliders are not working or dont allow decimal (as other users pointed out)

4) Now we can't render scenes as high poly as we could with the same cards (gtx 280 gxt 580) when we used the 2.46 it let us load the obj but on the gpu indicator on the right it says failed.

5) Hdris makes renders way slower generaly.

6) In some scenes when render time passes the 1 hour the screen fills with big white dots (like good old fireflies) and if we dont restart workstation crashes after about 2 minutes.

Hope we helped.

Keep up the good work but you may want to slow the process up and give more quality results, dont give up on users pressure Octane team. Users will always want more and more and faster than ever.

[abstrax]

Hello there been some time since our last post due to heavy projects.

Some issues we have with 2.50

1) All scenes tested with the exact settings are way slower with 2.50

Could you please send us an example scene?

2) On direct lighting ambient occlusion (3) or diffuse when samples are greater than 4000 and diffuse depth greater than 2 octane crashes the second the render finishes with out letting the user to save the image we can save it at 3999 but never at render finish due to the crash.

Here we need an example scene, too.

3) Some sliders are not working or dont allow decimal (as other users pointed out)

Yes, that problem will be fixed on Monday.

4) Now we can't render scenes as high poly as we could with the same cards (gtx 280 gxt 580) when we used the 2.46 it let us load the obj but on the gpu indicator on the right it says failed.

That is very likely due to the larger film buffer, since each graphics card now renders the full image and not a partial image anymore. I don't know how much RAM your GTX 280 has, but if it's a lot less than the GTX 580, I recommend not to use it for rendering at all, but only as a display card, since it's waaaay slower than the GTX 580 anyway.

Also, to get more VRAM, disable SLI, PhysX and Aero.

5) Hdris makes renders way slower generaly.

Could you send us an example for this problem, too?

6) In some scenes when render time passes the 1 hour the screen fills with big white dots (like good old fireflies) and if we dont restart workstation crashes after about 2 minutes.

That sounds more like a hardware problem. I reckon your GPUs overheat. With the new framework the GPU usage is on a maximum all the time and the GPUs get hotter than with beta 2.46b. And there seems to be a problem with the very latest graphics driver 280.26, which means you should use the previous stable driver 275.33, if you have already updated.

Hope we helped.

Keep up the good work but you may want to slow the process up and give more quality results, dont give up on users pressure Octane team. Users will always want more and more and faster than ever.

Thanks for the feedback.
Marcus

[vipvip]

excellent absorbtion add-on with 2.5.
thanx a lot !

[MaTtY631990]

I suppose it's not a big problem but the power value on blackbody emitters displays wrong. example - 40 watts would equal 39.9999991.

[colorlabs]

Hmm, looks like this release breaks the C4D export plugin v0.11c.

Code: Select all

There was an error parsing the command-line arguments:

Couldn't find match for argument Argument: I:\Art\2011-08-28 Ed Schrader music video\towerglass\towerglass00000000.png

USAGE: 

Is there any workaround for this? I set up an animation using absorption and now I wanna render it