Octane Live Platform Testing Release (pre-23) [obsolete]

[9fly]

just make some rotate from 7mb file add 1 light and crash.

Other files are crash on loading and/or some process like changing materials or image resolution. I have to error from connection with DB. That's one bright side.

Hope some crashes will be reduce in next week after this. Igot big reduce in pathtracing

[imensah]

you aren't supposed to switch a material to a macro.
A macro is not a material until it's complete.

We need to remove this from our list.

Radiance

not sure i fully understand... do you mean it is not yet working for this release?

I also noticed a hude drop in MS from 20 to 3 when pathtracing the attached scene, I have two emmisive objects in the scene a red texture emmisive and a blackbody. It seems only the texture one works. No more emmisive objects seem to have an effect on the scene.

Also does light travel through transparent objects? i can't seem to get that to happen

[Nostromo]

He meant the entry in the material switch menu that says "material macro" isn't supposed to be there. You need to create macros on the graph editor (bottom) and connect them to your material inputs.

Thanks for the emission zip, we'll test it.

[rope]

A part of the need to find the crash-bug(s), could you please explain the concept of the material macro.
Would like to check the manual, but the one deliverd with the release is version 2.2.

Thanks

[Nostromo]

The idea is to hold a collection of nodes and present them as a re-usable block.

The easiest to understand the concept is to get the material ones from the live DB and double click them to see what's inside. Macro can also have defined inputs that serves as a way to let other user tweak some of the parameters inside the macro. Look at the tained glass one, it's got a texture input so that from outside all you need to select is the color, without the need to know what's going on inside the macro.

/M

[rope]

The idea is to hold a collection of nodes and present them as a re-usable block.

The easiest to understand the concept is to get the material ones from the live DB and double click them to see what's inside. Macro can also have defined inputs that serves as a way to let other user tweak some of the parameters inside the macro. Look at the tained glass one, it's got a texture input so that from outside all you need to select is the color, without the need to know what's going on inside the macro.

/M

Tried to explore the secrets in the tinted glass, but it's impossibile, 2-3 clicks and it crashes. I can drag it from the Livedb in the graph editor, but there after double click, it crashes. I saw the tint node, who seems to give the color to the glass, but canot see slider to change color.

I think I give up for now waiting of the elimination of this beast of bug that semms to be in this prerelease.

[cpember]

hey dude, i wasnt bitching about anything, so before you go mouthing off at someone you've never met, read my post again. The whole point of testing is to test the goddamn software ok? I was just agreeing to the fact that the whole reason they pushed it out was because a lot of people here moan and cry when they dont get a build in 3 days. You have obviously never worked in software before, it's not an instant programming thing.. you run into issues ALL the time. I personally would have rather they waited an extra week or 2 to get a version out that THEY were happy with, instead of an intermediate version just because there's 300 threads about "when is next release??!!??".

agreed


I was just testing my 460 here and it still lists the core count at 224, so I dont think the newer stuff for that part of it is working.. on the benchmark scene it's a touch slower, i was getting 1.72ms/s (178 smaples in one minute) with last beta and with new build 1.59ms/s (164samples in 1 minute)

cheers

cp

ps: i vote for "when it's done" next time

Yeh I understand what you are saying but the fact is, the version we are testing is stripped of certain features that where meant to be in this release, which may be causing some of the instability.
Instead, they released what they had so we would stop bitching for it.

I highly doubt we would have as many problems if they released it when they where happy.

someone forced you to download ? let us try those betas and come back "when it's done" ok ?

[ROUBAL]

Very bad news :

This night I installed and used Octane live and I did some test with an ocs file I had in stock.

I reported some things in a previous post.

Today, I wanted to make some lighting trials with a simpler scene, and opened Blender 2.49b to make one.

I am not even able to edit the default cube ! I get the exact same bug as in Octane : the screen becomes white and half transparent and Blender doesn't respond. It is frozen.

I don't know what Octane has done with GPU management, but I can't use Blender any more.

I have tried a dozen times with the same result ! In 6 years of use of Blender in all its versions, I never encountered a freeze !

As it is my main tool, I'm not very happy !

If some Blender 2.49b users having already tried Octane lives could try to edit an object within Blender (x64 version on Win 7), their comments would be welcome...

[Nostromo]

Hey Philippe,

I doubt octane could do any harm to your gpu. pre-23 doesn't do any registry update, nor video card configuration tricks, we simply use the cuda API

Can you try rebooting afresh and start blender without touching octane at all ?

Regards
Marc.

[face]

Very bad news :

This night I installed and used Octane live and I did some test with an ocs file I had in stock.

I reported some things in a previous post.

Today, I wanted to make some lighting trials with a simpler scene, and opened Blender 2.49b to make one.

I am not even able to edit the default cube ! I get the exact same bug as in Octane : the screen becomes white and half transparent and Blender doesn't respond. It is frozen.

I don't know what Octane has done with GPU management, but I can't use Blender any more.

I have tried a dozen times with the same result ! In 6 years of use of Blender in all its versions, I never encountered a freeze !

As it is my main tool, I'm not very happy !

If some Blender 2.49b users having already tried Octane lives could try to edit an object within Blender (x64 version on Win 7), their comments would be welcome...

Maybe you don´t read it, but some exporters (3DSMax, Maya, Softimage) don´t work with the pre2.3.
I think that is the same thing as yours...

face