Inside Sabertooth
Learn how Sabertooth uses 3ds Max to create 3D interactive projects, including HBO Go’s Game of Thrones interactive experience
  • 1/3
You are here: Forum Home / Autodesk® Maya® / Modeling / Maya 2011 Bevel Bug?
  RSS 2.0 ATOM  

Maya 2011 Bevel Bug?
Rate this thread
 
42939
 
Permlink of this thread  
avatar
  • Total Posts: 4
  • Joined: 15 January 2007 01:03 AM

First excuse my poor english.

Ok. This is what I did.
1. Make a cub with Subdivisions Width 2.
2. Delete the half of faces.
3. Duplicate the half cub and scale X -1.
4. Select both cubs and combine , merge vertex.
5. And try bevel. All faces are gone.
6. Let’s reassign lambert1.  Back to normal....



Attachment Attachment
Attachment Attachment
Attachment Attachment
Attachment Attachment
Attachment Attachment
Attachment Attachment
Replies: 1
/userdata/avatar/2zzu59hm3.jpg

If i bevel onlly a few edges it dont bug but if select all i hawe the same bug.

Author: marrakech

Replied: 07 May 2010 11:15 PM  
avatar

Well, it can be a bug…

But try this: Before combine two objects, get reverse the normals of the negative scaled (it haves reversed normals)



Replies: 0
avatar

necro bug bump…

checked this in Maya2012 sp1 x64/win7/geforce GTX 480
And I get the same result after the bevel applied at once to all edges just as first described.
IF I use the initialShadingGroup’s Lambert.

All is fine if I apply another material before the negative scaled dup combine.

Here is a strange twist…
If I assign a different new material like phong: The object is visible again. And if I change that phong’s type to a Lambert it still is visible!

Now, here is an even stanger twist…
If I then RE-ASSIGN the object BACK to the initialShadingGroups ORIGINAL LAMBERT the object is STILL VISIBLE!!
In fact if I assure the shading network is the same as the original state by cleaning the scene with an “Optimize Scene Size” the object is still visible with it’s original shading group as if nothing was ever fubar?
No Idea why the material change would jumpstart the initialShader to start working again but that is what seems to be happening.

Not that this is an important bug. But jes in case knowledge of as much illuminates a fix for any related bugs. :)



Replies: 0
avatar
  • n8skow
  • Posted: 20 January 2012 07:02 AM

Sounds like the connection to the ShadingGroup node is getting broken.
I don’t have a solution - other than to simply reassign your material.



n8skow [FA]

Replies: 0