Hey Nick!
I was playing around with the online emulator, and I figured out the parameters to make the output window of the online emulator match that of cuzebox running locally pixel for pixel.
Here is the first part (changes to emu.css):
Code: Select all
--- emu.css 2023-02-14 00:00:49.758325274 -0500
+++ /home/user/emu.css 2023-02-13 23:57:43.914320594 -0500
@@ -193,7 +193,7 @@
html {
max-width: 1200px;
- width: 940px;
+ width: 988px;
margin: 0 auto;
/*scroll-behavior: smooth;*/
/*font-family: "Times New Roman, Helvetica, serif";*/
@@ -336,7 +336,7 @@
#emu_gameSelector {left: 5px;top: 40px;width: 320px;height: 120px;z-index: 100;}
#emu_gameFiles {width: 320px;height: 130px;position: absolute;top: 170px;left: 5px;z-index: 18;padding: 0px;border-radius: 5px;overflow: hidden;}
#emu_onscreenGamepads{width: 320px;height: 290px;position: absolute;top: 310px;left: 5px;z-index: 18;}
-#emu_emulator {left: 335px;top: 40px;width: 580px;height: 490px;overflow: hidden;/* background-color: #346cda; *//* background-color: black; */}
+#emu_emulator {left: 335px;top: 40px;width: 630px;height: 490px;overflow: hidden;/* background-color: #346cda; *//* background-color: black; */}
#emu_emulator .sectionWindow_content{/* background-color: #22205c; */position: relative;top: 0px;left: 0px;}
#emu_view_uam{
@@ -883,8 +883,8 @@
background-color: #0c0a38;
/* background-color: #070707; */
margin-top: 5px;
- width: 570px;
- height: 460px;
+ width: 620px;
+ height: 456px;
}
.verticalAlign {
And then I had to go in with Firefox's HTML Inspector, and manually edit both of the height and widths in the active canvas line to say:
Code: Select all
<canvas tabindex="0" id="emuCanvas" org_width="310" org_height="228" style="width: 614px; height: 452px;" width="614" height="452"></canvas>
I tried finding that in the original HTML, but I didn't see it there, so I'm not sure how to fix that canvas size properly.
And once those two sets of changes are made, the online emulator matches pixel for pixel with a local cuzebox instance (after you press F3 to disable the debug view, and then press F4 twice in a row to force cuzebox to properly resize its window).
Oh, and I like to link people to the online version of my games, do you think it would it be possible to make good quality with flickering disabled be the default, so the games look as intended by their developers?
The Flicker feature in cuzebox makes the games not only run slow, but it also makes games that don't need it look terrible. Maybe the proper way would be a bit flag stored in the database that indicates whether a game would benefit from flickering, otherwise default it to off? Just some stuff I've been thinking about. (Oh, and way back in the beginning of this thread Jubatian said that it should probably be disabled by default, since no games in existence currently require it.)
Edit: Though no matter what I do, it runs super slow for me on a Core i7 desktop machine. Using the latest Emscripten, I compiled cuzebox myself and loaded it locally on a web page, and it runs at native speeds, so I'm not sure what might be causing the slowdown. I thought it might be a shadow effect, but I turned that off and it didn't make a difference. Let me know if I can help debug the speed issue!