Search Issue Tracker

Fixed in 2019.1.X

Fixed in 2018.3.X



Found in


Issue ID




[Windows] Editor uses OS locale settings (i.e. commas instead of dots in float inspector fields) with Experimental .NET 4.6



Setting the Project to use the new Experimental .NET 4.6 support apparently results in the Editor using the OS's Locale for formatting. In case of a non-English Locale this results in a mixed English/non-English Editor experience, specifically noticeable when commas are used for decimal separation.

Steps to reproduce:
1. [Change Locale setting to non-English]
a) Open Start menu and type Region
b) In an opened window select Formats tab
c) Select any non-English format, that uses commas instead of dots for decimal separation (for example, German (Germany))
d) Apply, close the window
2. Open attached project "Locale"
3. Open scene "test" and select "RandomObject" from Hierarchy
4. Take a look at Component "Number Test"

Expected behavior: for float number "Random float" dots are used for decimal separation.
Actual behavior: for float number "Random float" commas are used for decimal separation.

Reproduced with: 2017.2.0b2, 2017.1.0f3.
Not reproduced with: 5.6 (no Experimental .NET 4.6 feature).

Comments (31)

  1. Immu

    Sep 10, 2018 16:38

    Breaking my shader graphs on each update...
    Any fix plans ? Is 38+ votes not enough @_@ ?

  2. PsycHead

    Sep 03, 2018 10:09

    Still not fixed on 2018.2.4f1
    This also breaks shader graph, which won't compile shaders with floating point default values on properties.

  3. Shturmovik

    Aug 31, 2018 13:36

    OK - this is it. Tired of not being listened to. Switching to UE4 where you at least have a chance to fix stuff that's obviously broken.

  4. fherbst

    Aug 22, 2018 13:13

    This affects animation and timeline heavily. Basically, animating anything complex isn't possible as there seem to be issues where Unity interprets a "20,345" as "20345" and thus converts it to "20345,00". If you change the key again - continue animating - it goes to "2034500,00" and so on. Everything basically explodes!

  5. Nickolauson

    Jul 12, 2018 00:04

    2018.2 still there.. :/

  6. E4est

    Jul 09, 2018 06:13

    Also present in 2017.4.5f1 which should be LTS.

    It affects ModelTarget imports for Vuforia where numbers are interpreted as if they were without a comma or dot. This results in way too big 3D models and detection to expect way too big reallife models.

  7. huulong

    Jul 03, 2018 19:02

    Still in Unity 2018.1.3f1.

    It also affects the Timeline Playable Wizard from Unity's own Default Playables asset (, which would create a TrackAsset with attribute [TrackColor(0,9150943f, 0,07338022f, 0,175978f)] (every other comma should be a dot), which of course doesn't compile.

  8. shaderbytes

    Jun 27, 2018 18:14

    this seriously needs to be fixed , it is a unity editor only issue , control panel is fine , all other programs are fine. Just Unity which is doing this and it only does this if I change to .net 4. changing back to .net 3 fixes the problem , but i can change bck as i have code the requires .net 4...

  9. shaderbytes

    Jun 27, 2018 17:58

    i dont know anything about the non english stuff, just know i switched to using .net 4 and now i have comma's for decimal points and i dont want it like that

  10. ppizarro

    Jun 15, 2018 19:16

    Still present on unity 2018.1.4f1. I cant set dots for decimal instead of comma... i have several errors with JSONObject class.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.