Mon, Nov 25, 11:42 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 25 12:38 pm)



Subject: Shadowmap nightmare... 1024 maximum??? What???


hogwarden ( ) posted Fri, 23 August 2002 at 7:29 AM ยท edited Mon, 25 November 2024 at 9:42 PM

Hiya... Big probs. The most I can set my shadow maps to is 1024. However hard I try and however many lights are in the scene, I can't set past 1024. Sorry, but 1024 is NOT enough for a good crisp shadow... esp hair shadows on a portrait. I have had this problem since moving from Win98 to XP. Any ideas on how to sort this out?? H:)


EnglishBob ( ) posted Fri, 23 August 2002 at 7:50 AM

Yep. Doubleclick on the dial, set the maximum to 4096 or whatever you want. OK that, then set your required size in the usual way.


hogwarden ( ) posted Fri, 23 August 2002 at 7:58 AM

Of course!!!!! Duh. case of "can't see the wood for the trees"! Mysterious how the maximum became changed, though, because this has only started recently. Thanks EnglishBob! I'll give it a try when I get home. H:)


EnglishBob ( ) posted Fri, 23 August 2002 at 8:08 AM

I haven't tried it, but if you set the shadow map limits in your Preferred State PZ3, it should be applied to every new scene you start. Did you re-install Poser when you upgraded your OS? That may be the reason it's changed. As far as I know, 1024 is the default limit (and 256 the default map size), and has been since Poser 3. However the limit is an arbitrary one and really only depends on how much RAM you have.


webvogel ( ) posted Fri, 23 August 2002 at 8:22 AM

Hey! Thanks! It`s so easy? I was thinking 1024 is the maximum i can have on my maschine EnglishBob, what is the limit with 256mb / 512mb ? Greetings,Webvogel


hogwarden ( ) posted Fri, 23 August 2002 at 8:26 AM

I was thinking that... I did re-install, and I had previously altered the preferred state file. I've 768MB Ram so I like to shove the shadow map right up to 4096 sometimes. I've been so busy writing PBooost that actually rendering in Poser has so many pitfalls I'd forgotten about!! H:)


EnglishBob ( ) posted Fri, 23 August 2002 at 8:32 AM

There's no easy formula, Webvogel - you just have to try it. It will depend on what models you have in your scene, and the number and size of textures. I regularly go up to 4096, on one occasion I had 4096 on two lights at once with only 128M RAM - but that was with standard Poser figures, and few textures.


mjtdevries ( ) posted Fri, 23 August 2002 at 8:45 AM

Basically the limit is the maximum amount of virtual memory you have. (RAM + swapfile) In a 32bit OS you will have a hard limit at 2GB. I have actually hit that limit myself by setting the shadow map size above 9000 :-) Swapping because of this isn't too bad, so don't hesitate to use sizes well beyond the amount of RAM in your machine. IMO Playing with larger shadowsizes is especially usefull for close-up shots of a face with shadows on it from hair strands.


Spanki ( ) posted Fri, 23 August 2002 at 9:15 AM

Attached Link: http://www.renderosity.com/homepage.ez?Who=Spanki&ViewArticle=1265

You might also want to disable "Casts Shadows" on any large ground planes i nyour scene (since they don't cast shadows on anything anyway. The link above is a mini-tut I wrote up after discovering this little tidbit (Warning: Nudity in the link)

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.


c1rcle ( ) posted Fri, 23 August 2002 at 9:39 AM

I set mine to 8192 the other day, took ages to render but it looked really sharp, the ground plane tip came in very handy for this one too. Rob


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.