Difference between revisions of "Engine Testing"
		
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
		
		
		
		
		
	
GoogleFrog (talk | contribs)  | 
				GoogleFrog (talk | contribs)   | 
				||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
# Type '!engine X' where X is the part after {BAR105}. At the time of writing X is '105.1.1-475-gd112b9e'.  | # Type '!engine X' where X is the part after {BAR105}. At the time of writing X is '105.1.1-475-gd112b9e'.  | ||
# If Nightwatch says 'Engine changed to X' then the engine was set successfully. See the heading below if it fails.  | # If Nightwatch says 'Engine changed to X' then the engine was set successfully. See the heading below if it fails.  | ||
| + | # Optional: Type '!game zk:test' to use the most recent version of Zero-K. Do this if there are unreleased fixes.  | ||
# Optional: Remove the password with '!password'.  | # Optional: Remove the password with '!password'.  | ||
# Not Optional: Do not change the game mode from Custom, this will reset the engine to default.  | # Not Optional: Do not change the game mode from Custom, this will reset the engine to default.  | ||
| Line 15: | Line 16: | ||
# Go back to the lobby, wait for everyone to indicate that they have completed the previous two steps.  | # Go back to the lobby, wait for everyone to indicate that they have completed the previous two steps.  | ||
# Start the game - for real this time (or maybe the second last time, because now you have to do the first-time ZK launch cache).  | # Start the game - for real this time (or maybe the second last time, because now you have to do the first-time ZK launch cache).  | ||
| + | # Play the game, or maybe test specific things.  | ||
# Note any weirdness, bugs, or performance issues on the battle thread or elsewhere.  | # Note any weirdness, bugs, or performance issues on the battle thread or elsewhere.  | ||
# Have everyone else in the room do the above.  | # Have everyone else in the room do the above.  | ||
Latest revision as of 02:08, 11 January 2022
Steps to test the engine[edit]
- Host a Custom room and set a password.
 - Check https://github.com/beyond-all-reason/spring/releases for the most recent version.
 - Look at the most recent release.
 - Type '!engine X' where X is the part after {BAR105}. At the time of writing X is '105.1.1-475-gd112b9e'.
 - If Nightwatch says 'Engine changed to X' then the engine was set successfully. See the heading below if it fails.
 - Optional: Type '!game zk:test' to use the most recent version of Zero-K. Do this if there are unreleased fixes.
 - Optional: Remove the password with '!password'.
 - Not Optional: Do not change the game mode from Custom, this will reset the engine to default.
 - WARNING skirmish AIs other than 'AI: Legacy' will not work as they need rebuilding for each engine.
 - Have people join the game, screw around in the lobby, etc.
 - Reassure everyone that it is fine if nothing appears to happen for many minutes when you start the game.
 - Start the game.
 - Wait for the engine to silently download in the background.
 - Have the game start, spend a while caching, and exit because you took minutes to connect.
 - Go back to the lobby, wait for everyone to indicate that they have completed the previous two steps.
 - Start the game - for real this time (or maybe the second last time, because now you have to do the first-time ZK launch cache).
 - Play the game, or maybe test specific things.
 - Note any weirdness, bugs, or performance issues on the battle thread or elsewhere.
 - Have everyone else in the room do the above.
 - Repeat
 
What if Step 5 Fails?[edit]
Two options:
- Ask GoogleFrog to load the desired release into the server.
 - Try a release further down the list.