Maya 2020.1 broken and useless (bug report filed)

[3dvfxprofessor]

Don't update to Maya 2020.1.

The Device/Pixel aspect ratio in Render Settings is broken. Pixel is set to 1000 and you can't change it to 1.

Worst: If you try to change it to 1 it will change Device to 1777.778 and you can't change this anymore.

This will cause that Arnold isn't able to render the picture in the correct format anymore.

Arnold is able to deal with this as long as you don't trouch the Pixel aspect ratio.

Redshift can't handle it completely. When you just open the Render Settings without changing anything the Render View shows a single line due to the Pixel aspect ratio of 1000. If I try to change the display settings in Redshift Render View to "Fill Window" Maya will crash.

I have filed a bug report rated CRITICAL to Autodesk today.

[mspeer]

Hi!

This is a known issue, but there is a workaround:

https://forums.autodesk.com/t5/maya-forum/maya-2020-1-input-values-1000/td-p/9397931

[3dvfxprofessor]

In my case it doesn't work. The aspect value has to be set to 1. I can't fix this with any method. Even editing the .ma file will not help here because the value will always be set to 1000.000 and finally 1777.778.

[mspeer]

Hi!

Please try to change your complete region / language .

(Switch to an English format / Setup)

This is for sure a region / language specific problem and the workaround was confirmed to work, by others.

Please (re)start Maya AFTER you changed the settings.

[3dvfxprofessor]

This works. Thanks. But you need just to change the regional settings for date/time. This seems to affect the number formats over all kind of applications like Excel where my dates are changed from 18.05.2020 to 20/05/18 now. 😉

[lennart.oberscheidt]

Use the environment variable as suggested in the other thread, works for us. This doesn't require you to change the language settings, which, of course, you wouldn't want to touch just to get maya running as other programs depend on that as well. 

MAYA_FORCE_C_LOCALE=1

However, what I don't understand is why Autodesk doesn't sticky a post on these forums detailing the (temporary) solution! After all, this IS a critical bug (and only easily work-arounded IF you happen to know how…). Also, it'd be easy to put into the 2020.1 release notes asap. 

Literally everyone I know, because I'm living in europe, is faced with this bug after updating to 2020.1. There is  literally NO way this hasn't come up during beta testing, because you are confronted with this basically 10 to 60 seconds after opening 2020.1. 

[ray]

Didn't 2020.2 solve the problem ? 

[3dvfxprofessor]

I installed 2020.2 a few days ago and had to set the environment variable again to fix it.

[ray]

🙄

[ray]

2020.3 is out, anyone knows if the bug was fixed ?

[mspeer]

Hi!

This is fixed in Maya 2020.3 .

(At least it's stated as fixed.)

I have not tested this for now.