I’m testing some things with the Away Builder Live Tool, and when I save a model with LZMA compression enabled, it doesn’t save out the 4-byte uncompressed size at the beginning of the LZMA buffer.
This is different from the Away3D SDK C++, which does save out the 4-byte uncompressed size. Also, when I use the SDK to write a LZMA compressed file, and try to open it into the Away Builder Live Tool, I get an Error #1000, which locks up my browser.
Is this a bug with the Away Builder Live Tool?
Or has anything changed with the way LZMA files are written since the SDK was released?
Thanks
]]>I’m using AwayBuilder 1.0 Gold, example scene attached.
]]>for (var i:int = 0; i < scene.numChildren; i++) {
var obj:* = scene.getChildAt(i);
// depth, class, name, numChildren
trace (i, obj, obj.name, obj.numChildren);
}
traces:
0 [object ObjectContainer3D] DirectionalLight1 0
1 [object Mesh] Mesh1 0
2 [object ObjectContainer3D] Camera1 0
Camera and Light is empty containers and (obj as Camera3D) return null.
* yes, I see mesh, it correctly added to scene
]]> This work bad is the user don’t change Shadow Light.
Is I touch the Shadow Light and select Directional Light and back again to set Null, I can set MultiPass happy and safetly.
Some time if I forget that I lost all setting job.
Regards Alexis
]]>To reproduce this bug just add RimLightMethod to any material.
Set strength to 0.35, for example, and leave power unchanged.
Save file and reopen it. Now check power value! It’s equal to strength!
Loading *.awd files in AS causes the same result. Maybe this problem occurs while loading.
]]>Create some VERY SIMPLE geometry:
1) Create a Sphere (Geometry)
2) Create a new Scene Object - Mesh - and use the Geometry created in step #1.
3) Save to a test.awd file
...now try to load this .awd file in Away3d. It uses the AWD2Parser but it dies because the geometry data is always null.
in away3d.loaders.parsers.AWD2Parser.as put a debug breakpoint at line 668. Check _blocks[3], this should contain the geometry data. It is always null.
If you attach a material/texture to the mesh, the texture save/loads from Away Builder into Away 3d, but the geometry is always null.
Bug with latest build? or am I doing something wrong?
]]>1 - When I manage my materials and then save the awd file, using the latest version of away3d, isn’t resolving the material correctly. In this case was a simple red lambert, but in the swf is showing me a white material.
2 - When I copy and paste some model on the editor and save the awd, the file save some material properties problems.
3 - Sometimes when I apply “effects” on the materials, this effects aren’t listed in the “effects list”
4 - I don’t know why when I save the awd file my textures goes low-quality denoting a lot of pixelation.
Any? :(
Cheers.
]]>I had AIR 3.7 beta. I removed it, restarted my computer and installed AIR 3.7 (stable).
Upon launching the .air installer of Away Builder 0.9.4 I get the following error (I’m translating it from Italian):
“An error occured.
It is not possible to install the application because the installation program is not configured correctly. Contact the author of the application to request support.”
I was trying to upgrade to 0.9.4 from 0.9.3 since I am having numerous problems (renaming elements requires me typing the names in the wordpad and then copy/pasting them to AB… and I am getting the error 1009 all the time now, I’ve tried exporting my mesh in any possible way, but AB simply doesn’t seem to like it… as soon as I try moving it inside a Container3D it crashes).