|
|
| Reporter | grayman | Assigned To | grayman | |
|---|
| Priority | normal | Severity | normal | Reproducibility | always |
|---|
| Status | resolved | Resolution | fixed | |
|---|
| Product Version | TDM 2.02 | |
|---|
| Target Version | TDM 2.03 | Fixed in Version | TDM 2.03 | |
|---|
|
|
| Summary | 0003763: Loading bar progress should better represent actual progress |
|---|
| Description | The loading bar measures the number of bytes read from the filesystem as the mission loads, and compares that against the total expected number of bytes to be read.
The problem is that total bytes is a fixed number for all maps, since the first time a map is loaded, TDM can't know what's going to be read ahead of time.
The loading bars of large maps reach 100%, then the loading screen sits there for a very long time as the mission continues to load. Some maps make use of this time by posting tips, but for most maps the player just sits there waiting, with no feedback. |
|---|
| Additional Information | Rather than gauging progress using a total byte count that has nothing to do with what actually needs to be read, change to a progress-based system. Identify key points of the load process, find the times at which those points are reached, and construct a map of the loading progress.
Using 10 missions of varying size, average the key point times and use those averages to paint the loading bar as a mission loads.
Leave 5s after the loading bar reaches 100% to allow for the reading of any posted tips.
This method provides feedback to the player for the entire loading process (minus the 5s pause at the end), and is psychologically better than the present method. |
|---|
| Tags | No tags attached. |
|---|
|
|
