JoeViking245

"Good" is always subjective. I don't think I've ever seen 'sets' available so probably on an individual bases. The CHD file will be in a folder with the same name as the games zip file and that folder is placed in the same directory as your Mame roms. So in you roms directory, you'll have: blitz.zip blitz [folder] In the blitz folder, you'll have the file: blitz.chd

That's a perfect location for it. Definitely do try again but maybe not 4 hours until you decide to do a fresh install. With all the trial and error, there could be that one little setting that accidentally got changed that'll leave you at wits end. GL

If through RA, you Load Core/Content, F1, Controls [assign buttons] and Save Core Remap File, you don't need to do anything when you load a game in BigBox except play. Any and all emulator configuration (especially in-game controls) needs to be done, and confirmed working outside of LB/BB. You don't by chance have RA installed in your Program Files directory? That could be the underlying issue. ..directory/file write administrator permissions and all that shtuff. If it's not, I think your best bet is to simply start fresh with RA. (LB/BB has Nothing to do with the issues you're having. Just sayin'.) Since nothing appears to be working correctly with RA, there's no loss in completely trashing your RA installation and installing fresh. From Windows, start [your freshly installed] RetroArch. Load Core find the core and hit enter Load Content go to the directory that has your games and select one (mine are in zip files, so I need to select Load Archive) you may be asked to select a core (again) do that and the game will start Hit F1 you'll be at RA's Quick Menu (starting at "Resume") Scroll down and select Controls Scroll down and map your controls it'll look different than my pict (was on a remote computer) Once done, scroll up and select Save Core Remap File Scroll up more and select Resume All should be good. At this point the game is running. Hit F1

Load the core, then load content (a game). Press F1 to back into RA and try the config/save.

Start up RA (NOT from inside LB/BB). Load the core for the platform you want to configure. Go (right) to Settings, Input, User1Blinds. Setup the buttons/controls (and for User2Blinds if you wish). Go back to Main Menu. Select Quick Menu (which doesn't show if you don't have a core loaded) then Overrides (very bottom). Select Save Core Overrides. Though probably not necessary, without making any other changes, load RA, do the config/save, exit RA, restart and test that core/platform. My upright cab has the I-PAC/2 and when I 1st tried RA, I actually completely gave up. About 6 months later I convinced myself it can't be that hard. Sure enough... the answer was right there the whole time.

Download the "Portable folder with FS-UAE" version of 2.8.3. Unzip it into the folder you want to run it from. (May need/want to uninstall you 'installer' version 1st.) This way everything for it is stored in that folder and you don't have to worry about the AppData folder at all. I don't recall if the Kickstarts folder is there right away or if it creates it on first run.

For a quick interim fix... You can try an AHK script. Add a new emulator that points to the script file. Associate the PS2 games to the new 'emulator'. Extract, Run PS2 bin file, Delete ERPS2binD.ahk (quick and dirty, but works) #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. ; #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. PCSX2 = F:\Emulators\pcsx2\pcsx2.exe ;change path to your pcsx2 location FullFile = %1% SplitPath, FullFile,,dir,,NameNoExt outdir = %dir%\%NameNoExt%_tmp if (A_Is64bitOS = 1) { RunWait, "C:\Program Files\7-Zip\7z.exe" x -y -o"%outdir%" "%1%",,Hide } else { RunWait, "C:\Program Files (x86)\7-Zip\7z.exe" x -y -o"%outdir%" "%1%",,Hide } RunWait, %PCSX2% --fullscreen --nogui "%outdir%\%NameNoExt%.bin" FileRemoveDir, %outdir%, 1 ExitApp (Be sure sure change the path in line #5) Note NO checked boxes. Add this to the AutoHotKey Script tab $Esc:: { Process, Close, pcsx2.exe } Note: The original "Process, Close, {{{StartupEXE}}}" won't work with the script. But the above does. What the script does is: Extracts the files in your .zip OR .7z file to a temp directory using 7z.exe. Runs pcsx2 with the extracted .bin file that's now in the temp directory. When pcsx2 closes/exits, the temp directory is deleted. Caveats: You need to edit line #5 in the script. 7z.exe must be installed. The .bin file name needs to be exactly the same as the zipped file name. This doesn't take in to account custom configs. So with that last one, this is almost useless. But a something none-the-less. Maybe if someone knows how to pass an argument to a script, a per-game config can be added in.

I bought the BB 1 year license and it did come with the EmuMovies discount. As stated... these two products are just amazing in conjunction with one another. Without hesitation, I did get the EmuMovies lifetime subscription and of course will be going lifetime with BB.

For me, I ended up just converting them all to .cso files.

Yes. ?

