Maya 2011 BUGS (Write Here)

#261

Use fbx. However not the 2011 version. Dont work for me with Nuke 6.0x

#262

COLOUR ME SURPRISED. Can someone please test this stuff so we don’t have to? It’s pretty embarrassing, how predictable the Maya fails are becoming…

Almost as predictable as your misconjugation of the word, “failure”.

But this thread is very informative all around. Looks like I’ll skip all the billions of NEW bugs the AD guys made and released without testing, and just stick with Maya 2009 for another year or three. I had actually just convinced my employer to go subscription for Maya 2011 based on all the new features… Now it looks like that money would be better spent on a new printer or something!

#263

Feeling slightly dirty for this because, well, it’s a cheap shot.

But… I’m not entirely sure that AD has tested ANY currently shipping Maya vs a current MacOS. Like, ever. Or even any MacOS, let’s say 6 months out of beta.

Either adopt Windows or pay the same price to be a second-class citizen.

Just sayin’

(Goes for Linux, too, btw)

–T

#264

Either adopt Windows or pay the same price to be a second-class citizen.

Not too dirty or cheap. Often, the handicapped, infirm, and elderly are regarded as second-class citizens anyway, so it shouldn’t be too surprising, although it is cold and cruel if you ask me.

But this thread is as much about Windows bugs as Mac bugs. I’m very happy that I didn’t already subscribe to Maya, and even happier to be stuck with Maya 2009 indefinitely. Sure, it has some bugs, but at least it works and I can get my jobs finished with it. And Maya hasn’t crashed on me in 9, 10 months…

Anyway, just my vile ranting. Autodesk: figure it out, or sell Maya to someone who can.

(nothing personal against Shawn or any other employee… you guys are great, and very helpful!)

#265

I’m glad you’re back to think you’re correcting my grammar but you missed a reference to the FAIL meme. It wasn’t a mistake. So this is for you and your correction:

http://failblog.org/

#266

setting the timeline Display Key Ticks to Channel Box returns an error.

// Error: specified channel box not found

also calling the mel command timeControl -e -sk “mainChannelBox” timeControl1; returns same error. The channel box does indeed exists as proved by command: channelBox -q -ex mainChannelBox;

Anyone else getting this? I tested both my mac and my xp64 box at work.

#267

I’m having this weird behaviors with Smooth Mesh Preview.
It’s displaying Cage+Smooth Mesh at random when only smooth mesh is selected.
Also sometimes some components stay selected (they are not actually selected but display as selected) even when i go to Object Mode and select another object. This also happens at random.

I’m on Win7 x64, Gtx275 (190.38 driver)

anyone had something similar?

#268

Biggest thing I’ve come across now to date is problems with working with Nurbs.

Cant select Isoparms… and my other components are not on the object but floating offset to the model. Seen this before in previous versions so guessing it may not be directly Autodesk Maya related. Anybody know a solution for this.

I still like using Nurbs and sucks not being able to work with em.

#269

@revilo3D

You ought to simply rename your current prefs folder, then Maya will create default prefs on next startup. Then you will probably see that the nurbs objects are working as they should.

#270

when I use command completion it loses focus on script editor, workspace becomes active. annoying…

#271

Component Editor->Hide Zero Columns does not functioning.

#272

I’m on 10.6.2 and playblast using qt always outputs 24fps… The only workaround is to use iff and combine a sequence in quicktime or djv view.
So ADSK if full of shit! :banghead:

We just finished a PAL TV commercial with a very tight deadline (as usual) where the sound was synced to a playblast - so we just lost a hole lot of time debugging this issue. Now we have an angry TV Station and Customer… We should bill ADSK for this!! :slight_smile:

#273

No doubt. :stuck_out_tongue: But be sure and log your situation with ADSK support so they know it’s a problem in 10.6.2 as well.

The other silly Playblast issue I was having where it only makes a short list of QT CODECs available was addressed by ADSK support by telling me to simply run Maya in 32bit mode. Nice. So if this whole 32bit CODEC vs. 64bit CODEC deal actually exists…why then does the recently shipped Adobe After Effects CS5 - available as a 64bit app only - have lots of those CODECs available? I’m confused.

#274

I don’t believe that it is a 32- vs. 64bit issue. I haven’t tried to run Maya in 32bit mode to see if there are more codecs (like ProRes 422/4444) available. No other application that I have heard of on OS X is bitching about using Quicktime conversion in a 32- or 64bit application. Final Cut, <CS4, Quicktime 7, Nuke etc. etc. is 32bit and has no problem making ProRes files. A buddy of mine are long time OS X application developer, specializing in multi sequence/big video playback and recording stuff - he laughed (rolling on the floor and everything) when I mentioned ADSK excuse… :slight_smile:

The framerate is a very BIG bug and should be enough for a service pack by it self!!

#275

The framerate bug does exist on windows as well. I already logged it.

#276

ya, that should toooooooooooootally fix it, considering I logged the “Maya IFF plug-in is still PowerPC only” for an Intel-only product repeatedly over the last 4 years. Toss another into the black hole.

#277

Hi, I’ve been reading through this thread all day and it’s a very interesting read :slight_smile: I can confirm most of the already listed bugs. Some don’t seem to “work” here, like the one cgbeige has with the submenu switching.
I am running Maya 2011 on OS X 10.6.2 - I skipped 10.6.3 because we had issues here with Maya 2010 and after doing a fresh install I just used the 10.6.2 combo update.
My main problems here are the really sluggish interface. Opening the Hypershade just kills me, the AE is so slow when switching selections that I wish that I wouldn’t have to select something and opening the Quality tab in the Render Settings is taking so long I can get a coffee inbetween… ok, it’s 5 seconds but it “feels” longer :wink: Oh, and what I miss most is the nice snappiness of the hotbox in 2010 - persp/top/front/persp…etc I missed that from my windows days and I was so happy that this thing got addressed in 2010 - but now it’s back and even worse. SO well… I just hope that these things will get fixed with the next update.

One thing I though found today (and this happened to me “live” in class in front of my students) is this:
Mapping a QT movie to an image plane. The movie has a DVCPRO codec applied, 1024x768, 25fps and running 14 secs. Applying that to the image plane works fine but the playback gets screwed. I am reaching the end of the clip after 14!!! frames - nice time remap but sadly unwanted. It definitely worked in previous versions - I have used this clip in class for several years now. I fixed it by making the clip an image sequence.

Can anyone confirm this for making it worth filing a bug report?

Cheers, Ingo

#278

file the report. That sounds a bit obscure to be known.

#279

alright - my little bugger is filed:

358108 Quicktime movie doesn’t play back at correct fps when used as image plane

#280

I just measured the time it takes to switch to the Quality tab, on my 2009 Mac Pro with both Mac OS 10.6.2 and Win 7x64 : the result is 2.5s on both systems the first time the tab is opened, and then it happens instantly.