• 1/2

3ds Max 2012 Service Pack details

Posted by Ken Pimentel, 16 May 2011 8:00 pm

At the risk of giving you too much information, here is the planned list of things we're fixing in the first Service Pack, which is roughly planned for mid-June. Internally, we're starting an extensive testing process to make sure these fixes don't destabilize other areas of the code.

The point of giving you this information is to see if we're addressing your chief pain points. This is the largest Service Pack we've done in a long time - mainly because we're responding to your concerns. We're simply grabbing fixes that might have shown up later and we're aggressively pushing them forwards. Remember, 3ds Max 2012 shipped with over 400 legacy fixes by itself - which was a major increase in the number of legacy fixes. We take quality seriously which is why we're trying to get as much information out to you as possible. Some of the fixes in SP1 are legacy, but most are related to Nitrous and CAT - two major areas of focus for us right now.

There are many other things we're still working on (Nitrous animation performance, pflow, etc.) that are not necessarily in this list, so don't assume that we're ignoring these issues. This is basically the list of known, reproducible bugs that we also have a handle on fixing in a short period of time. This is one of the largest SPs we've done, but that is mostly because of the new CAT core we're introducing and the impact of Nitrous on the code base. The goal is to be transparent and responsive because there will always be problems of one form or another. I'd say we're pretty damn responsive with a Hot Fix available 1 month after ship and the Service Pack 2 months after ship - faster than we've ever done these things.

The fact is that every sw product ships with bugs. Some bite more people than others. We're just being very transparent with the situation in the hopes that it helps people understand what is going on. I would not confuse this transparency with the lack of transparency in the past. Yes, the list is long, but CAT responsible for a lot of them - which as I've mentioned a few times, is because we're issuing a new CAT core that simply didn't make the release. Nitrous has been underway for a couple years now, but it is so large that at some point we had to put it out there and then identify any and all limitations so that we could better understand what people needed. We left in the DX9 legacy driver to protect you from any "surprises". Yes, you can say that Nitrous and CAT were "unfinished", but we had a fallback in one case and the other was simply an unpredictable situation we had to deal with.

Anyway, it would be a shame if people just look at the list and say - "ooh what a lot of bugs". It would suggest that the transparency might not really be an effective tool. Better to just wait for the SP to ship and then tell you about it. This is an experiment on our end.

