Autodesk 3ds Max
Posted by Shane Griffith, 21 August 2009 3:29 pm
The below were recently escalated items customers reported to us by Product Support. Hopefully you can see by this last year's HFs that we are serious about fixing things and not only for the lastest release. You can download the HF using one the following links, please make sure you use the one for the appropriate flavor of 3ds Max you have installed...
This hotfix addresses the following issues:
The Camera Map texture and modifier projected a bitmap behind and in front of the camera, instead of in front of the camera only.
Solution: The problem is now fixed, with the default settings (projecting to the front only). However, if you want to restore the legacy behavior (projecting in two directions), do so with MAXScript as follows:
For the texture map, both scanline and mental ray®, if the texture is applied to the diffuse slot of a Standard material on the selected object use:
$.material.diffuseMap.affectBehindCam = true
For either of the modifiers, if the modifier is at the top of the stack on the selected object use:
$.modifiers.affectBehindCam = true
Exception: For scenes using the Camera Map texture, then saved to an MI file, and rendered in mental ray standalone, there is no solution. The shader for mental ray standalone will continue projecting in two directions as before.
The internal Microsoft® Windows® messaging system in InfoCenter could make Autodesk 3ds Max 2009 / Autodesk 3ds Max Design 2009 unresponsive during CPU-intensive tasks. Autodesk 3ds Max 2009 / Autodesk 3ds Max Design 2009 is now more responsive during CPU-intensive tasks.
When encrypting a Maxscript file (encryptscript YourMaxScript.ms), the file would generate an error when executing the resulting encrypted file (YourMaxScript.mse). This error would also occur when reading from an encrypted MaxScript file. These issues are resolved.
Parameter Wire Subcontrollers
When Resetting a Scene Parameter, Wire Sub-Controllers would be removed due to the Maxscript Garbage Collection clean-up process. This only occurred when the scene was Reset or an XRef tree was deleted. It did not occur when exiting with a scene Open. This clean-up procedure was fixed for all instances of scene change states.
Please only report comments that are spam or abusive.