1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Compatibility with Google Warehouse into BTB?

Discussion in 'Bob's Track Builder' started by regnar94, Aug 12, 2010.

  1. Trying to make use of the google Warehouse for some site objects, understanding there can be issues with materials, but all objects imported into BTB so far seem to disassemble.

    What preparations can be done to the models downloaded from Google Warehouse if any?

    Haven't had any problems with my own created object, just from the Warehouse.

    1-r.jpg 2-r.jpg
  2. Kyle Puttifer

    Kyle Puttifer
    @ Simberia @Simberia

    There may be problems with poly count, as these models are built for Google Earth. Just download the SketchUp 6 file, then export as normal. You may want to resize the textures to powers of 2, etc.
  3. Kris Vickers

    Kris Vickers
    Hardware Staff

    Thats looking like its confusing itself as to which side to display the textures on.

    Try some kind of 'invert faces' option within the 3d software.
  4. I´m creating a huge xpack with a lot of objectos from warehouse and i simply open sketchup, export to 3ds, convert all textures to dds format, open in 3d simed to see if's everything fine and then import to xpacker.

    Looks like a lot of work but after do 2 or 3 is fast :doublethumb:
  5. I use Google Sketchup 6. not Pro , so I can only export as .dae format. I haven't yet found a compatible Callada plugin for 3ds max 9 that I use.

    Autodesk FBX converter can convert .dae files into .fbx files for import into 3ds max, but also seems to have problems with the warehouse models.

    It would seem taking in consideration the texture issues which I'm aware of, that the models imported into BTB still shouldn't disassemble, but that the material wouldn't display correctly or not at all.

    The models I would use from the warehouse would be low poly models.

    Haven't tried Sketchup 7 yet, but getting the warehouse models into 3ds max I think would fix the problem. :)