Feedback
|
Tell us what you think of the site. |
| Send Feedback |
Software Trials
|
Autodesk® 3ds Max®
|
|
Autodesk® Maya®
|
|
Autodesk® Softimage®
|
|
Autodesk® MotionBuilder®
|
|
Autodesk® Mudbox™
|
|
Autodesk® ImageModeler™
|
|
Autodesk® Sketchbook® Pro
|
|
Autodesk® Smoke on Mac®
|
| 2009 Hotfix Updates |
Posted: Feb 17, 2009
Category: Hotfix
Category: Hotfix
|
Social Media:
|
Recently released fix for the Undo problem.
This one proved be one of the more challenging issues to track down, mostly because of the apparently random nature of the repro case, but we think that the problem is now solved. If you are having issues with your undo stack randomly disappearing please download the latest hotfix and let us know if that solves your problems!
Hotfix â Autodesk 3ds Max 2009 â 2009.01.19
Hotfix â Autodesk 3ds Max Design 2009 â 2009.01.19
- The Garbage Collector has been modified to better manage memory. In this way, we are significantly reducing the loss of the undo stack.
The main symptom is that Undo fails and all undo history is removed (flushed). The issue seems to be affecting primarily animators but the problem does not prevents users from continuing to work (the stack continues working ok after being flushed). Certain custom maxscripts have been found to enhance this problem causing increased flushing of the stack.
Also included in this hotfix are two support escalations.
- Scenes that contain settings that require MR to log progress took much longer to render on the network.
Examples of this issue can be found when using mental ray to render shadow maps, scenes containing placeholders, SSS shaders and lightmaps. When attempting to render scenes containing any of these elements with mental ray via Backburner or with command line, render times can multiply by 5 times in some cases. The fix consisted of making sure network rendering would use the same filtering options as the "standard" rendering would allow, including the one for detailed progress logging, so that users could disable this one even when using network rendering.
- 3ds Max [Design] 2009 & Backburner 2008.1 did not work when running BB as a service on a machine with limited user account.
The issue was resolved by modifying the 3ds Max backburner plugin and this is not an issue with backburner itself. On some network configurations the InfoCenter feature does not obtain proper user permissions to initiate. The component would fail when used on machines with restricted rights, thus preventing the customer to send render jobs on their network of machines. A fix has been implemented to perform a conditional loading of the InfoCenter component, so that it would not load while using network rendering mode.
This one proved be one of the more challenging issues to track down, mostly because of the apparently random nature of the repro case, but we think that the problem is now solved. If you are having issues with your undo stack randomly disappearing please download the latest hotfix and let us know if that solves your problems!
Hotfix â Autodesk 3ds Max 2009 â 2009.01.19
Hotfix â Autodesk 3ds Max Design 2009 â 2009.01.19
- The Garbage Collector has been modified to better manage memory. In this way, we are significantly reducing the loss of the undo stack.
The main symptom is that Undo fails and all undo history is removed (flushed). The issue seems to be affecting primarily animators but the problem does not prevents users from continuing to work (the stack continues working ok after being flushed). Certain custom maxscripts have been found to enhance this problem causing increased flushing of the stack.
Also included in this hotfix are two support escalations.
- Scenes that contain settings that require MR to log progress took much longer to render on the network.
Examples of this issue can be found when using mental ray to render shadow maps, scenes containing placeholders, SSS shaders and lightmaps. When attempting to render scenes containing any of these elements with mental ray via Backburner or with command line, render times can multiply by 5 times in some cases. The fix consisted of making sure network rendering would use the same filtering options as the "standard" rendering would allow, including the one for detailed progress logging, so that users could disable this one even when using network rendering.
- 3ds Max [Design] 2009 & Backburner 2008.1 did not work when running BB as a service on a machine with limited user account.
The issue was resolved by modifying the 3ds Max backburner plugin and this is not an issue with backburner itself. On some network configurations the InfoCenter feature does not obtain proper user permissions to initiate. The component would fail when used on machines with restricted rights, thus preventing the customer to send render jobs on their network of machines. A fix has been implemented to perform a conditional loading of the InfoCenter component, so that it would not load while using network rendering mode.
