Chadmando

I went back and tried this again, I actually had controller companion disabled when MAME was in use, after I enabled (START + SELECT) to toggle it, it worked completely fine... (for hotkeys).

Here's a solution that I tested and works. Open up Launchbox, go to emulator settings for mame> Autohotkey script Enter this code: vk07sc000:: { SetKeyDelay , , 300 send {TAB} } This way you're not running new programs. The "setkeydelay" makes the button push a little longer otherwise it seems to ignore the press. I don't think controller companion will work, and I'm not sure if mame works with XInput, hopefully I am wrong though. If you plan on mapping more controls to the same controller you might have issues.

Yes I beleieve there is an option in there that blocks digital inputs, I am looking for it right now. EDIT: Looking at my set up I am using joytokey for mame, I must have had the similar issues as you. I played around with my settings and I can confirm it works within joytokey. All my joysticks are configured to keyboard buttons in mame, and I use Joytokey to send the inputs. I am using mame 0.173

Sounds good

PM me your email I'll buy you a copy if you want, it's only $3 =P. The program is awesome it saved me a lot of trouble.

Thanks for the reply. I understand, I made my post before I investigated things properly, I've adjusted my autohotkey script that I have running in the background and fixed most of my issues. I'm not sure if someone raised this issue, perhaps maybe it's worth making a warning pop up in the settings for project 64. If the setting in project 64 "PAUSE EMULATION WHEN THE WINDOWS IS NOT ACTIVE" is checked then project64 won't work properly with the startup screen, and will only start when the startup screen is timed out. Unchecking this setting fixes the problem. You have steam games working properly with startup screens? If I don't have steam open prior then the chat menu, and update screen, etc mess up the starting screen. I then have to manually change the setting in each and every steam game if I want to disable the startup screen. Is there a way to change this setting for all Steam games (without changing the settings for each and every individual game), just like how the option is available for emulators?

I love the idea of the startup screens, but this doesn't work at all for me. Project 64 always starts up after the start up screen is shown, no matter how long the startup screen is, it doesn't hide the console window no matter what setting I do. Every time close pretty well any emulator or windows game Bigbox "hangs" (as in does not accept any controller input until I alt-tab back into bigbox). Steam games console launches before the the startup is finished (using the default startup time) and then if the game loads faster, big box brings BIGBOX into view until the game loads. If I adjust the time to longer, the startup screen and game loads ok, when I close the game the startup screen is still on and hangs at the "startup windows" until I manually close it. I cannot seem to find a setting to change the startup times for all steam games, it looks like I have to do it manually to every one. I think Dolphin is the only emulator working correctly. EDIT: Some of my hanging issues after closing a game seem to be from my autohotkey script that I had used to alleviate opening mutliple instances of one game, as well as hanging after closing a game lol. It seems like the very same items that have been patched here are breaking with what I was trying to fix manually in previous versions.

I find they both work very well, I thought I had bad lag on the NES one at first but it's just the filters I had over the emulator were lagging things a bit. So far I haven't had cut outs unless the controller is dying. I find myself more often than not just using the Xbox one controller for the older 2d gen games, nothing else quite feels right besides oem with N64, ps1, PS2 + gamecube to me. My fav PS2 game required the use of pressure sensitive buttons which no other controller aside from the PS3 seems to have. That being said I have been contemplating buying 1 nice multipurpose controller.

I thought most motherboards would come with bluetooth installed nowadays, my motherboard is a rampage V extreme it has a built in wifi with bluetooth 4.0 module. I imagine any good bluetooth adapter, either if it's a dongle or a pci-e plugin to the motherboard should suffice. I would recommenced one that plugs into a pci-e slot that comes with a good antenna out the back. That being said, I didn't want to confuse you too much, but I do actually have 3 bluetooth modules in total. 1 for Xinput controllers, one dedicated to ps3 controllers (using pcsx toolkit), and one dedicated for the wii. They all work independent of eachother as to not conflict with eachother. You will need a dedicated adapter for proper ps3 controller input if you wanted to use a ps3 controller as well.

