Retro808

It is not the license it is the downloaded build. These at times can be a pain to troubleshoot. Depending on your answer to my questions though we should be able to figure this out.

Is that D drive an external drive? LB does look in the core folders as it uses symlinks to many files, even themes. If that D drive is an external drive and is ExFat and not formatted NTFS that would cause the issues since ExFat does not have some of the features NTFS does and can cause issues with symlinks.

Launchbox would not touch any media, games, or emulators you added. When you did the reinstall of 12.2 did you confirm it installed to the correct folder? Many times users did not notice it installed into a second Launchbox folder. \Launchbox\Lunchbox and when they open it they see nothing. Much in the same way you stated happened. Is the media actually missing from within their folders or just missing from within LB?

In your \Videos\Platforms folder. Each platform you have added has its own \Videos\[Platform Name]\Marquee folder.

The theme creator cannot do Startup/Pause/Shutdown currently. Those have to be done by creating/editing xaml.

I did watch them. Watching the videos though people cannot tell if a script is running. So, Thanks for confirming.

What I was saying I understand was the part about you deactivating the Startup. That part I understood. What I was trying to clarify is does this happen if you completely remove those scripts you use and run just the Startup screens and the emulator (with no custom script at all). Just trying to get more information to see if we can figure out why having the Startup screens on does not work all the time for you.

No worries. I understood what you meant. I am just wondering if it is a combination of using BigBox Startup and that custom AHK application together is causing this issue. As I mentioned I can run BigBox startup with Mame dual screen settings and it works fine.

@Sbaby Before you turned it off were you using the BigBox Startup with your script?

What video setting are you using in Mame. I run two screen setting on my big cabinet for all Mame games and not seeing the issue you are.

What I meant by the reinstall question is are you reinstalling by running one of the installers in the \updates folder or are you downloading a fresh version from our site? Also have you tried installing to a different drive and seeing what happens? Is this a LB build you made on your own or is this one of those prebuilt sets users can download?

open Event Viewer then on right navigate to Windows Logs > Application and tell us if you see any failures in there related to LaunchBox? Also, when you did the reinstalls of LB how did you do it exactly?

Might want to check out this thread. Looks like you can use the plugin with PCSX2 https://forums.launchbox-app.com/topic/63863-reshademanager-pre-realese-plugin-for-launchboxbigbox/

@SWEATYDRACO So are you up an running now?

From my earlier post. If you did not see that, no biggie. Like I said I was just looking to keep the post from spiraling as well...we see it did. Funny I do not think I have ever had any interactions with you on the forum before this one. I could be wrong. But I can guarantee I have never been disrespectful to you if I we have commented before. So what angst you have with me is all one of your own making and if you think a lot of other users share that sentiment, well that tells me all I need to know. Me saying something to you has only everything to do with the fact I asked for no more comments and you were the only one to comment unnecessarily again. I am not going to ban you or anything. All I am going to do is respond politely and professionally to you like I do anyone else I comment with. If you have an issue with me, well that's on you as I never worry about things like that.

I do not see why it would. I have several builds on different drives with no issue. Is that R drive an external drive? If you install to another drive does the issue still occur? If you can test please install a clean version and do not copy over anything from the install on the R drive.

We appreciate all forum members helping out, but I am going to ask to refrain from unnecessary comments like this. I mentioned earlier it needed to stop. Just trying to keep this from spiraling.

Thanks for that info. Do you know if you use or have MSI Afterburner / Riva Tuner running on your system? This has been known to cause this type of issue. Also in LB do you have logs turned on? If so can you provide a copy of the last couple logs.

I have the same controller and it is working fine. Have you updated the firmware lately? If you use the controller in the menu of an emulator does it exhibit the same issue?

I am going to cut all the unnecessary banter from this point on. Please refrain from unnecessary comments in posts and let's just stick to the issue. Let's start from the beginning. I am not even going to go to reddit as I avoid that site as much as possible. So you are going to have to provide some information for me. You say LB fails to launch and requires installation every time. What exactly happens? If LB fails to launch it fails to launch. It will tell you if you are missing framework needed. so are you getting any errors or it just does not load? You say you do not have antivirus but Windows Defender is in Win 10 and is known to block LaunchBox and BigBox dll files. Can you confirm you have checked defenders history and it did in fact not quarantine any LB files?

Not condescending at all. A valid concern for your particular use. Honestly though for a single developer (well we have 2 now) to think of each and every "common issue" to already have steps implemented is a daunting task so sometimes, things we as users think should already be there, are not yet implemented. I have been on this forum for over 3 years helping and this request is not as common as one would think it would be. Either way, always share with us your requests and feedback. It helps. If you want to make any feature requests use the link located at the top of the forum under "Help & Support". It is the best place.

This is how Jason originally coded it and likely never revisited it since it has not been something many users have asked about. To be honest I think I have only seen this questioned maybe 2 or 3 times. Most users typically already organize their roms in a folder structure they prefer and just have LB leave the roms there. Or have LB move them into the main LB folder. The best option it typically to already have the roms in the folder you want and use the Scan option to tell LB to scan it for new roms.

If you already have the games in the Switch roms G: folder choose the option to "Use files in their current location". If you have them somewhere else and are trying to get LB to move them into that G: folder location LB currently will not do that. And as mentioned changing the folder path in the platform will not allow LB to do this either. It is just not currently a feature.

Where you have your main LB folder is where LB will look. So whether you have on in internal D drive or an external J drive the \LaunchBox\games folder will always be pointed to that root folder. Which is why the wording states "my LaunchBox games folder" and not simply something like "my roms folder". Even if you change the rom folder path in the platform LB will still want to have a process to allow the user to move or copy roms into the LB folder structure. By "portable" we mean that everything, roms, media, emulators, settings are all contained in the LB folder and you can then move the entire LB folder anywhere you want and everything goes with it. Not solely meaning portable as in it being on an external drive. So currently there is not a way to change it so the options in the image below change to that new folder.