How am I to find the duplicate material in order to fix it?
This name doesn’t show up in searching either the materials or the project folder.
Error message:
Beast error: 3: Duplicate name
A material named Material-25510-Mesh-17134 already exists
I’m getting exactly the same error, except that it’s
Beast error: 3: Duplicate name
A material named Material-838-Mesh-8366 already exists
UnityEditor.DockArea:OnGUI()
So it’s a little different.
I get the "UnityEditor.DockArea:OnGUI() " too just didn’t look at the full reading in the bottom of the console window.
In fact this seems to be on many different errors.
I tracked the object down to a door that has a shader which is from 2.6
It’s the FX/Glass/Stained BumpDistort shader, I think.
If you can verify this, um… good? I guess I’ll have to update it. Once I get my head around that.
Why do you think this is the problem
and how did you track it down?
I did it by selectively going through the Heirarchy, group selecting different combinations of objects till it threw the error.
However after replacing the suspected shader with Diffuse, it still errored.
Stumped again.
sounds like a bug… did you put in a bug report? I got this as well…
I built it in the previous beta version… so I turned off the excess objects, and it rendered fine!
I’m still unable to track down this one. It happens reliably, but not in any way I seem to be able to solve. However I get the impression it’s going to be something that clears up as Beta’s develop.
Only if we get bug reports for it. 
Of course you’re right Shawn. I’d heard somewhere that you guys were flooded with bug reports.
I’ll see what I can do. Cause this error’s preventing me from doing certain Beast builds. I’ll post the report code here.
I’m finding it very difficult to track this one down.
I’ve made a new scene with the objects that seem to be breaking the beast render in it. However no matter what I do it just renders fine.
It seems as though it’s not any specific object, but more a combination of objects that’s causing Beast to stop.
And that combination is VERY difficult to isolate. I’ll keep trying.
FOUND IT!
Sorry about the caps. It’s such a relief.
Turns out there’s a material assignment at the heart of this. I tracked down the meshes that (when selected) were causing Beast to stop.
Then I re-assigned new meshes to those Objects. This did not fix it. So I assigned new materials instead. That worked.
So it seems that if you’re finding this problem, you’ll have to use different materials.
Well, it seems I spoke too soon. After copying the furniture from one apartment to another, I’ve found that I’m getting this error all the time now.
Obviously I don’t want to have to make individual materials for instanced objects. I’m guessing this is a bug.
I’ll submit a bug report, but I don’t have a file to accompany it, as my file is very large.
I’m getting the exact same issue on a project converted from 2.6 to 3 beta 5. Has anyone got any closer to discovering the root of the issue?
This bug was fixed with Beta 6. All I know is that I’m no longer seeing this bug.
From the bug database, it looks as though this should be fixed in the latest beta.
So, I’m getting this with 3.1.
I’ll research it a bit more and if I can manage to make a small scene with the bug happening I’ll send a bug report.
Meanwhile, can someone from unity check if the same bug creeped in somehow?
I submitted a bug report, case no : 387759
Thanks for the bug report, AcidArrow.
The bug is now fixed, covered with tests and the fix will be included in the upcoming minor version.