that’s much better! yeah my planks are big, I never look at size just modeled some boxes, and they are 2 meters long 
Color change could be HDRI lighting driven. My default scene has an 100 frames animation where each frame loads a different HDRI I can just toggle frames until what I want looks good. I wasn’t paying attention at color here.
Here’s the rhino file…walnut_2_planks.3dm (180.4 KB)
Good Night!
G
OK - some more comments on the scene:
The objects are meshes - that’s why you don’t get a decent texturing preview. At the moment, advanced texture preview doesn’t work on meshes (this is something we’re planning to fix). If you’d drawn extrusions or polysurfaces, it would have worked fine.
And there were lots of different materials in the file - many of them with modified texture mapping. Once I’d resized the meshes and applied the original material from the RMTL, it worked great.
Randomly? You mean, you picked the smallest.
OK - the inlays were hotly debated here - my opinion was that they were pretty. They are certainly low resolution, and we will consider again whether to include them or not.
Well, I did a random choice from a collection of 66 “textures” at 100*100px.
Each of them comes with whopping 10000 square full color dots available to make them apear like real wood.
Honestly I can’t believe that we’re really spending time with such non-disputable stuff here.
We’re not - the inlays are gone.
One shouldn’t stop here.
Here’s that walnut-texture you guys tested as a foreground object. All the cabinet maker can see here is jpg degradation, blur and blockyness, which is expected as any of the surfaces of the box only gets a fraction of the meager 256px overall.
please click to enlarge
All textures less than about 480x480 have gone.
I don’t know Rhino V6, sorry, but would like to understand something.
Nothing is being removed, only more possibilities are being added. As far as I know, Cycles - which already exists as a render engine for Blender - will be a plug-in integrated into Rhino, hopefully on both Win and Mac platforms.
–Mitch
That makes sense Andy. FYI many of our users use both meshes and nurbs. Most don’t even know it. And many model or import from other packages.
So you should be safe assuming that what is brough it will be a total mess. And most users are clueless about it.
So I’m glad I accidentally gave you a great example of reality 
Best,
G
Here’s a second version of the Material library:
http://files.mcneel.com/rhino/6.0/materials/MaterialLibrary_WIP_002.zip
Many of the comments have been taken into account. The main differences are:
Although there are quite a few additional textures in the library, we know there’s still missing stuff. Most of it was reported here, and we’re working on including it now:
Again - please download and test. Ideally, keep the unpacked folder structure on your desktop for now and drag and drop materials into models from there. That will make it easier when we come to ship.
Don’t worry about the size of the download - the textures will be an online resource that will not ship with Rhino.
Feel free to post renderings - good and bad - of things you’ve made with the library.
Thanks!
Thanks Andy!
How would that be a problem? 95MB is IMO not much for a one time download.
How would the online resource aspect work? Is this an additional download and installation the user has to do or will the textures be downloaded on demand?
If this is meant to provide regular users with a set of basic materials, I would consider shipping it with Rhino as part of the installer or offer an option to automate downloading and installing it during the installation process.
I expect any hurdles in installing it will leave you with less users having it installed. Specifically those users you target with this library. It’s more likely to be left out of automated installs where the admins are lazy or ignorant.
my 2 c
-Willem
Good point, probably this is something for @will and his package manager:
I wonder how an interface for many different libraries could look like.
If textures were included in the Installer they needed to get downloaded with every new service release. That in the long run causes lot of needless traffic, for RMA and for individual users. It’s particularly silly for for customers who don’t have a use for this material anyway. Offering texures as an online resource is more flexible and RMA may update the catalog at any time. If one wants to make use of the texures one click from within the Rhino interface downloads all textures, including the folder structure to the right place.
The textures themselves will be demand loaded. The actual RMTL files will be shipped with Rhino - so you will be able to drag and drop them from a ready made library, with the preview already available. At this point, Rhino will download the texture from the interwebs and place it ready in your texture folder.
The material library that ships now compresses to about 20Mb in the installer. The RMTL files compress to about 23Mb - most of which is the preview. Thus we won’t be bloating the installer any more than it is now, even though we will be shipping about 750 materials instead of 60.
That’s exactly how I figured it would work - one command will download the entire library for offline use.
I agree that @will could probably do a great job of this. However, I don’t want to predicate the delivery of the material library on the development of another major subsystem.
Hi Andy,
I understand the thinking behind this, yet I do not see why this should not be an option in the installer. IMO the solution you propose is worse than a bloated installer:
What if a user is not online or behind a firewall?
What if a user is on mobile data, how to make sure there is no expensive data transfer?
Will the user be prompted to download or will this be full-auto or an opt-in/opt/out?
For any other software I’d be annoyed and get wary when it starts downloading stuff by it’s own apparently not already installed but in a library that as such is incomplete/functionally broken.
I see a few possible improvements/additions:
Prompt for download at install time → do you want to download an additional material library?
If a user does not want the materials, DO NOT install partially broken RTML’s else download all
At a first run or first use of material library prompt: → do you want to download an additional material library?
If a user does not want the materials, DO NOT install partially broken RTML’s else download all
I think this behavior should be as transparent as possible, inform the user and offer options that make sense. Software that needs to be online all the time in case some parts are missing IMO is broken.
Thanks for reading!
-Willem
Thanks @jess, good to be aware of these things. For the time being I have to agree with @andy as I’m focusing on plugins initially.
William
Remember - all of our products are download now. So the question is not “how much do you want to download and when”, but more like “how many times do you want to download this”.
Holger wants the answer to be “one”.