Big File Sizes/ High Poly
-
I always export images with 3200x2165... good enough to be printed in a A3 format...
There's any specific comand in photoshop to the anti-aliasing job?
-
In photoshop when you redice a file it will anti-alias using the current setting. I think that most use bi-cubic by default. You should read in the photoshop help about each of the options though, because some are better for other things. You won't be disappointed with bicubic though, it works great. And I generally try to export 2x what I want my final image size to be at. Then reduce it in photoshop. That works great for me.
Chris
EDIT: Oh, and you can choose what type of resampling to use in the Image Size dialogue box (where you change the dimensions of the image). At the bottom there is a drop down list of different options.
-
@kwistenbiebel said:
The others seem to have covered most tricks already.
A thing that is handy as well, is setting the material browser to 'text names' instead of icons.
Also closing the 'outliner' panel gives back some editing speed.Besides all the workarounds that can improve workflow a little, I really hope SU7 will adress this.
When doing bigger arch projects, this problem always shows up...Is there a way to have materials appear as text names using SU6 for Mac?
-
@unknownuser said:
BTW all! Profiles? Does anyone ever use profiles? I think I turned them on a few years ago and didn't like them at all!
I've never used profiles either. I have no idea what their purpose is and I think they make the model look ugly.
-
Yep, those 'profile' things suck. Never used them either.
-
Profiles are essential for new users -- allowing newbies to tell easily when they are not making faces and helping to distinguish groups and components.
-
That is very true Paul. I'm glad you mentioned that. I still leave them for that reason, I though I generally turn them off when I render an image.
The reason they are there, as it was explained to me, is because often we perceive depth this way in real life. Items that have space behind them appear to have a more bold outline or a harder edge around them. I don't know that the profile edges accomplished that very successfully, but that was what I was told.
Chris
-
in the basecamp tutorial section there's a tip for this.
The essence is that you can make scenes without camera positions.
This way the scene tab behaves like a display mode.
Per tab you retain full control over displayed layers and such, as mentioned by earlier posts.
Good luck ! -
Ah yes, thats a great one! I highly recommend it
Chris Fullmer
-
@chris fullmer said:
Ah yes, thats a great one! I highly recommend it
Chris Fullmer
I wonder who gave that presentation. It was a really good one by the way
-
@kobus said:
in the basecamp tutorial section there's a tip for this.
The essence is that you can make scenes without camera positions.
This way the scene tab behaves like a display mode.
Per tab you retain full control over displayed layers and such, as mentioned by earlier posts.
Good luck !That is excellent. I do that a lot my self. One thing I never use is profiles or jitters. What the heck for? In fact I rarely use "styles" at all, and certainly never when modeling. navigating in Wire mode is always good. Thanks for the tips as well.
I feel like such a noob when I come on this site.
-
ahh, you're too nice Gaieus! I saw your portion was also referred to yesterday here on the forum. I think the tips and tricks session was the best! Though I AM biased....
Chris
-
Too bad we had such short times each. I had about ten of them and finally I turned out to pick the two that were the least "spectacular". (Not to speak about running into a couple of bugs which I could've avoided)
-
@kobus said:
in the basecamp tutorial section there's a tip for this.
The essence is that you can make scenes without camera positions.
This way the scene tab behaves like a display mode.
Per tab you retain full control over displayed layers and such, as mentioned by earlier posts.
Good luck !I use scenes a lot to manage layers. I actually use then to turn layers off and wireframe the view in large models to assist in navigating then shortcut or next scene tab to turn back on. for Camera views when exporting to render I actaully use two scenes - the first to set camera location and the second to set all layers on!
Another trick I use a lot with very large models say where I am adjust plant layout in a specific location or when working ob heavy geometry is to drag select any items or geometry where i want to work in detail shortcut to group, double click to edit this new group and hide rest of model, I then after editing explode that newly made group! I would say this is possibly one of my mostly used workflows to speed up modelling! Though shortcuts are essential to speeding this, but aren't they essential for all modelling anyway!
It was interesting some years ago a long time SU user suggested to me that trying to remember shortcuts to save seconds a day was a waste of effort. I would have to say good workflow using shortcuts could save as much as 5-6 hours in 8 hours of modelling!
-
@richard said:
It was interesting some years ago a long time SU user suggested to me that trying to remember shortcuts to save seconds a day was a waste of effort. I would have to say good workflow using shortcuts could save as much as 5-6 hours in 8 hours of modelling!
I totally agree with you on that Richard. it saves a tremendous amount of time. and your model gets even tidyer, because it is no effort to press a button to create a group/component (and for that matter press another button to explode it again )
modelhead, could you give me some clues of what you simplify in the components to reduce file size to this amount? could you perhaps post a before-after example? that would help me a lot to see if I am on the right way.
if you are good with a program you tend to stick to your habits very easily. but sometimes it is good to question them again and maybe improve them to get an even faster workflow. -
i stuggle with this as well. I do a lot of site modeling that requires trees and I like to use 2D cllips as often possible, but for aerial views, I kinda need 3D trees, and the good ones are so High poly. I guess I should play around with Proxies more to simplify and only turn on the biggies when it comes time to render or something, but Any other hints to manage the file would be grateful.
Ps. I havne't done it yet, but I have the link to the 3D basecamp workshop on this. I oughtta listen to it. . ..
I wasn't invited, you know. . .
Advertisement