 |
Yes, I can confirm this behaviour. The MediaBrowser is only showing materials that are actually defined somewhere and are not auto-generated (missing materials are auto-generated). I can change this, I guess, but I need to know first, how would that empty, auto-generated material definition in the MediaBrowser help in troubleshooting? It would just show an entry without any definition or references to anything, wouldn't it? |
 |
I could have very well sworn that the behaviour I'm thinking of was present in previous versions. I downloaded 2.8 out of due diligence and sure enough, it is not there. Perhaps 2.6? Ah, no matter, I'm most probably wrong. Well, while the ticket is open I should like to offer an example of why appearance in the media browser MAY be useful. If a user wishes to transplant a map file into another work environment without the custom materials that have been used in it, it would be of great help to have a visual indication of the folder structure of said missing materials. This is a weak argument, I know, the shader clipboard display at the bottom info bar gives a filepath to the missing material. That's one better than the plain grid and oftentimes cut-off name the textures pane gives, yet I feel a folder tree view of the material's place - a visual representation of the filepath - would be better still. Selecting elements using the (missing) shader, while having an approximate shortcut key (selectAllOfType -Shift+A), is also unavailable as a right-click context menu option - and if someone uses predominantly those to get around the editor, it'd stump them how to mass-select a missing shader if they mean to replace it. I don't mean to over-expound on trivial use-cases so, most sensibly speaking, at the very least I think it would be a good bit of UX consistency. You middle-click on any brush face and you get a material in the media browser, yet nothing happens with missing materials. It feels off from a user perspective. |
|
|
Well, I'll see what I can do! |
- Anonymous
