HaxeFlixel / HaxeFlixel/flixel-addons
FlxScreenGrab doesn't match PrintScreen results
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 196
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
In a customized version of crashdumper, I dump a screenshot on crash, using FlxScreenGrab.
Here's FlxScreenGrab's output:
Here's the system's native PrintScreen:
The FlxScreenGrab image's tileset has little artifacts in it -- perhaps because I'm using the "tileset smear trick" where you add borders to each tile to avoid cross-tile bleed. Also note that the flixel-ui elements are arbitrarily offset from the native screenshot.
FlxScreenGrab just looks like it does a naked draw dump from the stage, so how is this discrepancy even happening? It should be using the same draw logic as everything else, right?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating FlxScreenGrab and compare its screenshot output with the native PrintScreen result described in the issue, including the tileset artifacts and offset flixel-ui elements. Done means identifying the cause of the rendering discrepancy and confirming that captured images match the expected on-screen rendering.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100