We've checked it out. This is old hat really. We still have to trace off the geometry to form editable Revit families. Here's the solution to the problem of SketchUp to Revit. https://www.youtube.com/watch?v=eQJFxCTey5E

I see this thread is almost ten years old, but has this issue ever actually gotten fixed?

You need an API for UVUnwrapping then... hm... Maybe something WrapR might consider? (pinging Rich)

::sleepily opens one eye:: hmmmmm?... this sounds like someone is dabbling with scary things...

@exmole said: I see this was posted 10 months ago. Did you ever figure it out? I have the same issue. Unfortunetly, not yet. Will try to get someone at Trimble to look at it.

Sorry for the delayed response. It looks fine, thanks again! [image: TtoBovE.png]

Unless you're still using SketchUp 7 or 8, you don't need this; and even if your are, you still probably don't need it. What problem do you wish to solve by running this code?

Unfortunately even with your adjustment, the code does not work yet. When I launch SketchUp, nothing happens. And the "Ruby console" shipments this error message : @unknownuser said: Error: # <TypeError: no implicit conversion of nil into String> Or is the error? See you soon. David

HE SHOOTS HE SCORES! That fixed it - thanks so much!

And Yep with your code that works like a charm! The mystery is why that works for you and Solo for the original and not for me! Have you a secret resizing? [image: BxlF_sdm_measures.jpg]

I have some experience using SketchUp & Unreal, not Unity. It could be some sort of collision setting (use the actual mesh of the stairs for collision instead of its boundingbox - this is what I have to manually do in Unreal for stairs) OR increasing some step setting allowing the user to 'climb'. Simple google search results in: http://forum.unity3d.com/threads/how-to-get-a-rigidbody-player-to-walk-on-any-type-of-stairs.133573/ https://docs.unity3d.com/Manual/class-CharacterController.html

This method only works when format is set to decimal (or engineering which is also decimal) in the model info. If fractional or architectural are used '1.2.to_l.to_s" returns '~ 1 1/4"' without any decimal separator.

@dan rathbun said: I believe this was implemented in a cross-tab of checkboxes by Martin Rinehart. Thanks a lot! I had a feeling that I've seen it somewhere already; apparently I just can't google the desired result .)

Groups are implemented as a special case of Components. They add some convenience methods that expose some aspects of the associated ComponentDefinition, and also a "lazy uniqueness" mechanism. By that I mean that when you copy a Group, it behaves just like a Component does - another instance is added to the ComponentDefinition. Only when you perform some action on that requires it to be unique does SketchUp clone a second ComponentDefinition and wire the Group to it (same thing as the make_unique method does). Any other copies remain associated with the original ComponentDefinition until you also alter them. For Group copies, it is a one-at-a-time thing.

If you are using the Ruby API, Geom::Transformation.translation followed by Geom::Transformation.rotation.

If the DLL does not have Ruby interfaces, then you will need to load and use it via the Ruby Fiddle library. http://ruby-doc.org/stdlib-2.0.0/libdoc/fiddle/rdoc/index.html http://ruby-doc.org/stdlib-2.0.0/libdoc/fiddle/rdoc/Fiddle.html

It's not currently possible. Only a layer's color - RGB - is changeable in Ruby. Sadly no Alpha [or Textures] are possible. One 'trick' is to make a SKP containing all of the Layers you want to use, each with manually assigned colors, and with transparencies and textures if desired. Remember to include a guide-point at the origin so it's usable later. Now in your Ruby code load that SKP as a component definition. If you do it inside a start_operation...commit block and use compdefn.entities.clear! then the loaded component is deleted but its imported layers remain - although later on they'll purge if unused. Now you can use these layers by name. Depending to what you want to do you can also rename an imported layer if desired...

Thank you very much for these complementary solutions. Renaud.

Thanks TIG!

"Some_Dict_Name" needs to be "Medeek_SomePluginName" at a minimum, and can be expanded even more, like: "Medeek_SomePluginName_Purpose" if "SomePluginName" will have more than one dictionary, each used for different purposes. Or you can nest dictionaries inside another dictionary. So you can have one toplevel company dictionary for all your plugins, called "Medeek" (or whatever) and create child dictionaries for whatever plugins that need them. Those child dictionaries could have grandchild dictionaries. But it is most important to know that you must separate your dictionaries from those of other authors. (It is up to you how to separate your various plugin dictionaries.)