It would be incredible if a few official material libraries were created such as mold-tech, dupont, axalta, and any other standards.
a few other rendering engines already have such libraries like keyshot (linked) and maxwell.
https://www.keyshot.com/resources/downloads/materials/
what would be even a step further... Something I sort of have setup currently, but I'm no pro at material creation beyond some of the basics; I have a basic plastic material, and the diffuse node is ready to be hooked up to a rgb node. Which I have a library of colors that our client is constantly using to easily switch colors.
If that doesn't make sense...basically, have a library with different plastic finishes, like mt 11000 for example. Pull that in, and have maybe 2 options, direct color change to change the base material of the plastic, and/or, a top coat node to change the paint finish over the plastic.
Material library
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
- Phantom107

- Posts: 686
- Joined: Tue Jul 24, 2012 11:31 am
- Location: The Netherlands
I've been considering making a program for this, but I need a ton of references for accurate Octane materials.
Developer of tools for Octane:
Phantom Scatter - Phantom Node Link - Phantom Photo Match - Phantom Architecture
Phantom Scatter - Phantom Node Link - Phantom Photo Match - Phantom Architecture
- linvanchene

- Posts: 783
- Joined: Mon Mar 25, 2013 10:58 pm
- Location: Switzerland
Wasn't support for MDL Material Definition Language announced?
http://www.nvidia.com/object/material-d ... guage.html
https://developer.nvidia.com/mdl-sdk
Basic idea:
Many different render engines use the same MDL.
There could be one huge material library collection that could be used for many different render engines.
Of course you may still want to tweak the look with some custom textures or procedural nodes but the "physical properties" of the materials would be identical for certain real world material types.
Wishful thinking or is this going to happen?
http://www.nvidia.com/object/material-d ... guage.html
https://developer.nvidia.com/mdl-sdk
Basic idea:
Many different render engines use the same MDL.
There could be one huge material library collection that could be used for many different render engines.
Of course you may still want to tweak the look with some custom textures or procedural nodes but the "physical properties" of the materials would be identical for certain real world material types.
Wishful thinking or is this going to happen?
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
FAQ: OctaneRender for DAZ Studio - FAQ link collection
Yeah, would love that too!
http://www.C9W.de - Win10 - Dual E5 2620v3 - Display 1 GTX 1080 / Render 1 3090 RTX - 96 RAM - C4D MSA - C4D Plugin version: current - Standalone: current
Native plugin ecosystem: OctaneRender will enable easy loading of plugins through ORBX modules that continuously update the host application with new features. New plugins will also enable support of different shader languages beyond OpenSL, including support for Nvidia’s Material Definition Language (MDL).
Windows 8.1 | i7 950 | GTX 780ti | 24gb ddr3
+1 from me, too.
I love the idea of the LiveDB, but an overhaul of it is long due, imo.
It's not that the (most?) mats in there are obsolete, but so many user mats from so many versions ago, are still present in there, that it's eventually not possible any more, to figure out, for what version it was created or used as perhaps a workaround back then.
A table, where something like a "time of creation / or upload" could be seen, would be a great and helpful addition as well.
I love the idea of the LiveDB, but an overhaul of it is long due, imo.
It's not that the (most?) mats in there are obsolete, but so many user mats from so many versions ago, are still present in there, that it's eventually not possible any more, to figure out, for what version it was created or used as perhaps a workaround back then.
A table, where something like a "time of creation / or upload" could be seen, would be a great and helpful addition as well.