Please realize these are bug notes from our QE team and I do not have further information on them. If you think we're missing a "showstopper" we want to know about it. The SP will have all the fixes from the Hot Fix we just released - so you might see duplication there.

  1. 3dsmax.mat library missing from installer
  2. Bad wording in MassFX Dialog
  3. CAT: CAT inherit Position/Rotation is incorrect when creating absolute layer ( incorrect 90 degree offset,)
  4. CAT: CAT with motion layer added to container will crash
  5. CAT: changing rig structure crashes max
  6. CAT: Cloning rig elements could crash
  7. CAT: Collarbone rotations are inherited (by the arm bone) incorrectly in SetupMode
  8. CAT: Crash cloning CAT parent with motion layer that rt click cancelling
  9. CAT: Crash loading 2010 scene
  10. CAT: Crash undoing animation
  11. CAT: CRASH undoing with trackview open and motion layer
  12. CAT: Crash when working with a leg with no palm/ankle
  13. CAT: Digit issues: Crash undoing num digits change, digits width/depth scale per seg (not per-digit)
  14. CAT: Extra node interface is not available from the CATParentTrans
  15. CAT: Globals track view button freezes zelda
  16. CAT: Having transform gizmo active in Nitrous caused CAT motion panel ui to strobe
  17. CAT: Improve CAT Notification system
  18. CAT: Improve CAT Notification system: Mirrorring of saved pose causes rig to mess up
  19. CAT: NITROUS: Custom Foot roll rig hangs 3dsmax in Nitrous display
  20. CAT: Old rig files with segmented limb bones have the 2nd bone parented to the wrong segment
  21. CAT: Pin Bone doesn't work anymore.
  22. CAT: Quick exit crash with container workflow
  23. CAT: Quick exit no CER when click on create cat parent button
  24. CAT: Reset after using a motion layer path node leaves the foot flatforms behind in new scene
  25. CAT: rg3 file will keep the same hierarchy name for the bones
  26. CAT: RG3 rigs will not reload with a motion layer assigned.
  27. CAT: Right click canceling after shift cloning doesn't restore previous state and now CRASHES
  28. CAT: Saving clips does not save out controller types for position/rotation when not animated
  29. CAT: Set IK to max with ABS layers rotates wrist
  30. CAT: Skin problems with maramma facial rig
  31. CAT: Skin weight problems in Marine preset
  32. CAT: Stretchy issues
  33. CAT: Tail and Spine issues
  34. CAT: Toes are moving when rotated
  35. CAT: Twisty limbs solved incorrectly for palms
  36. CAT: Upper arm and Collar bone setup stretch issue
  37. CAT: When loading a new motion layer in cat motion editor, momentary disjointing of limbs before refresh
  38. CAT: Capture animation Retargeting utility fails with maxscript error
  39. CLONE - Ribbon - Error Parsing XAML file on startup
  40. Communications Info Center will not show infoballoon notifications until user opens settings dialog
  41. CRASH WITH INVALID OR EMPTY LOFT OBJECTS
  42. CRASH WITH SET KEY/AUTO KEY FOR MODIFIERS WHEN GHOSTING IN VIEWPORT IS ENABLED
  43. CRASH WITH UNWRAP UVW
  44. CRASH: LOAD ILLUMINATION_ASHIKHMIN_SHIRLEY.XMSL WITH QUICKSILVER ACTIVE.
  45. DOES NOT RESPECT FILE PARAMETER VALUES LOADING XMSLS. (RELIC)
  46. Download Vegetation link in Help menu doesn't go to correct webpage
  47. Environment Map (background) is black on 4870 + XP 32-bit.
  48. GRID VALUE NOT DISPLAYING CORRECTLY (STATUS BAR IS NOT UPDATED.)
  49. ISOLATE SELECTION" DOES NOT HIDE XREF'D SCENES
  50. MEMORY LEAK: LOADING FILES WITH SHADED ARCH & DESIGN MATERIAL + LARGE BITMAP.
  51. mr Physical Sky/mr Photographic Exposure Control is not updated immediately.
  52. Nitrous: "OBJECT COLOR" DISPLAY SWITCH DOESN'T WORK
  53. Nitrous: ALL OBJECTS SHOW EDGES WHEN SHOW GHOSTING IS ENABLED
  54. Nitrous: ANIMATED DEFORMED MESH STOP TO UPDATE WHEN PARTS OF RIG HIERARCHY HIDDEN
  55. Nitrous: APPLY TO ALL VIEWS FUNCTION NOT WORKING WITH STYLIZED RENDERING METHOD
  56. Nitrous: APPLYING HIGHLIGHT WITH INK 'N PAINT TURNS OBJECT BLACK
  57. Nitrous: Applying Unwrap UVW to the object corrupts 2D View in Viewport Canvas
  58. Nitrous: Autodesk Metallic Paint material doesn't work
  59. Nitrous: Benchmark: Bounding Box 5.5k is about 40% slower under Nitrous.
  60. Nitrous: BLACK BACKGROUND WHEN TONE MAPPING ENABLED WITH MR PHYSICAL SKY ASSIGNED BUT NOT ENABLED IN VIEWPORT
  61. Nitrous: CAN'T HIDE TARGET GIZMO
  62. Nitrous: CIVILVIEW: CRASH WHEN MODIFYING SURFACE PARAMETERS
  63. Nitrous: COMPLETE PROGRESSIVE RENDERING REDRAW NOT DONE AFTER UNHIDING EDITABLE SUBOBJECTS
  64. Nitrous: CUSTOM SAMPLE OBJECT IN CME APPEARS IN VIEWPORTS
  65. Nitrous: DEFAULT LIGHT DIRECTION IN ORTHOGRAPHIC VIEWS IS SUPPOSED TO BE SLIGHTLY OFFSET TO UPPER-RIGHT.
  66. Nitrous: DEFORMING MESHES + GHOSTING = KILLS NITROUS ,  CRASHES MAX
  67. Nitrous: DOF FLICKER IN QUICKSILVER
  68. Nitrous: EDGES OF SELECTED POLYS WILL NOT BE DISPLAYED
  69. Nitrous: Editable Poly > Edit Triangulation/Turn: No dotted triangle line.
  70. Nitrous: Environment Map still appears in viewport after Use Environment Map disabled
  71. Nitrous: EXTENDED VIEWPORTS CAUSE LACK OF PROPER REDRAW (FLASHING BETWEEN VIEWPORT POV SETTINGS)
  72. Nitrous: HIDE FROZEN OBJECTS CHECKBOX IN THE DISPLAY PANEL DOES NOT WORK PROPERLY IN NITROUS.
  73. Nitrous: LIGHTING FROM SHAPE LIGHTS LEAVE ARTIFACTS IN VIEWPORT WHEN CLOSE TO GEOMETRY
  74. Nitrous: LOST DEVICE AFTER COMPUTER LOCK
  75. Nitrous: MIRRORED OR NEGATIVELY SCALED OBJECTS HAVE WRONG EDGE DISPLAY
  76. Nitrous: No backface. It is transparent
  77. Nitrous: PERFORMANCE SLOW WITH LARGE POLY OBJECT.
  78. Nitrous: PREVIEW SELECTION NOT WORKING WITH POLY
  79. Nitrous: SELECTION WINDOW OUTLINE IS DRAWN ON ACTIVE GRID INSTEAD OF IN FRONT OF ALL OBJECTS
  80. Nitrous: SHADE FACE TOGGLE - SOFT SELECTION BROKEN WITH NITROUS WITH VERTICES
  81. Nitrous: SHADED MODE ISSUE (OBJECTS DISPLAYED IN VIEWPORT FROM PREVIOUS SCENE UNTIL RESTART)
  82. Nitrous: Shell Material: Maps are not shown in viewport.
  83. Nitrous: SHOW NORMAL IN EDIT MESH NOT WORKING
  84. Nitrous: STATUS NOT ACCURATE IN VIEWPORT MENU FOR DEFAULT LIGHT/SCENE LIGHT WITH CONSISTENT COLORS AND HIDDEN LINE
  85. Nitrous: UNSELECTING AN HIDDEN EGDE IN EDIT MESH SHOWS BACKGROUND
  86. Nitrous: Use NURMS Subdivision for imported FBX causes crash
  87. Nitrous: VERTEX CHANNEL DISPLAY DOES NOT SHOW CORRECT INITIAL COLOR
  88. Nitrous: VIEWPORT BACKGROUND TOGGLES OFF IN WIREFRAME OR BOUNDING BOX MODES
  89. Nitrous: VIEWPORT BACKGROUND TURNS BLACK AND FLICKERS IN WIREFRAME OR BOUNDING BOX MODES
  90. Nitrous: VIEWPORT LAYOUT CHANGES TO THE VIEWPORT SIZE SCALES OBJECTS IN VIEWPORT
  91. Nitrous: VIEWPORT MENU COMMAND FOR DEFAULT LIGHT/SCENE LIGHT SWITCH FOR CONSISTENT COLORS AND HIDDEN LINE ARE NOT AVAILBLE
  92. Nitrous: VIEWPORTS BACKGROUND DOESN'T FIT WITH SAFE FRAME
  93. Nitrous: WHEN USING THE MIRROR TOOL ,  ORIGINAL OBJECT WILL APPEAR WITH NORMAL FLIPPED IN VIEWPORT WHEN CERTAIN MATERIALS ARE APPLIED TO IT.
  94. NODEEVENTSYSTEM DOES NOT SEND NODE ADDED MESSAGES
  95. Normal flip issue with mirror object
  96. ONLY THE FIRST LIGHT WORKS FOR DIRECTX SHADER MATERIAL.
  97. PLAY SELECTED OPTION PLAYS ALL
  98. QUICKSILVER: OVEREXPOSURE WITH MR DAYLIGHT SYSTEM
  99. Realistic Material: Issues with Coordinates (2D) rollout > Angle.
  100. Realistic Material: Too much blurred due to Coordinates rollout > Blur.
  101. RENDER REGION IS NOT RESPECTED
  102. SELECTION WINDOWS NOT WORKING CONSISTENTLY WITH NITROUS DRIVER
  103. SWITCHING FROM MOVE TO SCALE OR ROTATE DOES NOT PROPERLY CHANGE TRANSFORM TYPE GIZMO DISPLAY ON ALL VIEWPORTS
  104. Tessellated geometry with Edit Poly modifier and Unwrap UVW crashes max
  105. Uniform scale in UVW Unwrap editor needs few adjustments
  106. UVs: Peel causes faces to become unhidden when using "Display Only Selected Faces"
  107. UVW Unwrap editor is extremely slow
  108. Viewport Canvas doesn't work with Composite Material / Product Experience Issues: Autodesk 3ds Max linked

