Import Component Pain
-
When I insert a component (usually FormFonts models) they turn on shadows and automatically place the component at the origin. Its a huge pain on large models, esp when I am at the final stages and adding entourage. How can you stop SU from doing this automatically?
-
Could you explain exactly what you are doing? as importing a component should not turn shadows on...even if that component was created with shadows on. And all FormFonts components import clinging to the end of your cursor, not the origin. They'll only head straight to the origin if you Copy/Paste in Place.
-
It seems to only do this with some models and not all across the board. Example - I just tried to recreate it in the model I am currently working on and it was fine. Did just as you said, no shadows and at my cursor. Then I started a brand new clean file and tried to import the same component (FF_Model_ID13477_4_LPWAD_23) and it turned shads on and zoomed right into the origin. Its crazy!
When it happens its a huge pain. It happens with 3D People components from FormFonts. I'll use my components window, navigate to my libray of 3D people, pick the model I want to insert, SU locks up for a sec, turns shadows on, then zooms extents and puts the thing at the origin. -
I finally figured this out.
If the component has a geo-location associated with it, then it automatically places it at the origin. If the component has a set geo location and has shadows turned on in the component file, then it automatically places it at the origin and turns shadows on in your file you placing it into (annoying with larger files).
I assume that whoever has created these models has a geolocation associated with their template file possibly. They simply need to go to Model Info and under location, choose clear location then resave their template.
Alan, could you get word around at FormFonts for the modelers to make sure that they do not have a geolocation associated with their models?
-
Thanks for pointing this out. This appears to be a feature that has crept up on us. All versions up to and including V7 had a two part attribute...you could 'Locate' a model anywhere you liked (all FF stuff was located to San Luis Obispo CA) If you export a kmz from any of these, that model will indeed be located in someone's driveway near an intersection in downtown SLO. However importing such a model into SU did not (and does not) result in the behaviour you noted. However there is also a georeferencing check box (up to V7); if this is also checked then you get the behaviour you noted.
This appears to be the case in the model mentioned. We'll make sure this doesn't occur again and try to track down any errant files in which this is the case.
V8 has no such two part attributes...either a model is geolocated, or not. The weird thing is that all the legacy FF models that are located but not georeferenced (all but a tiny handful, I'd imagine) show up in V8 as not being geolocated at all...yet they still spit out a kmz that places them in SLO.
Advertisement