![]() ![]()
mamearcade64 rtype -rompath /path/to/roms/ mamearcade64 pacman -rompath /path/to/roms/ Trying to run two games in a row followed by just the binary without any switches would look like the following: > the built-in front end), or quitting out of MAME and then running it again?įor clarification: I'm not using the built-in UI, just running MAME in single shots from Terminal. > To clarify: the problem is running multiple games per MAME session (exiting back to I've seen build issues on this machine before (usually when I've done something dumb), but never anything like this. #Mame emulator for mac sierra pro#I'm on a late-2011-era I7 MacBook Pro (8,2) that I've had since, well, late 2011. > the latest developer beta) and I'm having no problems. > I'm doing active MAME development on my 2013 i7 MacBook Air running Sierra (actually To clarify: the problem is running multiple games per MAME session (exiting back to the built-in front end), or quitting out of MAME and then running it again? I'm doing active MAME development on my 2013 i7 MacBook Air running Sierra (actually the latest developer beta) and I'm having no problems. Re: MAME 0.182 only runs once under macOS Sierra (10.12.3) Played Pac-Man once without issue, then had exactly the same symptoms as under 0.182.Īm I the only one experiencing this issue? It's just bizarre. Totally clean makefile - just did `make SUBTARGET=arcade -j8` after extracting the source. Dumb move on my behalf, but that's my fault.Īnyway, I figured I'd mention this in case it's useful.īuilt 0.181 for comparison got the same result But if I'd run it a second time I would have known not to overwrite. Unfortunately, I overwrote my 0.181 binary with 0.182 because on first run my 0.182 binary looked good. I built MAME 0.182 after the 10.12.3 update, and I don't believe that I ever ran the 0.181 binary after that update. The binary for this had been built under Yosemite (10.10.5, IIRC I skipped El Capitan entirely). #Mame emulator for mac sierra manual#Now, one of the few things that was brought over from manual backups was MAME 0.181. No Time Machine recoveries, no 'let's sync your Mac' stuff. When I say 'clean install', I mean it: it was a total reinstall of the OS and applications from scratch. #Mame emulator for mac sierra install#I did a clean install of 10.12.2 about three weekends ago. This hadn't occurred to me when I made the original post, but it may be relevant. > Unfortunately, I don't recall if I ran 0.181 after that was installed or not, so ![]() #Mame emulator for mac sierra update#> that's changed is that the 10.12.3 update to OS X was pushed down recently. > 0.181 was running fine on here a few days ago. Re: Just realised something that may be worth mentioning. There is no error log for the botched run - MAME didn't generate one, so no point in attaching a zero-length file Commandline for each run was `./mamearcade64 pacman -rompath /path/to/roms/ -v -log` this was straight from the build directory on a fresh build from clean source. Has anyone else seen this behaviour? It's really odd and I'm wondering if this isn't down to a change Apple made rather than something to do with MAME. Unfortunately, I don't recall if I ran 0.181 after that was installed or not, so can't give a direct comparison. About the only thing I can think of that's changed is that the 10.12.3 update to OS X was pushed down recently. file causing an issue.ĭownloaded the official 0.182 binary from and got the same result, so doubt that it's my build environment.Ġ.181 was running fine on here a few days ago. so this likely isn't a case of an older configuration, NVRAM, etc. Note that I have been testing out of 'clean' directories with fresh configs, etc. You get one successful startup and that's it. It doesn't seem to matter what the test game is, or the one that is specified on subsequent launches. However, attempting to start any game after that initial test run results in a black screen with the pointer on top of it (the pointer is controllable), and I have to force quit the emulator with CMD-OPTION-ESC in order to get out of it. My usual quick test to see if I have a functional binary post-build (`mamearcade64 pacman -rompath /path/to/roms`) works fine: Pac-Man starts up, coins up, and plays with controls and audio. MAME builds fine - no errors, no warnings. MAME 0.182 only runs once under macOS Sierra (10.12.3)īuild environment: OS X Sierra (10.12.3), Xcode 8.2.1, clang-800.0.42.1, SDL is installed as native frameworks (both 1.2.15 and 2.0.5), and SUBTARGET=arcade is set at build time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |