Krakatoa 1.0.2.30007 Beta
Max9x64
WinXP Pro x64
The attenuation map output is always 512x512 for spots and directional lights and 1024x512 for omnis,
even if I set the shadow map size to 4096. Can anyone confirm this?
Thanks
>Krakatoa 1.0.2.30007 BetaMax9x64WinXP Pro x64
>The attenuation map output is always 512x512 for spots and
>directional lights and 1024x512 for omnis,even if I set the
>shadow map size to 4096. Can anyone confirm this?
>Thanks
Hi Thomas,
I tested this in both the old 1.0.1.29090 and in our current inhouse 1.1.0.30026 builds and both save the attenuation maps correctly, for example when set to 2048, the omni creates a 4096x2048 map, the spotlight is 2048x2048. An omni with 4096 shadow map writes a 8192x4096 attenuation map and so on.
I might install 30007 to test with, but even of it was broken there, it is not broken in the current (and upcoming) Beta build, so it shouldn't be an issue.
Hi Bobo,
Strange, I get the same problem here with 1.0.1.29090 too, I´ve attached a simple scene to test for you.
On my System it creates a 512x512 map, but the shadow map size is set to 2048.
Hi Bobo,
Strange, I get the same
problem here with 1.0.1.29090
too, I´ve attached a simple
scene to test for you.On my
System it creates a 512x512
map, but the shadow map size
is set to 2048.
Hi Thomas,
I opened and rendered your file at home with Build 29090 and got a 2048x2048 attenuation map saved.
Out of curiosity, are you using a German localized version of Max or the English one? 512x512 is the DEFAULT attenuation map size if the shadow generator is set to non-Shadow Map, for example Raytrace etc. Chances are that if the name of the Shadow Map generator is localized, Krakatoa could mistake it for an unknown shadow generator class and assume defaults instead of getting the right map size settings.
If you are using a German version, we will have to work together to figure out what exactly is going on and how to fix it…
Cheers,
Bobo
Yes Bobo, I´m using a german version! Just let me know, if you have something
to test for me 
Tom
Hi Bobo,
I´ve noticed that DOF also doesn´t work in the german version, it seems to ignore
the f-stop value in the camera settings. In my fresh installed max 2008 (english)
everything seems to work fine.
Hi Tom,
I would like to ask you to run two lines of MAXScript in your German version of 3ds Max and send us the Listener output so we can figure out what the localized property names might be…
Open the Listener (F11) and type in
show (FreeSpot())
show (Depth_of_Field__mental_ray())
If you get any errors while evaluating these, please send them, too.
Thanks!
Hi Bobo,
I´ve attached a txt file with the Listener outputs.
>Hi Bobo,
>I´ve attached a txt file with the Listener outputs.
Thanks, we are looking into it.
Hi Bobo, are there some news about this problem?
Tom
Hi Bobo, are there some news
about this problem?
I know Darcy attempted to change the way the parameter is being accessed. Can you test in the new build and see if anything has changed?
Since we don’t have a German version here, we cannot test. (We will have to see if it would be possible to get one from Autodesk for such cases).