2D 3D
-
Now that's cool (in fact I am an archaeologist specified in Roman provincial archaeology and have dug in several Roman forts so far
)Now edit the components and hide the dges. From a distance those profile lines will simply cover the whole face.
-
From a distance those profile lines will simply cover the whole face.
Ya, as the image shrinks they tend to go black. Bigger problem is 2D face me object are semitransparent. As in this image, shadow show through adding quite a bit of clutter. Is there a way to make it completely opaque?
in fact I am an archaeologist
Ok, so that is where your Avatar comes from. I am no archaeologist but one of my hobbies is flint knapping. I can now make halfway decent projectile point out of obsidian. One might think making Stone Age tool is simple, but it is no easy task to make a nice lethal point. You need right tool, right material, and right technique to make it.
-
First thing to do to get the soldiers non-transparent would be to check the image you cut it out from in the materials browser. If you click the 'edit' tab you should get a little opacity slider at the bottom, make sure its at 100%.
If it's the iamge itself thats transparent, you'll need to pen up your image editro of choice and make it non transparent, you should then be able to import it back in to SU and use it as a projected texture to go over your old texture.
-
Ups, sorry, I had X ray turned on!
-
@ridix said:
Ups, sorry, I had X ray turned on!
That was my other guess
Would you mind sharing the image?
-
Here is the image. With only this many roman solders, my pc is starting to slow down! No go to make a Roman legion.
-
Hide the outside edges - it will ease your performance problems (and the soldiers would look better, too).
-
I'm assuming that the Roman Legionary is all geometry...as with the standard SU Face Me people. This can lead to an awful lot of edges when you start multiplying up the number of figures.
One way of avoiding this is to take a render of your figure, then use that image to create a "photo" version. This will allow you to get rid of all the interior lines. You can further reduce the number of edges by making the background of your exported image transparent and saving it as a png file. If you leave the imported png figure as-is, it will cast a rectangular shadow, so it's best to cut it out. However, you can be fairly brutal about this, because the transparency in the image takes care of the silhouette of the figure itself. You are only cutting it out for the sake of a realistic shadow...which is likely to be distorted anyway; so you can afford to make a very simplistic outline.
I've used this process here...not quite a Legion but 4 maniples, making up a cohort of 480 men...and it's still navigable (even more so with shadows turned off).
-
Looking good!
SU seems to use lots of CPU crunching when it comes to displaying edges. I have been using C4D for some time. With that software if you are not careful, one can easily create over a million polygons; that’s 3 to 4 million edges! And it still display ok on my PC. What is going on with SU anyway?
-
The general belief is that the same inferencing that makes it so easy to draw in 3D in a single window is constantly keeping track of a good many vertices in the model, thus making the program rather geometry-intolerant. That's why it's often a good idea to offload some of the work onto the graphics processor, by using images, rather than pushing everything through the CPU.
-
Yes, SU doesn't deal with too many polygons too well. Outlines and shadows multiples the strain many times. I tend to only use them when I export images or for very light models.
-
@alan fraser said:
I've used this process here...not quite a Legion but 4 maniples, making up a cohort of 480 men...and it's still navigable (even more so with shadows turned off).
480 armed men always facing your direction... scary...
I found that using using billboard images instead of drawn outline work much faster as well. I tried making a forest with the default SU tree and that bogged down very quickly. And I got a decent card, nVidia Quadro 3500. But using billboards made a huge difference. Something which was a great bonus to me when I render in V-Ray.
-
Back to something that Remus & Gaieus said early in this thread...
When creating a new face-me component, I don't have the face-camera option available in the original file that is saved in the Components folder (call this the Base file). I only see that option if I add the component to a new model, explode it, and create a new component in my new model. This is time-consuming to edit each component after I've inserted it into the model. I've looked at components I've downloaded from users on this forum and those that come with SU. These base files are strictly geometry (not components). Some can be inserted correctly as face-me components, others not. There is nothing unique (that I can see) about the files that work as face-me's versus the one's that don't. There's got to be an easy fix for this, but I sure can't remember/find what it is.
Thanks for the help.
Wyatt -
I'm not sure I follow exactly what you are saying, but my experience is that the 2D Face Me components that come with SU (and similar ones I make for FormFonts) are just that...components. Whereas the Face Me components that people generally post to this forum are embedded components. In other words, the file itself is a component, but it has a duplicate of itself in the component browser.
This is achieved by making a Face Me in the usual way (at which time it appears in the browser, like any other component) then saving the entire file. If you think about it, this is not the way you would save an ordinary component. You wouldn't, for instance, model a chair, then make it a component, then save the file...you'd just save the file. Obviously, if you do this with a Face Me, you have no way of actually specifying that it is a Face Me. The answer is that you do make it a Face Me component, but you don't save the whole file (with the embedded component) you right-click the component in the browser and save that instead...then discard the original file. This will save the component as a Face Me, but it will just be the straight geometry...there won't be a copy of itself in the browser, nor will it actually rotate when opened. Face Me components only rotate when imported into another file.
The only slight bug in this process at the moment is that when Face Me files are saved in this way, then opened, you can't see anything, because the camera zoom appears to default to a position about 1mm away from the origin. So you need to zoom to extents then resave.
-
Thanks Alan. I was trying to edit the component in its base file. When I insert the component into a new file, explode it, and resave it from the component browser I'm able to turn on the face-me features. It seems like there are some added steps there that slow down the workflow, but I'll live with it. Thanks again for the explanation.
Wyatt
Advertisement