No problem lol, I'm not the best at explaining things. I am using my built in bluetooth chip for the wireless Xbox one NES, SNES, Genesis controllers, not any dongles. If you're using a bunch dongles for each xinput controller that has a dedicated controller spot 24/7, that will definitely mess up your controller orders. With the one dedicated bluetooth adapter, the controller only shows up on the "windows game controllers" list when you connect, and when you disconnect it disappears, you should only ever have to sync them once as windows will remember all your pairings. It is actually very intuitive and I prefer this set up much more than the old dinput. If you are using an emulator with xinput support it should completely ignore any other plugged dinput devices. This chip supports up to 8 Xbox controllers I believe. The emulator itself is only mapped to a single Xbox one controller per player. With xinput, the emulator doesn't "know" which type of controller it is using, as each controller is simply simulating a Xbox one controller, it only knows what controller player one is, who player two is, etc. Windows does all this work before the emulator is loaded. Outside of the emulator the 8 bitdo controllers button layout match closely to what an Xbox one controller layout is (and if they're slightly different you can swap them around via a combination of button presses via the manuals). This way I don't have to map every single controller in the emulator, and all the buttons lined up pretty much the same way. Long story short: The emulator thinks every controller is an xbox one controller, the mapping remains the same. The emulator only knows what player to assign to what controller because windows has assigned it before hand.

Messing around with the bluetooth adapters can be very difficult for the initial setup, I agree, especially with a custom installed bluetooth chip. The end result is very nice though, the controllers are always synced up like a real wii every time I load a wii game, and to sync another I simply press the sync button once on the controller and once on the front of my pc. Though you cannot really use that same bluetooth module outside of dolphin for other programs like you can with the mayflash adapter. Most people install them into some sort of small case and run a usb cable to plug into a usb port outside of the computer. If you're good at soldering the wiring is extremely simple, and only requires a few parts. At the very bare minimum you need a case of some sort, a usb cable, a wii bluetooth module, and a voltage regulator (a sync button is optional, as you can sync the controllers with a hotkey within dolphin if you wanted. You can buy these items for very cheap on ebay or amazon, usually from chinese sellers (shipping can take a while). I personally got all the parts, secured them together in a way I like and then paid a local on kijiji to do the soldering for $40 'cause I suck at it lol. Here is the thread about it on the dolphin forums: https://forums.dolphin-emu.org/Thread-how-to-wire-a-wii-s-bluetooth-module-to-a-pc-usb-port I used this schematic exclusively https://forums.dolphin-emu.org/attachment.php?aid=17630 Like I said though, once configured in your pc , it's really only supported in the dolphin emulator.

No, if the emulator has proper support for xinput this shouldn't be an issue. The only times I had this issue was using dinput, and with improper plugins. I only map for one device for every player on every emulator using a xbox one controller, with 8bitdo bluetooth mod kits I can swap buttons at the hardware level before syncing them up for the first time, so my controllers all have the same button layout as the Xbox one controller (like A button on xbox one is = B on SNES, B= A, X= Y, Y=X). Before opening up the emulator you have to make sure you have the controllers ON in sequence to the order you want the players (same for when you initially map your buttons). I should clarify I am using windows 10 enterprise edition, this might not work with other OS's. For example, say I open up bigbox with an xbox one controller and decide I want to play two players on the NES, with two NES controllers. I first hold down the guide button to turn off the xbox controller so it will disengage that controller as player one (the annoying Xbox game bar has to be disabled/uninstalled so it doesn't pop up), I then grab my two NES controllers, the first one I turn on windows assigns that as player one, and then turn on the second, it assigns that as player two. Using that same controller I select an NES game and it loads up the game with the correct player order. If I want to change controllers I have to close the game, turn off the controllers and do the same sequence with whichever controller I choose. For a rare emulator that doesn't support xinput you can use a program called joytokey in conjunction with bigbox, and then you can assign your controller to a specific slot using its mac address or (hardware id or something like that) and then map keyboard keys to that specific controller.

Thanks! I got them from rose colored gaming They don't have genesis ones I bought that one off of a UK ebay seller, luckily it looked very similar to the others.

I have eyed the magic ns adapter before, the issue I would have with such a setup is that you have to remember which controller is which. The good thing with the 8bitdo is it supports xinput. Using my computers built in bluetooth; no matter what controller I use the computer will assign the corresponding controller to a player in whatever order I turned the controller on. Meaning I can use the xbox one controller, SNES, NES, genesis with whatever emulator I want without pressing physical buttons or resyncing (they all act like a wireless Xbox one controller). I can be using an xbox one controller for an SNES game, while a friend could use the oem snes controller as player 2 if they choose. For the PS3 I have installed SCP3Toolkit, and bought another bluetooth adapter exclusively for PS3 controllers. It also acts just like any xinput controller, except in PCSX2, where it will function exactly like a PS2 controller ( for those games you need pressure sensitive buttons). That's interesting about the mayflash, the other issue I had with it is the LEDs inside burned out really fast (less than 6 months) even with the update that turns them off when no controller is being used. I figured at the very least with a built in bluetooth I can just use one of those cheap usb sensor bars and not feel bad about chucking it and getting a new one if the same thing happens.

Just wanted to give an update to my original post: My original setup was a little cumbersome, it relied on a wii remote, and extensions to plug the controllers in. I have now gone completely wireless, thanks to 8bitdo's modkits. For those unfamiliar, 8bitdo have released pcbs that replace the ones inside your oem controllers. I now have bluetooth modified OEM controllers (NES, SNES and Genesis), as well as I invested in four retro-bit 8bitdo N64 controllers (as there isn't a mod for the oem n64 yet). To finish it off, I installed an actual OEM Wii bluetooth adapter into my PC, and added a nice blue button on the front of my tower to sync wii remotes. I did this because the mayflash bar wasn't quite cutting it (Wii remote sounds sounded like garbage, kept having problems with Wii motion plus controllers, also through my research it is supposed to be the most accurate adapter.

