ckp

updated to the latest beta today. LB startup time went from around 10 seconds to 9 seconds. navigating platforms come up quite fast, which is much more important to me than startup time. thank you.

oh dam, most exciting feature ever is plugins. there is a working video download plugin, so easy to use!! thats is something great! woohoo!!

that's a major bummer. maybe THE man himself @Jason Carr can help? i think controller problems have been quite an active topic lately. don't give up. try a little bit more in case anyone has an idea. it's going to help the product and other users, even if it can be frustrating for you.

I used to have that happen to me until I enabled all controllers in the BB controller settings. Does it also happen when manually starting BB?

@emko, you can try launching a vb script from your batch file to launch Bigbox. and if it doesn't focus, you can also have the vbscript give Bigbox focus. as an example, inside your batch file, instead of using your start Bigbox command, replace that with something like this (no start command needed): c:\scripts\runbigbox.vbs (you can create a .vbs file with notepad or any text editor, just save with .vbs as the extension) inside runbigbox.vbs could be: Set WshShell = WScript.CreateObject("WScript.Shell") WshShell.Run("""C:\LaunchBox\BigBox.exe""") Maybe that will work nicer for you?

I don't know if it will help, but what if you set BB to use all controllers in the controller options? Are you using Retroarch for those systems @AinsWorth?

try launching BB like this in your batch file, in case you aren't: start e:\mypathtobigbox\bigbox.exe

@emko, does Bigbox get focus ok if you launch it manually, not from your batch file? what is the exact command you are using to launch BB in your batch file? does your batch file launch or do anything else after it launches BB?

Try pasting this into your MAME emulator settings AHK tab and see if it's any different: $Esc::{ Process, Close, {{{StartupEXE}}}} But for me, I just set MAME itself to exit with the same controller combo as I use with LB controller automation and that seems to work ok, with nothing in the ahk tab.

oh bummer. no idea then if it happens often, maybe try adding the close startup process ahk script in the mame tab?

Hey @Charco, only time I ever had any issues with LB and MAME was when I had the new MAME port audio settings. But I think my only problem was having those settings and using MAME/BB through Steam link. Edit: also I don't use any script at all in the LB MAME emulator autohotkey tab for MAME. If you have something there to close MAME, maybe remove that and try it?

I can't really tell you since I never really got too familiar with everything in RL. I was just thinking that maybe you have some kind of hotkey clash between RL and BB. When I used RL with LB, I don't think I had anything in my autohotkey tab in LB, but that was before the problems came around like this. I wonder if it would help if you were to add this to your RL autohotkey tab in LB? Maybe worth a try? $Esc:: { Process, Close, {{{StartupEXE}}} }

I'm not saying that. I just didn't want to use RL anymore. I had no need. If you are having a problem with RL, then you should answer all the questions I asked and I can try to help, or someone else may know too. So, did disabling the RL exit key help? Is anything in your LB autohotkey tab for RL?

Yes, same here. Something changed in one of the last few versions. After that, we have had to handle the autohotkey contents differently for some emulators. I stopped using RL a long time ago and just use LB. But when this happened a few versions back, it affected Retroarch, Demul, and others for some people. Maybe it also affected RL, but I don't use RL anymore. And it can be fixed per emulator at least for Retroarch, Demul, and some others.

Maybe for Rocketlauncher specifically you could try disabling the exit emulator key you have setup up in Rocketlauncher settings.

Lets pick one specific emulator to look into first. For Project64, look at your LB project64 emulator settings autohtokey tab. What's in there?

You didn't answer this part: For the one specific emulator to discuss here, what is in the Autohotkey tab in its Launchbox emulator settings?

@ciskohansen What is one specific emulator where you have this problem? How do you exit a game, using Bigbox controller automation? For the one specific emulator to discuss here, what is in the Autohotkey tab in its Launchbox emulator settings? Edit: What is control+alt+supr? Are you killing the bigbox.exe process or does some key combo just make it start working again?

voodoo

That's great news and will hopefully help some other users!

awesome @cammelspit , you might try excluding all the LB/BB application binary files themselves in AVAST also, rather than just the directories. maybe worth a shot. edit: make sure you reboot after adding the new exclusions and then see if it still happens.

That's a bummer. Apparently you are not the only one experiencing this =/

Doing a Windows update is nothing near the same as an actual Windows reset/reinstall. All the same stuff is still going to be there. You might try killing the extra processes one by one that you see running in task manager until you possibly see the issue stop.

el cheapo seagate 5TB = ~$120, cheapest 5TB western digital or hgst ~$200+ if given he choice, sure, take western digital (i wouldn't even go for HGST if i'm going to pay the premium). but some people already have the seagate as a gift or due to budget. i'm just saying that they can last a fair amount of time and work fine if that's all you have or want to spend. for this purpose of this posting, the question is about what is better for this particular drive, internal vs external, so my advice is internal.

i use a couple big Seagate usb 3 drives because they are so cheap in price. I've been running one for two years with no issue and the other for 1 year with no issue. However, Western Digital is better. For me, these cheap seagate drives seem to be fine for storing emulation stuff, like roms, LB, emulators, media. What you can also do, and what I did with one of my Seagate usb3 expansion drives, is crack open the case and install the bare drive internally for an internal sata cable connection. It's much better than the usb3 connection. I do keep one drive connected by usb 3 for portability, but if you don't need the portability, just crack it open (youtube videos) and install it internally. That would be my advice. Oddly, it's cheaper to buy the entire external seagate usb 3 drive than to buy a seagate bare drive.