Bedwyr

I decided to mess with the wave files from BigBox. Dropped Select and Back to -7Db and Move to -3Db. That helped the poor ears quite a bit.

You mean you want to use Retroarch for everything? LaunchBox will happily do standalone emulators no problem. Understand the desire to stick with just one though. The only separate one I use so far is Dolphin.

Imgema said I checked the directories and everything is set up correctly. I also have all the cores RetroArch supports and updated them recently (online updater). Belay what I said and follow Sentai's prescription to deal only with one cfg file, try to get one system working inside Launchbox, and go from there.

SentaiBrad said Which is perfectly fine when its running. :P For now, keeping it simple is probably best. I take your point.

SentaiBrad said Don't mess with a config, just use the default one. You don't need a config per system unless you want one. It's why on my post I just said in a default RetroArch install. Also, they do offer save to the same file. First tab, Save to current config is above Save to New Config. If you save to current config with the default loaded that is what it will save your changes too. Again, you don't need to mess with custom configs unless you want specific Filters for specific cores and / or have special controllers that you want to use; for example I use Pixellate on 2D games, and my N64 controller on Mupen64. Or you think the default control bindings are no good. :) I have custom controls that make quite a bit more sense to me. For instance N64 Z trigger is mapped to the 360's left bumper and the bumpers are mapped to the 360's trigger. Which makes no intuitive sense, so I changed them. Likewise the NES, Gameboy, and GBA have A and B remapped to the 360's X->B and A->A. Left and bottom buttons made more sense as they rest under your finger more naturally.

I have to ask a couple three questions to figure out where you're at before I can relate what I know. I recommend setting up and isolating a single system before doing others. - Have you edited the Retroarch table on the second tab so that it refers to both the correct folder to access and the correct cfg file? - Is the default cfg edited? - Have you edited the core options file? If so, I recommend trying to delete the core options and letting Retroarch regenerate the file from scratch. - If all three of those don't work, I recommend validating which folders you're getting your default settings, core option settings, and core specific settings from. It's possible you've been trying to make retroarch load and refer to some extraneous cfg copy. (I HATE how Retroarch handle cfg loading and saving; it causes so much counter-intuitive trouble. Be nice if they could just implement a "save now to the same file" feature.) - If that investigation doesn't help, then I'd probably recommend loading a scratch Retroarch install, not changing either the core options or the default cfg. - Then download and load a single sample core, say for the 7800, and immediately set the option "config save on exit" to on and save the config "as" and create the new 7800 cfg. - Then exit the program and restart it, load the 7800 cfg and change the settings you want. Exit to save the config. - Load the program one more time and load the config to verify all your changes saved. - Now re-import your rom files for that system (7800 I assume). Might be worth just doing a subset of them if you have a lot. Then try to configure the system settings to load your cfg file and try to start a game. - Hopefully it starts. If it does, you may want to pause and enter the Retroarch menu and re-check all your settings.

Imgema said I don't know what i'm doing wrong. I set up my systems using the wizard. I choose RetroArch from the pre-set list. I set the paths to the games i want to associate. And after it's finished, RetroArch crashes immediately without error messages, every time i try to run a game. RetroArch works fine when i use it without LaunchBox. I also managed to make it work with RocketLauncher. So there shouldn't be a problem with itself. I tried to find a tutorial for how to setup RetroArch with LauchBox but i can't find anything :( Edit: I also tried to add MESS and it also doesn't work. Crashes the moment i double click a game. I found a problem with plugins when I was using the mupen64 core. It got so confusing I had to configure my retroarch install from scratch. Is this for all cores or just specific ones?

I've already got a workaround set up that uses the right stick button for mode shifting. Works fine inside Retroarch and can be mapped on other emulators. It's fine, but I am disappointed if something's changed. I emailed the mapping software author who supports guide button functionality on both controllers (One and 360). I'll report back if I learn anything.

