Maya 2011 BUGS (Write Here)

[xDreamer]

Changing viewport Background gradient color in default or High Quality mode does not affect Viewport 2.0 Background color.

WinXP x64

Can someone please confirm this !

[cgbeige]

ya, that’s a known issue.

[cgbeige]

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?

On OS X, all the files for the CER are in one place. If you check your crash log in Console.app, they are in a subfolder. You can zip those up and send them in a bug report.

I run this aliased command to find the saved crash file

cat /var/log/system.log | grep “Fatal Error”

and then open the directory:

http://grab.by/3I0o

and the files are all there:

http://grab.by/3I0C

If you can find the crash directory on Windows, they’d be there too.

[mikethomson]

Logged another one with Autodesk:

356239 render layer override orange text going grey when not in the attribute editor

This is in WinXP64. works fine on OSX.

[Duncan]

…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.

We now enable “intermediateObject” on the particle shape when converting to poly, so that only the mesh renders, not the particles. (you can simply turn intermediateObject off to get the old behavior). The new behavior interprets the particle system as construction history for the mesh.

Duncan

[Hamburger]

With the old color picker you could select a colour and right click to save it. The new color picker doesn’t want to do this anymore. Is this a bug or “new functionality”.

However it will save it if you close the window and open it again.

[cgbeige]

ya, the new colour picker just slots your picked colour into the first slot and moves over the last selected one.

[rock]

I am not sure you can classify this as a bug, but I find the the Maya 2011 Hypershade workarea font is too small. Does anyone see the same thing?

[Hamburger]

ya, the new colour picker just slots your picked colour into the first slot and moves over the last selected one.

Thanks for clearing it up Dave. Personally I prefer the old way but whatever.

[Hamburger]

Not a 2011 specific error but this one annoys me to no end.

1 Create a cube.
2 Instance it
3 Create a Lambert
4 Rename it Lambert2_name, change colour whatever
5 Assign it to both cubes
6 Open attribute editor’s Material Tab
7 Scroll down to the Hardware Texturing Rollout

Maya will say // Error: Found no attribute match for “lambert2.color”

The only way to fix this error is to reset the scene or close Maya. This has existed for a long time…

356316 Hardware Texture tab not found

[joit]

Hi,
Maya crashes all the time when I use mia_photometric_light in a “production scene”. It works fine in a simple scene with only a box and 1 light. If there is no workaround, there is no use of mia_photometric_light.

WinXP 64

[MarieJeanne]

Quick switching between two panel submenus crashes Maya.

Confirmed on Mac OSX 64 bit. We’re looking into it. Logged as 350487.

Thanks,
MJ

[stussy]

hi, the color chooser doesn’t work correctly on my machine. I can choose colors by using the wheel but I don’t see the values, nor I can type them in manually?? In the Channel Box I can see the values. :banghead: what a start

cheers

stussy

W7 x64, GTX260 latest dirver

[cgbeige]

is anyone able to render from the command line? I’m just getting a mess of library crap in the terminal and it’s not doing anything.

Starting "/Applications/Autodesk/maya2011/Maya.app/Contents/bin/maya"