It appears it does. (The #'s may come across as odd, but it all works. Trust me And no. I don't have an explanation.) By virtue of the ports on my video card, my cab is Display 2 and the TV is Display 1. My mame .ini is: # # OSD PER-WINDOW VIDEO OPTIONS # screen \\.\DISPLAY2 aspect auto resolution auto view auto screen0 \\.\DISPLAY2 aspect0 auto resolution0 auto view0 auto screen1 \\.\DISPLAY2 aspect1 auto resolution1 auto view1 auto screen2 \\.\DISPLAY2 aspect2 auto resolution2 auto view2 auto screen3 \\.\DISPLAY2 aspect3 auto resolution3 auto view3 auto Though I only have 2 (at most) 'monitors', I guess I set up all '5' on Display2. Hmmm. Probably don't need the others. When I load BB with dual monitors (with TV as primary), in BB Options, General... is has: Primary Screen: Screen 2. Marquee Screen: Screen 1. BUT..... BB is showing on the TV and the marquee (i.e. the game box-front) is shown on the cab.... like it's supposed to. And everything 'plays' on the TV. When I load BB with a single monitor (cab only. Primary of course)... Options, General: Primary Screen: [is blank]. Marquee Screen: Screen 1. BB and all platforms run as expected, including MAME. Sort answer long... tested, tried and true. MAME.ini and LB/BB settings are "fixed" (I don't touch/change them at all) and the only that I change is going from single to dual monitors and back.

Maybe not 'elegant' per say but doable.. maybe have two LB/BB startups. One that sets the primary on the PC (work/play) and one the sets the primary as the projector when guests come over. That way, all games load on the 'primary' monitor.

MAME has made it (relatively) easy for selecting monitors as DOS76 explained. The problem is some other emu's aren't as user friendly about telling it which monitor to use. They ONLY seem to want to use the Primary monitor. And moving them like Agrajag mentioned can be problematic too. Some emu's when moved and successfully full-screened do remember 'that' screen for next time. But not all. My setup is a cab monitor and a 60" tv. The cab is great for Arcade (with the controls and all). But with other Platforms (say, PS2), you just gotta 'go big' and grab the xbox controller. I pretty much gave up on trying to 'tweak' all emu's as to which monitor they show up on and resorted to show all on the "primary" monitor. (I think "monitor 1" and "monitor 2" is based on where they're plugged into the video card and doesn't necessarily determine primary). It's not ideal, but I created 2 BB startups. One (the regular exe) starts up with the cab monitor only (single monitor). The second (a batch file): sets the monitor and TV as dual monitors with the TV as primary... runs BB... then when it closes, resets to single (cab) monitor. Again, it's not ideal. But the (OpenSource) program I used (Monitor Switcher) for saving the different monitor configurations makes the batch file (or AHK if you want) an easy no brainer to create, whether you have 2 monitors or 20. (ya exaggerating, but you get the point.) I imagine you can set it per game or per platform (like Visual Pinball X with a table (monitor), back glass, DMD, marquee etc...). Hope this helps at least a little. Here's a write up I did talking about it a little more.

Ahhh.... another beautiful innate feature of LB/BB. In Launchbox: Click Tools. Download Platform/Playlist Theme Videos. Assuming your Platform is called Sony Playstation 2. Choose the available theme that suits your needs.

Try adding -exit to the default command-line parameter to VPX. Tools. Manage Emulators. Select Visual Pinball X (or however you have it called). Edit.

It loads and runs here, but ya.. no [built-in] sounds.

The chd's are a separate file and not all mame machines (roms) need them. chd's will have the exact same name as the rom. Most (if not all) chd's you may see "listed" as 0.207 will work for 0.208. Yes, some (most) of your roms should work. A nice easy check is something listed near the top like 1942. No chd file is required. (Also, may want to mind your pictured personal sticky notes )

Can you run the emulators/games outside of LaunchBox/BigBox? Which console/emulator are you trying to run?

Yes. #4708

Just re-read the OP and see you used winmove. Duh Joe, of course that will work. lol AND... (as you indicated) no need to "UnStretch". I use a winmove script [doh!] on my desktop for placing multiple windows 'just where I want them'. Very handy!

If I'm reading correctly, you already have a script that will 'stretch' the screen. Maybe you could: Edit RDP, go to the Additional Apps tab and Add Additional Application and point to the script to stretch it and check Automatically Run Before Main Application. Then add another 'app' that reverts it back to normal and check Automatically Run After... Option B is to create a complete script and use it as your 'ROM File' under the Launcher tab. It would something like: #SingleInstance force SetWorkingDir, D:\Emulators\Mame ;where mame is located. Note: No "\" after "Mame". MAMERun = mame64.exe GameRDP = D:\Emulators\MAME\roms\racedrivpan ;Path and Machine (rom) folder Run Stretch.ahk Runwait, %MAMERun% "%GameRDP%", , Hide Run UnStretch.ahk Exitapp It basically runs them in the same order, unfortunately. i.e. stretch before mame runs, vs after. Then UnStretch. The smarter person could tell you to simply put in something like: Run the mame game Now run the stretch script process Hang out until mame exits When mame stops running, run Unstretch script process ExitApp

When you launch Race Drivin' Panorama directly from mame does it span the 3 monitors? I think in mame, if you were to edit you mame.ini file in the section # # OSD PER-WINDOW VIDEO OPTIONS # and get it to work for RDP, save the file as "racedrivpan.ini" in put it in the ini folder of mame. Then when you run RDP, it'll use those settings for that game [only]. Of course, keeping mame.ini in it's original sate for all other machines.

Glad it worked! Now for the real fun stuff... Depending on the options you change, they may not save (between exiting and restarting Mame). So have your notepad and pencil handy and note the changes you make. When done, exit Mame and head back to the ini file and change the respective values under "DIRECT3D POST-PROCESSING OPTIONS". Make a backup of mame.ini 1st!!! Just sayin'. If you have a game that's unique to the others or your working with different overlays/bezels/artwork, you can 'save' game-specific settings by: Modifying the mame.ini file (as noted above but without saving as mame.ini) Save it as romfilename.ini ..into the "ini" subfolder.

I was just toying with these settings in the last week or so wanting the same thing you are. 'More options'. According my chicken-scratch notes (which I'm trying to get better at noting what it is I'm about to screw up), lines I changed were "video" and "hlsl_enable" and also "filter" from "1" to "0" (which I forgot to mention. Under "OSD ACCELERATED VIDEO OPTIONS"). The only other thing I think I may have changed in mine was the ...screen_chains to hlsl. # # BGFX POST-PROCESSING OPTIONS # bgfx_path bgfx bgfx_backend auto bgfx_debug 0 bgfx_screen_chains hlsl bgfx_shadow_mask slot-mask.png bgfx_lut bgfx_avi_name auto MAME 0.207 mame64.exe