Custom components import to origin...???
-
@dave r said:
I'm glad that method worked for you.
Just tried it on my work machine, Dave..... no good; still snaps to the origin!!!!
-
Did you try it with a new component?
-
Yep, created a new one....
I think I might re-install SU completely this weekend. It'll take for ever to try and work out what this problem is....
-
Andrew, before you reinstall SU, try renaming your Plugins folder so the plugins don't load and see what happens.
-
-
I will try that, Dave.
Thanks Rich, silly question I guess.....
-
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.....
-
@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 -
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 ! -
@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!
-
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") } -
@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.
-
@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!!
-
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
Advertisement