Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1361737

Dat's da one! See the last frame in post #39 in Doc's thread stiffb. Unfortunately both he and I combined the Map Size and ShadowCam adjustments when illustrating our examples, so we don't really compare the relative effects of one to the other, but you'll see it quickly with a little experimenting. With regard to system resources, keep in mind that increasing the Shadow Map Size will increase memory usage as well as render time, while adjusting the Shadow Camera's scale will not. Also, for way more than you wanted to know, check the link above, especially starting at post #23 by lesbentley regarding unhiding each ShadowCam's Z-Trans dial. There are a few misconceptions later in that thread though, regarding changes in an object's ability to *accept* shadows cast upon it when it's Cast Shadows option is turned on or off. What is really happening there is that when changing this setting on any object in your scene, the shadowcams positions are reset by the app to include within their field of view all the objects with Cast Shadows turned on. This change in the ShadowCams' field of view will usually alter the resolution of the shadows cast upon the objects -- but it is only the ShadowCams that are changed, not really anything about the prop's inherent ability to accept cast shadows as the thread suggests.