47 Comments

Altis1

Posted 16 May 2011 7:25 pm

Damn. That is a lot of fixes. Glad to see no. 76 in there.

timd1971

Posted 16 May 2011 7:41 pm

CAT... should've been called CAT SH*T at release.

yup...that sure is a LOT of fixes for a full blown release. hmm? :S

Ken Pimentel

Posted 16 May 2011 7:48 pm

CAT as shipped in 2012 was no different than CAT in 2011. We were unable to stabilize our CAT rewrite prior to shipping 2012. It did not make sense to hold up the ship date to include the new CAT core as that would prevent many from using the non-CAT features of the release.

We inherited CAT from an acquisition, we did not originate it. We are doing our best to make the most of the situation and we think users will be delighted by the new CAT core.

Companioncube

Posted 16 May 2011 8:27 pm

thnanks for the info ken

Mark Evans

Posted 17 May 2011 12:52 am

Thank you for the update Ken. I look forward to the SP.

timd1971

Posted 17 May 2011 4:54 am

just curious... in the terms of software development, to take quality seriously, is it typical to have over 500 serious "show stopping" bugs in a release that is "supposed" to be ready for "prime time"? Just curious is all... maybe this is the norm for 3D applications since they seem to be loaded with so much more than "typical" graphics software.

Rawalanche

