|
2008-11-02 02:50
|
screen0021.jpg (50,483 bytes) |
|
2008-11-02 02:50
|
screen0024.jpg (59,802 bytes) |
|
|
The Knightly builds don't contain the code for that, so I highly doubt they actually got the same message. :) The user count check in the new code is broken though. It will be fixed in the next test build (need to verify some of these new fixes for your bug reports before commit). |
|
|
Well basically they said stats weren't saving in the latest builds so they reverted to using older 3.6.10 builds. If the host accepts stats before the client he doesn't see the message for why the stats didn't save since it goes right back to the forming stage. So there may be 2 different problems causing stats not to save then. I take it the system in the multi_test will override the existing one when committed so if it is fixed then we should be OK. |
|
|
Well the new code does require that you accept the stats before it will send them to the server. This is required of all involved though, if using the newer code, since it will only send each persons stats after they have accepted. Knightly builds are still using the old code, so it's just multi_test build or the multiplayer test build I posted that have the new code. Knightly, and other builds based on the old code, still save automatically as soon as the debrief window loads. For logging purposes though, the new code does print out to the multi.log file whether stats saved or not, if it even gets that far. But you do point out a possible bug that I need to look into however. The new code is supposed to give the client a chance to save stats or not before taking them out of the debrief, whether the host initiates the debrief exit or not. It's possible that part of the new code simply isn't working like I thought, which could explain the problem in the new code builds. I'll give it a look and include any fixes in the next test build. |
|
|
It does give the client the chance to save them. It's only the message they can't see. Basically it moves so fast the clients sees the stats saved failed message but can't see the reason why. I would assume this only happens to the last client to hit accept since it jumps back to the forming menu then. |
|
|
Fixered. |
- Anonymous
