| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000727 | Spring engine | General | public | 2007-12-23 16:04 | 2007-12-28 19:58 | ||||
| Reporter | redstar | ||||||||
| Assigned To | Auswaschbar | ||||||||
| Priority | normal | Severity | major | Reproducibility | sometimes | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000727: Spring stops rendering under certain conditions | ||||||||
| Description | Running NTai under svn spring generates a bug where spring stops rendering to the screen and refuses user input or taking focus. When running NTai through a debugger I could see that the game simulation had not stopped, and NTai went on to play the game for 4 hours after the bug had occurred, generating game events that couldn't have occurred if it was a recursion bug in NTai. Argh reports the same bug. | ||||||||
| Steps To Reproduce | Run NTai with svn spring. I've experienced this in XTA and argh in P.U.R.E | ||||||||
| Additional Information | Possibly the windows event queue is not being handled correctly. Attempts to access the spring window itself failed, the only way to show it was to minimize other windows covering it. Key presses and mouse activity was ignored by spring. NTai logs show 4+ hours fo gameplay, which ended when I decided to turn ti all of and go to sleep. The bug itself occurs usually around the 20 minute mark. Peet had a similar issue only he found that increasing the speed to 20x gave the issue. I run at 3x speed in my NTai tests. | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Auswaschbar (reporter) 2007-12-28 19:58 |
This could have happened when the server runs faster than the client, so it was stuck in an infinite ClientReadNet <-> SimFrame loop. I added a timer so this should not happen anymore. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-12-23 16:04 | redstar | New Issue | |
| 2007-12-28 19:58 | Auswaschbar | Status | new => resolved |
| 2007-12-28 19:58 | Auswaschbar | Resolution | open => fixed |
| 2007-12-28 19:58 | Auswaschbar | Assigned To | => Auswaschbar |
| 2007-12-28 19:58 | Auswaschbar | Note Added: 0001568 | |
| Issue History |