It seems the drag game shortcut to Launchbox window to add a new game method no longer works

[jackmeat]

It calls up the import wizard as usual, but after going through the typical options, it ends with Ready to Import and 0 games in the window, and at the bottom of that screen. Tried this on 3 different games, one at at a time just now, all same result.

[JoeViking245]

The platform you're importing for may be "looking" for specific file types.  Especially if it has a default emulator assigned to it.

If it's just a few games, you can press Ctrl+N and manually add the new game(s) that way.

[jackmeat]

Just for windows. no emulators involved. up until possibly last update, i just dragged windows created shortcut (lnk) over to launchbox. this is something I have not changed at all in my method, so it seems something got changed in launchbox OR maybe something MS changed, but if so, not sure what that would be, i am aware of how to manually add them, i would prefer to use the method I have been using for the last, i want to say, 4 years?

[JoeViking245]

8 hours ago, jackmeat said:

i just dragged windows created shortcut (lnk) over to launchbox

I just ran several tests and wasn't able to reproduce the issue.  After dropping the file(s), I even tried selecting ROM Files (then Windows and left the selected emulator blank) and the shortcuts still imported.  I tried shortcuts dragged from my desktop and also buried deep in some folder.  I don't have a network, so can't test that aspect.   Not that it should matter, as I presume the logic for importing hasn't changed, I'm using version 13.25-beta-2.

My next [last resort] test was to import into a "new" platform. After dropping the files, I manually typed in the platform name "Joe's Platform" and set Scrape As to "Windows". When I got to the last window, it said zero games to import.  This might have been an adverse effect of too much testing.  I went Back one screen and checked Force importing duplicate games and then the shortcuts showed up.  Might be something to try.?.?..

[jackmeat]

16 hours ago, JoeViking245 said:

Force importing duplicate games and then the shortcuts showed up.

I tried doing this on a new Windows PC game that failed previously and it worked. So as a work around, if it just shows 0 games to import, I'll go back and try this force duplicate option. This is on v13.24 but I have not run into this issue over the past 4 years, so it is definitely something new. Thanks for the suggestion, certainly beats manually adding the games. Not sure if I should mark this band-aid as a solution or not?

[JoeViking245]

5 hours ago, jackmeat said:

I tried doing this on a new Windows PC game that failed previously and it worked. So as a work around, if it just shows 0 games to import, I'll go back and try this force duplicate option. This is on v13.24 but I have not run into this issue over the past 4 years, so it is definitely something new. Thanks for the suggestion, certainly beats manually adding the games. Not sure if I should mark this band-aid as a solution or not?

Since that did work, after "the import", in the left panel select the All category (or Platform, depending on your view) to show all games in your collection.  Then above that, type in and Search for one of the games you just imported.  If all "goes well", you'll see more than one.  "Goes well", meaning it (thin importer) is working as intended to keep you from importing the same ROM/file from the same location** multiple times.

 

Expanding notations and results of my previous tests:

**Say you have a shortcut (.lnk) on your desktop and copy that shortcut into D:\temp\.  (aka, 2 copies of the same ROM/file)

1. You drag and drop the desktop one and import it. 
   • If you drag and drop the desktop one again
     • it will not import. 
2. You then drag and drop either one and import into the same platform
   • they will not import (here, it probably does a Title compare?)
3. (after import in step #1) You drag and drop the desktop one and import it into a different platform
   • It [still] will not import (here, it probably does a ROM file [and location] compare?)
4. (after import in step #1) You drag and drop the D:\temp\ one and import it into a different platform
   • It WILL import
     • Note: Different platforms can have games of the same Title

At least that how it worked in my [simple] tests.

If the above search didn't reveal "the duplicate(s)", then the Title was changed after an import.  Search doesn't look at/for ROM filenames. If this is the case, do a Tools - Audit - All Games.  You can click the Application Path column header to sort and look for the exact same file/location.

 

Bottom line:

• Is the issue you came across intentional?  Yes.
• Could the issue be caused by operator error?  That would be a rude way to put it.
  • We'll call in an unintentional oversight.  
• Is the "work around" a band-aid solution?  I wouldn't go as far as to call it that.
• Is it a viable "work around"?  Sure.  If you wanted the same ROM imported more than once.

 

If the Search and/or Audit doesn't reveal any discrepancies, then the "work around" IS a band-aid solution to a possible bug.  I'm skeptical that's the case.  But I've been wrong before. I will be wrong again in the future. And... I will be the first to admit it. 

[jackmeat]

Ok, to do this all from scratch, I just installed Battlefield 6 (so NO way I would have it previously). I dragged the single shortcut created from the desktop over to launchbox, went through the usual, and got to the end. It says 0 games to install. Instead of hitting back and trying the duplicate option, I hit cancel and went to search for a duplicate. There is now an entry for Battlefield 6 as a Nintendo Switch game. So that is being created during the process of adding it even though it says 0 at the end. I am sure I can go back and force duplicates and it will go into launchbox. I am guessing Launchbox is maybe importing any game I install on windows as a nintendo switch game??? before I get to that add process in launchbox.

So new strategy, I just made sure the option to auto-import roms was turned off (it was previously on, and I don't recall going in and turning that on, but I remember reading about the option). Another game not installed before. Checking Launchbox first - No Hollow Knight. Installed Hollow Knight, checked Launchbox, no Hollow Knight. Dragged the shortcut over to Launchbox. It added Hollow Knight just fine. 

Moral of the story, I think the launchbox update turned on the auto import and it was importing my windows games as nitnendo switch roms???? so user error, if you want to call it that. but i don't think launchbox should be recognizing *.exe files as ROMs for emulation? Anyways, thank you for setting my head down this path to finding the problem. Maybe more of a bug in the auto import.  Make sure auto import is turned off. I think that is a solution.

Side note, I went and checked my Nintendo Switch under consoles, and it looks like anything installed since that update is a Nintendo Switch ROM, since I have Star Wars Squadrons, Bloody Zombies (COD modern warfare zombies), and the very interesting one, PrismVR dekstop, which is the software for my Puppis S1 router for use with my Quest 3. That is about the extent of things I had installed recently. So not only pulling windows games, but also productivity software.

 

[JoeViking245]

The intention on the auto-import feature is great!  Eliminating one-or-more steps of adding new games to you LaunchBox collection.

Myself, I have it disabled. But my collection is fairly well established and I'm not a "collector". So adding new games rarely happens. And if I do, I'm comfortable doing it "the old-fashioned way."

 

The auto-import process is generally pretty straight forward.  If there's new files in the platforms established Games folder, add them.  ("Games folder" as seen when you edit the platform and look in the Folders tab.)  They do have some general checks and balances [possibly?] based on the platform name?, the default assigned emulator? (if there is one). But for sure, the Scrape-As value (see link below). 

Certain emulators are "blacklisted" from looking in "the folder".  Instead, LB looks at what games have been installed in the emulator.  RPCS3 is an example of this.  To scan for physical ROM files for its associated platform is a pretty crazy-stupid feat because of folder/file structure and naming conventions.  Some information provided here: Non Auto-Import (platforms)

As for Switch auto-importing an exe file (and Windows games, I believe you referenced?)?  No idea. That platform is not in my arsenal.  Does sound like a bug.  Probably worth reporting.

It's not an exact science as not all emulators' ROMs fit into one "Box" (pun intended. ).  So it's definitely an ongoing work-in-progress.