bai: hah, those are good
bai: it's easy enough to add -confirm_quit 1 to the list of arguments in Emularity
that's what I hoped but when I try it causes it to abort, heh
I'm probably doing it wrong
heh
https://pastebin.com/gvxJN81u
does that look right?
yep
weird
seems like any args will do it
we're already passing in a dozen or more things; what's two more?
oh I see what the problem is, its not "-confirm_quit 1" it's just "-confirm_quit" and then the "1" is being treated as the rom name, heh
lol
and the other arg I tried wasn't working because I misremembered it
details
bbiab
computers should just automatically know what I want and do it!!
agreed!
oh right derp
works well, might be nice that it pauses when you hit esc to drop out of fullscreen or release the pointer lock
only weird thing is that the last frame stays on screen after you exit, so it just feels like it hung
bai: that's precisely what the code enforces.
(I was looking at your links last night)
it's that whole pausing functionality.
yeah. we could probably detect when the emulator exists in Emularity and blank the canvas or do whatever
bai: It's pretty wild your working inside the actual MAME project.
The Vice code that I'm fixing is all new unfinished code.
Thing is once this works I have to do it all over again for 3.1.
we try to keep our footprint in the mame code to a minimum, but I think by now the work of convincing people it's a valid platform has paid off, and now they just want to see the code get a little less hacky
But this is worth it because this project *worked* in the browser. It worked but no where near the state as the release on github. This repeats a 2d cad program port I consulted on. They didn't give me the latest source because they obviously didn't want me to steal out.
s/out/it
bai: interesting!
The magnetic/gravitional properties of this network/channel make me perform at least one typo in every output.
also, interesting fact - mame running in my brower is significantly faster than native mame running in the virtualbox vm I use to compile it
I dunno whether to be surprised, angry, or nonplussed about that
bai: bizarre. webassembly or asm.js?
bai: That speed difference will most likely be dependening on the repeition of the most used inner loops of main switch case. Perhaps time retrieval to determine screen syncs is vastly different between the platforms. I'd put some cout/printfs of how time computation is handing at those points.
wasm build. I think it's most likely just that virtualbox's video drivers are particularly crappy
sad that in 2017 we still can't use virtual machines for anything involving graphics
bai: It's been like that from the begining of emulation. Even Desqview in 1991 provided multitasking. But it was dog slow. But that was mostly because of RAM and a little bit of an overburndened CPU.
bai: The cause could be a compbination of drivers and how the host OS handles updates.
At this rate... I know WebGL will require at least another 10 years before anything serious under the browser.
It all comes down to how state is managed. If state were completely functional we'd be able to offload processing to other cores.
Redux in Javascript tries to do this. But in affect it's just a link list of states.
Of course graphics at various times are sequential mostly but the common tools for older systems were rectangular invalidation and off screen rendering before swapping to visual video memory.
Vice 3.1 does an awsome job for the c64. The sprite blur doesn't flicker as it did in early versions. And the sprite 'blur' is damned near perfect rendition of a stock c64.
;D
bai: My firefox 52.2 has javascript.options.wasm = false. Time to upgrade.
yeah sounds like it. both chrome and ff toggled wasm on by default a couple months back
yeah, i was just doing a little webasembly. nice stuff.
you can still use it under 47+. just flip the switch.
pull request accepted!
I was hoping to slip in some additional changes but they were too quick, so I've opened another pull request to export that new functionality - https://github.com/mamedev/mame/pull/2479
congrats
second one was accepted too
so we can now save and load states or reset/exit via the JS API
if there's any other functionality which would be useful to trigger from the js just let me know and I'll look into that too
hey!!
can you compile jaguar and the other wasm tests in the new flow/revision?