15.03.2015, 10:21
1.) It really doesn't really matter Bullet uses an very efficient method to do this.
2.) The collision binary would have to be rebuilt this is automatic and not an issue. Reading the data directly is possible however there needs to be work done before that data can be used. Primarily the work is creating the lists of collision object positions. Given that it takes time to create the collision objects in Bullet building the binary will save a lot time.
3.) 6000x6000 is only 36000000 raycasts the amount of objects does not matter this would take approximately 4 minutes.
It really depends on the server ColAndreas is much slower on Windows for me but our dedicated server can do 160000 raycasts per second.
2.) The collision binary would have to be rebuilt this is automatic and not an issue. Reading the data directly is possible however there needs to be work done before that data can be used. Primarily the work is creating the lists of collision object positions. Given that it takes time to create the collision objects in Bullet building the binary will save a lot time.
3.) 6000x6000 is only 36000000 raycasts the amount of objects does not matter this would take approximately 4 minutes.
It really depends on the server ColAndreas is much slower on Windows for me but our dedicated server can do 160000 raycasts per second.