MantisBT - Soldat |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000323 | Soldat | Graphics | public | 2013-06-18 14:23 | 2015-04-15 19:28 |
|
| Reporter | rzaba | |
| Assigned To | Shoozza | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | x86 | OS | Windows | OS Version | 7 |
| Product Version | 1.6.3 | |
| Target Version | | Fixed in Version | 1.6.9 | |
|
| Summary | 0000323: Starting single player game a few times causes FPS drop |
| Description | When you start a single player game a few times you can notice a slight FPS drop. This makes the game unplayable on slower computers. |
| Steps To Reproduce | Open Soldat and start a single player game. Leave it and start a new single player game. After doing this about 4/5 times you will notice that the frame rate is lower than usual. |
| Additional Information | In my case the frame rate changes from 60 fps to ~40 fps. If you have a fast computer, you will have to disable FPS limit or set it to a higher value in the soldat config (on a fast computer Soldat runs at let's say 200 fps; if you try to reproduce this bug, the frame rate should change to about 170-180 fps; if you enable the FPS limit, you won't notice any difference, unless you set the FPS limit to a higher value than the default (60 fps)). Restarting Soldat will solve the problem. |
| Tags | No tags attached. |
| Relationships | | related to | 0000160 | resolved | Shoozza | High CPU usage when quitting while map chages and rejoining | | related to | 0000333 | resolved | Shoozza | Memory crash | | related to | 0000520 | resolved | Shoozza | Stacking CPU when entering/exiting games |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2013-06-18 14:23 | rzaba | New Issue | |
| 2013-06-25 13:51 | Falcon | Status | new => acknowledged |
| 2013-07-07 20:01 | Shoozza | Note Added: 0001750 | |
| 2013-07-07 20:37 | Bistoufly | Status | acknowledged => confirmed |
| 2013-07-07 20:37 | Bistoufly | Product Version | 1.6.4rc2 => 1.6.3 |
| 2013-07-07 20:38 | SyavX | Note Added: 0001754 | |
| 2013-07-07 20:43 | Bistoufly | Relationship added | related to 0000160 |
| 2013-07-16 21:32 | SyavX | Note Added: 0001764 | |
| 2013-07-31 10:52 | skoskav | Relationship added | related to 0000333 |
| 2013-07-31 10:55 | skoskav | Relationship deleted | related to 0000160 |
| 2013-09-13 23:51 | SyavX | Note Added: 0001923 | |
| 2014-02-15 11:16 | skoskav | Relationship added | related to 0000520 |
| 2014-04-02 15:50 | homerofgods | Relationship added | related to 0000160 |
| 2014-05-02 11:31 | homerofgods | Category | Gameplay => Graphics |
| 2015-04-15 19:28 | Shoozza | Status | confirmed => resolved |
| 2015-04-15 19:28 | Shoozza | Fixed in Version | => 1.6.9 |
| 2015-04-15 19:28 | Shoozza | Resolution | open => fixed |
| 2015-04-15 19:28 | Shoozza | Assigned To | => Shoozza |
|
Notes |
|
|
|
Does this also happen in 1.6.3?
Or is this a new bug which was introduced in 1.6.4 beta/release candidate versions? |
|
|
|
(0001754)
|
|
SyavX
|
|
2013-07-07 20:38
|
|
Reproduced this in 1.6.4RC2 and 1.6.3
FPS drop is a side effect of high CPU usage "jump" that started after few (it was 4th for me) rejoin into single player game (there were 2-3 bot ingame).
CPU load stays high even after quitting into main menu.
Tested with windowed mode only (may test with fullscreen later). |
|
|
|
(0001764)
|
|
SyavX
|
|
2013-07-16 21:32
|
|
|
Reproduced this in 1.6.4RC3 too |
|
|
|
(0001923)
|
|
SyavX
|
|
2013-09-13 23:51
|
|
|
Reproduced this in 1.6.6 beta1 too... |
|