Bedwyr

Urgh. Ok, possibilities that occur to me: - Memory resident issues -- Controller Companion -- AnyDVDHD -- nVidia Experience -- Java (for Minecraft) - Windows 10 - Hardware -- nVidia gtx 660 -- 3670k i5 Any other possibilities?

Ok, so tried beta 6 and had the same problem. Uninstalled and reverted back to 5.8 and discovered I have the same issue. This happened right after rebooting windows so I know it's not a parallel program like Kodi causing anything. Could be a memory resident program like controller companion or anydvd. Clarified steps to replicate: - Reboot Windows - Start BigBox - Start a game in BigBox - Close BigBox - Open LaunchBox - Select Options

It is good, but man the Steam Controller has the greatest flexibility I've ever seen in a controller. I know the complaints against it and agree to some degree, but usually I'm not playing competitive twitchy stuff (and have M&K or XB1 for that). An example is the official config for Kerbal Space Program. Kerbal Space Program! A flight/space physics simulator with CAD style design interface. It uses much of the keyboard with multiple axes of control and then some. Their Steam Controller config has five contextual configs for each mode the game is in and full support for pretty much every keypress. I know you can do all that with a combination of, say, Pinnacle and AHK but this is easy to set up in one package. I think it's the multi-modal trackpad settings that puts it over the top for me and pretty much says "this thing can do *everything*. Anyhow, that's all fanboy gushing. Thanks for indulging me if it's not really up your alley; I just had to get that out.

Jason Carr said Hi @Bedwyr, the situation you describe is basically what happens when LaunchBox is busy working in the user interface thread. I put some work into making sure that long processes happen in background threads instead of the main user interface thread (to help prevent that stuff), but I haven't gotten all of them. I assume LaunchBox does come back after a while? Or does it stay that way permanently? Also, by the way, per DPI scaling, LaunchBox should show up fine without any blurring at most DPIs (100%, 125%, 150%, and 200% are the DPIs that I test with). The only exception to this is when Windows uses different DPIs for two different monitors, and Windows will unavoidably fall back to the blurring approach. Just curious that you're seeing blurring there. I think I may have found at least one trigger. First what I tested: - I started LB and opened Options at least 6 times, no problem. - Exited and restarted LB and opened Options at least 6 times, no problem. - Did this a third time, no problem. - Started and exited a game, no problem. - Launched BB, exited BB without starting a game, then launched LB and opened Options. Got the hang. I timed it for at least one minute. Clicked on the window and it stretched itself over the taskbar to full screen. Moments later got the "not responding" dialogue and killed LB. - Thereafter LB freezes when opening the dialogue window every time. So it appears running BB has something to do with it. Are any resources shared that maybe aren't getting released?

Ok, so regarding my issues. Tried Beta 4 update and it seems to have cleared the Big Box freeze ok as that was likely the same issue others had. The LaunchBox Options menu problem is still there, however. I have not yet tried other actions that bring up a popup window, but I'll report back if I see the same thing when using other functions. As it is... - It usually doesn't happen the first few times I try to load the options window. - However, after a few tries whether I've restarted LaunchBox or not, attempting to load the window will -- a) cause LaunchBox to lag with no window appearing -- b) cause the interface to attempt to go into some kind of fullscreen mode -- c) freeze entirely sometimes bringing up a program response dialogue (no error message or code) The fullscreen popping is weird because the text goes fuzzy as if it is trying to display using some kind of DPI scaling or lower fullscreen resolution. I'm pretty sure it's not the latter because I don't get resize flashing when I attempt to alt-tab out. The DPI thing requires a bit of background to explain. First: I'm running an HTPC on Windows 10 with a 1080p television at full resolution. The only display driver is a GTX 660 card. Windows 8 used to have a really crappy DPI scaling algorithm that got some pretty satisfactory improvements by 8.1. For whatever reason Microsoft went with a different or older scaling algorithm that leaves some scaled windows, especially older win32 program dialogues (think 7zip or Filezilla) fuzzy. There is a set of registry settings I can load at start time to force 8.1 style rendering, but for some reason it played hob with other software settings, so I disabled it. The appearance I'm trying to describe is exactly what those win32 windows look like when trying to display at 115% or 125% zoomed. As if LaunchBox went from a regular unzoomed window to a DPI zoomed fullscreen app popping over the taskbar. That's the point where it freezes. I *do* have DPI scaling disabled on the exe's compatibility tab so that I don't have to deal with the fuzzies. I have to squint across the room at smaller text, but it's still better.

