Jump to content
LaunchBox Community Forums

The_Keeper86

Members
  • Posts

    332
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by The_Keeper86

  1. 20 hours ago, MrMaddog said:

    Yeah, thanks for screwing up my entire Launchbox setup again!  It's bad enough that 'every' upgrade completely slows down  the program while I'm trying to use it, but this version is the worse.

    I never asked for automatic importing of my existing games but you code monkeys sought to put it in anyway w/o telling anyone...and don't say I should have checked the new features dialog because it crashed before it even came up fully.  I had to go through the changelog just to turn off a feature that I never asked to have in the first place.

    How do you expect people to even use the frontend if they have to constantly do alpha testing?  This is ridiculous!  You think that after paying a lifetime Premium price that the damn program should at least be reliable and stable.

    Excuse me for making my first post here come off as angry but I never had to complain about the quality of LaunchBox until today.

    Weird I have NONE of these issues! Never had an issue when upgrading to any new version.

  2. 1 hour ago, Nixx said:

    It was for Kurtastrophe " I copied over my descriptions folder from my Coin Ops Retro Arcade 2 tekno parrot folder into my TeknoParrot launch box emulator folder."

    You don't need to move your Metadata and Descriptions outside of your Teknoparrot folder, it should read them. (and it expect them).
    Once clicking update, you don't have launchbox db id set for most of the TP games ?

    Oh my bad 🤣How do I check for the db id? I do have TeknoParrot setup as a platform and one game added that I added manually.

  3. Hey guys!

     

    I've been using Pcsx2 qt aka 1.7 for the past several months and was wondering how to exit it? Escape just opens up the menu that shows achievements etc which I do love! But opening up that menu and selecting close game it just goes back to the Pcsx2 ui. I'd love to hear your suggestions! :)

  4. I got around to finally giving this a shot! Did everything you said but upon launching LaunchBox it still asks to install .net but it just closes abruptly without any errors. I even installed .net inside the prefix but still same thing. I'm using lutris-GE-Proton7-43-x86_64. Also I'm on Nobara atm I had issues with Garuda.

  5. On 4/10/2023 at 5:12 PM, Crossfader said:

    LAUNCHBOX ON LINUX IS ALIVE MWAHAHAHAHAHAHA!!!!!!!!!!!!!!!!!!

    Yep, I got it to work permanently.

    If you have previously read my posts, it's basically what I did, but then when you select Launcbox on Lutris, go to Wine Configuration and change the compatibility from Windows 10 to Windows 7. I will explain why later.

    OK, I have installed Launchbox twice on my brand spanking new PC twice, and on my laptop too, everything is working, there is the ocasional freeze on my gaming PC, but I assume it is because of brand new hardware that Linux and Mesa Kernels are not 100% stable yet.

    My new gaming PC specs:
    OS: Fedora 38 Beta.
    Linux Kernel: 6.2.10-300.fc38.x86_64(64-bit)
    Mesa: 23.0.1
    Motherboard: Gigabyte Aorus Xtreme X670E v1.0
    CPU: AMD 7950X3D
    GPU: MSI AMD RX 7900 XTX
    RAM: Corsair 64 Gb 6000Mhz 36CL

    MSI Laptop GE63VR 7RE Raider:
    Linux Mint 21.1 Cinnamon
    Linux Kernel 5.15
    Mesa: 23.0.1
    CPU: i7 7700HQ 2.8Ghz x4 (i think it is 4 core and 8 threads)
    Ram: 32Gb
    GPU: Nvidia Geforce GTX 1060 (GP106M)
    driver on lutris: the default Nvidia proprietary driver

     

    Ok, so the main thing about Lutris is to be running the latest Wine Version. When I started this, I was using lutris-GE-Proton7-33, but if I remember I was able to get it to work with 7-28, not sure of 7-27, currently I am using 7-42 (at the moment of writing this post, 7-43 just popped).

    I used Launchbox 13.2

     


    Guide:

    On Lutris, on the left side, go to Wine, select the configuration wheel icon, open it, and in Runner options, change the Wine version to lutris-GE-Proton7-33-x86_64 or above, avoid the lutris standard wine version, Eggroll Proton Wine is the way to go.

    Now at the top left corner, press the cross icon to add a game, select the "Install a Windows game from media" option.

    Type a name for your game, I choose Launchbox, press continue, then press the install button. A installation directory will appear, just press Install.

    Now it is the time to select the file LaunchBox-13.2-Setup.exe , wherever you have it stored in, and press Continue.

    It will start to install Launchbox, just follow the normal installation as if you were doing it on Windows, but expect it to crash while installing Dot Net 4.8, or right after completing it and attempting to install DirectX.

    After it crashes, press Close on the Lutris installation window. Now, on Lutris, you will see the game, for simplicity sake, I will just call the game Launchbox.

    We will need to install Launchbox again, but this time we will be doing it from inside the directory we just created. Copy the LaunchBox-13.2-Setup.exe file, into somewhere inside ~/Home/Games/launchbox, I drop it inside the Desktop directory, so ~/Home/Games/launchbox/drive_c/users/<my_pc_name>/Desktop/<here> .

    In Lutris, select Launchbox but don't start it, at the bottom, there will be two pairs of buttons, left is the Play button with an up arrow for settings, right is the Wine button with the up arrow for Wine settings.

    Press the up arrow for the Wine settings, and select "Wine Configuration", a window will open, in the Applications tab, at the bottom is the Windows Version, switch it from Windows 10 to Windows 7, then press Apply, then Ok.

    Press the up arrow beside the Play button,  and select "Configure". Go to Runner options tab and make sure the Wine Version is one of the latest GE-Proton, at this moment "lutris-GE-Proton7-42-x86_64" , then go to the Game options tab and on "Executable", navigate to the LaunchBox-13.2-Setup.exe file, you coppied inside the Launchbox directory so we can install it again. On Prefix Architecture , set it to 64-bit or to Auto. Press Save.

    Now press Play, it should start going through the Launchbox install process, but it will be different from the previous install attempt. Before, it tried to download Visual C++ 2015 Redistributable, dot Net Framework 4.8 and dotNet Core 3.1.6 dependencies and install them. This time it only does for 4.8 . The install will terminate abruptly, but don't worry, it should have been a success.

    Go back down to the arrow up beside the Play button, select "Configure" again, on Game Options tab we are chaning the "Executable" path again, this time to ~/Home/Games/launchbox/drive_c/users/<my_pc_name>/LaunchBox/LaunchBox.exe  , and press Save.

    Press Play, Launchbox should start. It will take a little while to load, just give it time. Just remember, it is not as stable as it is in Windows, have patience.

    Congratulations, you installed LaunchBox on Linux, but it is not over yet, as there are some differences, main one is you cannot drag and drop your roms folders as it will cause a crash.

    You have to install Retroarch manually. And you have to do this first before adding any roms, so things will go smoothly.

    ATTENTION!!!

    At this point, pop up windows will go in and out of rendering, often just displaying black, it helps if you have previously installed  Launchbox on Windows and so have some experience with adding rom libraries manually. Usually, just pass your mouse icon over areas in the window to cause them to render again, like the buttons.

    OK.

    At the top left corner, to the right of Launchbox, press the burger menu icon, then Tools > Manage > RetroArch >Download/Install (can't remember which one) .

    After that, same burger menu icon, Tools > Import > Rom Files , a window will pop up, just press Next at the bottom right corner, Then it will ask to add rom folder, search for the add button and press it, here the window is divided into two parts, the left for the path and the right for the rom folder. It is important to point at the directory where the rom folder is in the left part of the window and not at the rom folder directly, if you don't do this, you will only get a white screen on the right side.
    Press Next.
    It will ask what system it is for, if your folder is properly labeled, it will select the proper system, if not, then select it manually.
    Press Next.
    It will ask what emulator, since we only have RetroArch, it should be the only option.
    Press Next.
    It will ask if you wish to copy the roms to another location, in Launchbox, or use the current location of the roms folder, I usually just go with the current location to save space.
    Press Next.
    Then it is a series of questions about metadata options and Bezels, I always just press Next.
    It will add the roms to the Left now, and if you choose the standard metadata and bezel options then it should be downloading and updating the roms info and images.

    NOW Congratulations!!!!!!!! You did it.

    Enjoy LaunchBox, and consider getting a license. I am not affiliated with the Launchbox crew, I just appreciate what they have done with this software.


    WARNINGS!!!

    It is still unstable, but when comparing it to my laptop with Linux Mint, I think the problems I am suffering from on my gaming PC is mainly because of brand new hardware and the Linux and Mesa kernels  still having compatibility issues and Fedora Beta is, well, a beta release.

    On Linux Mint, it is much more stable, I don't have LaunchBox freeze for a good 2-5 minutes sometimes. The LaunchBox does not jitter when scrolling up or down with my mouse, I think this is because of Mesa 23.0.1 and my GPU 7900 XTX versus the Mesa 23.0.1 and the GTX 1660 on the laptop, maybe Nvidia is better with Launchbox, but they are both using DXVK.
    On Fedora, LaunchBox freezes and crashes if I try to minimise it. On Linux Mint, that does not happen.

    There is no need to go to Winetricks and install/add DLL Components, I tried to do this on Fedora, added dotnet48, vcrun2015,dotnetcore310, those components then changed the compatibility to Windows 7 and it just started to work. 
    Curious, on my laptop, I just changed the compatibility and Launchbox just started working.

    I have shutdown and restarted both PCs many times and Launchbox continues to work. I have played 7 games so far, a total of 2.5 hours and it works fine.

    The error I was getting previously on my old gaming PC that had Ubuntu 22.04 was an error saying system out of ram, or something like that, after some research, I found out it was because on earlier Wine versions, the Wine prefix architecture was set at 32-bit and it caused conflicts with libraries, so you need to set it to 64-bit.

    And I did set it, but I still got the error, problem was Windows 10 compatibility, I came across some forum posts talking about making changes to the Wine regedit on Lutris, but this is way beyond my capabilities, I am not an intelligent person, I have often difficulties learning, I am just glad I figured this out and can help the community.
    Maybe someone who is well versed can figure out the reason of this error and perhaps give us a fix, because Launchbox on Windows performs better in Windows 10 compared to Windows 7 according to the Launchbox website.

    Also I am running my libraries from a Nas (trueNas Core), mounted on a folder in my Desktop through NFS. LaunchBox reads the roms just fine!!!

    I apologize for the long post, but there was a lot to say.

    Hope you all enjoy it, and happy gaming.

    PS: For MAME, Probably same as RetroArch, just manually add it, I have not tried it yet, but should work.
    PPS: It also works with Windows 8 and 8.1 compatibility, but seems a bit less stable than 7, only tried this on my new gaming PC with Fedora, haven't tried with the laptop.

    I'm really surprised this hasn't gotten any replies. I really appreciate this! I'm gonna give it a try myself on Garuda. Have you tried Big Box? Also what about Linux native emulators?

    • Like 1
  6. On 3/17/2023 at 11:59 PM, retroNUC said:

    Still need to talk with various parties across GitHub projects as to where the fault lies and how it should be fixed properly, but I've put together a new version of RAHasher that now works properly with all CHD files. Download the attached file and replace the one located at "...\launchbox\ThirdParty\RetroAchievements\RAHasher.exe"

    Resanned my PS2 CHD collection with a 99%+ success rate. I'm not sure if LB will force retry entries already marked as COULDNTFILEHASH on a rescan, or whether you'll need to remove those lines before the rescan? 

    https://www.virustotal.com/gui/file/383ff365c89255e8d12e2580ae49e3af55ed59c3f2099e8eb173f0f231bba762

    RAHasher_Fix.zip 106.46 kB · 7 downloads

    Awesome work man! Worked great for me! :)

  7. 11 hours ago, Mitchinator1 said:

    It is possible to find the hash from RA and add it into the xml file for Launchbox. I was able to do that to get PS2/Dreamcast games showing achievements properly.

    Not an ideal solution, as it's one by one, but better than nothing for now.

    That sounds like a good solution! But it just reverts back to this

       

    <RetroAchievementsHash>COULDNTFILEHASH</RetroAchievementsHash>

     

  8. I know I mentioned CHDs not getting picked up for achievements due to something on Retroachievements end, but is there a way to force by name for the ones not getting picked up? I compress all my CD/DVD based games to CHD.

  9. 8 hours ago, faeran said:

    It's definitely possible when I circle back around to this one. Not entirely sure when that will be, but I'll keep these platforms in mind when I do.

    If anyone else wants to take a stab at them in the meantime, I wouldn't mind either 😉

     

    That sounds great! If someone wants to take a stab at it that would be awesome!

  10. 15 minutes ago, C-Beats said:

    It does work, but I have noticed that their app sometimes has a hard time finding the data it needs to generate the hash sometimes. If you look in your data files if the hash value is "COULDNTHASH" then the app threw an error trying to hash your file because of this issue

    Thanks, I did go back through some of my CHDs and some do get picked up some others that do have achievements didn't. So I guess its on their end like you said.

×
×
  • Create New...