I need understand how wonderlands loads garden arches. I have saw garden arches has textures in a separate folder and the total size of model is 6 megas. Should I put the textures in my model separately?.
Yeah, this replies are very useful. :D.
I have another questions, However. What is better, in terms of impact on performance, load dae or kmz file?. Load a model with textures in a separate folder or load entirely in wonderland?.
Thanks for reply :D
There shouldn't be much performance difference between kmz and dae -- a kmz is just a dae file with a particular zip file structure. Once the content is in world, it all works the same way.
When I'm adding new models to the world (I use maya vs sketchup or blender), first in the maya I assign my textures to the meshes I've created and export them to a collada format with relative paths. Then I make sure that when I load them into wonderland, both the .dae file and the texture file are in the same directory so that the loader can find the texture in the event I assigned the wrong path in maya.
Long story short: Before you load any models, make sure the textures (or atleast a copy of them) are in the same directory as the .kmz or .dae.
Does this answer your question?
Finding textures when loading collada models is always fun ;-) Depending on the tool used and the export settings the texture paths in the collada (dae) file can be either relative to the location of the dae, or absolute in the filesystem.
With the latest changes in WL core you should now get notified if the loader fails to locate a texture when you import (or dnd) the model. Once the model has been imported correctly we actually store a mapping of the texture name in the collada file and the actual file location (relative to the deployment url) in the .ldr for the model. I took this approach, rather than rewriting the collada file with WL specific data so that the collada files could be imported back into art tools if so desired.
With kmz files (from Sketchup) the texture paths are always relative, so for kmz we don't bother storing the mapping in the .ldr file.
If you have examples of collada files that don't load correctly then please send me a zip of the model and I'll fix the loader.
Now I'm confused, I've been using sketchup and was beleifing that when I export to a .kmz file that the textures are included in the .kmz. If they are not it would explain why the textures in some of models don't get displayed. When using sketchup are the textures exported aws part of the kmz or not. If not how do I get them into wonderland using drag and drop?
Yes, the textures are definitely bundled with the .kmz files that SketchUp exports. I have been having all sorts of trouble with textures not displaying properly. In my case, the textures are appearing on the wrong surfaces. Given the "distractions" this week, I haven't had a chance to go back and test my theory, but I believe I have a solution for at least some texture problems. Before you export the model, try purging the unused textures. On the Mac, you select Window --> Model Info. In that dialog, make sure "statistics" is selected, and then click on the button "Purge Unused." Then export the .kmz and see if the model imports better into Wonderland.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.