Jason Carr said @Bedwyr, I'm confused. Is the beta still locking up for you when you go to Options? Or is it just reverting that fixed the issues? If the beta is locking up then I'll need to get it fixed. Yep, it was just the beta. I haven't encountered a single lockup in either LaunchBox or BigBox so far on 5.8. I can try the update tomorrow possibly.

Sorry about that. I just did an uninstall with a fresh download of the non-beta. Everything is intact and operational.

Likewise. BB hangs after exiting the emulator (Retroarch) on the "loading game" screen. I'm going to revert to non-beta for the moment. Edit: Oh dear. And now LB hangs every time I select "Options" Edit edit: Rebooted and everything worked well the first couple of times I tried them. Then after loading a game from BB a third time the freeze repeated itself including the LB behavior. I'll uninstall LB and re-load only the stable version.

Try one of the other ones. I can think of three, two are pay: - Joy2Key - Pinnacle/Padstarr (Padstarr is their latest) - Controller Companion (avail through Steam) I've tried almost all of them and would say that Pinnacle is likely the most flexible if you exclude AHK which is more scripting language than mapper. Controller Companion is my current favorite. I haven't pushed it to its limits, but very clean and well put together. Their keyboard solution is *sexy*. I'm using it to control Chrome as opened from Kodi and so far pretty happy. Just need to tweak it to allow it to send an alt-f4 signal so I don't have to un-fullscreen Chrome.

I usually limit to Retroarch, Dolphin, and maybe a PS emulator. If I observe weirdness again on these or other emulators like MAME I'll certainly let you know.

Now if the worldwide hacker/dev community can come up with a Steam Controller wrapper for the Windows interface, we'd be all set. I won't hold out hope though. The updates on the the controller, in beta, are too frequent I bet for hackers to dedicate time to it risking a fix breaking. And Valve is on record wanting to open source as much of the controller's hardware and software as possible.

The latest Windows 10 update (KB3140768) according to a Kodi user seems to have fixed most or all of the issues regarding XBox One controllers. I've tried plugging one in and so far so good. Kodi responds normally with no inappropriate mapping or bizarre analog input behavior. Big Box likewise responds well and normally. I've tested Retroarch with a SNES core loading FFII and controls respond normally. This is in response to the weird remapping issue that came with the big wireless XB1 release in Oct or Nov. That update appears to have remapped control inputs to something distinct from the 360, notably changing the axes the L and R triggers are on causing unusual control responses and sometimes no control responses. This appears so far to have been fixed. I cannot speak to the nVidia issues in the other thread. That may be a different problem, perhaps unique to a recent video driver update. It's not clear to me what's happening. The Kodi thread: http://forum.kodi.tv/showthread.php?tid=202869&page=5

