ckp

So @SentaiBrad, what does it pull? Does it pull game specific videos for the games you are importing, or platform videos? Or both?

Oh, then now it's even more confusing if it pulls from EmuMovies, since this checkbox is not even on the dialog for EmuMovies art selection, it's on the dialog before that one for LB DB.

I was afraid it might really be something like that, so I never check that box off thinking it might overwrite something I already use. This seems like a confusing place for this, or at least the way it's presented seems confusing to me. @SentaiBrad, I don't have a screenshot right now but you can't miss it if you just import a game by drag and drop and look at the last item where you select which art you want (like box front, clear logo, etc).

When importing games I see this optional checkbox on the 'download images for your games' screen in the wizard. What is it supposed to do?? Download a video for the games you are importing? Theme? I have no idea.

Sure, that's great. I think some of your xml file(s) got trashed or were wrong for some reason, like maybe you moved LB or games or emulators at some point.

i just noticed if yuo run project64 emulator gui, you always gets a popup asking for support. in the program files, open Config>Project64.cfg and set the run count to -1. this will get rid of the nag

Might try deleting the emulator in LB and readd it.

That should be the default LB emulator way of doing it, use full path. As a test try putting that rom in c:\temp and update the game location in LB

did you try this?

just open a cmd.exe window. change to your project64 app, like using: cd /d "R:\emulators\project64" (then press enter) then type project64 followed by your rom file with full path to start with: project64.exe "r:\roms\n64\mygamefile.n64" (then press enter) replace paths and file name with yours. the game should launch. that's how LB does it. if it doesn't work, you can try changing the full path with rom file name to just the rom file name only.

you might also try going to the edit game window and browsing for the actual rom even though it's filled out anyway, find your rom , select it, and ok out of the window and try it. this will ensure the game and path is right just in case something got messed up.

Well, however you construct your command line to launch the n64 game with project64.exe, it should work in LB if you make sure the command example looks the same in the emulator edit window. So, I'd suggest you try to launch a n64 game from command line to see if that works and then match it to LB.

What if you uncheck the extract rom setting in the LB emulator settings?

are you running project64.exe as admin by any chance?

i'm not by my LB right now, but aren't n64 roms in .zip format?

now lets see a screenshot of one of your games by right click and choosing edit game. show the default window that comes up AND the emulation tab in it.

what i'd like to see is the screenshots for Launchbox (described in my post above), since you already mentioned things work ok from your emulator alone.

also, do you have any additional applications set for the games in LB or in the p64 emulator ahk tab?

you should post screenshots of one of the games that fails to run (right click edit screen) and a screenshot of your emulator settings (manage emulators, edit emulator).

I had focus problems like that until i set Big Picture setting to run in Windowed mode.

@Beastachu , does it work outside of LB just using the emulator alone? That might be a good starting point.

I haven't seen the UI for this, but it could be kept simple and have the OR ability. Like, many apps I've seen with search filters just have a drop list selection for the filter condition that defaults to ALL (which it sounds like is the current behavior) selection, with the ability to select ANY for the filter condition, so that if you select ANY, it means any of the filter items that match are a hit (OR-ing). Edit: here is an example screenshot of the filtering I'm describing:

Yeah, it's not really the nomousy part that was a problem for some people that reported this. It was just that for some time things were working just fine using the Close process script on exit, but only in the last version or versions it caused this new problem for some people for some reason. Using the line below instead for Demul as discovered by llhanK seems to have cured this more recent issue. Maybe it's related to OS and/or controller used, I don't know. I just know something changed in this area for some people and this new method works for me, thankfully. WinClose, ahk_class window ahk_exe demul.exe

I'll try that to see what happens with Demul. But it's a non issue for me for RA because simply removing the script altogether for RA 1.4.1 solves the issue with RA. Edit: The new close method works for me with Demul!! Thanks @llhank !! Great job! I'll read up on the new method. Maybe it's a more graceful proper close of the application. Maybe it's best to use this new method for all the emulators that I currently use the old method for, even though it seems to work ok for the others. But you have three different ways to close each of those 3 emulators and I'm not sure how to know which was is best for each application? Maybe it's in the ahk docs.

I'll take it!