Ringbuffer init fix #684
Merged
Ringbuffer init fix #684
Conversation
This file contains 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
|
I'll let it slide for now - but next time, don't combine separate changes to one commit Nice fix though - good work :) |
|
Sure. In this case the second fix was hidden by the first. But I understand. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Must reset read_ptr_index_ in CommandProcessor::InitializeRingBuffer becaue a game can initialize the ring buffer multiple times.
Left the new condition on the assertion as the value 0xFFFFFF seems to acceptable and it's preventing 4B4F07FE to go ahead.