Sorry your browser is not supported!

Hey guys, it's been a while. Believe it or not, I'm using DBPro to make something for an engineering company. Makes a change for me from rubbish FPS games! My question:

Is there a co-ordinate limit in DBPro?

I'm making a program to check building positions, and it's checking drill locations over a very wide area, 79,300 DB units (which are metres in the real world). Now, in a range that's tight to the origin it works fine (10,0,10), but funny things start happening with drill locations at extreme distances (79300,102,77645).

I CAN post my source code if people are interested, but it's pretty confusing without loads of backstory. Basically, I'm just wondering whether anyone else has had strange results at extreme co-ordinates like me.

I can simply change the DB scale, so instead of one unit being one metre I can make it a smaller scale but I'm reluctant to go through and put a scale factor on all the loading in and saving points.

There's no limit that i know of, however you can expect some inaccuracy at very high values. People tend to reset the positions at extreme values by moving the camera, ground, characters, whatever else to zero in a way that the user doesn't realize this ever happened.

You have 7 significant digits of accuracy with floats, so at the extreme of 99,999 metres, you have 1 cm accuracy. The nearer to the origin you get, the more decimal places you get.

You can use double floats for increased accuracy if that's possible in your implementation. You'll have to be carefull though as commands which take a float will automatically reduce the precision without warning you.

Ah OK, I hadn't realised that was how it worked! I've never really delved into the accuracy side of things with DBPro before, it's quite interesting.

@ Quel: I've worked around it by making the user enter a value for the centre of each smaller worksite, where all the boreholes are clustered around a 100m area. This has solved the problem completely, so thank you. The program then just loads a different list for each worksite, which means everything in the project isn't displayed at once but it doesn't need to be.

Cheers guys!