Fix double-scanning & pixel-doubling handling in openglnb
output mode
#3092
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.
Description
The adaptive CRT shader always forced single-scanning in
openglnb
output modes which was wrong (e.g., 320x200 content always appeared single-scanned). This fix corrects that. See the updated comments block for the fixed double-scanning/pixel-doubling criteria.The issue was reported by @SmilingSpectre and mmpp0 on the eXoDOS Discord.
Manual testing
log_display_properties()
insdlmain.cpp
to log the actual rendered dimensions as well.opengl
,openglnb
,texture
andtexturenb
for all VGA modes in Deluxe Paint II (both visually and by looking at the debug logs; 320x200 modes should result in 640x400 render dimensions for VGA).output = opengl
+glshader = none
special case results in doubling for VGA modes (i.e., 640x400 render dimensions for 320x200 modes).output = openglnb
+glshader = none
special case results in no doubling for VGA modes (i.e., 320x200 render dimensions for 320x200 modes).Checklist
Please tick the items as you have addressed them. Don't remove items; leave the ones that are not applicable unchecked.
I have: