This is not properly Octane related but not so off-topic I think...
Is there any material definition standard ?
Think having lots of materials already definited in (for example) Luxrender and you want to move to Octane. Would be usefull to just use the same material definition files.
At least in unbiased renderer.
Just a thought.
Material definition standard
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
in my opinion Octane is too young, we must wait at least till v1.0 final.
anyway interesting thought
ciao beppe
anyway interesting thought

ciao beppe
As the OctaneLive material database gets filled out, it will be very helpful to all users to quickly add materials to scenes and to also see how some cool materials are made. Is this what you are talking about?
Win7 64| Two GTX 470s | Phenom II 920 | 8 GB
Win7 32| GTX 260 | Athlon X2 5000+ BE | 2 GB
Win7 32| GTX 260 | Athlon X2 5000+ BE | 2 GB
jakchit : Yes, I knew Collada (very little) but I was thinking something limited to material definitions.
In general, it would be usefull to mantain untouched them when moving from one render engine to the other.
There are several "common" standard (step / iges / stl / slp / obj ) to describe the geometric components that you can, more or less, easily use to move from one software to the other... but what about the materials ?
Can the .mtl file format used in Octane be exchanged in other render engines ? And the opposite ?
But really, it's just a tought...
In general, it would be usefull to mantain untouched them when moving from one render engine to the other.
There are several "common" standard (step / iges / stl / slp / obj ) to describe the geometric components that you can, more or less, easily use to move from one software to the other... but what about the materials ?
Can the .mtl file format used in Octane be exchanged in other render engines ? And the opposite ?
But really, it's just a tought...
Win7 64bit | GTX480 | i3 540 3.07GHz | 4GB
I don't know what exactly is the mtl file for. I thught was material related but, you're right, I controlled and there're too few info inside.
Actally it contains data for un-textured materials too... anyway my main idea is the same.
Actally it contains data for un-textured materials too... anyway my main idea is the same.
Win7 64bit | GTX480 | i3 540 3.07GHz | 4GB
.mtl is a very basic description of a material. Just some colors, indexes and image names - not very usable in Octane.
What Octane needs is a good an robust scene & material definition files in XML - an own format that would completely replace the current .obj workaround step. When this will be done and the file specification released, converters from other material specifications into Octane .ocm could be written (by anyone).
What Octane needs is a good an robust scene & material definition files in XML - an own format that would completely replace the current .obj workaround step. When this will be done and the file specification released, converters from other material specifications into Octane .ocm could be written (by anyone).
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net