test(mismatch): Debug Build for debugging mismatches #1750
+52
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
helmutbuhler
added
Experimental
|
Can we close it now that the targets have been built? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The build in the CI here is intended to make it easier for playtesters to generate replays and log files that can be used to debug mismatches.
A messagebox at startup explains this build a bit:
Technically, this build enables debug and debug crc logging and puts that log file next to the replay in case a mismatch happens. It also does a crc check every frame instead of every 3 seconds (default). Luckily, this interval is decided by the host, so retail players can still play with players using this build.
It's important to select the vc6-releaselog build in CI for this to work! (The other versions will show an error message)