StefanoCos
commented
1 year ago Possible Solution:
Ensure that every float.Parse() is correctly parsing the string to a float, regardless of the system's culture settings. This can be achieved by using an overload of float.Parse() that takes a NumberStyles and IFormatProvider parameter, and specifying NumberStyles.Float and CultureInfo.InvariantCulture.
using System.Globalization;
// ...
float positionXValue = float.Parse(row["PositionX"], NumberStyles.Float, CultureInfo.InvariantCulture);
float positionZValue = float.Parse(row["PositionZ"], NumberStyles.Float, CultureInfo.InvariantCulture);
float positionYValue = float.Parse(row["PositionY"], NumberStyles.Float, CultureInfo.InvariantCulture);( In visual studio ) This can be achieved by using the Find and Replace feature in Visual Studio with regular expressions.
Open Visual Studio's Find and Replace dialog by pressing Ctrl+H.
Check the "Use Regular Expressions" checkbox. It is represented by an asterisk .* symbol.
In the "Find what" box, put: float.Parse((.+?)).
In the "Replace with" box, put: float.Parse($1, NumberStyles.Float, CultureInfo.InvariantCulture).
Click on "Replace All" to replace all occurrences.
This should replace all instances of float.Parse(row["PositionX"])-like expressions with float.Parse(row["PositionX"], NumberStyles.Float, CultureInfo.InvariantCulture)-like expressions.
oyvind-stromsvik
briochie
Description:
When spawning game objects from data read from a CSV file, the position values assigned to the new objects are extremely large, leading to a warning in Unity about floating point precision limitations. The issue appears to occur after reading and parsing the position data from the CSV file, performing some calculations, and assigning the calculated values to the position of the new game object.
Expected behavior:
The position values of the new game objects should be similar to the position values specified in the CSV file, within the range of the Unity world coordinates.
Actual behavior:
The position values assigned to the new game objects are extremely large, often in the range of -1.758448e+13, which is beyond the scope of what Unity's single-precision floating point numbers can handle with high accuracy.
Cause:
The issue is related to the parsing of the position data from the CSV file. It's possible that float.Parse() is not correctly converting the string values to float, potentially due to culture-specific number formatting issues. In some cultures, the decimal separator is a comma , instead of a period ., which can lead to incorrect parsing of floating point numbers.