Rich - thank you for re-creating and posting your file. However, it gives me the same result that I am trying to resolve. I want to drag a text label off any of the groups within the parent and that text label must display the name of the parent, not the name of the group within the parent from which the text label is anchored to. I suppose the only solution is to have an unobtrusive unnamed object, such as a guide point, within the parent to attach my text label to.

Dave - I'm talking strictly SU - not LO.
Rich - can you publish your SU file please?

Let's say I create 3 groups and assign a unique instance name to each ie. A, B and C. And then I create a parent group from those 3 groups and assign it an instance name of D. Now I attach a text label to the parent group - but instead of seeing "D" in the text, I see whatever sub-group the text leader is attached to. Would it not be more logical to see "D"?

We should be given a pop-up warning if we are about to edit a component - especially in a large model. Glancing at the Entity info inspector panel does not work well because the top of the panel is sometimes obscured and would therefore take an action to reveal it. And even if it's un-obscured, just glancing takes time when you are focused on the work at hand. If I edit a component without knowing it has copies elsewhere in the model, it creates a huge problem.

If i have a thin slab, and I begin using the circle, rectangle, line etc tool to draw on its face, the inferencing engine will pick up any object that may be in contact with the bottom of the slab. It will not restrict itself to the plane of the face. Same goes for the query tool. This happens when the camera is at some distance only. Actually, I believe this same reaction happens with the move command - i think I am grabbing the top edge of a thin slab - when in reality, I am grabbing the bottom edge. Again - only when the camera is at some distance. This came to light as i was maneuvering some wide flange beams so they were all flush with eachother on top. The beam's top flanges are relatively thin. And as I was checking the elevations of the beam's tops with the query tool, I was getting unexpected results.

I reached out to Trimble. They are working on it.

As I toggle between scenes, regardless of order, the screen turns blank just as the transition is complete and the scene is supposed to appear in its saved position. If I nudge the orbit tool, the scene appears - although out of alignment - obviously - which would throw off the established annotations in already created in the LO file. If I pan or zoom, nothing happens. If I double-click the scene tab it appears momentarily, then vanishes. Same if I double-click the scene name where it's listed in the Scenes inspector panel. Issue only occurs with some scenes and, for what it's worth, never happens with those set up in plan view. Scenes that properly appear share the same style with those which vanish. If I open the LO file created when everything worked fine, the problematic scenes appear - but in wireframe style. If I start a new LO file, the problematic scenes appear blank. My scenes in SU and LO worked fine for months. Now this. It must have something to do with recent version upgrade from '21 to '22.

When I launch Thomas Thomassen's editable text tool, it pops up on the left monitor instead of the right one where I typically run SU. Can this be remedied? I have TT's library version 2.12.3.

And can it be improved so we can immediately start typing into it without first having to deal with the default string of text that reads "Enter text"? (Or have said text pre-selected like the native tool does?)

Was this corrected in 2022 release?

Sweet!! I wonder what else I have been overlooking.

Well, when I zoom into my LO screen, I do see a change. However, it is inadequate. The choice for heavier line types beyond 2 pts in the LO tag palette should be offered. Thickening the line scale in the viewport palette defeats the purpose of trying to make, say, one of a dozen rectangles stand out from the rest.

I follow this routine, but the results yielded show little change when I want to thicken a solid line. Am I doing something wrong?

SELECT THE EDGES IN SKP AND ASSIGN THEM A SPECIFIC TAG [LAYER] BUT MAKE SURE THE LINESTYLE IS SET TO DEFAULT ....THEN IN LO, SELECT THE VP, GO TO THE SKETCHUP MODEL PANEL, OPEN THE TAGS MENU, FIND THE THE TAG [LAYER] THAT NEEDS THE OVERRIDE, CLICK ON THE LINE DESCRIPTION, CHOOSE THE SOLID LINE, SET TO 2 PTS, CLICK OK.

I use version 21. Thank you for the solutions. All that's left to do is adjust the left side extension line's end point to provide a gap.

i just glanced thru some convertico tutorials and have come to the realization that the conversion is out of my bailywick/skillset. hopefully, if enough people will complain, trimble will correct the design

I wish we had a rotated dimension tool like AutoCAD. As far as I can tell, the only workaround is to use the protractor in SKP to determine the angle of the dimension line relative to the objects, then switch to LO, set the linear dim as usual, rotate it and finally re-afix the points to the objects.

If i change my file explorer, my IT guy might flip out.

I miss the way the old red Sketchup logo used to stand out from the others. Especially since it's partially obscured by the dropbox glyph. Maybe LayOut's also...but I can't remember. Visual clues improves workflow. I hope they change the color from blue back to red in a future version.

I just took notice of an improvement to the move command that must have been introduced in either '20 or '21. Prior to that, you could not move more than 1 object [group/component] at a time using any bounding box red cross-marks. The marks simply would not appear. However, in subsequent versions, if you select 2 or more objects, the marks do appear and if you grab one, you can move the entire set.

That's crazy.

BTW - I actually modeled the ISS' orbit a few years ago. See attached.

EARTH AND ISS ORBIT TO SCALE.skp

Why would a skp file exhibit such unexpected behavior such as the one I attached? Not only is the object's skin splotchy, but the scene transition is exaggerated. Same thing happens on different computers.

ODD BEHAVIOR.skp