[00:15] So, this is not doing the trick. [00:15] But there's a lot of reasons it's potentially not doing the trick, so I'll continue my death march [02:07] Watched some shows, now back on the games. [02:07] I'd be interested, balrog, if there are other things beside -nodrc [02:08] I get this in my crash log [02:08] Uncaught RuntimeError: null function or function signature mismatch [02:08] at 04fbbb42:0xf6a97 [02:08] at Object.Module.__ZN13sound_manager4muteEbh (mameseattle.js.gz:1) [02:08] at MAMERunner.value (loader.js?v=d8c2b936:1163) [02:08] at loader.js?v=d8c2b936:1685 [02:08] is that unrelated? [02:08] I think that's sound with the loader and the browser. [02:08] I THINK they all do that [02:09] what is the usual way to get the ingame menu? [02:11] The what? [02:11] Oh, tab [02:13] thanks. [02:17] I finally have a nodrc test! [02:20] (Run Puppy, which has a very small load.) [02:23] { [02:23] "name": "Run Run Puppy", [02:23] "arcade": "1", [02:23] "bios_filenames": [ [02:23] "" [02:23] ], [02:23] "peripherals": [ [02:23] "" [02:23] ], [02:23] "native_resolution": [ [02:23] 320, [02:23] 240 [02:23] ], [02:23] "extra_args": [ [02:23] "-nodrc" [02:23] ], [02:23] "driver": "runpuppy", [02:23] "wasmjs_filename": "mamekonamigs.js.gz", [02:23] "wasm_filename": "mamekonamigs.wasm.gz", [02:23] "file_locations": { [02:23] "mamekonamigs.wasm": "mamekonamigs.wasm.gz" [02:23] } [02:23] } [02:23] so, there, everything looks cosher. [02:23] kosher. [02:24] ncaught (in promise) 39105096 [02:24] In the log: [02:24] drc_cache: RWX pages supported [02:25] So, I don't know what's going on there. [02:27] how can the log be accessed? [02:27] Console log in your browser. (Dev tools, in chrome and brave and edge) [02:27] I was there, but it wasn't clear if it was that helpful [02:27] It's all we got [02:28] Looking in 32x, which we had some time ago, the settings are definitely: [02:28] "extra_args": [ [02:28] "-nodrc" [02:28] ], [02:39] So, again, a lot of them are missing vital ROMs, that's something I'm stepping through and it's curing a bunch [02:49] so the uncaught in promise thing is basically just a crash and provides no useful information beyond that, rebuilding with SYMBOLS=1 would give more useful info in those cases [02:59] So, to help us nail things down, after I've done the walkthrough and gotten all the promise ones, I'll get the mame drivers for them in a column. [03:04] OK, I [03:04] 1. Added a DRIVER column [03:05] 2. Sorted it by the DRIVER column [03:05] That will start to show patterns. [03:16] DFJustin: would a SYMBOLS=1 build still be small enough to work? [03:16] also, DEBUG=1 might catch some of these hangs and turn them into crashes [03:16] (due to asserts) [03:20] By the way, example: A set of these are vector items that simply never got resolution set. [03:20] So they implode. [03:35] yes it will still be small enough to work (but big) [08:28] *** Sgeo has quit IRC (Read error: Connection reset by peer) [14:34] *** Sgeo has joined #jsmess [14:47] DFJustin: cool [16:12] Another bundle working [21:06] So, it's clear all the Seattle-drivers crash. [21:07] Like, even with nodrc. [21:07] So I'm going to recompile that driver with DEBUG=1 and SYMBOLS=1 [21:56] So, this is interesting. [21:56] Oooo. [21:58] If you build with debug it tacks on a d to the driver. [21:58] Nice [23:14] OK, so, here's new data. [23:14] I compiled seattle driver with the stuff and I've run it against blitz99 [23:14] Here's some relevant lines: [23:14] rc_cache: RWX pages supported [23:14] drc_cache: RWX pages supported [23:15] Build defines 1: LSB_FIRST=1 MAME_NOASM=1 MAME_DEBUG=1 [23:15] Starting NFL Blitz '99 (ver 1.30, Sep 22 1998) ':' [23:16] Orphaned streams: [23:16] loader.js?v=d8c2b936:1052 CD/DA ':pci:09.0:ide:1:cdrom:cdda' [23:16] loader.js?v=d8c2b936:1052 CD/DA ':pci:09.0:ide2:1:cdrom:cdda' [23:16] CHS: 4088 16 63 [23:16] arcade_blitz99:1 Uncaught (in promise) 51324816 [23:16] So, yeah, crash [23:20] I'll continue work on the other drivers