I'd like to put a request out there if someone can do a start up video deo based on the theme of the old canadian video game show Video & arcade top 10. https://www.youtube.com/watch?v=mbxXmMgwtaU it's pretty cheesy but it brings back so much nostalgia lol.

Ok, I didn't think so, thank you. I will write up an AHK script.

Is there a way to set a combination of keyboard keys to close bigbox? Currently I have X set to close bigbox but I'd much rather a combination to close it instead. It only seems to accept one key in the settings. Thanks!

Hello, I am currently refining my PC autohotkey scripts to try and eliminate any issues to be more of a foolproof setup, for guests and my young son. I have an autohotkey script running in the background 24/7 on my PC. I used the Xbox one center button to open and close emulators, and also to launch bigbox itself. There is one issue that presents itself sometimes where a emulator/game gets stuck open after closing Bigbox, is there a script I can use to detect all the windows/ games opened by BB, and if they exist force them to end task when BB is closed? If tried using the Close, process, {{{StartupEXE}}}, and tried to use variations of that, but I have no idea what "startupEXE" ? is this a windows title? Executable name? I have troubles using it in any other scripts. Thanks for the help!

I'm not sure if this is because of the latest update with windows, or an issue with the latest launchbox, but I have noticed that upon launch of a game Bigbox wil frequently not "let go" of the controller causing me to accidentally open up multiple instances of one game. This has not been an issue before. I am updated to 8.4 beta 7. Using windows version Windows 10 pro build 17134.112

Alright thank you, umm one more question, do you know where the settings are for messen to load fullscreen automatically when opening a game>

Just playing around with Messen and it seems pretty damned good already, do yo have any recommendations for an SNES emulator? I am currently using SNES9x

I'll give these a shot, do they support Xinput properly? Xinput with FCEUX is starting to appear problematic to me. I have solved my issue (using windows 10 ver 17134). My emulator settings are "fullscreen after game is loaded". My resolution and setting mimic that of a real SNES on a crtc (resolution goes down to 1280 1024 32 bpp). What was causing me issues was Windows "focus assist". I turned all automatic rules OFF ans set it to "ALARMS ONLY". I have no clue why it was causing me issues.

So this just started happening out of nowhere, possibly due to stupid windows updates. When I load an nes game through launchbox, my resolution just keeps changing back and forth from 1080 to the resolution I have fceux set to run on (with a blank screen). Same thing happens if I drag and drop a nes rom file to the emulator executable file. If I open up fceux, and then manually go to open a rom through the menus it opens properly. Any clue what could be going on? I haven't changed any settings since it last worked, but there was a recent windows update.