Persistent IDs with Re-loaded Components

[bmike]

I am wondering if this is a bug or intended behavior. I am having issues with LayOut dimensions not reconnecting to the model when I reload subcomponents and then update LayOut.

Example images below.
I create a model of a timber frame project, and I save this as a SKP file.
I then insert this into a new SKP project (it comes in as a component) - I proceed to setup paired section cuts to allow me to isolate the frame for shop drawings (section cut in front of and behind primary bent and wall lines).

My structure looks like this:

The ‘Container’ component contains the TFRAME component (used to work on joinery / framed details) and the secondary section cuts.

Primary section cuts are in the main model space (outside of any components).

Loose items / geometry / etc. are tagged as needed.

So I have 2 models: TFRAME and CLIENT-TFRAME-SHOPS. The ‘shops’ is what I use to move to LayOut. When inserted into LO I detail as needed.

Often I will need to update joinery or details upon client / engineering review or stretch / change sizes. When I reload the TFRAME component into the TFRAME-SHOPS model and then update LayOut I am losing many connections to dimensions. I am aware that using solid tools will often result in the ‘Reconnect to Model’ to fail as the ID / geometry within the model has changed - but I am losing connections to things that I have not even adjusted, or things that should automatically adjust.

Screenshot of LO before reloading the sub-component:

Screenshot after moving the rafters and top plates 2", reloading the sub-component into the main SKP model and then updating LO:

Screenshot after selecting all dimensions and to reconnect to model:

Note in the last images the dimensions are not red-but the points that the dimensions were referencing have not updated with the moved components…

I did not have this issue prior to using my sub-component / reload process and wonder what might be going on behind the scenes in SKP / LO to cause this issue.

I have moved to this process for a couple of reasons, but primarily as it allows for easy use of ‘back edges’ to show joinery (double section cuts isolate the parts of the frame I need to show) and it gives me a ‘clean’ model to focus on joinery / modeling / sizing / engineering as needed.

I don’t believe I had these issues prior to re-loading - if I adjusted the sub-component of the frame within the main SKP model (moving things, adjust joinery, etc.) - LO behaved as intended - dimensions would (mostly) auto-update and re-connect to the model without much fuss.

Any idea from the SKP team on why this behavior exists? Is the re-load somehow changing the IDs that LO was referencing?

[bmike]

Files located here:

https://www.dropbox.com/scl/fo/v01p3x5tpm4k3zdm72ntd/AGkmn0AQxF-dXRae1t4u310?rlkey=hxvjhwnfqobytu39mqph1xslu&dl=0

[bmike]

Bumping this so someone from the SKP team might see it - @colin @Barry @TheOnlyAaron

For my next project I will have to edit in place and not use the reload component - too many pages and too many details to manually update and chase around.

[MikeWayzovski]

I think that the persistent ID’s get swapped for new when reloading, and if they were attached as construction points in LayOut, get lost/detached from the dimensions.
@kengey had a nice extension to check the PID in SketchUp, but it is no longer present in the extension warehouse.
While the PID remains when exploding in the same host model the reload or insert from a collection will assign new PID’s to the entities (faces, edges and vertices)
These PID’s are integers, and start low in numbers, so I can understand that it is done this way, for the chance of identical PID’s is inevitable.
Maybe it’s be possible to write some ruby that reinstates the original pid’s if we are allowed to assign them.
aI made some Ruby for identifying vertices:

module VertexPIDTool
  class Tool
    def activate
      @model = Sketchup.active_model
      @selection = @model.selection
      @view = @model.active_view
      @ip = Sketchup::InputPoint.new
      @drawn = false
      @state = 0
      @model.start_operation('Display Vertex Persistent ID', true)
    end

    def deactivate(view)
      view.invalidate if @drawn
      @model.commit_operation
    end

    def onMouseMove(flags, x, y, view)
      @ip.pick(view, x, y)
      view.invalidate if @ip.display?
    end

    def onLButtonDown(flags, x, y, view)
      if @state == 0
        @ip1 = Sketchup::InputPoint.new(@ip)
        @state = 1
        view.tooltip = "Select a vertex"
      else
        vertex = @ip.vertex
        if vertex
          pid = vertex.persistent_id
          UI.messagebox("Persistent ID: #{pid}")
        else
          UI.messagebox("No vertex selected.")
        end
        @state = 0
      end
      view.invalidate
    end

    def draw(view)
      if @ip.valid?
        @ip.draw(view)
        @drawn = true
      end
    end
  end

  def self.activate_tool
    Sketchup.active_model.select_tool(Tool.new)
  end

  unless file_loaded?(__FILE__)
    menu = UI.menu('Plugins')
    menu.add_item('Display Vertex Persistent ID') {
      self.activate_tool
    }
    file_loaded(__FILE__)
  end
end

Copy paste in the ruby console and activate via the menu.

[kengey]

@MikeWayzovski

Maybe it’s be possible to write some ruby that reinstates the original pid’s if we are allowed to assign them.

persistent_id is readonly.

[bmike]

So this breaks my proposed new workflow then… and sort of defeats the purpose of component ‘reload’.