Posted 17 May 2011 7:36 am

Still no fix for slow Mental Ray Yippie!

moulder6

Posted 17 May 2011 10:31 am

Thanks, Ken! Sharing is nice Now let's see if they are all really fixed with the SP

Ken Pimentel

Posted 17 May 2011 2:34 pm

What is blocking you from using it? The majority of people can use 2012. You'll get the SP1 in a month, 2 months after ship, so you have 10 months plus the fact you're unlikely to adopt any future release on day 1. Sounds like you've got 11-12 months of usage ahead of you.

You've got to differentiate between transparency (us telling you about bugs) and being opaque on the subject. Perhaps you're better off not knowing about bugs and then you can proceed as you have in the past. All the CAT bugs are in 2011, all the Nitrous bugs can be avoided by using DX9 legacy. We shipped a Hot Fix that fixes a bunch of the rest in that list.

SuperCoon

Posted 17 May 2011 2:47 pm

"You've got to differentiate between transparency (us telling you about bugs) and being opaque on the subject. Perhaps you're better off not knowing about bugs and then you can proceed as you have in the past."

I end up on a yearly basis waiting on a release to be stable enough to transfer my workload too, so I'm already proceeding on a normal basis. Additionally, your transparency is appreciated; however, being opaque is pretty much impossible for AD upon install of a new release - that's my point. Here is a thought for you: Instead of me proceeding as I have in the past, why don't y'all not proceed as you have in the past and give me a working release for a full 12 months.


