I have just uploaded an update for AWData that should fix the white material issue you are having.
with bsp typed awd files, a custom path was giving a custompath/images/filename.jpg instead of custompath/filename.jpg while there was no issues with the awd's not having the bsp. can you let me know if it works in your case? Fabrice On Apr 28, 2010, at 10:32 PM, dp wrote: > Thanks for the replies guys, yes I guess I wont be altering the > geometry just want access to apply materials. > > However I haven't yet made it that far... as I cant seem to get the > output from prefab to work, I've tried a couple of models now, and > both times I just get a blank white screen, the last model was a > simple cube (2 meshes - floor, and ceiling/walls).. Any ideas? > > thanks. > > On Apr 26, 1:37 pm, David Lenaerts <[email protected]> wrote: >> Also, I should add that changing the geometry would invalidate the tree in >> most cases, resulting inrendering issues (sorting, culling, visList errors), >> so you shouldn't ;-) >> >> David >> >> >> >> >> >> On Mon, Apr 26, 2010 at 1:04 PM, Fabrice3D <[email protected]> wrote: >>> If you mean awd, yes but not using library. Just access directly the meshes >>> objects. >>> On other hand, the awd's with BSP outputs do have a new class companion, >>> CentralMaterialLibrary, in order to access the tree material(s) if you need >>> to. >> >>> Fabrice >> >>> On Apr 25, 2010, at 5:40 PM, dp wrote: >> >>>> Great work on the new engine, looks like it will be great. >> >>>> A quick question though - Is it still possible to access all the >>>> materials/meshes with this new format at runtime? and modify them? >> >>>> eg. >>>> model.materialLibrary.getMaterial("....").material = >> >>>> cheers, >>>> david. >> >>>> -- >>>> Subscription settings: >>> http://groups.google.com/group/away3d-dev/subscribe?hl=en >> >> --http://www.derschmale.com
