Posted by: Peter Quirk | December 11, 2008

Improving the tool chain for bringing Sketchup models into realXtend

Back in July I posted a tutorial on how to use Google Sketchup to bring models from the Google 3D Warehouse into realXtend. It proved to be the most popular article ever, and has been translated into a number of languages. The process has a number of manual steps which annoyed me. Another concern was the way that the exporter script dumped all objects in the same directory, but the xml2mesh tool (or rexmeshtool?) would crash if there were .material files from multiple models in the directory. My original process included a batch file to cloak all .material files from other models by adding a .cloaked suffix and  another script to uncloak It was also clear from questions from readers that the process was error prone. Yesterday I decided to fix it.

The solution involved hacking the Ruby scripts to create a separate folder for each model exported from Sketchup, and invoking the rexmeshtool application after the OgreXmlConverter was run. A side benefit of the process is that the log files for each export and conversion are stored in the model’s folder.

Since I was using a newly built PC, I installed the just-released Sketchup 7 and started to modify the scripts mentioned in the tutorial. (The scripts were written by Fabrizio Nunnari, based on the initial script by Kojack.)  When I finally tested the results this morning, realXtend 0.4 wouldn’t import the meshes. Since I was using a new version of Sketchup, a new version of realXtend and a freshly rebuilt laptop, I had to test a number of configurations to determine where the problem lay. I was able to import the meshes produced by Sketchup 7 into rexserver 0.31 using rexviewer 0.31 on an older laptop, but could not import them using the rexviewer 0.4 connected to rexserver 0.31. I logged a bug report in SourceForge this afternoon and posted a message in the realXtend group. Eight minutes later Gustavo Alberto Navarro Bilbao confirmed that he had discovered the same problem with realXtend 0.4. I have subsequently verified that the meshes can be loaded without errors by the Cegui Mesh Viewer.

Since I had to learn Ruby yesterday to modify the exporter script, and the author of the script was also a first time Ruby coder, I’ll do a little cleanup before I post the revised scripts here (today or tomorrow). The scripts are not backward-compatible with Sketchup 6. If possible, I’d like to address that problem before I release them. If any Sketchup plugin developers have pointers to the API documentation for chdir, mkdir_p and similar calls for Sketchup 6, please drop me a comment.

Advertisements

Responses

  1. […] Read the original here: Improving the tool chain for bringing Sketchup models into … […]

  2. […] Vote Improving the tool chain for bringing Sketchup models into realXtend […]

  3. […] warehouse, Ogre mesh, realXtend, realXtend_0.4, rexmeshtool, Ruby, Sketchup, xml2mesh |   In a recent post I described changes to the Ogre export scripts for Sketchup to simplify the import of models into […]

  4. hi,i tried this sketch up model to to realxtend,but i had problem with rexmesh tool and xml converter zip have some error so i cant use sketch up models directly ,so i import sketchup files or models in to maya and from thet using ogre converter i convert it as a mesh files and add material in server itself .Thanks

  5. hava any link to get correct ogre rexmesh tool and xml converter exe please………..

  6. One other way to get SketchUp models to realXtend is through DeledLite Engine.

    Lately, I think I’ve been popularising this Deled engine but actually don’t work for that company nor is that my product. :-)

    But, it has been the most reliable stuff available out there.

    Download Deled Engine (http://www.delgine.com/index.php).

    Install the plugins (http://www.delgine.com/plugins/viewPluginCategories.php), OBJ and 3DS importers and OGRE and Multiverse exporters.

    SketchUp –> OBJ or 3DS –> DeledLite –> Export.

    This pipeline was perfect with even large models.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: