Ventuz Forum

Hello,
in V4 the Texture loader node has output properties about the loaded image, width and hight. Where can we get access to this in V5?
Now, the texture loader is integrated in the material node and there aren't any output properties.

Thank's

you can still connect a texture loader to the material stage... and this has of course the texture size as output

greetz

christian

O.K. But it is not straight ahead...
From the manual:
"A Texture node is a quick way to add an image or texture to an object without the need for creating a Material node and add the desired Material Stage.
In all respects, it behaves exactly as a Material node, and has the same properties and controls."

But when you have a material node and add a base texture material stage, there are no output properties or a separate texture loader node with the needed output properties.
And in the case you drop only the texture loader, it creates a material node with a extra connection to the texture loader node... strange...

thank's

hi jochen,

O.K. But it is not straight ahead...

yes... but maybe the new material system is not so strait ahead... it needs a lot of klick just to archive simple stuff...

this little workaround gives maybe a bit more overview what textures you are using without diving into the depth of the material system . i will put it into my repository and i am sure, i will use it many times

greetz

christian

joschy wrote: From the manual:
"A Texture node is a quick way to add an image or texture to an object without the need for creating a Material node and add the desired Material Stage.
In all respects, it behaves exactly as a Material node, and has the same properties and controls."

But when you have a material node and add a base texture material stage, there are no output properties or a separate texture loader node with the needed output properties.
And in the case you drop only the texture loader, it creates a material node with a extra connection to the texture loader node... strange...
thank's

Hey,

what you quoted from the UserManual refers to the Texture Node. The behaviour you describe is the Texture Loader Node.

These are two/three different things:

In the end it all comes down to the Material Node. The Texture (Hierarchy) Node is a so called Alias of the Material Node. An Alias is a kind of shortcut. So it creates a Material with a Texture Stage. ( Same: Color (Hierarchy) Node is an Alias of the Material Node too, with Lighting Model set to No Light).

Remember the selection list you got In Ventuz 4 when you dropped a Texture Node to the Hierarchy where you could select Texture/Live Video/Movie etc... it's gone in V5.
Now, to get a Movie or Live Video in V5 was lot's of clicking. So we implemented another set of "shortcuts". When you drag the Content Node (Movie etc) to the Hierarchy, it automatically creates a Material with that Content Node bound to it.
You can also drag the Texture Content Nodes to the Layer Editor and Ventuz creates the according Layer.

Howdy,
Götz