Oh and a weird addition: In Retroarch Esc is no longer shutting down the program. I don't know why. It could be related, but I think it's most likely a separate problem that is concurrent with this, especially because I observed guide button problems in an unrelated program. Huh. I just tried assigning "exit" and "menu" function to other controller buttons. Neither work. I have an active button set up in there so a right stick click plus left stick should exit Retroarch and right click plus back button should bring up the menu. Neither work. This is mysterious. Correction. Retroarch is responding appropriately to other button input. Config file mistakes. Regarding the main problem, the Guide/Home button should show up as button 10 in Retroarch, right? Retroarch is responding to every input but that one. I might like to get a driver check of some kind. Right now the wireless dongle is showing up as its own driver category. The 360 is showing up as a generic HID gamepad, driver circa 2006. Is that a change from how it worked before? Can others confirm or deny this?

Okie dokie. I need help from someone else a) using Retroarch, b) using a 360 controller, and possibly c) using Windows 10. It looks like my 360 guide buttons quit working. That is they *work* by connecting to the receiver, but they appear to be dead as an input button. Both Pinnacle and PadStarr aren't reading Guide button presses. I have no idea what the cause is, but one suspicion is that MS did something to Xinput on the last W10 update. Or Xinput as a whole. If someone is using the Guide button on this controller for any reason (I usually use it to exit programs), could you check and respond? It'd help me narrow down what's going on here. - Did Retroarch ever try to access the Guide button? That'd be a good check to make if it did. - I'm already familiar with the XBox bar function in Windows 10 and, yes, it's disabled. I checked. - Do other mapping programs use the Guide, like Joy2Key? How about AHK's scripting? They have access to guide inputs?

darkaegis said Bedwyr said Some more information that could be useful for you. Someone posted a link on Kodi to their Steam Controller Linux driver. https://github.com/ynsta/steamcontroller Ooh, that's actually pretty promising and I was wondering how long it'd be until something like this came out. Looks like something similar to DS4Windows that "wraps" controller input into Xbox360 input. I assume the Steam Controller would then show up in the system as a generic controller after the driver is installed. Upside is that it would show up in Launchbox/Bigbox, likely, but we'd lose the ability to use community and saved user setups. Looks like it's Linux only, atm, but I wouldn't be surprised if it were ported to Windows eventually. That said, and correct me if I'm wrong, but it seems like something we, as users, would install more than something that'd help Jason directly. Not super useful, but perhaps there are some clues about how the hardware presents itself.

Some more information that could be useful for you. Someone posted a link on Kodi to their Steam Controller Linux driver. https://github.com/ynsta/steamcontroller I only deal with dedicated GCC and G++ stuff for scientific computing, so I'd be pretty pants at interpreting this and finding some independent/compatible Windows implementation. Yet there still might be something of use for you here.

WheelArt full sets are only at Hyperspin's FTP, correct? They couldn't be pulled off EmuMovies IIRC. I'd gathered you'd added some kind of EmuMovies support in beta and the fleeting thought of another art source occurred to me, but Hyperspin's server is a separate donation thingy.

I wonder if the API resources might have some clues? I don't deal with this kind of programming, but perhaps there's something of use: https://partner.steamgames.com/ https://partner.steamgames.com/documentation/api

That's disappointing, but I've seen it too. I think the biggest problems people have with it is a) they're not used to something that has a different control response than stick, b) they're not aware of the myriad settings available, and c) they're trying to treat the trackpad as a trackpad instead of a simulated trackball, where finger flicks, horizontal constraint settings, and haptic feedback actually work.

Speaking as an unrepentant fanboi, and partly tongue-in-cheek, have you tried it? I was surprised how well it works in FPS settings and how granular the adjustments (such as rotating the horizontal bias in the simulated trackball so your thumb can engage natural motion and still not jump mouselook up or down) can be. And then there's the ability to do as I just did and play Civ V for a couple hours not missing the mouse one bit. That's an accomplishment on Valve's part. The weakest points are really: - Twitch RTS like MOBAs. You just can't get away from a mouse for those. - Super complex games like aircraft simulators or heavily macro'd MMOs. And even then mode-shifting when they implement it might mitigate that. - Button and stick location. It's a slight reach for small hands. Now that's not a whine, it's just a defense of the thing from someone surprised it's actually as good as it is.

