Playmaker Forum

PlayMaker Help & Tips => PlayMaker Help => Topic started by: nFighter on May 06, 2019, 10:17:16 AM

Title: Serious bug in Unity that affect PlayMaker
Post by: nFighter on May 06, 2019, 10:17:16 AM

After moving from 2017 LTS to 2018.3 my project become totally unusable for 2/3 of players. Nevertheless I could not reproduce any of the errors on my laptop, everything was perfect. I made a research and find the problem:

in .NET 4 / 4.6 Unity editor use OS locale settings (i.e. commas instead of dots). It could brings errors when you use ArrayMaker (and other PM solutions that utilize proxy objects) or convert float/string/int. In this topic (https://hutonggames.com/playmakerforum/index.php?topic=20487.0) you can find an example of weird stuff you can get.

Here is the issue tracker (https://issuetracker.unity3d.com/issues/windows-editor-uses-os-locale-settings-i-dot-e-commas-instead-of-dots-in-float-inspector-fields-with-experimental-net-4-dot-6) and forum discussion (https://forum.unity.com/threads/editor-is-using-windows-locale-settings.442847/) around.
Bug was found in 2017, fixed in 2019.1... great job, unity team.

For those who can't just switch to 2019.1 the solution is roll back to .NET 2

Title: Re: Serious bug in Unity that affect PlayMaker
Post by: jeanfabre on May 17, 2019, 01:18:03 AM

Hi,

 yes, do not use .net4 at all until 2019, 2017 and 2018 are totally buggy with .net4

 Bye,

 Jean