Notes |
|
|
I can reproduce this with 98d, but not with 98e. Can somebody try to reproduce this in the last official 98e beta build? |
|
|
|
|
|
|
Can you try to get a crash log using 3417? I only keep the debug databases for the official beta builds, so I can only use crash logs generated by them. |
|
|
|
In case you didn't notice, I uploaded a new crash report last night. |
|
|
|
Unfortunately the crashlog doesn't reveal the reason for the crash and I still can't reproduce it. Can you post your ini file? |
|
|
|
> Can you post your ini file?
Yes. |
|
|
(0002993)
|
Torr Samaho
|
2012-03-29 11:42
(edited on: 2012-03-29 11:43) |
|
Interesting. With your ini I can reproduce the crashes, but the debugger doesn't show what's happening immediately. So this seems to be a non-trivial crash. Can you check if the crashes happen for you with my ini (skulltag-no-crash.ini)? If they don't, it could be very helpful if we find out what's the difference between the two ini files that causes or prevents the crashes.
|
|
|
|
Hmm, your ini doesn't yield crashes naturally, but after entering "timelimit 0.1" into the server console it started to crash. |
|
|
|
Hmm, doesn't start to crash for me after entering "timelimit 0.1" into the server console. Did you change anything else? |
|
|
|
I'm having a hard time with trying to reproduce the crashes with your ini. But it crashed twice when following these steps. I don't follow these steps with my own ini.
1. Start the server.
2. "File -> Join server".
3. Add 4 bots.
4. "Settings -> Configure Server -> Visible to the public" uncheck.
5. "Settings -> Configure Server -> Visible on my network" check.
6. "timelimit 0.1" in the server console since it automatically changed to 0. |
|
|
|
Interestingly, the crashes don't seem to happen in possession only in teampossession. |
|
|
|
This was quite tricky to debug, but I think I figured out what was going on and fixed it. Please test if this fixes the problems. |
|
|
|
Impressive. It seems that you managed to fix the crashes.
BTW: I'm unable to set floating point timelimit values in the server dialog "Settings -> Configure server... -> Gameplay". So if you have float value set, the value will be rounded off when you configure your server. |
|
|
|
This should take care of the problems in the server window. |
|
|
|
It did. How come the timelimit is always updated whenever you configure your server if timelimit is 0.1, but not when it is 0.5? |
|
|
|
It was a numerical precision problem. This should take care of it. |
|
|
|
It took care of it. All the issues here should now be resolved. Good job. |
|
|
|
I'm glad to hear that :). |
|