Thread: Why is Autodesk torturing us with this Materials Editor - Chapter 2

Downloaded the SP2. Now, so far, several "appearance" materials that were different from each other, are changed to be all the same. It appears that under Assets, they share the same Appearance "Name" and I haven't figured out how to fix that...but my question is why should I be "researching" this? Perhaps there's a simple explanation, but if there is, if someone can tell me why this new roadblock to productivity has a side benefit, I'm all ears. (I have just about had it with Revit 2013, and will soon be submitting models to support to go back to Revit 2012.

btw, I had created these different materials by copying & renaming a particular basic material I was using. All worked fine before SP3...

Found a way. I have to rename my materials a second time. Now I have to go through the entire project...

Nope that doesn't work either. So I will re-install this cr*ppy program. Very frustrating.

SP2, excuse me. Someone once described the 2013 Material Editor as "a bag of smashed ass" Spot on. It has singularly turned a nice upgrade into a downgrade, unfortunately.

Having fun talking to yourself narlee? Please don't multiple post - use the edit button to add further details/comments.

As for your predicament - join the club - and search around here a little, there are a number of threads that go some way to make "sense" of what is yes, the least intuitive part of the present Revit GUI. Good luck.

Yes, it was theraputic, but I apologize for being so annoying that way.

For me...the slowness of the material editor is the worst thing about Revit. It takes way too long to edit materials!

Yup. The speed (or lack of) is a nightmare. I do find that closing and restarting Revit will help a great deal, but that's just a workaround.

If you kill all of the Render Appearance previews that are defeatable, its not that slow. Its not as fast as 2011, but i have faith that something better will eventually come out. But, you can get it CLOSE to the 2012 version. Instructions are on my blog.

I'll throw in a bone to chew on then: it took me a while to get used to it (and yes, kill all the render previews) but since then, it's starting to grow on me... Really looking forward to the day that all those fancy-pancy property sets become approachable in the project environment.

I see beautiful things to come. They're only just beyond the horizon..

Sooo, probably one or two more halfbaked, crappy-a$$ solutions and then the fun really begins!