Only first material(sub mesh) is considered for nav mesh

[GoogleCodeExporter]

We have a bunch of assets made of multiple materials. I can send you an example 
if you like.

As it stands only the first submesh is considered for nav mesh. 

I have altered MeshUtil.cs to consider them all.

Please find it attached.

Thanks

Dan

Original issue reported on code.google.com by daniel.t...@gmail.com on 21 Jul 2011 at 7:45

Attachments:

• MeshUtil.cs

[GoogleCodeExporter]

Original comment by steve...@gmail.com on 23 Jul 2011 at 12:22

• Changed state: UnderReview

[GoogleCodeExporter]

Thanks Dan.  The changes have been integrated via r298. Just minor cosmetic 
changes from what you sent.

I'm probably not going to do a bug fix release since you don't need it and v0.3 
should be coming out in the first week of August.

(If anyone else is reading this and it is causing you critical problems, let me 
know.)

Original comment by steve...@gmail.com on 23 Jul 2011 at 5:32

• Changed state: Fixed
• Added labels: Impact-High, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fix distributed at part of CAINav v0.3.0.

Original comment by steve...@gmail.com on 24 Sep 2011 at 7:05

• Changed state: Deployed