Timber-eXoProjects

Confirmed, thanks a lot Works perfect now 🙂

It seems there's a problem with the visual presentation. My values are saved correctly but if I scroll down the Custom Fields and scoll back up, the values doesn't fit the names anymore. If I double click on the values, they disappear (if they were on the wrong line) or come back again (if they belong to the field). Added two screenshots, screen1 is correct, screen2 has mixed up the values after I scrolled down and back up again. If I click "Cancel" and edit the game again, the Custom Fields are still correct. But if I scroll down/up another time, they're mixed up again.

thank you 👍 I created a feature request in bitbucket: https://bitbucket.org/jasondavidcarr/launchbox/issues/9117/include-custom-fields-in-the-search

I just realized that custom fields are not taken into account when using the search function and stumbled across this old topic here I have added an ID to all my games, currently as a custom field ("eXoID") But I can't use the search function, only the filter function. But since there are thousands of IDs, it's not easy to find the entry in the filter list... So it's not easy to search for a specific ID Are there any plans to add the custom fields to the search function yet @C-Beats @Jason Carr ? If not, I'll submit a feature request for this... 😉

Ah, sorry! I noticed too late that it got already fixed in the beta (I was still on the stable release), Thanks a lot 🙂

Hey C-Beats, any news on this issue? I also noticed this when I entered the exact values of my physical box and activated "Draw Spine Image". If I uncheck the spine image, the size of the box is displayed correctly. direct compare: this ist the spine image, it's not that thick and also I think the spine image size shouldn't override the fix depth entry at all:

That's great ! Is it also possible now to store all 6 sides of the 3D Model (front, back, spine-left, spine-right, top, bottom) ? Or is the spine still just doubled?

No, it's a real SymLink, not just a Windows Shortcut. Here's the tut from our discord: How to run Launchbox from a Network Drive or NAS with a Symlink (tested on Windows 10 & 11) Install eXodos Download & install this shell extension (`https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html`) - no restart required Using File Explorer (may work with other file explorers), Right click on the installed Networked eXodos folder and select 'Pick Link Source' - this selects the Networked eXodos folder as the soruce Navigate to the Local folder you want the system to associate the Networked eXodos folder and right mouse click and select 'Drop As' pop out menu and then click 'Symobolic Link', it will create a 'new' folder with a small shortcut icon over It has now created a Symlink folder and Launchpad can now be run from your network drive or NAS It will affect performance as it's running over a network, however in my tests I'm happy with the speeds.

Ah, so you changed the paths of the game folder? Then the plugin can't find them I guess. They need to be in /eXo/eXoDOS relatively to your Launchbox folder. I recommend to use SymLink for the eXoDOS folder then. Just create a SymLink in /eXo/ to the eXoDOS folder on your NAS. You will find a detailed tutorial on our discord too.

(I also would recommend to update to eXoDOS v6 of course, we changed a lot in the way the scripts and plugin work and added lots of games, images, manuals, extras and... 😉 )

The plugin can be found here: /Plugins/eXoPlugin.dll IIRC we had this once before where the files are on a NAS and somehow the permissions won't work for the plugin to "see" the folders on the NAS. I think the solution was to reset the permissions on the NAS and set them again. But I'm not sure. Do you have the Launchbox installation on your NAS too or do you use SymLinks?

@C-Beats is right, the flag is set by the eXoPlugin we added to the collection. It checks for presence of the unzipped gamefolder. Since you can start the game, the folder must be there. But the plugin can't find it. - do you use a NAS or network drive for the eXoDOS installation? - do you changed the path of the eXoDOS folder for the gamezips? (Should be /eXo/eXoDOS/) Maybe the plugin has no permissions to access the folder?

Hi, why do you even try to import the eXoDOS games into LB ? this means you would lose all the metadata, extras, manuals, images ... that come with eXoDOS. If it's about importing eXoDOS into your existing Launchbox environment, there is a merge guide. This is IMHO the better way, because it preserves the curated collection and everything coming with it.

currently "Spine" is used only for top and bottom of the 3D box (as the same image). However, there should actually be four different images to create an accurate 3D Model of a full (e.g. DOS Big Box) scan: Spine - Left Spine - Right Spine - Top Spine - Bottom (added vote and comment to your bitbucket item @Retrofrogg)

wow, that sounds awesome !!