And aren't computers and million times faster than the NES?
How hard would it be to pull the sprites from a ROM at startup, depixelize them, save them to a hashmap or something, and render them instead of the original sprites?
By the way, I think it would be impossible to implement such thing in an emulater without getting CPU use about 1 million times heavier.
gui.gdoverlay([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0])
gui.image ([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0])
gui.drawimage([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0])Putting bitmaps on top of background takes little processing power. If the depixelized sprites are indeed taken from the ROM and saved separately, this is pretty doable (with some code tweaks probably):There's even this: http://forums.nesdev.com/viewtopic.php?f=3&t=9935gui.gdoverlay([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0]) gui.image ([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0]) gui.drawimage([int dx=0, int dy=0,] string str [, sx=0, sy=0, sw, sh] [, float alphamul=1.0])
This looks great. https://youtu.be/NfqtOXZoyVo
Hay guyz, http://johanneskopf.de/publications/pixelart/ How hard would it be to pull the sprites from a ROM at startup, depixelize them, save them to a hashmap or something, and render them instead of the original sprites? Make emulators at movies beautiful.
Running the smoothing algorithm on the individual sprite chunks would likely result in suboptimal results, as the algorithm doesn't know where edges are supposed to meet.
It's generally impossible to tell beforehand how sprites are supposed to combine ingame without applying game-specific knowledge. If you try to run the smoothing algorithm on the combined sprites at runtime, you still might not know which sprites are supposed to go together, like when Mario overlaps with a goomba.
For better results, you will have to develop a game-specific solution, and apply the new renderer into your emulator of choice. It gets unweildy very quickly if you want to do it for more than one game. You may be better served by just enabling HQ2X on your games, but that only does so much.Is there a way to apply it to the final screen render?
How hard would it be to pull the sprites from a ROM at startup, depixelize them, save them to a hashmap or something, and render them instead of the original sprites?
+fsvgm777 never censoring anything.
You know. Just mainly because you completely avoided responding to a post that was especially made for you to respond to. Since, I don't want to repeat it word for word, with a quote and because it was actually dedicated to that discussion at that place, and you're bringing it up here once more, I'll just link my post here about the original discussion and wait for your response. Be sure to respond at the dedicated place which is where it all started, which is not this thread thanks.
You shouldn't need a degree in computer science to get into this hobby.
The original poster asked about changing the graphics of games, and I expressed my disapproval of it.
How hard would it be to ...
Everybody get naked. This shit is amazing: https://youtu.be/GSeLdQASixE
There's disagreeing with something and then there's beating people over the head with your disagreement until they agree just to shut you up. Take a moment to reflect on your actions and your experiences with the site and categorize yourself accordingly.
It'd be nice if games could automatically be rendered in Unreal Engine 4.
