Least used function of SU
-
Imperial and metric units are not so much functions as they are settings, so I wouldn't include them. For me, the least (as in never) used functions would be:
polygon
fog (although I can see where it might be useful)
walkthrough
outliner -
Until I heard it mentioned above I didn't know what my least used tool was. The mention of "freehand" set my light bulbs off. I don't think I have ever used it except once to play around with. After that fog, and outliner, but I do like fog and I do not wish it to go away.
-
Freehand is useful from time to time, but did you know that it has an shift-modifier to it? Check it out. Hold shift while drawing and you get a freehand line that is free of inferencing. Its a 3dpolyline. That is a tool I never use.
Chris
-
@chris fullmer said:
Hold shift while drawing and you get a freehand line that is free of inferencing.
Duh...
-
It locks the line on to a plane, though, which is a bit annoying.
-
Every mentioned feature have their specific use. Fog can belong to the least used functions for some people, but it is very useful for a lot of people. Styles are simply a must - and an amazing feature. Layout is getting better, and is soo cool.
I never used the "print" icon from Sketchup!
-
Autosave, is slows your modeling down, get into a habit of saving before any major operation.
Layout, too many great apps out there that do a better job for Google to be wasting resources on this. -
I use metric (inches confuse me), and actually use flip along axis quite often, as well as fog and styles (I think half of my models have their own styles...). Oh, and use sun for shading. More realistic, no slower.
My least used functions would be;
tape measurer
protractor
the zoom tools
eraser (I probably should...)
and section cuts. -
I'm surprised how often the tape measure and guidelines end up on these lists. I suppose it depends on what you do. I find these tools essential when I model.
Don't you ever wonder about a certain measurement in your models? -
@solo said:
Autosave, is slows your modeling down, get into a habit of saving before any major operation.
Layout, too many great apps out there that do a better job for Google to be wasting resources on this.Hi Solo, I think autosave is a must have feature - the slows down happens probably because other performance problems, but it can be easily disabled. About performance, I can only think about the core modeler itself - cannot run in 64 bits and cannot use 10% of the actual GPUs abilities.
I just cannot think about any other app that do what Layout does - can you explain?
Regards.
-
i use autosave but this thread just helped me get a new system i'm going to try out..
i always wished autosave could be set to make sequential files (i.e. autosave_house01, autosave_house02, etc.).. sometimes i like to go further back into a model than what autosave and the current file will provide me with..
a normal save doesn't give me what i want because then you can't go back. 'save as' is what i want but i never really used it because i have to manually type in the sequential numbers..
'save a copy as' however will automatically add the sequential number (ie - house copy, house copy 2, house copy 3).. i just added a shortcut for that command (⇧S) and after a quick test run, it's looking real good..so yeah, maybe autosave will become a least used function for me
-
@unknownuser said:
i always wished autosave could be set to make sequential files (i.e. autosave_house01, autosave_house02, etc.).. sometimes i like to go further back into a model than what autosave and the current file will provide me with..
Sounds like a candidate for a new plugin...
-
@thomthom said:
Sounds like a candidate for a new plugin...
thing is, (and i've never really tested or confirmed this) is that i'll sometimes get a hang or occasionally a crash when using certain rubies and i'm starting to think it might have something to do with autosave..
joint push pull for instance usually runs great but on rare occasions, it will hang.. i'm wondering if it has something to do with the saving of the file while the ruby is running ?? -
Oh, that's so true! Every model done (finished or not..) and the model folder is full with every step imaginable of the entire "development history" - for now, a manual process. This autosave configuration is a must have, but I think that it must be integrated with Sketchup.
And yes, I too think that crashes are related to certain operations when saving, like plugins.
Advertisement