megashub

I mapped buttons for page up and page down for use in Big Box. Normal stuff. Page Up works fine, but Page Down doesn't respond at all unless I open the Options menu and hit Back to return to the normal view. After I do this, Page Down works fine. No clue why.

Unfortunately not. But what I did was backed up my Arcade.xml file in case I borked it, and then opened it with Notepad++, with the ToolBucket plugin installed. From there you can perform a multiline find and replace. In your case you'll probably be finding the whole set of lines for the app you want to remove and replacing it with null.

Ooo. In that case, would you be willing to share the script/solution you settle on? Would love to not need to reinvent the wheel.

Sounds right! question (selfishly): Which lightguns are you working with? My Sindens will hopefully arrive in a few more months.

That's more of a LaunchBox question than something for this plugin to solve. If your lightgun software has a commandline argument to close all running instances of the software, you could use this plugin to bulk add two Additional Apps. One that Runs Before Main Application to run the software for use while playing, and another that Runs After Main Application which kills them both. Or, if the lightgun software can't do that, you could do the same thing by writing a small script to find and kill them based on their process ID #s. Or you could write a script that is Run Before Main Application which first launches the Lightgun software, but then stays running in the background watching for the game to close, and then kills the lightgun software before exiting the script.

oh wow. I had no idea these entries were in readable file formats. I would have gone this direction long ago had I realized that. Thank you so much for letting me know. I have no further need for a plugin in order to make such corrections.

This is a great plugin. Thank you for making it. Are you accepting payment for additional features, by any chance? Desired enhancements: Exact Pattern match search of existing Additional Apps Bulk Find/Replace (exact pattern match only). Example: Application Command-Line Parameters of an Additional App contains a typo: -hiddne -exit -play Perform a Find/Replace using pattern: dne Plugin finds all Additional Apps that contain that exact pattern and presents a multi-select list for the user to select which games to modify. User provides the new string to replace: den Plugin makes the replacement on all selected games By restricting this new feature down only to exact matching, I'm hoping the complexity is much lower (no fuzzy searching, no wildcards, etc etc). Thoughts?

I don't know if this issue is specifically what was addressed, but there was this note in the 11.11 changelog, so it may be worth evaluating it

Calling all 360 stick users! Please go vote on this enhancement request, originally opened in 2017 and still pending in the backlog. Requests with the most momentum behind them will generally get higher priority, especially if the level of effort required to do the work is low, which I believe this one will be. Basically, it's @James35 's %romname% variable concept above + the use of this plugin to bulk update your rom collection within LB.

Looking pretty likely that this is a Theme issue. I'm 1 hour in using the Default theme, with the exact same elements in use, and no problems at all. I was seeing issues as early as 30 minutes when using AllNightLong. Update: confirmed. 2 hours in now, and absolutely no performance problems.

It was one of the 21 offered for download in the BB Themes Manager, so I grabbed it that way. It's AllNightLong. I'll go find the view after this test is over, but it's a vertical wheel of clear logos with game details and gameplay video. I was using it with an auto-populated Favorites playlist, if that matters.

This test has been running for nearly 90 minutes. No problems at all. I'm going to try to find a view that uses both Clear Logos and videos in the default theme next. Edit: Found one. Starting a new test. If this one comes back clean there's no difference functionally between this view and the one that causes the machine to CTD, other than the Theme in use. If it does turn out to be Theme-specific, what's a way Theme makers can find the offending code?

Okay. Moved to new test: Switched to a vertical wheel (text titles only), but with game details (static art and gameplay video). Stay tuned.

45 minutes in now and not a single blip during the spin on this test. That's a pretty stark contrast from the previous tests. Only thing I changed was the theme, which shifted the view to this covers-only wheel. The test is still running and I'll keep monitoring, but I think the next test should be a view using the Default theme that includes the videos, if one exists. Yes?

The only background apps I have running to my knowledge are Steam and Epic. I have no AV/Security software installed. It's just Stock Win10 x64. Drivers: done. All drivers are current version (it's a very new installation). Updates: Same. Current stable release. I have the default theme on a test run now. The default view (or at least the view it gave me after I switched back to it), is just a horizontal wheel of static cover art that it spins (no video or text beyond the title in the top right corner). That's been running for 15 minutes now, with no visible blips or lags developing yet. For comparison, the other theme kicks off the gameplay video for each title when the spin stops. Perhaps that's an important factor? Will keep monitoring it.

