Maya 2011 BUGS (Write Here)

djx · 2010-04-16 18:03:55 UTC

I only notice that behaviour if I leave the keys unmapped. If I reassign them then that seems to be permanent, with no dual functions.

I did notice that after loading my old hot keys pref file, I had several with the dual function. eg I use X to toggle xray, and it took a while to work out why grid snap kept getting turned on. Once I removed X from grid snap and toggle xray (press and release) and then reassigned to toggle xray it seems to be ok.

Its not the first time I’ve seen maya choke on old prefs. In this case it seems fixable though.

David

tharrell · 2010-04-16 20:07:04 UTC

Dave,

We’re having a load of issues with the latest VRay build at work currently… particularly if the scene has any cobwebs in it from prior builds.

After two days of debugging and all kinds of nastiness, we’ve rolled back to 1.8.something. In your case, I’m pretty confident that it’s the build and not 2011-specific.

PM me if you need more specifics to compare with your issues…

–T

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.

tharrell · 2010-04-16 23:34:54 UTC

And my turn to ask for confirmation on something…

Is anyone else having oddity with the mel command line (in the main window) randomly forgetting about its up arrow history?

Maya 2011, Mac OS X 10.6.3

–T

tpalamar · 2010-04-17 05:37:01 UTC

There are new features with FG. They added FG Quality and FG Tracing. Also this is from the docs:

The new Normal Tolerance option allows you to specify the maximum angle up to which a final gather point normal may deviate from the surface normal for the final gather point to be considered for interpolation. A higher value reduces rendering time while a lower value may slow down rendering.

cgbeige · 2010-04-17 07:39:09 UTC

Ok - thanks. I sent Vladimir an email so hopefully they’re looking into it. I’ll just grab an older build in the meantime.

drmaya · 2010-04-17 07:51:12 UTC

I’m in love with MaYa 7

Alias>Autoshit

flys · 2010-04-17 07:57:39 UTC

This works fine for me, but not Send to Maya from Mudbox … but mabe this is a Mudbox bug

My sistem is windows vista 32bit

merluzzaio · 2010-04-17 14:14:35 UTC

Hi to all, I’ve found this bug, but can someone ensure if I’m right pls?

ok let’s start…

Open maya, create a poly like a cube or something else…

open uv texture editor select some edges and click on “Separate the UV’s along the selected edges” and then select some uv’s points ctrl+RB and select “to shell”

ta daaaaaa!

all uv point are seleted… :surprised and no shell, no separation…nothing happens!

byez

merluzzaio · 2010-04-17 14:16:27 UTC

this work fine for me, win 7 x64 n’ ati hd5770 byez

Samuka3000 · 2010-04-17 16:02:52 UTC

i’ve been reading this thread closely and honestly i think it’s kinda’ scary to make the switch from 2009 to 2011… well, that’s the impression it gave so far.

AdanVC · 2010-04-17 16:37:24 UTC

Yeah!, me too :(,

tpalamar · 2010-04-17 17:55:00 UTC

I just tried it and it worked fine. The problem is that you are cutting the edge and then converting your selecting (which is both sides of the cut edge) to UV’s. Your selection is both sides. Omit ctrl+RB and select a single UV on the side that you cut and then choose select shell. It works fine.

SheepFactory · 2010-04-17 18:13:46 UTC

Works with zero issues here on my gtx 275 as well.

pritishd · 2010-04-17 19:29:54 UTC

I use component editor for editing my smooth skinning. The “Hide Zero Column” function does not work with this version, and it’s a pain to find the column now.

Bummer!!

djx · 2010-04-17 23:03:21 UTC

cgBeige, I’m not sure if this is what you meant by a camera marking menu, but…

Press Command:


 if( `popupMenu -exists tempMM` ) deleteUI tempMM;
popupMenu -alt 0 -ctl 0 -sh 0 -mm 1 -b 1 -aob 1 -p viewPanes tempMM;
  string $camList[]=`ls -ca`;
  for( $cam in $camList ){	
  		string $parent[] = `listRelatives -f -p $cam`;
  		menuItem -l $parent[0] -c ("lookThru "+$parent[0]+" viewPanes;");
  }
  setParent -m ..;

Release Command:

if( `popupMenu -exists tempMM` ) deleteUI tempMM;

David

cgbeige · 2010-04-18 08:37:22 UTC

djx:

cgBeige, I’m not sure if this is what you meant by a camera marking menu, but…

Press Command:


 if( `popupMenu -exists tempMM` ) deleteUI tempMM;
popupMenu -alt 0 -ctl 0 -sh 0 -mm 1 -b 1 -aob 1 -p viewPanes tempMM;
  string $camList[]=`ls -ca`;
  for( $cam in $camList ){	
  		string $parent[] = `listRelatives -f -p $cam`;
  		menuItem -l $parent[0] -c ("lookThru "+$parent[0]+" viewPanes;");
  }
  setParent -m ..;

Release Command:

if( `popupMenu -exists tempMM` ) deleteUI tempMM;

David

awesome - thanks. But how to do assign a release command to a marking menu? I’ve never done that.

merluzzaio · 2010-04-18 10:12:12 UTC

This works for me if I don’t apply any mapping (planar),if I do I meet again that problem.
anyway thank you mate.

gustavogf · 2010-04-18 10:31:27 UTC

I tried some of the bugs listed here and it’s working fine for me (OSX) (dragging icons to other shelfs, viewport update – maybe this one is a graphics card issue?) I’m yet to test the Windows version.

Actually, in OSX my Help files are strange. Is there some way to download only the Maya docs? I don’t wanna go to online help every time I need it.

SheepFactory · 2010-04-18 11:21:22 UTC

%90 + of the “bugs” in this thread are due to the poster having incompatibe gfx drivers or some unsupported hardware really.

Animasta · 2010-04-18 15:36:46 UTC

Ok, here’s an annoying bug I’m running into today.

I’ve got two surfaces setup in the (slow-as-heck) hypershade. One for the color of my model’s lips, the other for the color of the skin. Now, whenever I extrude any edges, the new geometry will have the color of the model’s lips (even though the area I’m extruding is nowhere near the lips). So I reassign the shader for the skin to the newly created geometry. I extrude again and guess what, the new geometry, along with the section that I just reassigned the skin shader to, go back to being the color of the lips.