Custom components import to origin...???

Rich O Brien

And how do I get rid of it...?

utiler

I will try that, Dave.

Thanks Rich, silly question I guess.....

utiler

So after much hair pulling, a total re-install and numerous trouble shooting ebbs and flow I realised it was something with my template file that was causing the problem. I may have avoided the the re-install but SU has never looked so good with all the unused crap I have loaded over the years....!

Thanks for helping out guys; if there's one on-line community that feels line we are all under the same roof its this one....

Now, where's that Pinterest link.....

optimaforever

@utiler said:

So after much hair pulling, a total re-install and numerous trouble shooting ebbs and flow I realised it was something with my template file that was causing the problem. I may have avoided the the re-install but SU has never looked so good with all the unused crap I have loaded over the years....!

Thanks for helping out guys; if there's one on-line community that feels line we are all under the same roof its this one....

Now, where's that Pinterest link.....

Hello, can you develop please?
I have the same issue with several of my components that import exactly at the origin and I can't avoid that. When working with heavy models it's always a pita to have to dezoom to pick the compo at 0,0,0 and move it to the wanted place...
Thanks

TIG

If a model [or a component created from it] is 'geo-located' then the first time it's inserted in a new model it snaps to the origin with no user input.
To avoid this remove the component's geo-location under the relevant item in its Model Info.
Always take care with imported SKPs that they are not geo-located !

optimaforever

@tig said:

If a model [or a component created from it] is 'geo-located' then the first time it's inserted in a new model it snaps to the origin with no user input.
To avoid this remove the component's geo-location under the relevant item in its Model Info.
Always take care with imported SKPs that they are not geo-located !

Ah! interesting info, thanks Tig!

TIG

You could try running some code in the Ruby Console...
e.g. this might remove the geo-location from all of your model's current component definitions...

Sketchup.active_model.definitions.each{|d| d.attribute_dictionaries.delete("GeoReference") }

Rich O Brien

@tig said:

If a model [or a component created from it] is 'geo-located' then the first time it's inserted in a new model it snaps to the origin with no user input.
To avoid this remove the component's geo-location under the relevant item in its Model Info.
Always take care with imported SKPs that they are not geo-located !

Can you access this 'geo remove' data via api? Would be a nice addition to your Purge plugin.

utiler

@rich o brien said:

@tig said:

If a model [or a component created from it] is 'geo-located' then the first time it's inserted in a new model it snaps to the origin with no user input.
To avoid this remove the component's geo-location under the relevant item in its Model Info.
Always take care with imported SKPs that they are not geo-located !

Can you access this 'geo remove' data via api? Would be a nice addition to your Purge plugin.

Agreed Rich!!

TIG

I've looked at automating this but my suggested fix seems to fail when resetting the component's attributes....
So I won't be adding it to PurgeAll any time soon