Ahh got it! That's good to know, and now I totally understand why this is such an odd-man-out issue. Happy to help give you as much useful testing data as I can.

Good thought. Yes. I have tuned all power settings in Windows.

Here's a detailed breakdown. These are high performance machines geared specifically toward AAA-capable gaming and are configured as such OOTB (at least in my case running an 8th gen Hades Canyon NUC): https://blog.itcreations.com/intel-hades-canyon-nuc-8-review/ I think this is why it's a software-side problem. Is Attract Mode fully unloading the media for a given game and letting go of those resources before loading up the next one? Because if it's holding on to cache or isn't fully killing processes every time, it's possible it's just grinding to a halt over time. But I can't speculate well because I don't understand how Attract Mode works under the hood.

Ram: 32GB DDR4, default theme, sure. I'll run a fresh test with default theme and report back.

2nd attempt to capture details about the progression of this problem: 12:55 start progressed exactly the same as first attempt 2:01 was the last time the clock updated. 2:20 all video and images stopped displaying almost entirely. Every third or fourth game, the video appears and plays, sometimes only for a second or two. Only the text title information is reliable and keeps changing with every spin. 2:47 CTD

10:19 start 10:23 slight jitters noticed toward the end of the spin 10:33 jitters still slightly noticeable, a few more, but still very slight. Only apparent on the longer-duration spins where max spin speed is achieved. Noticing on the long-duration spins that when the wheel is spinning at its fastest, only a small subset of logos are being rotated and displayed. Though the game selection itself does still seem to involve the whole game list. At the beginning when Attract Mode first started, the high speed logo spin appeared to include a larger quantity of logos. 11:07 during the spin, logos are starting to disappear for a second or so and then reappear and the spin has begun to get disjointed. It’s like the visualization of the spin is starting to lag. Seems to happen less severely or even occasionally not at all on short-duration/slower spins. I noticed throughout the test that the audio of the video that was just playing stays playing during the spin to the next title. Is that by design? I think the previous video remains up and playing in the background during the spin. 11:13 slowly getting worse. It’s not just the wheel that lags, but the text titles changing lag at the same points as the wheel. Despite the now-obvious lag while spinning, the video playbacks themselves remain smooth and lag-free. 11:16 the previously selected game is starting to flash back up on the screen for a second or two intermittently while the wheel is spinning to the next game. 11:17 Sometimes it takes so long for the lag to catch up that the spin kicks off again before it settles on a game. This may be the death spiral that ultimately crashes the app. 11:20 LB’s clock is no longer staying current with the actual time. Stuck at 11:17. The wheel while spinning is almost not visible at all. When it does stop on a game, the wheel visually displays in chunks before getting spun again a second later. 11:21 There’s almost no graphical content left on the screen the majority of the time. The lag is cumulatively so bad now that it’s just the theme background and the text elements that stay on screen. The images and video content flash on and off, and mostly stay off. 11:27 Interrupted Attract Mode to check Event viewer. LB:BB’s clock has refreshed to current time. While Attact Mode was not active, LB:BB Process was consuming 18% of CPU, 582MB of memory. Disk and network are both at 0%. Nothing else running on the machine comes anywhere close. When Attract Mode began again, it’s performance was still badly degraded. It did not clear up as a result of being interrupted. Maybe none of the video players are actually being unloaded all the way, and they gradually build up until the system runs out of resources? 11:36 LB:BB has stalled and is entirely unresponsive. Awaiting CTD. 12:23 Still hung and not responding. Hasn't CTD'd yet. Probably would have if I hadn't interrupted it to check the resource consumption.

That was definitely an intentional decision. The last thing I wanted to worry about on this build was hardware horsepower. I'm sure it would struggle to play the topmost tier of games, but those aren't in scope for this build anyway. I was pleasantly surprised it played Tekken 7 and KI flawlessly. Nah, the problems I've run into have all been, predictably, software quality-related (low quality rom dumps, pain-in-the-ass emulator configs, controller configs, etc). So chasing this Attract Mode annoyance is minor in comparison. Still, if there's a memory leak at play here (which is my current belief), if I can help the dev find and fix it, great.