Good Job, Jeff! In this case the texture would've been probably the last thing I'd've checked.

Thanks, Gents! That will help me keep what little hair I have left! Cheers, Caoimhín

GOT IT THANKS !!!!!!!!!

@maverick83 said: Is there a smart way to do this domino-like thing? Thanks!! in answer to the question; copy along path [image: AGX0_Capture.JPG]

If I'm not mistaken once you've imported the texture into your SU file you can right click on that texture in your Materials panel and theres a Save As option or something like that. Click that and you can browse through your folders until you find SU's Materials folder and drop it in the appropriate one, or make a new one. -Brodie

Sounds like you went in to xray mode somehow, try going view->face style->shaded with textures.

Ah yeah, good that you put the picture up! That's definitely this camera thing you somehow succeeded to insert into your model (I would wonder however how you did it). Use the script Remus suggested.

Thanks !!!

Thanks All...and yeh Adam! Darren, I figure I'll follow Pete's lead and see how community pricing works out: hopefully volume will make up for a slim profit margin :`)

@chris fullmer said: @honoluludesktop said: A entity can only be on one layer. Yeah, but groups and components are entities. And a group entity can be on Layer 0 and all its contents be on Layer 100. Or its contents can be split up on all sorts of layers. I wondered about this; by (my) definition, entities are primitives. That is they can not be broken down into more basic elements. What do you think? @chris fullmer said: @honoluludesktop said: Groups can not share surfaces. That sounds mis-leading to me in that they can have faces in the exact same 3d location. Maybe they can't share entities sounds better in my mind. Tried it. Couldn't make two groups share the same surface. However, two components can share the same space. @chris fullmer said: @honoluludesktop said: A component instance are entities that comprise a component definition. I'd reverse the order of these. First comes the definition, then comes the instances (sort of). The definition is aptly named because it is the base "definition" for the instances. The definition is what is shown in the components browser. Once you select the definition to insert into the model, you then have an instance inserted in the model. So all components are instances (except the definition shown in the comp. browser). Let me think about this. An instant is part of the model, a definition is data noted in the component browser and outline. @chris fullmer said: @honoluludesktop said: Component properties are common to all instances. Instances actually can have different properties than the definition. The X,Y,Z location, any changes in scale, and materials applied to the outside of the instance, are all properties that are saved uniquely to each instance. I was thinking of the things that an instance of a component share with other instances of that component. @chris fullmer said: @honoluludesktop said: Component instance comprises of its definition. Yes, as a a starting point. Like I pointed out above, the instance when inserted into the model is an exact copy of the definition. But scaling it, applying a material to it, or moving it will change properties to that instance. Oh, and all these properties can be changed without making the component unique or different than its definition. S***, when I scale a component, it scales by itself, but each instance's common surface, can share common property (like color). So we have properties that are shared (like color), and those that are unshared (like scale). Is scale a property, or should it defined in another way? @chris fullmer said: @honoluludesktop said: A scene (among other things) is a collection visible layers. A scene is a collection of visible layers (among other things) And I would love to detail all those other things, because I think that scenes are much more useful than many people realize. Its all in the "among other things" that there is some great functionality. Perhaps too complex for elegant definition?

Fair question thomthom. Good answer Gaieus. Thank you.

Are you asking this or saying? (BTW there's no kmz download for this one so I can't tell how it would behave in GE but I doubt it would animate). You can do the animation in SU, can't you?

@gaieus said: Yeah, this often drives people who haven't experienced it before crazy. There are a bunch of commands you can only perform when something is selected (reverse faces for instance) and until you select the proper entity, no shortcut option appears. I had hoped that behaviour would change for SU7. It's not really intuitive. Maybe we can try to make our voice heard for SU8...

@xrok1 said: toxicvoxel, just to clarify, you painted the metal face inside the component and everything else on the outside. is this correct? Affirmative.

Mirjman Thanks! this rb is a big help.

Toxic, Nice work, I like it. This kind of design is very popular in mobile phone showrooms. Where do you plan to obtain fittings, have them made or buy finished ? I do a lot of retail design and did a couple of similar interior designs. Here is a good recource for similar shop systems I used on one occasion. Two series Fluo wall and Fluo partition: http://www.fluosystem.com

Generally the big wite cursor issue is a graphics issue. Try changing the setting within SU to turn off hardware acceleration or something like that. You might also update your drivers if Mac's let you do that kind of stuff.

Unfortunately, I think you were right before; I don't think there's any way to set a default folder to save models. It just goes to the last folder you saved a model in, and we get a list of recent places. That's it. I could be wrong though, you never know.

@gaieus said: Okay, so what I found out (at least that's how it works for me) is: If I create the group after adding the guide to it, everything works fine (see Group and Guide1 in the example file) If I rotate the group (with the inside guide included), the outside guide line will be drawn by the exact double value of rotation as I rotated the group - see G2 in the file where I rotated the group by 30 degrees around the red axis but the secondary guide is "rotated" at 60 degrees (measured to the green axis; see from the side). If I only group the rectangle and the guide AFTER rotating them first, the secondary guide is drawn parallel again. Ah. That's good info. I couldn't work out what determined the direction of the mis-aliged guide. Hopefully this should be enough info for the SU team to terminate this bug. ...what's the most reliable channel to report a bug? (which SU had a bugtraker system)

It says it exports/imports FBX files. You should give a chance to it - supposedly it's a better format than 3DS for conversion.