awd data format runs in all away engines. yes AWData parsers are in the f9, f10 and f10 lite trunk
exporters to awd format are available in F10 branch (no embeds) and in AwayAir branch (with embeds). Prefab exports to this format. > Never heard of this thing, and its not in the API Refrence. doc will be updated... team is kinda super busy atm. awd = away data This is a dedicated format, holds only the data away3d needs. the 1.1 version of the format holding a new kind of data will even make this format the only way to use a new feature that will be introduced soon. Fabrice On Mar 11, 2010, at 4:16 PM, Reinorvak wrote: > Is this AWData something that was created with Away3D Lite? Never > heard of this thing, and its not in the API Refrence. Currently > running Away3D 2.3. > > If its on the SVN, where can I get access to it? > > On Mar 11, 9:50 am, Fabrice3D <[email protected]> wrote: >> its loading fine in Prefab, because I do not use the lib. >> so why not load as obj in Prefab and export as awd? >> >> only change in your code would be change Obj.load by AWData.load >> >> Fabrice >> >> On Mar 11, 2010, at 3:12 PM, Reinorvak wrote: >> >>> Hmm, fun stuff there. I don't think the OBJ loader actually creates a >>> materialLibrary when loading the obj file. Rather it applies the >>> texture to all faces. So if you want to do it dynamically you'll have >>> to go down to the faces each time and change all of their texture's if >>> you want to change it. >> >>> Interesting enough, I can load the obj file through prefab just fine, >>> and I exported it back out thinking it may have some vodo-magi, but to >>> no avail. The model still loads fine but the texture is still in no >>> man's land. >> >>> On Mar 10, 6:58 pm, charglerode <[email protected]> wrote: >>>> Surprisingly, in my case, the texture does show up on the model. >>>> Everything appears to be working absolutely perfectly until I try to >>>> access the material library. It appears to me that the obj loader is >>>> loading and applying the texture properly, but it doesn't place it >>>> into the material library for us to access. Which means, I can't >>>> replace materials dynamically which is exactly what I'm trying to do. >>>> I've been trying to work around this for the better part of a month >>>> with no luck. >> >>>> On Mar 10, 2:55 pm, Reinorvak <[email protected]> wrote: >> >>>>> Hello there, I'm have the same problem I believe. The model can appear >>>>> on the view and shows up with the basic color materials on it. The >>>>> modelLibrary is null within the object but otherwise its there. >> >>>>> The accessing of null might be from a different object maybe? >> >>>>> Now I've been banging my head against the wall at this away3D OBJ >>>>> loader, but to no avail can I figure out why model has no materials. I >>>>> believe the OBJ loader doesn't actually set up a materialLibrary, but >>>>> actually just applies the material to all faces within the mesh. >> >>>>> I've stepped through everything I could on the away3D side and found >>>>> that the image is loading correctly, the mtl is loading correctly, and >>>>> the obj is loading correctly, the texture just fails to make it back >>>>> to the model on screen. Instead, it assigns it to this container >>>>> object in the OBJ loader who doesn't belong to anyone. >> >>>>> Not quite sure whats going on here, help us out mates! >> >>>>> Rein >> >>>>> On Mar 9, 12:49 pm, charglerode <[email protected]> wrote: >> >>>>>> I load an OBJ file using the Loader3D, object loads and is displayed >>>>>> correctly. However, when I try to access the material data from the >>>>>> loaded Object3D it's null. In fact, any property I try to trace comes >>>>>> back null. Any Ideas?
