Thanks, just wanted to add that I've been involved in using and enjoying emulators and cores for more than a decade and wanted to thank you for your contribution to the retro gaming scene!

@marukotenada the poster hasn't been here in 4 years - there's a slim chance it will reply back. Please don't bump old topics - open a new topic instead and explain your issue.

After playing with this quite a bit, I discovered that the controller becomes active as soon as the right trigger button is pressed. This seems very strange, but at least I know how to work with it.

@stevenhurwitt No, I don't.

@chizzer
We've all been there. In fact I just recently was scripting some batch file operations and introduced a space after something that broke it all. Gotta love those facepalm moments.

Glad you got it sorted now.

@greenhawk84 said in Jittery/Stuttering graphics:

games as MK2 on Mame2003

You should probably consider switching to FBNeo (or maybe a more recent version of MAME), nowaday our midway emulation is very accurate, as a matter of fact MAME2003 doesn't emulate shadows on MK2 while FBNeo does.

This diff should do the trick, clearing also any keyboard type controllers

diff --git a/es-app/src/main.cpp b/es-app/src/main.cpp index 26faeb2..26bc328 100644 --- a/es-app/src/main.cpp +++ b/es-app/src/main.cpp @@ -320,6 +320,9 @@ int main(int argc, char* argv[]) bool splashScreen = Settings::getInstance()->getBool("SplashScreen"); bool splashScreenProgress = Settings::getInstance()->getBool("SplashScreenProgress"); + //dont generate joystick events while we're loading (hopefully fixes "automatically started emulator" bug) + SDL_JoystickEventState(SDL_DISABLE); + if(!scrape_cmdline) { if(!window.init()) @@ -365,9 +368,6 @@ int main(int argc, char* argv[]) return run_scraper_cmdline(); } - //dont generate joystick events while we're loading (hopefully fixes "automatically started emulator" bug) - SDL_JoystickEventState(SDL_DISABLE); - // preload what we can right away instead of waiting for the user to select it // this makes for no delays when accessing content, but a longer startup time ViewController::get()->preload(); @@ -386,7 +386,10 @@ int main(int argc, char* argv[]) } } - //generate joystick events since we're done loading + //generate joystick events since we're done loading and clear the input event queue + SDL_PumpEvents(); + SDL_FlushEvent(SDL_KEYDOWN); + SDL_FlushEvent(SDL_KEYUP); SDL_JoystickEventState(SDL_ENABLE); int lastTime = SDL_GetTicks();

I don't think it's 100% correct, since any errors during startup would leave the joystick disabled, further testing is needed.

@folly said in Colecovision Start-Up Error: Turn Game Off Before Inserting Cartridge or Expansion Module.:

8afd7db2 root-beer-tapper-1984.rom
546f2c54 mr-do-s-castle-1984.rom
ef50e1c5 one-on-one-basketball-1984.rom

Those 3 are already supported, just different versions of the romsets (tapper, mrdo and 1on1). I added another bunch of coleco games today, i'll try to finish your list this week-end.

@mitu ahh ok, perfect, I'll give that a try today and hopefully that will work around the permissions.
Thanks again 😊

@sleve_mcdichael said in Duke Nukem 3D, expansions game saves saving to parent game's directory:

...that last one, /home/pi/.config/eduke32 is where files are being saved (I presume just because it's the one most recently added to the list?). Where is this coming from?

It's the default configuration folder for an application (i.e. $XDG_CONFIG_HOME/app).

Will this work like I think it does? Initially, it seems to. The logfile is saved to CWD so deleting it from there seems to work, also.

Yes, pretty much.

@koerty I think gaussian is the preferred option for most psx games for accurate sound emulation

@dsquared said in Can’t Save|Load Games Without Going Through Retroarch Menu:

I am trying to save my game play by using the select + right trigger combination.

Did you mean bumper?

Edit: I just looked at your GamePi case. That doesn't seem to have the full button layout. Do those buttons on the back correspond to L1/R1 (bumpers) or L2/R2 (triggers)? Default configuration (I see you are using a third-party image, so your mileage may vary) uses L1/R1 for quick load/save.

Ok thanks Mitu