[2010/Apr/13|20:37:33] V-Ray: V-Ray for Maya version 1.50.00 from Apr 13 2010, 07:30:22
[2010/Apr/13|20:37:33] V-Ray: V-Ray core version is 1.90.03
QWidget: Cannot create a QWidget when no GUI is being used
Stack trace:
  4   libSystem.B.dylib                   0x00007fff81503886 __kill + 10
  5   QtCore                              0x0000000104a2ef05 qt_message_output(QtMsgType, char const*) + 117
  6   QtCore                              0x0000000104a2fa43 qFatal(char const*, ...) + 243
  7   QtGui                               0x0000000104d42dcc QWidgetPrivate::init(QWidget*, QFlags<Qt::WindowType>) + 764
  8   QtGui                               0x0000000104d430d4 QWidget::QWidget(QWidget*, QFlags<Qt::WindowType>) + 132
  9   QtGui                               0x0000000104cb5c39 QDesktopWidget::QDesktopWidget() + 41
  10  QtGui                               0x0000000104cf56db QApplication::desktop() + 59
  11  libvray.dylib                       0x00000001275cc7f3 DLLApp::createGUI(void*) + 67
  12  libvray.dylib                       0x0000000127654395 VUtils::vrayInit(int, GUIHandler*) + 69
  13  vrayformaya.bundle                  0x0000000126e3e8dd initializePlugin(MObject) + 9581
  14  libOpenMaya.dylib                   0x00000001269fc957 Tplugin::primaryLoad(Tstring const&, Tstring*) + 743
  15  libOpenMaya.dylib                   0x00000001269fcd32 Tplugin::load(Tstring const&, Tstring*) + 34
  16  libOpenMaya.dylib                   0x0000000126a4e6b9 TloadPluginAction::loadPlugin(TfilePath const&, Tstring const&, bool, Tstring&) + 2217
  17  libOpenMaya.dylib                   0x0000000126a4f9c1 TloadPluginAction::execute(TargList&) + 3553
  18  libOpenMaya.dylib                   0x0000000126a501ae TloadPluginAction::doCommand(TargList&) + 14
  19  libCommandEngine.dylib              0x0000000100aa9279 Mel_Command_Dispatch(SphNode*) + 329
  20  libCommandEngine.dylib              0x0000000100ad28b4 node_exec + 100
  21  libCommandEngine.dylib              0x0000000100af8488 f_catch + 40
  22  libCommandEngine.dylib              0x0000000100acc1d9 f_not + 25
  23  libCommandEngine.dylib              0x0000000100af78e4 fc_if + 36
  24  libCommandEngine.dylib              0x0000000100ad28b4 node_exec + 100
  25  libCommandEngine.dylib              0x0000000100af7af2 fc_ifelse + 242
  26  libCommandEngine.dylib              0x0000000100ad28b4 node_exec + 100
  27  libCommandEngine.dylib              0x0000000100af96a5 f_function_entry_node + 2357
  28  libCommandEngine.dylib              0x0000000100ad28b4 node_exec + 100
  29  libCommandEngine.dylib              0x0000000100ad2afd sophia_call_executable + 109
  30  libCommandEngine.dylib              0x0000000100af55fb SophiaExecutable::evaluate(void*) + 107
  31  libCommandEngine.dylib              0x0000000100ab03c9 TcommandEngine::executeCommand(Tstring const&, bool, bool, TmelCmdResult*, unsigned int) + 1369
  32  libExtensionLayer.dylib             0x00000001012bffa2 TscriptAction::execute(Tevent const&, TinterpreterResult**) + 1170
  33  libExtensionLayer.dylib             0x00000001012c005b TscriptAction::doIt(Tevent const&) + 11

edit - so it seems this is a problem with the V-Ray plug-in. I’ll tell them.

[InfernalDarkness]

In Windows it is the worst Screen goes to white blank if you do something and after that you can’t do anything until rendering is finished. It’s been like that since the very beginning of MR.

I wonder how on earth they could not fix that? V-Ray for Maya works fine without render time “white freezes”.

Haven’t had that issue since Maya 8. Are you saying it’s BACK in 2011?

[Hamburger]

V-Ray for Maya works fine without render time “white freezes”.

Not anymore, as cgbeige points out it’s worse in 2011. 2010 you could still model, hypershade around and some other things will still rendering. It’s not really possible anymore.

Also, I have noticed when using the hotbox and archiving of a scene it will freeze the entire operating system. If you do a heavy operation via the hotbox it will steal focus from other apps and you can’t do anything until the operation finishes.

[hombrezoo]

I found something odd, wonder if anyone had the same issue.
I had originaly mapped all my hotkeys and I updated them to the new version, and some of my personal hotkeys now have a double function, and activate something else besides doing what they were mapped to do. I unmapped the undesired function and remapped them again with the one I wanted but everytime I restart maya it remaps the other stuff as well.
“X” “C” “V”, those are the most annoying ones, they activate now the snapping mode.
Using the trial version
windows 7

[cgbeige]

Also, I have noticed when using the hotbox and archiving of a scene it will freeze the entire operating system. If you do a heavy operation via the hotbox it will steal focus from other apps and you can’t do anything until the operation finishes.

oh - so it’s not just a problem on OS X. Any Linux users seeing this too? It’s brutal.

[stussy]

I am not sure you can classify this as a bug, but I find the the Maya 2011 Hypershade workarea font is too small. Does anyone see the same thing?

it is not only too small, is the font below the nodes Courier New? wtf

[joie]

Is it me or the new color selector can go beyond 500 in the V channel in HSV mode?, before you could go to thousands literally.

Also, Is there a way to change the comma separation between decimals in the color picker to dots?.