akatoosh
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by akatoosh
-
-
So, just curious, can I lower the background image quality?
-
24 minutes ago, Lordmonkus said:
For the vast majority of people performance with BigBox is quite good especially on modern hardware. I even run it on pretty old out of date hardware and it is fine.
I can only suggest to look at the Performance thread I just linked and your system for possible software conflicts causing issues. One example of recent software causing issues and not just with BigBox but other programs as well is Nvidias Geforce Experience software.
Saying that Kodi runs better on your Pi is a not a direct comparison because a Pi is a known set piece of hardware and has far less stuff running in the background along side it while a Windows based PC has a near infinite amount of possible hardware combinations and even more possible software conflicts.
I've checked the performance thread and unfortunately nothing there has solved my issue. I've done everything from disabling services to installing the video codec and disabling AV software. I don't have Geforce experience installed; I actually have hardly anything in the background. I've recently reinstalled windows and since it's a dedicated gaming machine, the only programs I use are Steam and steam games, emulators and launchbox. This happened both before and after the fresh install.
My brother also experiences the issue of scrolling through content in big box being 'jittery', and he has vastly different hardware than I.
If it helps, these are my specs:
GTX 970
i5 7600k
8GB DDR4 2400 RAM
Windows 10 (latest)
512GB Crucial M.2 SSD
3TB Seagate HDD (Games storage)
-
14 hours ago, Guywiththegun said:
I'm getting lag too. The worst is going into and out of platform categories. Really sucks.
Yeah, I love Launchbox and Big Box, worth the buy, but Kodi on my Raspberry Pi has better performance.
-
12 minutes ago, noiseordinance said:
I'm glad I'm not the only one. I've since updated my box to 16GB RAM with no changes. It's sorta frustrating to use my controller to flip through Kodi seamlessly, and then get into Bigbox and have an unresponsive UI. I will say that my initial post was incorrect... I said I was having the problem with both wired and wireless devices, but my wired device was a USB cable attached to a keyboard, but turns out it was only for charging, and was not truly wired. I've since hooked up a wired SNES controller, and this does seem to help. So in my case, it might be a wireless issue.
akatoosh, have you tried a wired controller or keyboard? Any improvement?
What I don't get is my house is isolated from the world, and I have just a single 5ghz wireless network in my house. I realize this could be an wireless interference issue (at least in part) but I don't get why all of my control devices work beautifully in Kodi and other applications, but lackluster in Bigbox.
I don't think it's a wireless issue since as you said, my wireless controllers work fine everywhere else. I have a wireless keyboard but haven't noticed it happens with that. I'll report back.
-
Rather than create a new thread I thought I'd reply to this one. I have the same problem. I don't think my CPU is an issue- I have an i5 7600k, GTX 970 and am using an SSD. The issue is the same; flipping through games/platforms is less responsive than I'd like it to be. It seems to have a delay and not respond to button presses depending on how fast I'm moving through them. Similar to what the OP said; if I push 'left' ten times, it might only actually move left about 5 or 6, which feels pretty janky in use. I've gone through all performance troubleshooting steps that I've seen, even down to disabling animations. I can live with it but I'd like to know if theres a way to fix it.
-
15 hours ago, Lordmonkus said:
Instead of using additional apps what about just adding new emulators to LB that point to the same Cemu install but with a different name and command line parameters ?
Cemu User 1
Cemu User 2
Cemu User 3For example. You can then choose which emulator loads using the Launch With... function.
Thanks a bunch! That's a great idea and would also not require me to edit the additional apps for every game that uses separate profiles.
-
So, this may not necessariy be asking for help as much as a feature request, but regardless I'll ask in case there is a solution.
Basically, I use CEMU emulator, and I have multiple save folders on my computer for multiple users. I load each of these with a command line argument in cemu. Launchbox's additional apps feature doesn't allow for command line arguments when you check "use emulator" so I have to type the full path of the emulator as well as the arguments I want to use (not exactly the intended use of additional apps but it works).
This works fine, except for one thing- the "escape" shortcut to close the emulator that I set through launchbox in the emulator settings doesn't work (presumably since I'm not loading the emulator like launchbox wants me to.)
I hope I've made this clear enough, but I can provide more details or screenshots on request.
So in short: additional apps doesn't support extra command line arguments while "use emulator" box is checked.
-
1 minute ago, SlottedPig said:
LOL ok i will jump over to the dolphin forums and see what the devs have to say on that.
Please let me know if you find a solution. So far all I've found are various bug reports on the issue with no solutions.
-
AHA. I've "solved" the issue. This has nothing to do with Launchbox. It happens whenever you try to open a Wii game with Dolphin via the command line.
-
Just now, SlottedPig said:
Right so I feel like launchbox may be pushing some attribute to dolphin that is causing the issue. If you open dolphin first even if the wii remote is on, it vibrates real quick and then you can play as normal. Once you add launchbox to the mix it vibrates in perpetuity while it crashes. Its like a small issue because you can simply just keep the remote off till after you get into the game, but still annoying if you dont have a keyboard near you to close the crashed dolphin out.
Right, which is a bit annoying since the main appeal of LB/BB is to not have to use a KB/M, for me. My theory is that LB isn't giving Dolphin enough time to register the Wiimotes before it opens the games, though I'm not sure.
-
5 minutes ago, SlottedPig said:
I think my post was misleading, if the wii remotes are off, then it loads no problem, its only if they are on when launchbox calls dolphin that this occurs. Yes I am using dolphin bar.
I'm also using a Dolphinbar. I wonder if opening Dolphin before the game launches would help? Or does Launchbox already do that? Because I know that when you open Dolphin, it takes a second to register the Wiimotes (they vibrate).
EDIT: To be more specific, if there was a delay between when Launchbox opens Dolphin and when it launches the game, that may help?
-
6 minutes ago, SlottedPig said:
I also tried turning everything off and still have the same problems. I would love to test this on an older version of launchbox. Is there links anywhere for this?
That's unfortunate, as I've tested on the latest Launchbox version and turning off the remotes always works for me. Are you using a DolphinBar?
Or did you mean you tried turning off controllers... if so disregard that first bit.
-
@Jason Carr this also happens to me regardless of whether or not a controller is enabled in Big Box, as it happens in Launchbox as well. I've recently done a fresh install of Win10, so conflicts with other things should be minimal at the moment.
-
Just wanted to let you know I'm having the same issue. Have to disconnect all Wiimotes before opening a game. This happens in both Launchbox and Big Box. When I launch the game, immediately I see "Dolphin has stopped working." I've also noticed that this happens with all recent versions of Dolphin I've tried.
Launchbox Crashing Dolphin
in Troubleshooting
Posted
Nope, nothing ever happened. There have been various bug reports to the dolphin devs but it looks like they've all been dismissed. The workaround is the only solution we have right now.