Building: Parts being saved in DB only with one decimal place

[xenomat]

Hi all,

 

i', running a Epoch Sauerland Server and we noticed, that all placable Parts (Walls, Floors, Crates etc.) are written to the Object table only with 1 decimal place for X and Y axis. When building the object, everything seems fine until the server is restarted. Then parts are getting places with the values written in the Object table.

 

This makes building stuff without gaps or shifting nearly impossible.

 

Example:

WoodFloor_DZ    [204.666,[14428.2,17044.2,3.34]]
WoodFloor_DZ    [204.582,[14423.7,17046.3,3.34]]
WoodFloor_DZ    [204.527,[14419.2,17048.3,3.34]]
WoodLargeWall_DZ    [89.792,[15167.4,17501.5,6.978]]
WoodLargeWall_DZ    [89.792,[15167.4,17496.6,6.978]]
WoodLargeWall_DZ    [89.792,[15167.5,17491.7,6.978]]
WoodLargeWall_DZ    [89.792,[15167.4,17486.8,6.978]]
 

On my Epoch Chernarus Server the parts are mostly written with 2 decimal places, which makes it much more accurate.

 

Could anyone explain how this data is written to the database? And why only with 1 decimal place, when the column obviously allows 128 characters (datatype "varchar(128)"). So even 3 decimal places should be no problem and would even be more accurate (height and angle mostly use 3 decimal places).

 

Thanks&cheers,

xenomat

[xenomat]

Update:

 

Right now i think this has to do with a limitation of the single values to a total of six digits. As you can see above, we built in an area with coordinates with 5 figures, so there is only 1 decimal place left after the dot.

For testing purposes i built a crate in the lower left corner of the map and i had values of XXX.YYY (so three decimal places after the dot seem to be possible only if the first part is short enough).

 

So, i'm not sure if this is intentional or a bug. But it would be really nice if this could be expanded/fixed/whatever in future versions of Epoch. :)

 

cheers,

xenomat

[vbawol]

I have Sauerland running on our 1.0.5 box I will do some building to try to reproduce this.

[OtterNas3]

It is the way things get stored to the Database on higher coordinates like [123.123[10000.123,12500.123,250.123]

This would be reduced down to [123.123[10000.1,12500.1,5.123]

 

This is not a Sauerland bug, it is related to the Arma engine which cant handle variables/floats with more then 6 digits!

[vbawol]

Good to know, thanks OtterNas!

[xenomat]

It is the way things get stored to the Database on higher coordinates like [123.123[10000.123,12500.123,250.123]

This would be reduced down to [123.123[10000.1,12500.1,5.123]

 

This is not a Sauerland bug, it is related to the Arma engine which cant handle variables/floats with more then 6 digits!

Yes, i already thought that it's not Sauerland but has to do with some kind of limitation.

But that's unfortunate... :(

[fexxianosch]

Hello there, i got the same issue and tested/reproduced it, too.

is there a way to force arma somehow to save with more than 6 digits?

 

Regards fexxianosch