ShadowmapSizeLimit bug in 2016 SP1

[artgrail]

If I change NitrousGraphicsManager.ShadowmapSizeLimit default 512 to something else (1024, 2048, 4096) 3ds max starts eat memory (I have 32GB) and in a few seconds uses all available memory (25GB at the moment).

Video card: ASUS GeForce GTX 780, the drivers are the latest (355.60).

[artgrail]

Actually the memory leak is still alive with SP2. Max continues to eat memory, just a bit slower (10-15 minutes).

[lightcube]

I've seen some bugs in SP2, but in my case SP2 solved the memory bug. I couldn't even use 2016 until SP2 because of the SP1 memory bug. But after SP2, now it's often on all day and night without a problem with memory. And I spend no small portion of my time troubleshooting/educating others on Max... and I've noticed that the memory bug disappeared with my clients after SP2. So if there is still a memory bug in SP2, it's probably more subtly than a 10-15 minute bogey.

Not that I'm not looking forward to some of the magic I suspect they are sprinkling into Max 2017... or even a SP3 in 2016. Just saying.