SuperCoon

Posted 17 May 2011 2:53 pm

You know Ken I'm not trying to be rude, and I surly don't mean to sound that way, so please forgive me if I seem a little out of line - I'm just frustrated because 2012 (as other past new release) is still on the shelf.

MikeMS

Posted 17 May 2011 2:58 pm

Always glad to hear about bugfixes! Thanks for transparent and operative work!
P.S.: I often use Reaction Manager for animation purposes and its very annoying - when typing number values in it and for proper updete of numbers I must click on anather line... this is very old window update bug.

PiXeL_MoNKeY

Posted 17 May 2011 4:56 pm

Unfortunately the problem isn't Autodesk it is similar with other products from other vendors. Cinema4D is on a 12 month .5 paid update cycle (12-24 month cycle depending on how you interpret it), yet released their 3rd update since September of last year. Their 3rd release includes over 100 fixes, release info here:
http://www.maxon.net/downloads/updates/cinema-4d-r12/r12043-important-notes.html
Unlike this list it doesn't appear their list is cumulative. So it is hard to believe that the problem is just Autodesk as others are doing the same, with similar or longer periods of time. Most other packages are also on 12 month or subscription programs (from what I could find), but not all make their update information available so can't really add their information here.

Unfortunately it appears some are having different experiences with the release(s). While others appear to wait for the community to say it is good, or out of fear of issues, before trying it themselves. This leads to the problem of what is proper definition of "ready". I would love to hear what some real metrics you expect to be used to define the improved or stable state of the application. The fixed a large amount of legacy issues, and did do beta surveys (though the numbers in those appear to be really small compared to the actual beta user numbers). So again what are some real world development metrics that should be used? That means not your opinion but "x" amount of fixes, "x" amount of features added, "x" amount of beta tester survey results, "x" amount of decreased CER data retrieved during testing, etc. By real world I don't mean 100% this needs to be an obtainable value that they could actually target. I am all for making the experience better for everyone, but some of the current requests don't provide a valid obtainable option, just user perception of what might make it better.

Ken I hope this transparency carries over to release information as well. With getting information about what has really changed and not letting the community find it out themselves.

-Eric

Ken Pimentel

Posted 17 May 2011 5:09 pm

Complex sw will always ship with bugs, if you don't think this is the case, then you simply haven't tried enough complex sw. We held back some fixes because we were worried about the risks of shipping them and the beta warned us it will be a problem. It was, and we shipped the fixes as a Hot Fix within a month. Yes, we should have had the HF ready to go on the day of ship, but we didn't.

Overall, the 2012 release is solid. There are many more people happily using it than there are people struggling with it. It is very unfortunate if you're one of the strugglers, but we have a SP coming in a month. I think this is about as responsive and open as any sw company I know of.

SuperCoon

Posted 17 May 2011 5:32 pm

I guess that's were the problem is, we both seem to think the other one is struggling.

ctedin1

Posted 17 May 2011 9:25 pm

Yes, thanks for the transparency. +1 vote for lots of that. Nice to see my particular problems are being addressed and I can look for workarounds until the Service Pack is up. Mainly in CAT, which is a shame, since it shows lots of promise. Nice to hear that the core is being worked on, and that they are investing in the future of CAT.

oguzbir

Posted 17 May 2011 9:40 pm

I would like to add that Standard Camera preview for DoF and Motion Blur does not work with the nitrous.
or is it just me..
?
Anyway..

jeffreysbrown

Posted 17 May 2011 10:09 pm

