I just installed the windows version, and the UI is a lot slower than 2009.
The hotbox is slow and changing views is slow…
None of this happens on a Linux install. Pretty weird…
Maya 2011 BUGS (Write Here)
The general interface speed doesn’t seem slower to me. The hypershade takes a few seconds to open but once open seems maybe even a little quicker. The quality and features tabs in the render settings do take a second to open the first time but afterwards are instant. I don’t get the crash with changing materials in the attribute editor. Colour sliders work perfectly for me. Virtual slider works fine. Screen doesn’t go white whilst rendering, but does stop any other interaction with that session of Maya. Hotbox/marking menus are instant. Hotbox commands aren’t slow. Pressing w twice does not break the undo. Paint Effects brushes draw interactively. Viewports update straight away on switching. Mesh reduction doesn’t crash Maya.
So thats over half the bugs in here that I do not experience. Yay for hardware/driver specific bugs. All this is on Windows 7 x64 Core2Quad and gtx 260.
I will post any I do find when I get a better chance to try things out. I think there is one when converting nParticles to polygons that stops the particles from showing, but I am not sure it might just be my stupidity.
I have the same set-up (minus the CPU) as you and using ADSK qualified drivers 190.38, but I get the crash when changing materials in attribute editor. 
But all those other things work (thankfully!).
@leif3d:
can you tell something about the LINUX_version ? id like to know , if now , with QT integrated - are there still problems once using “Beryl” ( or any other of the “effects”-desktops )
do you have any recommendations about installing Linux ? i want to use Ubuntu , but i am not sure if maya works well with it .
for me , the hypershade also takes even “a little” longer now to open up than before ( especially in scenes with lots of materials and lights and utility-nodes ) - i was hoping before the 2011_release, that it would just pop up very fast now with QT , but i guess this has nothing to do with the QT_integration , and seems to be so slow , because the appropriate maya_command_task ( API_call ? ) takes soo long to check all the materials / lights / whatsoever in the scene …hopefully this is going to be fixed some day - as i cant imagine , that the entire_task of “filtering” a scene , with it’s materials or lights , would really take so long ( but maybe this entire aspect is still handled via MELscripts … maybe , i dont know ) - and with raising amounts of materials and lights - in complex scenarios - this can be somehow annoying , when you need to wait for a minute , until you can access all the lights from within the hypershade ) … and once this task is not htreaded , you cannot even “work on”
i am not sure right now , if this just happened on “referenced” material / lights , or if is just the number of elements that make maya so slow in handling materials and lights in complex sets .
another window which now takes much longer to pop up , is the SCRIPTEDITOR …
but overall - i am “with maya2011” now , as i like it a lot - as there are soo many great “small” additional-features , such as handling reference_edits . or the new “namespace-editor” seems to be a great step
next steps would be ( hopefully ) an improved lightlinking_flow as well as a big_rendering_update ( MR ) , concerning renderlayers / passes … per face_assignments of materials on renderLayers and such things in order scenes won’t screwUp once you are working on renderLayerAdjustments
a threaded “renderWindow” with full possibilities in accessing all renderpasses on the fly ( like in cinema4D ) and maybe ( one day ) “fCheck v2” ( haha )
keep up that FLOW autodesk … keep it up ! hopefully this developement is going on and on .
on Vista and Windows 7 Im finding Maya is freezing for 5-10 seconds when I tab fully across to the furthest node in the attribute editor using the arrow keys.
Its not happening on XP64, so Im wondering if its something I can disable in the newer versions of Windows.
When it freezes, if I switch to another app or window, it “unlocks” it.
XP64 here, and the same thing happens. Moving to another application and back unlocks it.
I think its a wacom issue. It doesnt happen with my mouse.
I just timed one of these “freezes” when navigating from the shader node to the shape node and back again, via the arrows on the top right of the attr editor…it froze Maya for 2 mins 7 seconds.
I tried the latest wacom driver for my intuos 4 but that driver causes all my 3d apps to crash before even fully open. Anyone else having odd 2011 + wacom problems?
Here is a quick summary of the content of this thread so far. Bug report number is included when available.
Not all the bugs reported here are experienced by everyone.
Some reported bugs weren’t included here because they lacked a simple quick description. Others weren’t included because the author stated something like “it’s not really a bug”.
And again, this list may seem long, but actually Maya 2011 is working pretty well, and will be even better if Autodesk releases a patch to resolve these issues quickly (think hotfixes for 3ds Max).
Visibility status of layers not updating correctly.
Dragging a shelf icon to another shelf sometimes deletes the content of the destination shelf.
This happens if the destination shelf wasn’t previously opened in the current Maya session.
Shelflayout doesn’t support multi row (356149).
All scripts including shelflayouts are broken and now display icons in a single row.
JPEG images saved from the Render panel have bad pixel aspect ratio (355435).
Import options missing from OS native dialogs (355066).
Mesh reduction crashes Maya (354954).
UI MEL scripts that simply fail in 2010 crash 2011 (352066).
Running slow commands from the hotbox prevents interaction with the entire OS UI or applications.
Some buckets rendering brighter than others.
Maya’s Qt dialog doesn’t recognize Application bundles on OS X.
So you can’t pick Photoshop without digging into it and finding the binary files.
Quick switching between two panel submenus crashes Maya.
Viewport 2 slower on Nvidia cards on OS X.
(Nvidia’s problem).
Stuff disappears all around in viewport 2.
JPG image format no longer renders in maya software render.
Playblast always outputs at 24 fps, ignoring the fps setting (356150 and 356185).
Subprocess module bug with file objects (356116).
Autodesk modified the subprocess module without making a note in the docs. subprocess PIPE’s no longer return a valid new-style file object
Error with scene modified state (356148).
setting the scene’s modified state via file -e -mf false; still does not work correctly on an unsaved scene.
Mip_rayswitch_advanced causes fatal error (356153).
Floating windows stay on top of every other windows, even when switching to a different application.
While using the move tool press W key twice by keyboard or mouse: this will break undo. Same with rotate.
Not experienced by everyone.
Changing material or light type in attribute editor = crash.
Only if the AE is not docked (i.e. floating). Not experienced by everyone.
Nonstandard resolution Shelf icons not resizing correctly after Maya restart.
Render settings window : first time switching to the “Quality” and “Features” tabs is slow.
Interactive Skin Binding tool window doesn’t list Influences correctly (356224).
Drawing with Paint Effects : no update as you paint, only when the stroke is finished (LMB released).
Not experienced by everyone.
As always when finding a bug, try to reproduce it using a fresh set of Maya preferences and the recommended graphics card drivers.
Report it to Autodesk using the “Report a problem” feature and publish the bug number here, so that others can refer to it when communicating with autodesk.
When reporting here, specify your OS / graphics card setup.
global proc closeMe(string $win)
{deleteUI $win;}
if (`window -exists Window1`)deleteUI Window1;
window Window1;
formLayout;
textScrollList -numberOfRows 8 -doubleClickCommand "closeMe(\"Window1\")"
-append "Double Click me to Destroy Whole Maya";
showWindow Window1;
deleteUI destroys whole [color=blue]Maya[/color] .if called by double clicking command in a textScrollListItem
thread is focused for bugs.not code styles.
so : here Window defined as a string as you like it. but still crasH ~½½%~!’
global proc closeMe(string $win)
{
deleteUI $win;
print "HelloOO";
}
$mywin=`window Window1`;
formLayout;
textScrollList -numberOfRows 8 -doubleClickCommand "closeMe($mywin)"
-append "Double Click me to Destroy Whole Maya";
showWindow Window1;
happens absolutely random. ( not in all the scenes… but happened a few times here at work. )
im using Vista 64 here… all Drivers Up to date.
and yeah, it did hapen with everything new. i testet it up at work on our “test drive for Softwares” PC… so it was a just born maya in sort of way. 
Thank you Shawn for logging the bugs, or for verifying that they were already logged!
Changing material or light type in attribute editor = crash.
Got that one too, plus:
- create polyCube
- create nurbsPlane
- create omni light - turn on raytraced shadows
- attach shelf fur preset to cube… (Punk)
- open render window
- start an ipr session
- open render settings and create a physical sun sky
- go to the render menu, launch the option dialog for IPR render current frame
- turn off render on local machines, change task size and auto render threads
- hit Start IPR…
- crash…
Don’t know if this is a bug, but in the hotbox you use to be able to click-drag and scroll through the top menus. You know have to re-click for every menu.
Suddenly in mu pers view I can’t access View.
Need to restart Maya to have access again.
Maya 2011 doc:The mia_material_x_passes shader now provides support for additional
render passes such as: Diffuse Without Shadows
when tested in a simple scene(some primitives on a poly plane floor) with all the objects
assigned to mia x passes shaders, the “diffuse without shadows” pass showed hard
shadows on the floor. However, any objects with transparency higher than 0.005 casted no
shadow over that pass. Changed the material of the floor to a blinn, all the cast shadows
disappeared as expected.
Just a reminder - if you get the CER (Customer Error Report) Window coming up, please send it in to help us track down the problem.
Thanks,
Cory
Is there a way to send in the CER from an offline workstation? For example, can I zip up some log files and email them somewhere?