http://store.steampowered.com/app/353370/ Really Long Amazon Url $50 The lesson is that it kinda sorta works outside Steam. I think when they added the Desktop Mode profile, it became more usable in Windows proper. However I don't think that profile is directly editable. I haven't dug through forums or looked for XML files in the Steam folder though. When you shut down Steam, it'll shut down the controller too. But you can hit the controller button and it'll turn on and use its default profile including mouse movement and clicking. Dunno what signals the d-pad and stick send though. The other lesson is that it presents itself to Windows differently. I think it acts as an HID device and a kind of keyboard/mouse hybrid.

Bedwyr said - The Steam Controller will only be operational with mouse-and-keyboard set as noted here. Interestingly I couldn't exercise any control over BB or, after using my real keyboard to start a game, control a Retroarch game. Sorry, dumb. Sorry sorry. The controller can work fine with proper keyboard bindings. Still is a mess in Retroarch though.

Oh and just so it's clear, this has been a multi-year HTPC tinkering quest that's involved a lot of organizational compulsions. The Steam Controller threw a spanner into the (mentally deranged) works. The idea of the Steam Controller controlling absolutely everything from Chrome, VLC, and the BluRay player to Steam, emulators, and other games is so so very seductive an idea. It rather sticks in the craw that a user interface could have existed that would remove the need for K&M at the couch and their design only really works with Steam as the wrapper. Poop. ;)

Well I'll be dogged. Right after posting that I went into Steam to see if I could disable the overlay and it turns out you can't do that for non-Steam games. The option doesn't exist (even for regular games you have to exit Big Picture to access the check box). After searching it looks like several community threads have requested this as a feature since 2014.

So I'm still experimenting with the best, cleanest model for running media on the living room machine. Currently Kodi seems to be the most well-behaved UI thus far. I'm trying out different operational models as experiments though; which program seems to be the best as a launcher for the other. I saw at least one person is trying to run Big Picture from inside BB, for instance. I just tried launching BB from inside Big Picture and observed a couple of things. - It seems to work ok with a regular Xinput controller *as long as you don't hit the home button*. Steam overlay is operational but does not play nice with BB. Anyone else have experience with that? - The Steam Controller will only be operational with mouse-and-keyboard set as noted here. Interestingly I couldn't exercise any control over BB or, after using my real keyboard to start a game, control a Retroarch game. - With Steam Controller active, it appears to interfere with a regular Xinput controller. Turn the Steam Controller off and restart BB with the Xinput controller and it will work again (but don't use the overlay). This mesh with everyone else's experience? Again, I'm not necessarily asking to get it working well, just experimenting, tinkering, and seeing how LB and BB work in the corner cases. The only other thread I saw besides the above two was this one and another one specifically about Steam Link.

Reposting from what I wrote in Kodi. If anyone wants to experiment, this may be worthwhile: Ok, this is just a reference I'm posting for experimenters who want to try some different things. A long time ago Major Nelson posted 32 and 64 bit drivers for the XB1 as a USB plug-in device here. He removed those links once the wireless adapter was released but a news site still has direct access to those links and they do appear to be dated 2014. The news site: http://wccftech.com/xbox-controller-pc-drivers-download-courtesy-major-nelson/ The links (valid as of posting date): 32: http://mjr.mn/XboxOnePCDriversx86 64: http://mjr.mn/XboxOnePCDriversx64

On reflection I have a guess. The problem may have started with a driver update the day Microsoft released the Wireless dongle for XB1-Windows. I should check the Kodi conversations to see if anyone has more insight. For now I'm back to the 360 controllers.

By the way, when you're talking about shader behavior, are you talking about texture mapping, 2D sprites, or both? I haven't loaded up Ocarina yet on RA. I need to do that to make sure I'm loading correct res textures and Zelda grassland texture is best for checking that. My main complaints were about 2D art assets displaying slightly wrong (as in Ogre Battle dialog bubbles) or just low-res muddy (like Peach's letter and text in Mario 64 or worse, everything in Dr. Mario). Or are they these issues related?

Ok, finally got em in there plus a couple feature requests. Nothing major. I'm regarding the Retroarch issue as PEBKAC (problem exists between keyboard and chair). I had a folder setting incorrect in Retroarch, most likely.