sketchucation logo sketchucation
    • Login
    1. Home
    2. Mark ADDS
    3. Topics
    Oops, your profile's looking a bit empty! To help us tailor your experience, please fill in key details like your SketchUp version, skill level, operating system, and more. Update and save your info on your profile page today!
    🛣️ Road Profile Builder | Generate roads, curbs and pavements easily Download
    M
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Groups 1

    Topics

    • M

      'AUTOMATING" SAVE/RELOAD

      Watching Ignoring Scheduled Pinned Locked Moved SketchUp Discussions sketchup
      4
      0 Votes
      4 Posts
      2k Views
      Rich O BrienR
      No, its more of a monitoring tool. What you need is a GIT type environment that pushes commits to the master from branches. Version control within SketchUp's ecosystem is something I hope they implement to meet the needs of small teams that live/work in the ecosystem. https://speckle.systems/ This is the type of system I'm talking about where interoperability between file formats and teams is seamless. Maybe a command line tool could be developed to monitor file changes and push them around as needed. The other thing would be a macro via Auto Hotkey that did what you do manually when you execute it. All rather flaky solutions tbh...
    • M

      Component origin as inference point

      Watching Ignoring Scheduled Pinned Locked Moved Newbie Forum sketchup
      5
      0 Votes
      5 Posts
      638 Views
      TIGT
      There are several tools to draw cpoints [aka guide-points] - including Rich's excellent PenTools. http://sketchucation.com/pluginstore?pln=Pen_Tools and http://sketchucation.com/pluginstore?pln=tt_guide_tools This simple snippet pasted into the Ruby Console adds a cpoint at all selected component-instances' insertion points. Naturally, you'll need to have Guides set to be visible to see these cpoints... Sketchup.active_model.selection.grep( Sketchup;;ComponentInstance ).each{|e| e.parent.entities.add_cpoint( e.transformation.origin ) }
    • 1 / 1