Open torch2424 opened 5 years ago
Found out screen tears were not a canvas issue, definitely an issue on the wasm end. Made a branch to test and make screenshots of the actual image data and then place into a canvas and got some tears:
Actually screen tears were from graphics timing
Not sure if you're looking for bug reports ;-) Donkey Kong Country has some interesting bugs. There's about a 90% chance of items not appearing when they're supposed to, so sometimes if you leave an area and come back, things will appear that weren't there before. In Pokemon Silver, Marill's graphics right at the beginning of the game don't show up right. Bionic Commando has some fun graphics and audio errors. There's kind of a crawling tear in the screen, but it's fairly subtle. The audio seems lower-pitched than it should be. The first two issues are perhaps related to interrupt timing, or maybe to the times that writes to the graphics hardware should succeed or fail. The screen tears are probably a lack of double-buffering. The sound could be an issue with wavelength calculation, or something. It might be that the whole emulation is a bit slow? Or maybe it's just my machine? That browser tab pretty close to pegs a core.