Feb 27, 2014 - Rhinoceros is version 5 SR7 64-bit. Once you have your model the way you want it in SketchUp, export it to the DWG format. In Rhino, import the DWG file. Free Rdp Serial Port Redirection Software here. Then for each element of the model in Rhino, do the following two steps. Use the 'MeshToNURB' and 'MergeAllFaces' commands to clean up the model. You need to look at how the model is put together in sketchup, esp if using layers to get the model into logical individual pieces in rhino - do a few tests. This is a smaller and cleaner file than going through dwg. If you are exporting sections as 2D dwg then the file will need a lot of cleaning up in rhino (or anything else).

Before you begin, we have one word of caution. Both the SkpReader and SkpWriter APIs were written prior to SketchUp's acquisition by Google. Neither API is under active development. However, we do make bug fixes and provide limited support through the. Were I a SketchUp user, I'd tend toward adopting COLLADA as my primary interchange format for use with SketchUp, and drop SKP from my workflow as much as possible; in my estimation, the above effectively makes it a dead format. I mean, if you guys posted a similar disclaimer in reference to 3DM and your SDKs, I probably wouldn't buy the next version of Rhino.

• Reply by on March 2, 2011 at 9:43am. In a way, yes, it is theoretically possible to have a 64-bit application interact with a 32-bit application. The work required to do that is essentially equivalent to allowing plug-ins to run on a separate computer across a network.

To make it work, every single piece of information that went between Rhino and a Plug-in would need to be saved, copied to the other, read, and then operated upon (currently, plug-ins share memory with Rhino, so when a plug-in wants to know something about a 200MB mesh (for example), it doesn't have to request a copy of that mesh and wait for the copy to happen). I guess that's the long winded way of saying all your statements are probably correct - especially the 'it would require a lot of work' part:) - Brian • Reply by on March 2, 2011 at 10:23am.

Before you begin, we have one word of caution. Both the SkpReader and SkpWriter APIs were written prior to SketchUp's acquisition by Google. Neither API is under active development. However, we do make bug fixes and provide limited support through the. Were I a SketchUp user, I'd tend toward adopting COLLADA as my primary interchange format for use with SketchUp, and drop SKP from my workflow as much as possible; in my estimation, the above effectively makes it a dead format. I mean, if you guys posted a similar disclaimer in reference to 3DM and your SDKs, I probably wouldn't buy the next version of Rhino.

• Reply by on March 2, 2011 at 9:43am. In a way, yes, it is theoretically possible to have a 64-bit application interact with a 32-bit application. The work required to do that is essentially equivalent to allowing plug-ins to run on a separate computer across a network. To make it work, every single piece of information that went between Rhino and a Plug-in would need to be saved, copied to the other, read, and then operated upon (currently, plug-ins share memory with Rhino, so when a plug-in wants to know something about a 200MB mesh (for example), it doesn't have to request a copy of that mesh and wait for the copy to happen).

I guess that's the long winded way of saying all your statements are probably correct - especially the 'it would require a lot of work' part:) - Brian • Reply by on March 2, 2011 at 10:23am.