OctaneRender® 1.024 beta 2.49 TEST (lin/mac/win) [OBSOLETE]

[mib2berlin]

Dear octane team, don´t forget the expanding materials in "Current Mesh".
It bugs.
And i am still no able to render in PMC mode on my system.
Tested with the Render Suite Files, the screen goes brighter and brighter until white/yellow.

Cheers, mib.

[Saramary]

One more bug. Strange bug.
I rendered with 3 cards (disabled in preferences 0th card to wich are monitors connected, to work in 3ds Max in parallel). Then I went to eat and enabled in preferences 0th card to render faster. And then, when I went back, I again have disabled 0th card and saw a strange thing: before disabling it was 1063 s/px already rendered, and after disabling one card this number become 963 s/px! I understand that the speed of render must be (and is) decreased after disabling one card, but the count of already rendered samples per pixel must be not changed...

[face]

It seems, that Octane crashes more as the previous builds if you render animations.
After the max sample is reached, all stopped.
I think then the part of writing the png should start...

face

[Refracty]

I also made the experience that Octane crashed after reaching the max samples in batch commandline mode.

[abstrax]

It seems, that Octane crashes more as the previous builds if you render animations.
After the max sample is reached, all stopped.
I think then the part of writing the png should start...

face

Could you please give us some more information: Does it crash or just stop rendering? Does it happen very often? Do you render on multiple cards? What is your maxsamples setting? Can you give us the command line that made Octane crash?

Thanks for your help,
Marcus

[abstrax]

Dear octane team, don´t forget the expanding materials in "Current Mesh".
It bugs.
And i am still no able to render in PMC mode on my system.
Tested with the Render Suite Files, the screen goes brighter and brighter until white/yellow.

Cheers, mib.

What do you mean with "expanding materials in "Current Mesh""?

Regarding PMC: Which scene of the demo scenes caused this effect? Could you please post a screenshot?

Thanks,
Marcus

[abstrax]

One more bug. Strange bug.
I rendered with 3 cards (disabled in preferences 0th card to wich are monitors connected, to work in 3ds Max in parallel). Then I went to eat and enabled in preferences 0th card to render faster. And then, when I went back, I again have disabled 0th card and saw a strange thing: before disabling it was 1063 s/px already rendered, and after disabling one card this number become 963 s/px! I understand that the speed of render must be (and is) decreased after disabling one card, but the count of already rendered samples per pixel must be not changed...

Sorry, that is currently by design. We will change this in the future, but it requires quite some work to not lose samples of the disabled graphics card.

Cheers,
Marcus

[mib2berlin]

Hi abstrax, it is indifferent which scene i use, this sreenshot is the benchmark scene.
But it is the same with every scene from demo suite or own scenes.
I meant the expanding and collapsing materials.
If you colapse all materials, like in screenshot, and change on material setting all materials expand again.

Cheers, mib.

[face]

It seems, that Octane crashes more as the previous builds if you render animations.
After the max sample is reached, all stopped.
I think then the part of writing the png should start...

face

Could you please give us some more information: Does it crash or just stop rendering? Does it happen very often? Do you render on multiple cards? What is your maxsamples setting? Can you give us the command line that made Octane crash?

Thanks for your help,
Marcus

It stop rendering on sample 63/64 and should save the png. If nothing happens, i click in the Octane window, the windows becomes a overlay in white and the message, that Octane is crashed is shown. Sometimes, Octane renders all frames from 90, sometimes Octane crashed on 3 or 4 frames from 90.
Maybe i must correct me and the png is saved, but i can´t confirm it, because it can be, that i have rendered the frame in an other try...
The Crashes was with 2 GPU´s which are set in the preferences and not via the command line.
The command line is:
-e -q -o "G:\Octane\ProjectB\render\strands_01.png" -s 64 -m clones.obj -r "G:\Octane\ProjectB\clones_anim.obj" --cam-up-x -5.32704e-009 --cam-up-y 0.99878 --cam-up-z -0.0493831 --cam-target-x -0.995734 --cam-target-y 1.46652 --cam-target-z -0.371133 --cam-pos-x -0.995734 --cam-pos-y 1.83717 --cam-pos-z 7.12544 --cam-fov 53.638 --film-width 1024 --film-height 720 "G:\Octane\ProjectB\clones.ocs"

I will check it with a single GPU when i sleep.
Hope it helps...

face

[face]

...And i am still no able to render in PMC mode on my system.
Tested with the Render Suite Files, the screen goes brighter and brighter until white/yellow.

Cheers, mib.

Have the same issue on Linux, try to set the maxsamples from 16 to 7, this works mostly for me on Linux...

face