ayatollahbaloney
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by ayatollahbaloney
-
-
I've cleaned out and reinstalled DirectX, and still have the same issue.
Any ideas for what I can try next?
-
Unfortunately, my case isn't that simple. I've tested with a keyboard and mouse attached, and it still freezes. Clicking with the mouse does nothing. Pressing eg. windows-key and then using the mouse to refocus to big box does nothing. It is thoroughly frozen, it hasn't just lost focus.
However, it would appear that it only freezes if the very first input it receives is from a controller. If I first press a button on the keyboard and then use the controller, everything appears to work just fine.
-
Takes a few seconds to test, I can do that after work.
-
I do not have a mouse connected. Alt-tabbing "out" of BB (it's the only open app) and back does not help.
-
If your controller was DoA after boot, driver/dx issues do seem more likely imho. Even so, controller input shouldn't be able to make BB freeze completely.
Using BB as a custom shell sounds very interesting, mind doing a howto or something if you figure it out?
-
My install is a brand new PC with a clean install of W10. I can remove all trace of DX and try reinstalling that.
-
1 minute ago, arcath said:
So it seems I am having a similar problem.
My machine boots up from Win8 and Big Box starts. I use the controller to do anything and Big Box freezes up and the only thing that will fix it, maybe 50% of the time, is hooking a keyboard back up and pulling up task manager. Only then will Big Box become responsive again.
I thought it was my 360 controller and/or the wireless dongle but its doing the same thing with a usb snes buffalo controller.
Suggestions?
What is your setup?
I set up a new PC with W10, hardware: i5-7400, GTX 1050, and 8GB RAM. Tried using wireless X360 controllers with a (admittedly shoddy) chinese receiver. Tried using DS4 controllers via bluetooth and via the USB dongle. Tried using an ipega bluetooth controller.
It doesn't always freeze, but it freezes far more often than it works.
Waiting for a while before pressing does not appear to help.
I have given up for now, but if this issue is solved, I may reconsider later on. -
I have now switched to using DS4 controllers, and Big Box still hangs on the first button press. Process must be force closed using task manager.
So the cause is not the shoddy chinese receiver, but "something else" that mysteriously makes BB lock up. I've spent way too many hours trying to set this up, so I'm giving up and reverting to retropie.
-
2 minutes ago, DOS76 said:
Are you using Windows 10? There shouldn't be any issues with the 360 wirleess receiver drivers as I have a few of them and they are working perfectly
Yes, I am using Windows 10. The receiver and controller are working fine on linux, but windows driver seems to not handle it correctly. The dongle is of the china variety however, so I might have better luck with the original receiver.
-
Yes, it also happens when manually starting BB. But apparently only the first time.
I've played around a bit, and it would appear that the x360 wireless receiver windows driver is the issue. It works fine on Linux, but on windows it is pretty much useless.
-
I've set BB to launch on startup on my new Windows 10 installation. I've set up PS2, NES, SNES emulation and got them working. But when I boot up the PC, BB starts, and when I press "A" to select a system, BB freezes. It doesn't respond to anything. Only "solution" is to fetch a keyboard, pull the PC out of the shelf to connect it, press ctrl-alt-del, awkwardly use task manager with the keyboard, then start BB manually again.
How do I go about finding the problem?
-
Just now, DOS76 said:
Ipega BT controllers have to be configured in RA and they do work in BB
Yes, I did that. And that worked. But I don't want to use the Ipega controller. However, once I had configured the Ipega controller and then configured the x360 controllers, the config worked.
-
1 minute ago, SentaiBrad said:
If everything is crashing or not working related to a controller, but it's working for all of us, then I am leaning towards a Driver issue actually. Something seems wrong there. Big Box should never crash like that (and doesn't for the record), and RetroArch and PCSX2 are working. RetroArch does automatically config the controller for Xinput controllers. The Ipega controller won't most likely. For Big Box, you will need to go in, select the controller you're using (or check the box to use all attached controllers at once, which can cause issues with some drivers and arcade boards), and then set up the needed controls. Also, you need to touch the controller config for PCSX2; RetroArch automatically doing it is actually rare. Most emulators don't.
I'm using the latest microsoft driver. And BB most definitely crashes "like that". It doesn't respond to keyboard when this happens. The only thing that works is ctrl-alt-del.
-
Just now, SentaiBrad said:
Oh, and for the record, EmulationStation is much more complicated to get up and running unless you go out and buy a pre-made box that is highly illegal. It's one thing to make a front end, which that's all EmulationStation does, and then it's up to the user to do the rest of it. It's another to go on ebay and sell boxes pre-loaded. Or, a friend helped / set it up for you, but the box resellers are a common plague in our hobby.
Emulationstation, as it is in retropie, is dead easy. Write an SD card, insert into RPI, boot, autoconfigure controller. Upload roms to a folder, and off you go.
I've set up emulationstation on windows, and it worked fine. My one issue with emulationstation was that I couldn't get pcsx2 to exit with select/start like I can on launchbox. But I guess that is a smaller problem than "BB crashes on first button press".
-
Just now, SentaiBrad said:
For setting up a controller in RetroArch, it's actually done automatically if it's a 360, Xbox One, PS3 or PS4 controller (the last 2 require extra software to work with PC's). So it's even more so, download RA, import games, download the core, make sure the associated platform is set correctly and go.
In theory. I tried automatic configuration. That really didn't work. I've spent the past 6 hours trying to get two controllers working with retroarch. I have absolutely no clue how I got it working, but the x360-controllers seem to finally have stuck after I first configured an ipega controller, then the two x360 controllers, and finally removed the ipega one.
(some of my woes with retroarch: https://forums.libretro.com/t/cant-get-sane-controller-setup/10156)Not all emulators are happy, for some reason pcsx2 refuses to let player 1 press "up" (yes, it's not retroarch, but I didn't touch controller config in pcsx2). And bigbox simply crashes on the first button press from a controller, so even though the emulators "mostly work", I can't actually use it as a 10-foot interface - which is why I actually paid for it.
-
Oh, and the big box process just hangs around when closing it, making it necessary to open task manager to close it. Or reboot.
-
I started off with retropie/retroarch/emulationstation, which "just works" out of the box, no documentation necessary. I decide I need a beefier system to emulate more games, and move on to a kaby lake i5 with a gtx1050ti.
And I'm trying to set launchbox/bigbox up to work kindalike emulationstation/retroarch. But the controls seem to be all over the place. If I attempt to use enable/volup in a game, the game closes (but it does adjust the volume, I'll give it that). In NES, select works as it should. With SNES however, select alone closes the game, making it impossible to select 2-player. And I haven't configured NES and SNES differently (both are retroarch cores). For PCSX2, enable/select doesn't close the game, for that I have to whip out the keyboard. But it does on NES. edit: Oh, and "A" on my X360 wireless controller also pauses the game on NES in addition to fire/jump/whatever the game usually does. What?
I'm becoming increasingly frustrated, and googling for setup tips nets a whole lot of terribly long-winded instruction videos. None of which (according to the title atleast) appear to deal with actually setting up the controller. To make it even worse, the instruction videos reference other instruction videos that are apparently vital. I don't have the patience to sit down and watch several days worth of videos to get this up and running. Isn't there documentation available in some format that can be skimmed to find the relevant parts quickly and then read those?
I have now decided to start from scratch, so I removed everything, and installed launchbox from scratch. I import all my NES roms and set up the default emulator for NES. Enter big box mode, enable controller, enable controller automation. I don't touch the controller assignments. I am then unable to go back to the main screen using "back", or using the keyboard. Only way out of settings is by exiting big box. Restarting big box and pressing "A" to enter NES games makes big box lock up. What the hell?
I'm beginning to regret paying for this...
Big Box crashes on first button press
in Troubleshooting
Posted
After upgrading FW on the PS4 controllers, BB doesn't crash until exiting the first game. Sort of progress, I guess. It freezes in the middle of animating menus, and doesn't respond to anything.