Maya 2017 problem when I manually input values - they get reset

[Anonymous]

Hi all,

I have this weird problem with the Maya 2017 UI. Whenever I go to change a value with my keyboard, for instance depth on an image plane, or intensity of a light. I input the value, press enter or click in another field or tab out, it will just reset to what it was. So I have to use the slider instead, and with the slider I can't get the exact values I need. 

Anyone experienced this and know a solution? There's nothing special about any of these values, happens all over the UI.

[Anonymous]

Hi all,

I have this weird problem with the Maya 2017 UI. Whenever I go to change a value with my keyboard, for instance depth on an image plane, or intensity of a light. I input the value, press enter or click in another field or tab out, it will just reset to what it was. So I have to use the slider instead, and with the slider I can't get the exact values I need. 

Anyone experienced this and know a solution? There's nothing special about any of these values, happens all over the UI.

[Anonymous]

For me the problem is not the reset, but only with the dot ("." character). With i type some with dot, it will not accept the dot, but the number. Example:
i type 2.25, Maya recognize, 225. so, i need to click in the field where i need to put the numbers, so imagine, is there 0.00 on the field, i sub select the 00 after the dot, type the 25, then select the sub before the dot, and type 2. It works, is annoying, need fix son, but that way i don't need to go back to Maya 2016.5

[Anonymous]

For me the problem is not the reset, but only with the dot ("." character). With i type some with dot, it will not accept the dot, but the number. Example:
i type 2.25, Maya recognize, 225. so, i need to click in the field where i need to put the numbers, so imagine, is there 0.00 on the field, i sub select the 00 after the dot, type the 25, then select the sub before the dot, and type 2. It works, is annoying, need fix son, but that way i don't need to go back to Maya 2016.5

[Anonymous]

Yes that is true, I can't even type a dot anywhere when this happens, so I sometimes copy and paste one. But it still doesn't always save the text input. 

I am currently mostly getting around this by CTRL and left or right dragging the numbers, but it's very inefficient.

[Anonymous]

Yes that is true, I can't even type a dot anywhere when this happens, so I sometimes copy and paste one. But it still doesn't always save the text input. 

I am currently mostly getting around this by CTRL and left or right dragging the numbers, but it's very inefficient.

[eugenius113]

Same problem in Attribute Editor on Windows 7 SP1. On Windows 10 is no such problem.

[eugenius113]

Same problem in Attribute Editor on Windows 7 SP1. On Windows 10 is no such problem.

[Anonymous]

Like ClimberFX said it's definitely related to the periods, I saw that I can type whole numbers fine, but whenever it's a float it happens. I'm on Windows 10 so I don't think it's OS related. Do you have older Maya version on any of your computers? Maybe there's some old settings issue.

[Anonymous]

Like ClimberFX said it's definitely related to the periods, I saw that I can type whole numbers fine, but whenever it's a float it happens. I'm on Windows 10 so I don't think it's OS related. Do you have older Maya version on any of your computers? Maybe there's some old settings issue.

[yyaca]