I pleased to see this effort at improving transparency. At the least, it should give reassurance to those experiencing bugs -- or alert them to notify the team that an issue might have been missed. To paraphrase Jaron Lanier: It's easy to write a small program that is bug-free. It is _impossible_ to create a large system that is bug-free. But good to have notice that Autodesk is striving for the impossible ;>)

-Jeff B.

phloog

Posted 18 May 2011 12:18 am

CAT fixes rule...no complaints here...prefer to see the glass half full of fixes

Ken Pimentel

Posted 18 May 2011 2:58 am

Don't forget, post feature requests in one of the new uservoice forums: http://autodesk.uservoice.com/forums/76763-smallannoyingthings

Bugs are things that don't work as documented. Everything else is a feature.

spacefrog

Posted 18 May 2011 5:42 am

@AndyMurdock:

AFAK the list above ist the one they target for the Servicepack. Currently only a hotfix isreleased, which covers a subset of this list, as far i can see...


Kristoffer Helander

Posted 18 May 2011 8:53 am

I love how open to the community Autodesk have become with sharing things like this and listening to what users have to say; it is great. Sure, there are bugs but what software does not have bugs?! I love CAT and the Nitrous so I'm looking forward to the SP!

Gothmoth

Posted 18 May 2011 11:47 am

i say:

next time take the extra month and do a proper beta test so that you don´t need to give US a hotfix after one month... and AD a bad reputation for releasing buggy software.

Ken Pimentel

Posted 18 May 2011 11:52 am

re: Gothmoth
That would not have made much of a difference. We had a proper beta test and the results of that suggested our quality was better than the prior release. The beta users knew that a) CAT was an issue; b) Nitrous wasn't quite "all there" yet. Yes, if we had delayed a month, the HF fixes would have been picked up, so less clamor/angst. The problem is that 3ds Max is in over 18 other suites that Autodesk ships, so slipping max is not really an option.

lo_

Posted 18 May 2011 11:54 am

Aside from bug fixes, are there any features/additions planned for the service pack? (this is not a complaint or demand, just a question)

Ken Pimentel

Posted 18 May 2011 12:01 pm

re: features
Can NEVER be part of a service pack or hot fix. That is one of the rules we live by across Autodesk.

Samab

Posted 18 May 2011 12:07 pm

"Aside from bug fixes, are there any features/additions planned for the service pack?"

You don't get new features in SPs and HFs, just fixes.
If you are on Subscription, you can get new features between major releases in the form of SAPs (Subscription Advantage Packs), I have no idea if, or when, or what will be in them. Ken may have a better idea about that, but I don't expect he will tell us just yet.

"next time take the extra month and do a proper beta test so that you don´t need to give US a hotfix after one month... and AD a bad reputation for releasing buggy software."

You effectivly get that if you do as I have and keep using 2011 untill the fixes come. Delaying the release would stop those who are happy to use it as is now.

im.thatoneguy

Posted 18 May 2011 3:59 pm

2 show stoppers that are causing me a lot of trouble:

fn badfunction = (for i = 1 to 10 do return i) returns an error. This is killing a lot of scripts and is a regression.

Also the multi-pass DOF no longer works.

Ken Pimentel

Posted 18 May 2011 4:10 pm

log the problems, that is the only way they'll get fixed: http://www.autodesk.com/3dsmax-defectsubmission

André Holzmeister

Posted 19 May 2011 3:03 am

Since max 2011, and still in max 2012, when you try to right click to set path in Asset Tracking freezes max for a while. It is very annoying to fix many paths when you are working on a network!

André Holzmeister

Posted 19 May 2011 3:09 am

when you link to an object it no longer highlights the parent anymore, so max leaves you with no clue if you got the link to the right object, only way to be sure is to select the parent and move it or to see the hierarchy tree...

André Holzmeister

Posted 19 May 2011 3:41 am

