C-Beats

I sincerely doubt it will, but does moving the 2nd monitor to the right of the first make any difference at all? I suspect right now the text view is the main thing causing your issues right now though.

Would depend on the theme in question for an exact response but if the themes use our built in scrolling text control there are properties you would have to manually change to adjust it to your liking.

Also out of curiousity could you send me a pic of your Windows Display Settings like shown below. Curious how you have things set up in there and if that is playing a part in this at all.

@Benjc Could you try a non text view and let me know if that corrects your issue? I don't believe the way the marquee view is written right now that it will work properly in text views. We have made some changes to that system internally but they aren't in any public release yet unfortunately. That being said it should appear blank (forcing a black screen) when set up properly, and it doesn't even appear you are seeing that. Will you test the non-text views for me and see if see any changes, and also PM me your BigBoxSettings.xml (located in \\LaunchBox\Data])? I'd like to take a look and make sure there aren't any settings that may be negatively impacting your ability to see the marquee.

@Benjc also useful information would be. Are you seeing the black screen on all views? Are you using a wheel view when you see the black screen, or a text view? Is the screen black during both platform AND games views?

Set by the theme and platform you are using. What theme are you running on Big Box?

Are you using default marquee view @Benjc or a different one? I won't be able to test exactly with that resolution as I have nothing even CLOSE to it, but want to make sure I'm looking at the same file you're trying to use.

That bottom thing is the metadata/information for the "Consoles" Platform Category. It is auto-created for console systems and then the imported system is assigns it as it's parent. If you use the "Platform Category" side bar filter instead of "Platform" you would see it (and could edit it as well).

Aww you cut the vid at most important part! lol. What file was generated after you pressed OK there and then closed LaunchBox?

Games start where ever the emulator is designed to start from, we don't tell it to launch on a specific window. If the emulator doesn't have a setting that says "Launch on monitor X" it usually set to launch via the primary monitor (as marked in Windows display settings). Also just so I'm clear, is Windows recognizing your marquee as 1920x360 or does it see it as a different resolution?

Should be able to run the download media tool again and on the last page select the middle option (do not replace). The download tool will then skip any image you already have downloaded and only get the ones missing.

How did you import the platform? Drag/Drop, manual, or some other method? Did you manually edit the notes of your platform?

What do you mean by its resetting itself?

Not a problem, send it when you can and we can go from there.

I doubt it is the cause of the issue but can you see if \\LaunchBox\LBThemes\ is readonly, and if so remove that flag and tell me if that helps at all?

The errors the exact same? What theme are you trying to load when you get them? Can you post one just so I can see the message, some times the key is hidden in the nasty wall of text, may prove to be useful.

Yeah, that is intentional. Those links or shortcuts are created on start up and then cleaned up on close. Now that you are seeing that can you try to apply a theme and tell me if you continue to see the errors you were having?

As I stated it isn't the only cause, but is nice that you can confirm it isn't the cause this time around. Some other things you can check are: Ensure the folders in your Core folder are NOT read only for any reason Ensure you don't have any sync software that could be locking the folder Can also be helpful that you delete the following folders from the Core directory while LaunchBox and Big Box are closed then attempt to open LaunchBox after to see if the symlinks are then created appropriately: \\LaunchBox\Core\Data \\LaunchBox\Core\Images \\LaunchBox\Core\LBThemes \\LaunchBox\Core\Manuals \\LaunchBox\Core\Music \\LaunchBox\Core\PauseThemes \\LaunchBox\Core\Plugins \\LaunchBox\Core\StartupThemes \\LaunchBox\Core\Themes \\LaunchBox\Core\ThirdParty \\LaunchBox\Core\Videos

Most of these errors are caused because the symlink creation process that occurs on start up fails. The most common reason is the drive LaunchBox is on is not NFTS but there are other causes. You should be able to turn on debug logging and then try to start up into the theme to get the error, then just close LaunchBox (or Big Box) and look in the log to see whether that process failed or not, and any information as to why it failed. Another easy way to tell if this process happened correctly is to open LaunchBox, then go to the \\LaunchBox\Core\ folder and look for a LBThemes or Themes folder. If there is an actual folder there (and not a shortcut) then the symlink process is failing on your machine.

Hey @BadServo was trying to look into this but having a hard time replicating. Could you zip up your data folder and PM it to me? I'd like to take a look at your settings and see if I can use them to track down the cause of what you're seeing. Also is there anyway for you to get a few screen grabs pasted here so I can make sure what exactly you're seeing so I do my best to replicate and confirm the issue? @lotus if you are still experiencing the issue (only mentioned because of the linked forum thread). Could you perhaps do the same?

Are you using any third party scraping tools? The way LaunchBox is programmed, when saving to file we overwrite, not append, and save the properties directly to file which would make duplicate tags like that impossible. I suspect you have something else touching or modifying your files.

Glad you got it sorted out.

We use their API to check whether the credentials you entered are valid or not so either your computer is having issues hitting their API and getting the response back, or their API is telling us the credentials are wrong.

Just do a fresh LaunchBox install to a new location and import what you want to that install. The two installs (if both using defaults) won't interact/conflict with each other at all. They are both self contained.

It is how the system has been designed at the moment. It's something we are aware of and are looking into what we can do to make that process a little less cumbersome.