Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 27 5:12 pm)
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.
I'd like someone else to verify this so I know it's not just me being stupid somewhere.
Open a new default scene in Poser 8 SP1.
Navigate the Object Palette to show the Properties of Light 1; should be Depth map shadows & Shadow Blur Radius 2.0.
Open the Scripts>Python Shell window and type in the following:
light = poser.Scene().Lights()[0]
light.ShadowBlurRadius()
Should return 2, which agrees with the GUI
light.SetShadowBlurRadius(6)
light.ShadowBlurRadius()
Should return 6, which agrees with the changed GUI
light.SetRayTraceShadows(True)
GUI Shadow Blur Radius changes to 0.0!
light.ShadowBlurRadius()
Python still thinks it's 6!
llight.SetShadowBlurRadius(2)
light.ShadowBlurRadius()
Python now thinks it's 2, but the GUI still thinks it's 0
If you render as the scene now is, the render engine takes the value of 0 from the GUI, not the value of 2 from the Python. If you change the GUI to 3.0, the render engine will now use 3.0 for the Shadow Blur Radius even though Python still thinks it's 2.
If it's not just me, this is not how it behaved before SP1 and, in my mind anyway, is certainly wrong. Anybody confirm this?
Whichway