[rdc]

Hey Shapkin,

Excellent detective work! I can now reproduce this here

You are correct, the system local setting is the root cause. I've looked into the code and can provide an explanation for the behaviour:

• The geometry files contain the vertex data as floating-point with a '.' separator
• An instance of a java.util.Scanner is used to parse that data
• The scanner will pick up the current system locale and use that to interpret the floating point number

That's all well, but on systems that do not have "." as a floating-point separator, an exception will be thrown that forces the geometry back to a triangle. The workaround is to, as you say, change to a locale that has a "." separator.

Many thanks for finding and reporting this issue!

[DrNoes]

shapkin, on 23 March 2013 - 11:23 PM, said:

Hi all,
I have had the same issue. And I think i know the root cause.
Looks like it's happens then you have non "." (point) separator in your system for float numbers. For me it was "," (coma).
So just set US locale setting.

For plugin developers: Please dont use system separator It happens inside of com.arm.mali.shaderdevelopmentstudio.callscript.Geometry. The java.util.Scanner throws java.util.InputMismatchException then trying to parse float number.
Sorry for my English.

Thanks shapkin! That did it! Well done!

adding "-Duser.language=en -Duser.country=US" to the eclipse.ini worked.


But this is just a workaround... Hopefully this is fixed in the next version/patch... shouldn't be too hard i guess.