Bedwyr

But the weird thing is that I had no issues in Windows 8. What changed???

I'm going back to the 360 Controller for now and will keep the XB1 controller equipment around for troubleshooting purposes. Hopefully the 360 still works right.

This is really bizarre. Ok. I've upgraded to Windows 10 for a few months with no problem. I've used the XB1 controller in Steam with no problem both before and after the upgrade. However, now that I've been experimenting with a number of HTPC setups, something weird is going on. - In Kodi, I could not use the controller as the left trigger would cycle through options very fast. I could partially depress the trigger to stop it, but not consistently. I found the following links: http://forum.kodi.tv/showthread.php?tid=202869 https://www.reddit.com/r/kodi/comments/3tx3xb/xbox_one_wireless_adapater_not_working_with_kodi/cxpwo8c I'm not completely sure what to make of it, but apparently the axes changed with a newer driver edition? Something about combined vs separate axes? That could explain something, but not everything. - In Project64 as I mentioned in the support forum, I cannot map the XB1 controller for similar reasons. the controller setup keeps reading a -z axis input (left trigger apparently) for all selections, indicating that the left trigger is constantly at a full -z deflection the the trigger not-pressed. - Now in PadStarr (the successor to Pinnacle), the same thing is happening with my old Chrome profile but with the lovely addition of bizarre mouse behavior even though I have the triggers mapped to scroll-up scroll-down inputs. What in the world is going on and what changed? I checked all three with the wireless adapter (release Oct 20) and with the USB cable in case there was a driver difference. No change in behavior. Steam works great, but everything else is unusable. What gives? I've tried researching this, but there's too much conflicting information out there from XBOne console owners drowning out any PC user information. The Kodi discussions seem to get closest to the heart of the issue. I did find this discussion in Steam, though: https://steamcommunity.com/app/347830/discussions/0/537405286635358498/ I tried following their suggested link and it merely goes to a set of hooking-things-up instructions. No drivers: http://support.xbox.com/en-US/xbox-on-windows/accessories/connect-xbox-one-controller-to-pc Man this is frustrating.

I discovered the problem Project64 was having regarding controller setup. Microsoft changed how the controller triggers work. I only discovered this as Kodi is behaving exactly the same way: http://forum.kodi.tv/showthread.php?tid=240570 This may be useful information in the future for others using the XBOne controller. And more information: http://forum.kodi.tv/showthread.php?tid=202869 It appears that the trouble (maybe all of the trouble?) stems from the wireless adapter for the controller and how it is interpreted by Windows (10?) as a wireless network device with an associated Xinput HID device.

Dumb idea but maybe a solution. Why not dump screenshots into your front images directory, replacing the box covers for the system and refresh the images?

Fixed and working. Still wish I could use a high res texture render like Rice, though. Games like Dr. Mario 64 and Ogre Battle 64 have a lot of muddy textures using the gln64 plugin.

SentaiBrad said Oh, you're having controller issues in P64, not RA. Nevermind. I haven't been using Project 64, I traded it for the Mupen core in RA. Yep. As such I'm still inclined not to use P64. *However*, I've now apparently screwed things up for Retroarch. I can now load the mupen core and then the game, but not a newly created mupen cfg and then the game. I deleted as many cfg files as I could think of (usually core options did it???) and still get the latter behavior. Truly frustrating.

Share for the Google search engine? (never know; dummies like me might need to track the solution down.)

Oh yes, I should add that after experimentation I've discovered that all versions of Project64 appear to have issues with Windows 10 or my drivers. Even if the display software didn't crap out the Xbox One controller appears to be super-finicky for the controller binding plugin. It keeps throwing out a left or right trigger output (z-) into every button assignment I try. Impossible to assign anything. Project64: es totalmente muerto. I'll keep my clean copy of 2.1 and 1.6 around, but I doubt it'll get installed again.

Ah. Had forgotten that the game needed to be loaded. So Rice causes immediate crashes. Is that a known behavior? I found this but don't know what to make of it: http://ubuntuforums.org/showthread.php?t=1128246 I also reproduced the settings (delete core options cfg->load core->load game->pause->change graphics core->close content->load game->crash) and wrote the results to a log file, but no real clues there I can suss out. Rice is mentioned twice at the end: "Environ GET_VARIABLE mupen64-gfxplugin: rice" but not other clues such as a segfault or other issue.

Sure thing. I shall certainly try to do so (and have solved a couple of these in the meanwhile). It may be a bit as I'm fighting a headache and some unrelated time issues. I'm registered over there now, at least.

Integration continues and I'm getting more impressed with this software. Looking forward to integrating with Kodi. I'd like to beg and plead for help with a side question, though. For some reason I can't register on the Retroarch forum. Sadly I have to hope for some help here even though it's not quite on-topic. Please be kind. I'd like to make plugin and graphical changes to mupen64plus. That's easy to do in the standalone installation. However, I'm trying to unify to Retroarch as much as possible. I recall there being "core options" in RGUI in 1.0.x. In 1.2.x is there a similar place to make adjustments or change graphics plugins to, say, Rice?

Hi. New user here. I just wanted to report back two or three hiccups I noticed in BigBox. (Good job by the way, it works very nicely so far.) - Well, more feature request than bug: LaunchBox has a habit of blindly accepting rom files and associating by name. One nice option that might be worth having is restricting a rom search to specific suffixes (in Windows at least). I blew away old saves after noticing this so it's not a big deal, but it could have someone like me not paying attention and getting duped games. - A couple of times using the clear logo art I had the game menu list pushed off the screen. I think the art glitched because I saw a long one-pixel-wide bit of color down the left side and I could still control that menu from memory. I erased the downloaded art with my own wheel art copies from Hyperspin. Try randomly downloading the art for StarFox and see what happens in the menus. That might replicate the behavior. - Dragon Quest III (SNES translated) doesn't pick up screenshots properly. The Screenshots are using the standard Hyperspin/EmuMovies naming conventions. There might be a name block of some kind given that the media use a Japanese transliteration in the title of the screenshot: "Dragon Quest III - Soshite Densetsu (Japan) (Translated En)". Not really an issue, but thought I'd mention it. - The option in BigBox to *not* keep favorites at the top of the games list is not working correctly. Favorites stay at the top whether that's checked or not. I do like favorites, but I also like keeping things alphabetized. - The rotating animation for the left side lists is jumping slightly. I switched to sliding as it was giving me a slight headache. The rotations for videos and game boxes look fine. - May be a Retroarch issue (1.2.2.7), may not be. I swear I set per-core settings in a file and had that exact file loaded at game runtime. The game runs windowed with no correct controller settings and uses the old RGUI interface. It shows the correct cfg loaded, but incorrect settings for what I saved. I have to change the UI back to XMB, explicitly point out the assets folder so it'll load the correct graphics for XMB, and then re-check all the settings for the platform I want to use. I'm wondering if one has to set cfg only when loaded from LaunchBox. I haven't tried loading from Launchbox, exiting (auto-save on exit set), and then loading Retroarch and that cfg directly to see if something is glitching from LaunchBox's side.