This is not a bug, but when will Max team create a decent skin modifier? the one we have has so many issues with influence painting that it is better not to use this feature, it does not work properly... and what is worse, when you hide a skinned model it still slows your viewport.... skin does it, skin wrap does it... this technology is very bad, slow and you should update this, please. We are suffering from this since the first skin modifier release... do you guys hate us?

timd1971

Posted 19 May 2011 4:58 am

109. Gradient Ramp and Falloff (possibly Gradient) environment maps are not working correctly in Nitrous, viewport and renders. QC FAIL.

marcatore

Posted 19 May 2011 8:40 am

and what about backburner??

Any fix?
it's not problem proof as previous version.

Ruff-Stuff

Posted 22 May 2011 10:03 pm

CAT crashes when xrrfed

im.thatoneguy

Posted 24 May 2011 12:43 am

That bug submission form could be dramatically improved:

1) It needs to remember our contact information/system setup (otherwise even a prolific bug reporter like me isn't willing to sit there for 10 minutes entering in my Video Card etc even for non-video issues).
2) Most studio artists don't have a clue what their serial number is.

Ken Pimentel

Posted 24 May 2011 12:46 am

we are working on improving the bug submission form as we speak, I agree it sucks and you shouldn't have to put up with it much longer.

im.thatoneguy

Posted 24 May 2011 2:24 am

Great! Hopefully that'll encourage more people to participate.

The 'Autodesk Customer Feedback Program' system's bug report system is by and large pretty good.

Wurzelsepp2000

Posted 24 May 2011 9:54 am

Another CAT problem:

If I use "apply Max IK" for example the spline IK for tails.
Most of the time I get an error or warning if I reload the
scene file. I get a
"Missing Dlls" warning with the following issues:
FileName: Scripted Plugin Class: applymaxIKCADef SuperClass: 0x1160

and sometimes this:
MAXScript Scripted Custom Attribute definition loading Exception
-- Compile error: Undeclared variable: slider
-- In line: slider s


Isn´t it possible to load up a screenshot here? ;-)

Btw: I´m "Max 2012 Design eng" as a commercial version with win7 (64bit) AND
"Max 2012 Design eng" as an educational version with win7 (64bit)

Cheers

Ken Pimentel

Posted 24 May 2011 1:57 pm

CAT fixes are going into the Service Pack for 3ds Max/Design 2012 in June. Check out my blog posting on that subject. I do not believe this will go into 3ds Max 2011 at this time.

Samab

Posted 24 May 2011 2:09 pm

People have been asking about the new CAT core and Max 2011
http://area.autodesk.com/forum/t56106
I'm sure some would appreciate another 2011 SP with the CAT fixes, though you said there would not be one.

timd1971

Posted 1 June 2011 1:51 am

the Maya team always seems to be on the ball just a little bet better?
http://area.autodesk.com/blogs/cory/maya_2012_hotfix_2_now_available

nice how they actually tag the splash screen with what version of the hotfix has been installed... i know max usually will have a tag of the SP in the splash screen...but wonder if it will this time? When it doesn't, kinda leaves ya wondering?

Aaron F. Ross

Posted 5 June 2011 6:17 pm

Transparency is good. Keeping users in the loop is good. Autodesk has nothing to lose, and everything to gain, by fostering goodwill in the community.

timd1971

Posted 14 June 2011 4:40 pm

anyday now! : )

Ken Pimentel

Posted 14 June 2011 6:13 pm

It's in testing, found some side effects, team is deciding if we go forwards or respin.

lo_

Posted 14 June 2011 6:30 pm

for the love of god, respin!

timd1971

Posted 15 June 2011 3:12 am

Spend a little more time please, and release a better solution instead of a half ass one. Already in possession of somewhat half ass solution which helps some, but need a prime time solution please.

If u feel releasing will help in much needed areas, then release and expect the usual complaints. Then follow up with another SP or hotfix, then another better refined SP. U know, how the quickly responsive Maya team is doing.

Add Your Comment

You must be logged in to post a comment.

Please only report comments that are spam or abusive.