I'm wondering if it's "easier on the system" to, as another poster suggested in a previous thread of mine, just make every prop an image and then import that image as a layer? From my understanding ASP6 renders every object and it seems, at least in my mind, that you would get better results if every prop (couches, photos, posters etc.) in a scene was just translated into an image layer, this way ASP doesn't have to do all that work. It came as a realization of mine as I was creating a keyboard. ASP about shat itself when it was rendering all those keys. I took a suggestion from another poster regarding a seperate issue of mine and applied it to this one. Just made an image rendering of the keyboard and voila, all better.
So anyway, am I wrong on this? Will it cut down visual quality? Thanks for your time. Much appreciated.
I was wondering about images...
Moderators: Víctor Paredes, Belgarath, slowtiger
The CPU power needed to process images and vector layers depends on some simple attributes.
Vector: number of points; the more, the heavier.
Image: just the image size.
Everything else, like layer transfer effects, blur, whatever, is the same for each type. So if you have a very complex prop like a keyboard with 88 keys chances are good that this will render much faster as a single bitmap.
Vector: number of points; the more, the heavier.
Image: just the image size.
Everything else, like layer transfer effects, blur, whatever, is the same for each type. So if you have a very complex prop like a keyboard with 88 keys chances are good that this will render much faster as a single bitmap.
There's a bit more to it than that. Vectors are resolution-independent -- so you could export one movie at web resolution and another at HD quality from the same AS file. Other factors (like zooming into backgrounds) are also a lot easier to deal with as vectors in many instances.
If you do intend to use bitmaps, try to use higher-resolution images than standard screen resolution (<100 dpi). This avoids pixel chunking if you get too close..
If you do intend to use bitmaps, try to use higher-resolution images than standard screen resolution (<100 dpi). This avoids pixel chunking if you get too close..
You can't have everything. Where would you put it?
Please don't use dpi numbers in this context since they're confusing and of no use. It's better to say "choose image dimensions which fit your project's dimensions".
If you want to render in HDTV (1920 x 1080), a background image must be of at least that dimensions - more when you want to zoom in. But don't overdo it, more than 150% size is overkill (and clogs your processor).
If you want to render in HDTV (1920 x 1080), a background image must be of at least that dimensions - more when you want to zoom in. But don't overdo it, more than 150% size is overkill (and clogs your processor).
Ha ha! Yeah, that was misleading. I was attempting to (approximately) describe screen resolution, actually... And I know Germans favour long words, but substituting "choose image dimensions which fit your project's dimensions" for "dpi" is going a bit far, don't you think?Rhoel wrote:Possible typo here? Should that read >100dpi. I try to use 300dpi on background images, or just set them to 12 Field or 15 Field resolution (Let's here it for the old school standards).jahnocli wrote: try to use higher-resolution images than standard screen resolution (<100 dpi).
Rhoel
You can't have everything. Where would you put it?