Yep, you are correct, which is why I said I may be wrong, I rarely use geolocation and the quick test I did didn’t show the issue. But now awake and with coffee in hand I made a better test and yes, if I take a component from a geolocated model and add it to another geolocated model, test case done only a few houses away, the component will be placed at the original location.
Annoying, and it helps explain why a variety of items in the 3d warehouse are strangely geolocated.
I will however Note that they only seem to use the insertion point, they aren’t glued to that position like a truly geolocated component would be.
SketchUp Team
Anyway to flag this or update in a future release? A few times now this has caused my models to crash and it seems like unintentional behavior. I get that not a lot of folks use geolocating, but that just makes this all the more potentially troublesome because those people won’t realize why a model is loading miles away from all of the rest of their assets. I just don’t see why a component should bring along it’s geolocated data, to me a component saved out of context is designed to be a reusable asset in a new model.
One more reason not to insert things from the 3D Warehouse into your model directly without inspecting them. There are so many items that are geolocated, far from the origin, to the wrong scale, with an odd axis placement or just bloated high-poly geometry that correcting just one problem won’t get us far.
I agree, and I always open and check a 3D warehouse model first, then insert it into my main model. I don’t often use the 3D warehouse models though. However, on the rare occasion where I actually need to geolocate my main model, my entire library of created assets on import ends up miles from the origin and freezes my computer. These are all components created by right-clicking a component in a model and hitting “Save As” so of course I assume those assets are clean and not importing the rest of the model with them. Creating a project with models entirely of my creation saved as components shouldn’t result in this error. Sure there are workarounds, but I don’t often geolocate my main model, so even with workarounds I inevitably import the first component only to remember this issue. It’s like accidentally importing a model while my materials tab is open, I’m one of the lucky few where that can take my model import from a few seconds to 10+ minutes, and that issue, to my knowledge, has still not been resolved several years later. Still having to do that workaround. Would like to avoid adding another workaround to the workflow. Anyway, this isn’t a feature request, but I appreciate the feedback tweenulzeven. It’s really correcting what seems to be an unintentional error to me. Still, I may do just as you’ve recommended if only to have hope this may get corrected.
In the component browser, instead of clicking the compinent and adding it to your model the usual way, try dragging and dropping it from the browser into the modelling area.