This is even more annoying because refers to attribute editor (don"t know if only), but channel box accepts period character without a problem.

Just switched gears to 2017 and everything seems to work fine until once wants to tweak values with fractions in attribute editor. Small bug - big frustration... The funniest thing is that we're going to wait for the first SP to get rid off ... the "period" problem.

BTW Dose anybody reported that bug to the support ?

Cheers,

YYaca

[yyaca]

This is even more annoying because refers to attribute editor (don"t know if only), but channel box accepts period character without a problem.

Just switched gears to 2017 and everything seems to work fine until once wants to tweak values with fractions in attribute editor. Small bug - big frustration... The funniest thing is that we're going to wait for the first SP to get rid off ... the "period" problem.

BTW Dose anybody reported that bug to the support ?

Cheers,

YYaca

[eugenius113]

Yes, but with no result(((

Here is answer to my bug report:

Please send your reports here: http://download.autodesk.com/us/support/report_a_bug.html?SelProduct=Maya

We have to show that many people has this problem.

[eugenius113]

Yes, but with no result(((

Here is answer to my bug report:

Please send your reports here: http://download.autodesk.com/us/support/report_a_bug.html?SelProduct=Maya

We have to show that many people has this problem.

[yyaca]

So what does the video look like? Did he do everything correct? Honestly I wonder what could be done wrong...? Simply the case is to a "." character in attribute editor especially. Nothing really fancy... or maybe I missed something?

Cheers,

YYaca

[yyaca]

So what does the video look like? Did he do everything correct? Honestly I wonder what could be done wrong...? Simply the case is to a "." character in attribute editor especially. Nothing really fancy... or maybe I missed something?

Cheers,

YYaca

[eugenius113]

Yes, the problem is in the sign ".", here is a video from support response:

[eugenius113]

Yes, the problem is in the sign ".", here is a video from support response:

[Anonymous]

I use an English Windows 10 but localized to Norwegian. I tried changing to English keyboard and input thinking it may be some issue, but it didn't help.

[Anonymous]

I use an English Windows 10 but localized to Norwegian. I tried changing to English keyboard and input thinking it may be some issue, but it didn't help.

[Nadja.Bueckmann]

Hi @Anonymous,

I just tried to recreate the issue you describe. I can´t reproduce it on my side.

I think it is related to the language version of your OS.

As I understand you use a Norwegian one. It would be interesting to find out which language version the people use who reported the issue as well. 

I will report it to the development team, so that they can have a "second" look into the issue.

Best, Nadja

[Nadja.Bueckmann]

Hi @Anonymous,

I just tried to recreate the issue you describe. I can´t reproduce it on my side.

I think it is related to the language version of your OS.

As I understand you use a Norwegian one. It would be interesting to find out which language version the people use who reported the issue as well. 

I will report it to the development team, so that they can have a "second" look into the issue.

Best, Nadja

[eugenius113]

---

Nadja.Bueckmann написано:

I will report it to the development team, so that they can have a "second" look into the issue.

---

Thank you, @Nadja.Bueckmann. Glad to hear it!
I use Windows 7 SP1 with Russian localization. I also tried to change the OS language to English, but the problem remained.

[eugenius113]

---

Nadja.Bueckmann написано:

I will report it to the development team, so that they can have a "second" look into the issue.

---

Thank you, @Nadja.Bueckmann. Glad to hear it!
I use Windows 7 SP1 with Russian localization. I also tried to change the OS language to English, but the problem remained.

[yyaca]

Yeah, good to know somebody cares !!! 

I'm on Windows 10, localization - Poland. The same failure with language change to English.

Greetings,

YYaca

[yyaca]

Yeah, good to know somebody cares !!! 

I'm on Windows 10, localization - Poland. The same failure with language change to English.

Greetings,

YYaca

[Anonymous · Accepted solution]

Hi @Nadja.Bueckmann ,

I have solved it, or rather managed to reproduce it for you guys.

The problem is gone if I in Windows go to Control Panel's "Time & Language" and then "Region & language" and choose "Additional date, time & regional settings". In "Region" I choose "Change date, time or number formats". If I choose "English, United States" here, the problem is gone if I start Maya. So it is surely related to the different way our languages write numbers with decimals ( comma vs period).

This isn't a very good solution for me, but I can live with it until you guys fix it 🙂

[Anonymous · Accepted solution]

Hi @Nadja.Bueckmann ,

I have solved it, or rather managed to reproduce it for you guys.

The problem is gone if I in Windows go to Control Panel's "Time & Language" and then "Region & language" and choose "Additional date, time & regional settings". In "Region" I choose "Change date, time or number formats". If I choose "English, United States" here, the problem is gone if I start Maya. So it is surely related to the different way our languages write numbers with decimals ( comma vs period).

This isn't a very good solution for me, but I can live with it until you guys fix it 🙂

[yyaca]

Thx for sharing.

It is some workaround, but it WORKS 

Really appreciate... thx once more!!!

Regards,

YYaca

[yyaca]

Thx for sharing.

It is some workaround, but it WORKS 

Really appreciate... thx once more!!!

Regards,

YYaca

[eugenius113]

You are genius! I changed to English (UK), and it's worked: 

(I had to change the OS language to English in order to take a screenshot).

This is a temporary solution, but now we can easily wait SP1.

I hope @Nadja.Bueckmann will report it to the development team and they fix it.

[eugenius113]

You are genius! I changed to English (UK), and it's worked: 

(I had to change the OS language to English in order to take a screenshot).

This is a temporary solution, but now we can easily wait SP1.

I hope @Nadja.Bueckmann will report it to the development team and they fix it.

[Nadja.Bueckmann]

Hi @Anonymous,

thanks a lot for finding and posting the workaround. That will help a lot of users who have the same issue as you.

I added this information to the ticket I created for development.

Then it´s easier for them to find all the necessary background information to solve the issue as fast as possible.

Best, Nadja

[Nadja.Bueckmann]

Hi @Anonymous,

thanks a lot for finding and posting the workaround. That will help a lot of users who have the same issue as you.

I added this information to the ticket I created for development.

Then it´s easier for them to find all the necessary background information to solve the issue as fast as possible.

Best, Nadja

[Treidge]

Just wanted to chime in with some additional info: you don't have to change the whole Format setting — changing the Decimal symbol from comma to dot will suffice. It'll be a bit more convenient to have just this setting altered in the mean time before this issue will be fixed internally in Maya.

 

[Treidge]

Just wanted to chime in with some additional info: you don't have to change the whole Format setting — changing the Decimal symbol from comma to dot will suffice. It'll be a bit more convenient to have just this setting altered in the mean time before this issue will be fixed internally in Maya.

 

[eugenius113]

@Treidge, thank you! It really works!

@Nadja.Bueckmann, please add this information in the ticket 🙂

[eugenius113]

@Treidge, thank you! It really works!

@Nadja.Bueckmann, please add this information in the ticket 🙂

[Anonymous]

True, thanks for adding. But not if you use certain programs that use these values, such as Excel or whatever. I just keep the Region window open and change before/after opening the program.

[Anonymous]

True, thanks for adding. But not if you use certain programs that use these values, such as Excel or whatever. I just keep the Region window open and change before/after opening the program.