smargorps

@deathshakespeare Got updated to the new version number, everything still works great! Ah, yeah, it's interesting that was the case because my sets are inconsistent, so it's almost just as likely I might have tried something from the other format and not even have known until later. Glad to have gotten that cleaned up then. But thank you again. I hope it can help others as well. We can't be the only ones in this predicament.

@deathshakespeare !!!!!!! That seems to have done it! I re-updated to 13.27-beta3, dropped your files in and went to check it out. The config it came with was of course much less set up than mine, but I started with just changing the directory, so it at least saw my original cache. I was able to run stuff that was already cached (which had stopped working on the previous updates), but it wasn't working to try to pull new/unarchived stuff. I figured it might be related to not having actually set the rest of it up, but to try to save some time setting it back up by hand, I decided "might as well try" and I dropped my original config in. It started working with new pulls, existing archives, everything else I've checked so far! Despite the warning to not use the original config and it seeming to work when I did, do you know of any other reason to not expect that to be okay long term? Otherwise, I appreciate it so much! I don't know what else I can do besides say thank you so much, but if there is anything, let me know! Was it possible that this fix "for me" was something that was general enough that it might also actually end up helping more people, or was it coded to something so specific in my logs that you wouldn't expect it to work for others? Partly just curious, but partly might be good to warn people that it wouldn't work, or definitely let people know if it might work as an alternative to your original version. I think the only other thing I thought to bring up was maybe editing the version number in the Settings? I don't know what all the etiquette is when you're just throwing something together like this as a "quick patch" or whatever and not really trying to make it an official "update". But even for your original version, it was nice to see 2.16 as a proof that it wasn't the 2.17 I was using, but it was partly weird to "downgrade" at that point, and I'd imagine might also be confusing for those who might actually be going from 2.16 to yours.. Or just to confirm somewhere in it that it just plan isn't the same 2.16 from the original github you started with or whatever. Just a thought! But thank you again so much, this is so cool!

@deathshakespeare I was so excited to see this post, but it's not working for me, at least. I re-updated to 13.27-beta3, copied your files into place, pulled it up and I'm still getting the same error message I posted above. I did need to change my cache path back to what it was, which I thought seemed a little weird, but it otherwise didn't see all the previously archived games I had in there. I tried a couple different games and same thing. I will try to attach the logs. I also tried with running it as Admin I downgraded back to 13.26 with the 2.17 ACM that was working for me previously and it was right back to working. I will try to attach those as well for comparison. I don't know if it matters, but I pull my games from my server, which is mapped to my Z:, which again, was working until 2.16 broke. Then the 2.17 got me going again. Maybe I'm still doing something wrong. Maybe I have a setting wrong or something, I don't know. But if the expectation is that it should pretty much drop in, I end up with the error when I do that. I know you're not a developer and may not just know right off the bat, but maybe it sparks someone else to have an idea too. Thank you so much anyways, I will keep my fingers crossed. WORKING-events-2026-04-30.log NOT-WORKING-events-2026-04-30.log

I have also been having with the 13.27 betas with 2.17 ACM. Ran into it first with beta-1, still happening beta-3. Coming right from it working just fine on 13.26, it stops working. Then after reverting back to 13.26, it's fine again. Would really like to stay up to date with the releases, but until LB can do this functionality on its own, I might just have to stay on 13.26.

Sorry for late response; I'm just now getting back to this. But looks like that did it; everything seems to have imported. Nearly +200,000 to my LB total. Insane. After fiddling with it for too many minutes, I found a mention somewhere that the images won't load unless you've "seen it" it in FP and then import. Since pages and pages of blank boxes goes against my desire to be able to browse the now almost 250,000 entries that I'm never going to actually get around to playing, I guess I'm going to be saying goodbye to 2.3TB of my available drive space in a few days when Ultimate finishes downloading. Running the importer off of an Ultimate installation should make all of the images browsable, yeah? But either way, thank you again for the quick fix on that, even if I wasn't able to get right to it. I'm sure others appreciated it in the meantime too. And I guess.. is there anything to keep in mind if I run the importer again with Ultimate? I'm not about to end up importing a duplicate set of 200k?

Oh, no problem on my end, no apologies needed. Can't be too mad about user tools being worked on as you can. Totally understand, will just keep an eye out and work on something else in the meantime. Thank you!

I feel dumb like it's just me not able to figure this out, but it seems no matter what options I'm picking, it just isn't working. I don't realllly need it to, but it would be pretty cool to add the chunk to my giant LB setup. I have green checkmarks for the directories, which it seems to correctly call me out for when I pick the wrong folders.. When I try to do Select All, it seems to not like even the very first one. 'unrecognized token' seems to be the kind of message I get when there is a space in the name? Does the same when I pick a different individual name with a space. And if I select something that doesn't have a space, I get this, with "no such column" Then it just says it's reverted changes and nothing happens. I glanced through some of the thread, but maybe I didn't see if this had come up for anyone else.

I was running into this same situation and was hoping to find the answer in the comments, but it looks like it's still been unanswered. In case someone else stumbles into the same situation, I was able to combine the "search, then search again, but end up with duplicates" into just one search with OR operands: ~"*(USA*" OR ~"*USA)*" OR ~"*(USA)*" so it found all of the combinations to be imported in one shot. EDIT: And then, of course, 15 minutes later, I realize if you just add searching World at the same time, you can combine that step too instead of needing to go back to add it to each section. ~"*(USA*" OR ~"*USA)*" OR ~"*(USA)*" OR ~"*(World)*" ~"*(Europe*" OR ~"*Europe)*" OR ~"*(Europe)*" OR ~"*(World)*" (but I'm not going to get new pictures)