Move damage algorithm

[allegro]

Instead of having to issue a new client version to change the damage calculations, why not move that processing to server-side and just have the client report data like VS on touchdown?

[DaKurt]

I don't think that's possible with mysql. another problem would be that we would have even more traffic here (imagine you land on grass an make, lets say, 10 little "jumps" you would have to send 10 times this value). It's much easier to put it in the client. We use Visual C++ which is much faster and more flexible in calculations like that...why would you prefer it another way? I think with 0.6.4b works quite fine till now, doesn't it

[DaKurt]

imagine the case that we would want to make an update where very high g-forces in flight would damage your aircraft's hull. Well we would have to send every second some data to the server?! I don't think that would be a good solution

[allegro]

Of course not, you would record the data in the client and then upload it all at once at the end of the flight.

[CAPFlyer]

Sorry dude, but your asking to upload several megabyte-sized filed in the end because what you're ending up doing is essentially creating a flight data recorder that downloads at the end of the flight to the maintenance server. That's a lot of data and a lot of server load that doesn't exist. You're wanting to trade a really minor load on a person's computer (once the tracking information is optomized) to a server-side application where the limited resource is the server. As has been mentioned in other threads, this program is skirting on the limits of the bandwidth limits of the current hosting plan and because of that, we're having all of these "Error 500" problems. If we dump more load on the server and bandwidth, it will only cause MORE problems. Why would we want to do that?

[DaKurt]

thank's for the great explanation CAPFlyer