Loading...
  OR  Zero-K Name:    Password:   

Simple Map Loading Bug Test

6 posts, 1154 views
Post comment
Filter:    Player:  
sort
I have not seen any useful information regarding the map loading time problem with 96.0. This is because I have not been able to talk to anyone who has the problem for long enough to get them to test anything. Hence this thread.

Could everyone who has the problem please do the following. These instructions are for the ZKL folder structure.
  • Make sure that no lobby program is running.
  • Look in ...\Documents\My Games\Spring
  • Move the folders 'maps', 'packages', 'pool', 'games' and 'cache' somewhere else. You may not actually have a games folder, this is ok.
  • Create two folders 'maps' and 'games'.
  • Download zk-v1.2.1.0.sdz from http://packages.springrts.com/builds/ and put it in 'games'.
  • Move a map (preferably one you have had a problem with) from the maps folder you removed and into the new maps folder you just created in ...\Documents\My Games\Spring.
  • Go to ...\Documents\My Games\Spring\engine\96.0 and run spring.exe.
  • Select a game and a map. There should be only one thing to select from each of the menus, if there is more than one option then something has gone wrong.
  • Press "Test the Game" and report upon the loading time as well as the time spent pathing. Timing this accurately could be useful.

To fix your install simple delete the new 'maps' and 'games' folders and put the ones moved at the start back where they used to be.


There are some permutations on this test which would be useful to try. Remember to run through the full procedure on each test. It is especially important to remove 'cache'.

Try a different game. Download ba-V7.78.sdz from http://packages.springrts.com/builds/ instead of zk-v1.2.1.0.sdz.

Try a different engine. Instead of running 96.0 try running 91.0. It can be found in ...\Documents\My Games\Spring\engine\91.0.
Also try the latest engine develop version. It can be obtained automatically by joining the BLEEDING EDGE room.

Try a different map. Run the test with a very large map (such as http://zero-k.info/Maps/Detail/7385 ) or a very small map (such as http://zero-k.info/Maps/Detail/28633 ). If the small map loads very quickly but the large map takes a long time then it indicates that pathing is at fault.

DErankAdminmojjj 's edit: fixed links.
@KingRaptor: added more details
+4 / -0
Skasi
10 years ago
You could try yourself. If you didn't experience the problem yet, check out large maps such as Glacier_Plateau-v03.
+0 / -0


10 years ago
quote:
Try a different engine. Instead of running 96.0 try running 91.0. It can be found in ...\Documents\My Games\Spring\engine\96.0

I think you meant

...\Documents\My Games\Spring\engine\91.0

?
+1 / -0
I have performed a test both on Linux and on Windows and can not reproduce the issue in this way. The thing happened also to me a couple of times while playing/speccing, but even then the time was acceptable (although longer than I would expect).

On Linux I computed the time using "time" and letting the game exit automatically. The below times for Linux are with the 10s autoquit substracted (but they will be a bit higher than windows as they include AI initialization for example).

Computer: i7 with 8GB RAM
Linux (Arch 64 bit) times:
- 0.96 Epic, not cached : 46s
- 0.96 Epic, cached : 18s
- 0.91 Epic, not cached : 41s
- 0.91 Epic, cached : 41s (the UI appeared very fast, but the game exited very slow)

Windows (Win7 64 bit)) times (using an external chronometer):
- 0.96 Epic, not cached : 46s
- 0.96 Epic, cached : 10s
- 0.91 Epic, not cached : 47s
- 0.91 Epic, cached : 13s

Did tests also for http://zero-k.info/Maps/Detail/26020 (this is much larger than the ones mentioned before)
- 0.96 Epic, not cached : 47s
- 0.96 Epic, cached : 33s
- 0.91 Epic, not cached : 34s
- 0.91 Epic, cached : 17s
+1 / -0


10 years ago
Bumping in light of latest thread.
+0 / -0
10 years ago
Am I the only one who has not had this problem? I am running on Xubuntu 12.10 32 bit if it makes a difference.
+0 / -0