Jump to content
LaunchBox Community Forums

Retro808

Moderators
  • Posts

    7,262
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by Retro808

  1. That is likely going to be some media the theme is using. You would have to either change the images the theme is using and/or change some code in the theme. We can give you a better idea of what to do if you let us know what theme it is and share a pic of what you are wanting to change in that theme.
  2. Can you get the games to run directly in Mame without LB? If not then that is the issue to start with. It would also help us troubleshoot if you let us know how you imported your roms (what method of import did you use) and did you set up MAme yourself or have LB do it.
  3. @skizzosjt Same thing here that you are seeing. Close Active Window binding works without issue. Using the same AHK in Pause Screen exits fine as well.
  4. @evanestal So if the roms work directly in Mame (without using LB) then it is a LB setting issue. I do not use all the custom command lines that LB places when it sets up Mame so that might not be the issue. What version Mame are you running? Can you provide some more pics. Right click and edit a Mame game and post the following pics: 1. Metadata tab 2. Launching tab 3. Emulation tab >Tools >Manage >Emulators and edit Mame post a pic of your Associated Platforms tab.
  5. Check your associated platform tab and make sure you have the correct platform name listed there.
  6. If you got the rom set from Pleasure dome then all roms will work. Did you get the set from that site? When you say that it does not play when launching through LB what exactly happens? Do you get an error or just it tries to load then goes back to LB? The clunkiness, I take it that this does not happen when running though Mame directly, correct? It could be a frequency issue when running through LB, but if you had LB set up Mame then it populated some command lines as defaults. One thing I found with a couple builds that had this similar issue is the command line for -waitvsync was the culprit. Reading Mame's documentation this can have differing affects on OS/Video driver builds. Try removing that specific piece in your Mame set-up in LB and see if the issue goes away.
  7. Moved again? It has never been moved since Scan storefronts on startup became a feature.
  8. There is no option in BB. You have to manually edit the theme’s code.
  9. The devs are aware there is a small set of users having this occur. If you need an official statement please see Faeran’s second post in the beta testing thread. Going to ask anyone seeing this issue not to post about it in the beta thread as it is not beta testing related. Please keep this thread relevant so the team can see a singular post with any feedback for this issue.
  10. Are you looking for it to be a clear logo on the selection wheel or as the header on the screen? The Unified\Images\Theme\Logo folder would only be for the logo header on the screen not for the selection wheel. If you want it for the selection wheel the best place is Launchbox\Images\Playlists\[NAME OF PLAYLIST\Clear Logo\ Also make sure in BB you refresh the image cache. In the settings area of BB there will be a refresh image cache option.
  11. I think we are going to need more information than that.
  12. Here is a link so you can click on the contact us. Also a pic of the email as it looks like translation may have changed it from support to destek. https://www.unbrokensoftware.com
  13. If you are on Win 7, 8, 0r 8.1 then LB version 13.8 is the last version you can use. Older Winows OS will no longer be able to use 13.10 and future LB updates. You can email our team for the 13.8 installer if you do not have it in your \Updates folder. support@unbrokensoftware.com
  14. You pasted the script in the wrong section. You were advised to paste it in the “Running Script” tab.
  15. Nothing storefronts related was removed. It was just updated to fix an issue. The "Enable Automatic Imports On Startup" is still there in the >Manage >Storefronts setting.
  16. Been following this thread as it is a good learning experience. End goal is to have even 20% the knowledge of @JoeViking245 and @skizzosjt. So setting up AHK as an emulator and testing using the scripts provided I am seeing the same thing as @5thWolf. With the last one skizzosjt posted I get the same thing 5thWolf is showing in the video. Without fail and it does it on a couple machines. I modified a bit and so far no issues. It launches numerous times flawlessly. What is odd is if I change the Send line to read Send, f it reverts back to what happens in the video. Even if I add the sleep timer in it. For some reason it does not like sending f. Any ides why that would matter? Or is this just case of some stupid fluke with this particular game? SetWorkingDir %A_ScriptDir% #SingleInstance, Force Run, Z2TAOL_P03.exe WinWaitActive, ahk_exe Z2TAOL_P03.exe Send {Alt Down}{Enter}{Alt Up} $Esc:: Send, !{F4} ExitApp Return
  17. The reinstall likely installed LB into a double folder \Launchbox\Launchbox Open up your original \Launchbox folder and see if you have another Launchbox folder inside it. If you do you can remove that one and rerun the 13.8 installer. Make sure the path is just \Launchbox. At the end of the installer UI it will show you the install path. Change it there is you see it is \Launchbox\Launchbox
  18. Video playback is a premium feature.
  19. We do not really troubleshoot rom seller builds of LB as we have no way of knowing what they did. Your best bet is reaching out to the seller. Not to mention most here look down on those scum. I will say look in your \updates folder and if there is the installer for the prior version you can reinstall it over top of the build.
  20. Yes. It has it's own exe and you can load from within LB. You can also be in BB and select the option to close BB and open into LB. Yes.
  21. All prior versions you installed are in your \Updates folder. It will not change any settings. Just run the installer. Verify it installs to \Launchbox and not \Launhbox\Launchbox.
  22. Yes. You can either just select the game roms in Windows and drag and drop them into LB to begin the rom import process or in LB -Tools -Import -Rom Files then select the Files button and manually select the roms. A few things to consider: If you do not have the roms stored in the default Mame rom folder you will need to make sure you open Mame and update the rom folder location. You can do this either by manually editing the Mame.ini or just opening Mame exe without a game and navigate to the directories setting and manually select the folder path. If you donwload individual roms as opposed to a Full Mame rom set I would first make sure your roms work in Mame directly to ensure you have the needed support files. During import I would not have LB move the roms. Leave them in your original folder. Depending on the Mame set you have moving individual rom files out of a Mame set could break things. Leaving them in the Full Mame set folder negates the need to fuss over having a non-merged, merged, or split rom set. Just makes things easier. Also doing this way if you ever update the full mame set you do not really need to update anything in LB (Except in some rare instances of rom name change/removal).
  23. In LB right click the Genesis Platform name and edit it. Go to the "Parents" tab and see if you have a check mark for the platform to show up in 2 places. Remove the one you do not want it to show up in.
  24. Did you do what the error is telling you to do? Restore the file from one of the backup copies in your \Launchbox\Backup folder?
×
×
  • Create New...