Maya 2011 BUGS (Write Here)

#381

Thank you, mduvekot.
I had looked @ that page before actually & clicked on its various links without finding anything that took me directly to any download for the fix.
Dug a little deeper this time & located it. If this is your site though, first thank you much for creating & maintaining it, & second you may want to make a link to the fix a little more clear in your bug documentation.
Thanks again!
-J

#382

Done, thanks for the suggestion

For download and release notes, see

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15407662&linkID=9242259
http://images.autodesk.com/adsk/files/maya2011_hotfix3_readme.pdf

#383

You rock, man!
SO nice not to have to sort thru hundreds of columns for every selection!!
-J

#384

Sorry if its already been said. 2 BUGS

Bug1
If I create a plane and assign an image, in my cases 24bit PNG that contains trans(not square image, it is 620x480(not that it should matter)). Size of the plane is 6.4x4.8. In my Uv editor it takes up a portion of the 1 to 1 UV space as usual. So I Grab the top two points(UV’s) and raise them to the top with grid snapping. The bottom of my image shows up on my planes top edge, ever so slightly. Enough to ruin hours of rendering. So I have to go in and lower all my UVs very slightly.
Edit: just to note, this was not an issue with previous versions. I used the specifics of the files above as it seemed to be a consistent bug.

Bug2
This has been around for a while:
Playblast the from say frame 200 to frame 300. The audio track starts from the begining on playblast render, not at frame 200. Annoying.

#385

Thanks, for bug#1, wouldn’t normalizing the UVs fix this?

#386

Yes normalize works fine but if I am grid snapping, should it not be to the center of the grid already? There have never been a need for any extra steps. Its no biggy really, it just caught me by surprise after a nightly. Either way I have to do an extra step and remember another odity, vs other maya versions.

#387

maya 2011 is more buggy than maya 2010.
it’s the worst shit I have ever worked with and finally I’m doing my last project with maya mentalray.
after my project I’ll try to be a compositing artist, I can’t stand the pain anymore.

almost nothing is working in maya 2011.

I don’t want to get detailed atm. cause I am in deadline stress and everything is painfully disassembling.

but at first glance - the renderlayers are like in maya 7.0!!!
no chance at all. not working at all.
you assign something, switch back and forth and the renderlayers are ****ed and you end up with having no sg. assigned anymore.
write to custom buffer shit is still not fixed with 10 times more rendertime
menues are missing - fe. sometimes the light options where you look through barndoors… disappearing
maya is incosistent.
rendererrors - fatal errors without cause.
geometry render problems - mr. exited with status 210, 209, 1, 3, 23084720 and so forth.
partly sampling problems
reference system is ****ing up things in scenes with all these namespaces.
passes still producing inconsistent results.
and so forth.
interface is extremely slow. hotbox needs time to open - workflow in general got very slow.
viewport laggs whilst having not the right drivers.
backburner hassles (seems that every studio has this problem - producing errors without cause, rendering only on one thread and so forth)

thanks autodesk for releasing a peace of crap.

finally after 8 years of maya I really want to change business and be a happy vray render guy.
my current pipeline consists of scripting 7 hrs a day to make things work.
I still want to be an artist and want to concentrate on doing artistic stuff.

fuc()*£ £)£)(*£-3

now I got it from my soul, all the best to all others here in pain.
bastian

#388

I got Maxwell, Which is a joy to use.

#389

Are you guys taking the time reporting these bugs or just ranting about them on CGTalk? Doing the latter certainly won’t get them fixed.

#390

I still will report them.
but what would it make a difference saying - hey autodesk, your renderlayers are still ****ed. I haven’t seen any progress other than porting the whole code to python and making nice qt feature and shitty dark interface.
anyway, at least mr. gets hybrid slowly, but still I think no-one will use it in some time. as everyone switched to nuke when it came out.

#391

I know it sucks watching bugs linger version after version, but short of not renewing your subscription this is the only effective means we have at our disposal to influence the development.
I do think this thread has merit though as long as it culminates in filing those reports.

It might help to clean up your language somewhat. Cursing is counterproductive.

#392

I love a good rant. I’m OK with people who are pissed off, frustrated and angry at Autodesk for not fixing stuff that matters to them. I get that.

But I’ve completely had it with people who fail to substantiate their claim that Maya is buggier now than before. I record every issue I see in a public place and log everything I can reproduce with Autodesk. In my experience, working around the issues that Maya has requires that you have some way of formally describing the problem, either in writing a flow chart or diagram or whatever. Only when you have that, can you begin to explain the problem to others, co-workers Autodesk, people here and get some help or a fix from Autodesk.

It would be nice if people put a little more effort into reporting the problems they find so that their contributions actually contribute something.

And as for that shitty dark UI, see http://www.thnkr.com/wiki/index.php?title=Maya's_UI_color_scheme for a solution.

Frankly, I think I have or a solution for pretty much all of the issues Sorath raised.

#393

The only issue I have is the Slow interface thingy when you have to scroll a Window, I think it’s been reported loads of times.

#394

KaMate: Yep, I have that too. My interim “solution”? Turn mouse wheel scroll off in the preferences until they fix it.

Michiel, I agree with what you said.
Also I think your public bug reporting site is a great commodity to the Maya community. I hope you keep it going.

edit: Sorry… it’s Michiel… not Michael…

#395

It is only annoying if you scroll the wheel, I use a Magic Mouse anyway so I set it up to need two fingers on it for scrolling and zoom.

#396

It makes a huge difference if you actually explain the problem your having with a feature in Maya rather than just say it’s ****ed.

The only feature/bug request that Autodesk have outright rejected of mine was the “thesis” I did on how to improve the 3D Texture Paint tool.

#397

Wow… using a Magic Mouse in Maya. Brave man. As much as I like the mouse for browsing, I don’t think I could ever use it for Maya. :slight_smile:

#398

Interesting to hear a complaint about the interface colour scheme from a lighting, shading and comp artist. If you recall how our eyes work with colour and value its a blessing if you ask me. Ive been already doing neutralising to my maya scheme for years.

What do you mean by mr getting hybrid, in relation to people using nuke?

#399

Seeing ICE and 3ds max’s new material editor makes me jealous. Ive got no real beef with Maya 2011 except the hypershade can be a dog to use sometimes.

#400

well the dark interface is kinda nice for judging a shading or a render.
I agree, but changing all buttons is really confusing. before I just remembered the forms and colors of the buttons, by them I clicked them. now they’re different.
anyway… I don’t do color grading in maya… so I’m fine if only nuke would be dark.

and also I agree, the hypershade of maya is kinda sick… also the open gl delays in hypershade.
some diving into nodes in houdini is way nicer.
I always thought porting to qt means that maya then runs solid like in houdini, sadly that isn’t true.

anyway, I’ll stop complaining now and keep on fixing.
I’m just getting really strange comments from all 3dmax vray guys here - that they never get any errors and never had any hassles with anything.
And me is fixing nightshifts cause of simple problems…