Yeah, I saw your post and that's what made me ammend my initial post with the thought that it could be a sorting issue. Any luck with it? It's not a huge deal, I was just curious what it could be since there's not a lot of difference between the code for the WireColorMaterial and the ColorMaterial. Could the problem exist with the ColorMaterial as well?
On Jun 14, 3:55 pm, Shawn <[email protected]> wrote: > It seems like you may be encountering the same problem I mentioned in > this > thread:http://groups.google.com/group/away3d-dev/browse_thread/thread/7e4512... > > For what it is worth, it doesn't seem to be happening with > BitmapMaterials. That may make it a non-issue for you in the long run > like it did me. > > Best, > Shawn > > On Jun 14, 11:06 am, savagelook <[email protected]> wrote: > > > > > Looking at it, it could also be some kind of culling/sorting issue, > > but I'm still unsure about why its happening. Does not happen in > > away3d 3.5, just away3dlite 1.0. > > > On Jun 14, 1:57 pm, savagelook <[email protected]> wrote: > > > > Why is it that when I use the WireColorMaterial in Away3dLite that > > > even when I set the "alpha" value to 1, my object is still > > > transparent? I've tried setting it up with both the constructor and > > > afterwards with its properties. It always ends up with > > > transparency. > > > > var material:WireColorMaterial = new WireColorMaterial(); > > > material.color = 0x000000; > > > material.wireColor = 0xffffff; > > > material.alpha = 1; > > > material.wireAlpha = 1; > > > > I should also mention that this material is being added to a 3DS > > > model. All other supported materials, though, seem to be working fine > > > with it.
