OctaneRender™ Standalone 3.05 Rounded Edges Test 4[OBSOLETE] Tweet

[abstrax]

Thanks for the feedback and apologies for the trouble. We will have a look at it now. I haven't investigated the problem yet, but even if there was some issue in test 3 it should not crash.

[enricocerica]

Same for me with one of the scenes I saved with test 3, it crashes when loading the scene, though works fine when I revert to test 3.

just read my post above ...

Just save your file in a previous version (not a test version) and it will work in test4, works for me.

Well, this is not to complain but only to relate the problem and help solving it

[mojave]

Hey guys, there was actually an issue loading scenes with that version number due to an internal conversion issue and we have fixed it.

However, we are not planning to do any further test releases until Friday when we plan to release 3.05 unless you experience any mayor issue.

Thanks for the heads up.

[smicha]

Same for me with one of the scenes I saved with test 3, it crashes when loading the scene, though works fine when I revert to test 3.

just read my post above ...

Just save your file in a previous version (not a test version) and it will work in test4, works for me.

Nevertheless it's a bug and shall be fixed.

[calus]

Same for me with one of the scenes I saved with test 3, it crashes when loading the scene, though works fine when I revert to test 3.

just read my post above ...

Just save your file in a previous version (not a test version) and it will work in test4, works for me.

Nevertheless it's a bug and shall be fixed.

Yes, that was not my point either.
I thought people in this topic may also want to try the Test4 version, that was the way to achieve this.

[roeland]

PS. Any plans to introduce math operation nodes (add, multiply)?

It depends. Math operations on textures generally have to be evaluated inside the shader while rendering. We support a limited set of operations (multiply, mix, clamp, apply gradient…) which are evaluated on the GPU. For single values (like int, float) we don't have direct support but it can be emulated with a simple scripted graph:

Code: Select all

local MyGraphScript = { _name = "+" }

-- onInit function, this is called once in the beginning.
function MyGraphScript.onInit(self, graph)
    -- define input and output infos
    local inputInfos = { {type=octane.PT_FLOAT, label="a", defaultValue=0},
                         {type=octane.PT_FLOAT, label="b", defaultValue=0}}
    self.inputs = graph:setInputLinkers(inputInfos)

    local outputInfos = { {type=octane.PT_FLOAT, label="+"} }
    local outputs = graph:setOutputLinkers(outputInfos)

    self.value = octane.node.create{ type=octane.NT_FLOAT, name="color", graphOwner=graph }
    outputs[1]:connectTo("input", self.value)
end


function MyGraphScript.onEvaluate(self, graph)
    local a = self:getInputValue(self.inputs[1])
    local b = self:getInputValue(self.inputs[2])

    -- expression goes here:
    self.value:setAttribute("value", a + b)
end

return MyGraphScript

We could add explicit nodes, on the other hand a scripted graph has more flexibility (you can have more than 2 inputs, or inputs of different types, and multiple outputs).

--
Roeland

[Jolbertoquini]

Hi Guys,

Pascal thanks for the point I tested and is working perfect to me. Also with our CAD now. I attach a image of reel production model and I'm really happy!

I didn't have any crashs, if I use the scene from other versions as pascal "Calus" described and is fine the CAD data of KUKA is missing some fixes and clean up on this model so I'm not surprised they may cause issues and a bad look, anyway here a test if you see the Grid and left side module, This are saving a lot time for modelling.
Thanks Otoy Guys for the nice help.

[mojave]

@Jolbertoquini

Thanks for your feedback guys!

[NVN]

@mojave

is there a chance to get something like Vray?

[mojave]

@NVN

The current implementation is bound by the mesh geometry, that's why you don't see such a large radius being applied. It is however quite fast compared to other render engines implementations and that's why we have decided to keep it.

We are working right now on a completely new mode which will likely be slower but way more robust, and which should give you similar results as the one you show.

We're however planning to keep both modes so you can choose depending on what's working better for your scene.