That's an odd combination of issues. I've been fighting Xinput problems with the XBOne controllers ever since the wireless update, but missed the new nVidia drivers with Vulkan support (and from what I'm hearing, I might be glad that I did; it sounds like a botched update that was withdrawn). http://nvidia.custhelp.com/app/answers/detail/a_id/4054 For myself, XBOne Xinput issues appear to be resolved and they behave with control output (no changes in the L/R trigger assignments and the like) exactly like the 360. This was reported in the XBox One controller thread on the Kodi forums and I just verified with my own build and Retroarch. It's working smoothly so far.

Jason Carr said Hey, @Bedwyr, good to see you. Yes, it is certainly possible, which is why it's on the short list right now (per the most recent email I sent out). Hoping to get to at least give it a shot before the next official release. Which email was that? I got a series that came from bitbucket while I was in a meeting with a research professor. We were talking about Github and project planning, expecting an email of his when they came in. I got flustered and deleted them. Happens when there's multiple software projects going on. Either way, good to hear. I'm still trying to figure out the status of the Steam Controller and what, exactly, it does when Steam is either running or not running. Valve refers to the not-running mode as "Lizard mode" referring to the rudimentary emotional human brain ("lizard brain"). A number of redditors and Steam fans suggest that Lizard Mode is a combination mouse-and-keyboard in HID rather than Xinput... but maaybe it runs through Xinput when Steam is running?? I dunno. It's hard to get answers and you know how Valve is.

Hey. It's been a bit since I've been on the forums, but I wanted to ask a musing question. Is it possible, maybe even probable, that creating a full Xinput implementation would solve multiple problems, not just the Steam Link one? My major bugaboos are the weirdness that is XBoxOne's current configuration and running BB through Steam using the Steam Controller.

Hey. I think I'll try a little more experimentation today. I'd like to do some testing with controllers, Launchbox as launched from Steam, and launching games directly from Steam. But, as I wrote in another thread, I'm having trouble running emulators from Steam and need help. So two questions: - I know Ice is a product used for this, but antivirus software detected malware. Is this accurate or a misdiagnosis? I can find no similar experiences from others when I search Google. - I tried to create a non-game link manually, but it didn't work. I created the link directly to the emulator (Retroarch) and tried to use a launch option string that looked like this: -L "cores\snes9x_next_libretro.dll" -c "config\snes9x_next_libretro.cfg" "name.smc" Is there a reason it won't work? Again, I would like to test controller behavior using both Launchbox and Steam directly as links. Thanks.

I'm a bit "off" today, but wanted to try an experiment: run a single retroarch SNES game within steam and see how the steam controller reacts. I don't want to run ICE as it may be coupled with ransomware. What is the best option to launch retroarch with a game in Steam? I tried to create the correct command-line options in "launch options" but Retroarch is just hanging. -L "cores\snes9x_next_libretro.dll" -c "config\snes9x_next_libretro.cfg" "name.smc"

That is probably the most useful thing I've found in RA to date. Before I figured out that you could use that toggle setting to mode-shift the controller, I had savestates mapped to the d-pad (XInput controller). Up to load, down to save, and L/R to change the savestate number. It worked fine, but I had friends who would instinctively try to go to the d-pad for NES controls and get weirded out when it didn't work. Which is completely understandable! Now a right-stick click + d-pad does the trick and the controller is now much more flexible.

Jason Carr said No!!! We must have MOAR VOLUME!!! DISTORTION!!! BLOWN SPEAKERS!!! Hopefully I can get that volume control stuff in there soon. ;) Hardy har. No problem.

Is this on 5.5 or later? I've got an Emumovies subscription and wouldn't mind trying it out on this instead of copying stuff over from Filezilla.

Yeah, I come from a different engineering background and usually assume that unless there's a compelling feature or there's a security exposure issue, I'm usually disinclined to update. But that's the aerospace instincts talking. Thanks for the ref.

1.2.2.7 from Stable. 1.3 fix a lot?

Thanks. Gah and they moved the shader options. They used to be next to the video filters. I can't set the shader settings without a game loaded. editorial: I'm grateful for the UI changes they did make, but the organization of options and methods violate all kinds of UI design principles. The menu system doesn't need a re-think. I think the entirety of Retroarch needs to be re-factored toward a friendlier interface from the way automated controller bindings work to the way file saving works ("Save to Current" doesn't exist btw... the menu options are: "Information", "Load Configuration", and "Save New Config"... no option to save to loaded config except "save on exit"). As a citation: https://www.cs.umd.edu/users/ben/goldenrules.html At a glance I'd judge the Retroarch UI to be bad at 1, 2, 4, 5, and 6. editorial over. Thanks for obliging.

Yeah that worked. How do you disable filters, though (without loading notepad++)? In the menu there's no option to simply disable a given filter.

Not exactly per our discussion earlier, but I tried to change the video filter in Snes Next on a whim to see if there was something I might like. No filter setting was stable; retroarch would immediately crash when any filter was selected. I got similar crash behavior using Mupen64 and I'm honestly kind of put out about that. Why such an allergic reaction to a filter setting in this case?