triXope

I realize this post is somewhat old now, but I've had this same issue for quite some time and thought I might share my findings so that I may help anyone still experiencing this issue (and hopefully shed light so that someone else may come up with a better solution). Up until recently, I have been fine with installing any game updates and/or DLCs into Yuzu. But due to a recent change in my setup, that was no longer working out so I needed to come up with another solution. First off, the issue does lie with Yuzu, not LB/BB. And second, it IS possible to launch integrated XCI files (those containing base game + updates and/or DLCs) from Yuzu via LB/BB. #1 A game directory/location MUST be set within Yuzu pointing to any and all games you wish to launch. #2 Any game updates and DLCs MUST be active within Yuzu (aka not disabled via game property settings). #3 Any time a new game is added to the specified game directory, Yuzu must be launched (for Yuzu to initialize the game and add it to it's list) and you must click "Reset Metadata Cache" located under Yuzu filesystem settings. #4 I have found that some integrated XCI games won't launch properly if there is cache generated, so I run a script to clean out cache files any time Yuzu closes. #5 Last but not least. And this is the most finicky "problem" relying on a magic number... LB/BB will not launch an integrated XCI (game + updates/DLCs) if Yuzu does not have a chance to fully load the games list before the selected title is launched (this only is an issue the first time Yuzu is launched on a fresh boot). As a result, the base game will load but ignore any game updates/DLCs associated with the select title. If that game is closed and relaunched, the updates and DLCs should load fine, provided the first launch was kept open long enough to load the full game list in the background (this clearly is not ideal as no one wants to wait for a game to load only to close and reopen it). This becomes more so the larger your list of games becomes, and if small enough, it may not even be an issue. But if it is, the solution I have come up with to handle this (which is a bit more of a hack than I'd like), is to run a Powershell script at system boot which will launch Yuzu hidden, wait X amount of time for the games list to fully load (where the magic number comes in), and then close Yuzu (my BigBox starts with a 20 second intro video, which I don't bypass, to allow ample time for any background processes to complete). That way the games list will have a chance to fully load and be ready for when you do go to play a game. Hopefully the devs will take a look at this and figure out the underlying issue, but in the meantime, I know this seems like a lot, and a bit hacky, but it works for me (hopefully just as a temporary workaround). And hopefully this will help others to understand (better than myself) what is going on, and potentially come up with a better solution. I'd love to hear what anyone comes up with.