Lancer-am

Special popups that warn against all default behavior changes between versions possibly? Again may not need toggles, but again I was upgrading to 9.5 which this feature had been added in 9.4 so I would have had to go back and read previous changelogs, but between small iterative versions you don't really expect default behavior to change. Between major version changes maybe but not iterative ones.

Yes it was, a small one liner in 9.4. Again, this changed the default behavior of Big Box. Should have been better called out. A pop-up asking if you want this enabled during installation or something.

Nevermind, I found the hide auto generated playlist toggle. It seems that should be off as a default setting. It wasn't very well called out.

I have a Mame setup that was working great on 9.0, all of my auto generated playlists were displayed correctly. After updating to 9.5 The only thing tht shows up is Favorites despite all of the playlists existing in LaunchBox. If I tell the playlist to be included in the system list, then they show up in systems but not under playlists. It is almost like it wiped the file for Bigbox playlists and forgot to recreate it. I have tried auto creating the playlists again to no avail.

When I first setup my home cab, I went with a .174 Merged set. Now I have a full .204 set that I would like to change to. Am I going to need to blow away my previous Mame setup in LB and re-import? Or is there a way for me to do the update in place? If I delete the rom list that I have, will it need to redownload all of the media files?

I deleted my autohotkey script entirely as others have mentioned and I can at least send the close command twice. Only graphics focused background process running is GeForce experience.

I am having the same issue. I don't have afterburner running. On exiting PCSX2 it drops me back to the desktop, weird thing is that the big box process is still running and I have to close it out through task manager.

If you have an Nvidia card, you can also install Moonlight on your phone and do this same thing. I have a Moga Pro controller that I put my phone in and stream big box to it. I turned on the Xbox 360 controller emulation within Moonlight so that I did not need to adjust any controller settings in my emulators since I use 360 wireless controllers on them already. It works very well so far. I am have a 980ti and my desktop is connected to my router via Wireless AC. My phone supports wireless AC as well. Runs perfectly smooth at 720P 60FPS.

Here is the code, make a blank text file. Set the first folder to where your startup videos are located Set the second folder to the location of your working startup video Replace the final line with the exe of your big box install. Rename text file to .bat and use that to start Big Box. **edit** Just got home so I could actually write this against my install. Made some tweaks. This works like a charm. @echo off REM Location of your startup vid collection set folder=C:\Users\Lancer\LaunchBox\Videos\Startup_Vids REM Location of your current working startup vid set destfolder=C:\Users\Lancer\LaunchBox\Videos REM Get count of the number of .mp4 files in folder above then get random number then divide REM it by the count and take remainder. No. is 0 to count -1 for /f "delims=" %%C in ('dir /b /a-d "%folder%\*.mp4" ^| find /c /v ""') do set /A num=%random% %% %%C for /f "delims=" %%F in ('dir /b /a-d "%folder%\*.mp4" ^| more +%num%') do set name=%%F & goto next :next REM echo startup is now %name% copy "%folder%\%name%" "%destfolder%\startup.mp4" REM Replace this with your Big Box exe start "" "C:\Users\Lancer\LaunchBox\BigBox.exe" If you want to get really fancy and don't want to lose the pretty BigBox icon, you can create a shortcut to the bigbox exe, then re-point the shortcut to the batch file.

Batch file to randomly overwrite the startup.mp4 then launch Bigbox.

Thanks for your help guys, I appreciate it. Glad to have this one working now.

SOLVED IT! Ok some important lessons learned. As I suspected, it was what Launchbox was passing to Cemu that was causing the issue. Unfortunately I could not find any logging in Launchbox to see what that was. So I decided on a poor man's logging. I created a simple batch file that pointed to cemu and used parameters to bring in the switches and paths that Launchbox was sending it. Then I assigned that batch file as the application path for Cemu. C:\Users\Lancer\Downloads\cemu_1.7.0\Cemu.exe %1 %2 %3 break This left a cmd window open so I could see what was there. At first glance everything looked ok, but I noticed rather than "-f -g" it said "-g -f" Which was weird because I had it set as "-f -g" in edit emulator. I decided to try just -g. Weirdly Launchbox still was passing "-g -f". On the game I decided to put in custom parameters of just "-g". Low and behold it launched....... So I went into the XML for the emulator and it was just like I had it in edit emulator. Finally I went back into edit emulator and went into Associated Platforms. I had the default command lines entered there as well but they were "-g -f" which was overwriting my other command lines. Basically Cemu does not like -g before -f. If you guys want to replicate my issue switch those two and I bet it throws a fit like it did for me.

Just tried fresh install of both Launchbox 7.6 and Cemu 1.7.0d. New file locations, everything local, and no change. I guess I should mention I am also on Window 10. I'm at a bit of a loss.

I tried copying the game to my system and running it but still no change. I am going to try a fresh install of Launchbox next and see if that changes anything. I transfered this install to my server that holds all of my roms since it is strong enough to play WiiU and that didn't change anything either. Fresh install of Launchbox is the only other thing I can think of.

It was worth a shot, but still no difference. This feel like something is getting messed up from what launchbox is passing to cemu, like I said this works correctly if I just launch it from the command line myself using the same format the launchbox says it is. Is there any log launchbox where I could see what command it is issuing?