Jump to content
LaunchBox Community Forums

fromlostdays

Members
  • Posts

    983
  • Joined

  • Last visited

Posts posted by fromlostdays

  1. Actually, it turns out I already have a script for Demul in launchbox (It's been a long time since I messed with it). Anyway, in case I wasn't clear, go to Emulators/Demul in launchbox settings, then in the box that pops up go to the Running Script tab and put this:

    ; This section makes the emulator go fullscreen and closes Demul when pressing Escape
    Sleep, 9500
    Send {Alt Down}{Enter}{Enter Up}{Alt Up}
    $Esc::
    {
        Send !{F4}
    }

     

     

     

  2. I was getting the same behavior, and same numbered errors. Changing the LB default theme to the old theme seems to have fixed it. To be clear, it's not happening on my main launchbox build. Its only happening on a smaller build I have for hand picked games. The only differences between the two are:

    The smaller build obviously has less games imported

    I've imported games more recently to the smaller build

    The big build is on an M.2 drive (not C Drive); the smaller on a SSD (Also not C Drive)

    Lastly, the big build refers to games on a different hard drive (all my games stored seperate), for the smaller build I let launchbox import the the games and store them in LB/Games.

    Thats all I can think of. Other than that, same versions of LB, and both were using the newest LB theme until I changed it to the older one on the smaller build. Definitely a puzzle. The first time it happened to me was during an import. And after that, it would usually happen if I tried to scroll games in LB, but not all the time, and it would happen scrolling random systems. 

  3. On 3/21/2023 at 12:58 PM, Kjetter said:

    Might not be the right place to ask, but worth a shot I guess..

    Anyone know if there is a reason why there is a dedicated Sega SC-3000 and Othello Multivision category?

    The SC-3000 is more or less a SG-1000 with a keyboard, and has no games of its own afaik (every SG-1000 game is SC-3000 compatible and most (if not all) are marked "for SG-1000 and SC-3000" on the box). As far as I can tell the entire game database for SC-3000 are only less fleshed out duplicates of the SG-1000 entries.

    As for the Othello Multivision, that is just a licensed SG-1000 clone. Again, doesn't really have any games of it's own. There were roughly 5-10 games published by the same company that manufactured the console but they are also marked "SG-1000 and SC-3000", and every SG-1000 game would run on an OM (and vice versa). Currently only one game is entered in the game database for Othello Multivision (although without any information or images attached), but every single one of them is entered in the SG-1000 database.

    Just wondering if there really is a purpose in maintaining three databases that, if completed, will consist entirely of three sets of the exact same games. Is there not a better way to set it up, where all three variations of the console could share a database?

       

    I would say there is absolutely a purpose in maintaining a database for the Othello, that said, all of the information you just shared should be in it. If im understanding right, it literally played SG games? If it had no exclusives of its own then I don't think we need duplicate entries of the games, though. But if it ran its own disks or carts or whatever even if the data was duplicated, it's worth preserving them distinctly imo. But that would depend on them having seperate rips. 

  4. 5 hours ago, Slag-O-Matic said:

    it will only affect the game that I'm playing and will not change the default controller configuration for the platform/engine.

    You seem to have accidentally made it even more complicated than it already is haha. So, this all depends on how you save the config. You CAN save it per game. You can also save it per core, or per content directory, or per Retroarch as a whole. 

    5 hours ago, Slag-O-Matic said:

    Or more simply: I can make a change to the platform/engine and those changes only apply to newly-added games going forward.

    No. If you save your changes per game, no other game will be affected. If you save it per core, every game that uses that core will be affected, and if you save it per Retroarch, everything (every core) will be affected. Get the words "platform/engine" out of your mind, and think of cores. A core in retroarch is basically just an emulator built in a form that retroarch can use. So if you save any kind of config, inputs or otherwise, per core, then anything that uses that core will be affected. You can't even use the word "system" because some cores emulate multiple systems, and if you save a core config for that core it will affect all the systems that core emulates. So for example the "genesis plus gx" core emulates Sega Genesis, Sega Game Gear, Sega CD etc. So if you save settings "per core" on a Sega Genesis game, those settings will transfer over to Sega Game Gear, Sega CD etc. if you use the same core for multiple systems. 

    5 hours ago, Slag-O-Matic said:

    I can make a change while playing a game on that platform/engine and that change is only reflected in the game that I'm playing and won't affect anything else going forward.

    Yes, if you save the binding per game, only the game that's open when you do it will be affected.

     

    If you are wanting individual bindings for specific games, my advice is to just edit the bindings on each game and save per game. Until you know what you're doing, you should stay away from saving anything per core and certainly saving anything to the Retroarch.cfg.  

     

  5. Number 1: Always start the 8bitdo controller by holding X & Start on the controller. This will start it in xinput mode and should fix your problem unless you did something funny to the input binding settings in RA. 

    Number 2: Launchbox does download Retroarch for you now automatically, but are they not fundamentally linked. There's nothing you can do in launchbox that will affect the settings in Retroarch. It does not preconfigure controls for you. However,

    Retroarch has a bunch of preconfigured controllers on its own, and honestly the controller should work even not in xinput mode. That said, you should try to use xinput mode always for other reasons too. So getting in the habit of starting the controller as stated above is a good thing, regardless. Try that and see if RA doesn't recognize the controller. If it doesn't,

    Retroarch is a monster of emulation but the consequence of it being able to do so much is that it has tons of different configs and different layers of configs, its all very complicated. When you say you setup systems in Retroarch, do you mean that you saved settings changes in Retroarch either per config, per core, per directory or per game? Or do you just mean that you set the system up  in LB? If you don't have any specific settings saved in RA that you don't want to lose, I'd say go ahead and reinstall the emulator itself. Only because if you don't know what you're doing and you're messing with input settings its going to be even more difficult if not impossible to troubleshoot the issue. Controllers are supposed to work out of the box in RA.

    Retroarch only saves certain settings in the retroarch.cfg and then only if you have set the setting to tell it to do that. haha. The rest of it's configs are in the "config" folder but honestly like I said it's all very complicated to type out. Better to start fresh.

    If you take anything away from this it should be that the controller should work just fine, try starting it in xinput mode, and there's nothing you can do in Launchbox to fix it. Any fix to the settings would have to be done in Retroarch itself. You can reinstall the emulator and start fresh without touching launchbox at all, no need to delete or readd games, just make sure the new version of Retroarch is in the same directory as the old (not at the same time haha, delete or move the old one first)

  6. @C-Beats

    I can't see this being intended behavior, but the current version of launchbox automatically opens steam, if steam is closed when opening launchbox. I can't say how long this has been going on because I usually leave steam open, or if it was the result of a launchbox update or a steam update. I was scrolling the forums earlier on my phone and I saw a post about Steam taking focus when launching a steam game through Bigbox, though, and I wonder if these issues are related.

    If this IS intended behavior my apologies, you can delete this. 

     

  7. You can use this batch script to create m3us for every game in a system: 

    Couple things: do read the directions in there as you do need a specific folder structure. I recommend using file2foldergui to move each game (set of discs) into one folder if you haven't already. Also this batch file creates m3us for every subfolder in a single directory, meaning you'll get an m3u even for single disc games (this is by design, and single disc m3us work just fine, but they aren't necessary. I like just all my games to have the same extension in launchbox). Alternately, you can just create a single folder for all multidisc games manually and leave the single disc games out of that directory while running the batch. Let me know if you have any questions. Lastly, as is, this works with cue files only. However, under the Support section another user and myself figured out how to make it work for CHDs.  

  8. A few ways. 1: Right click the game in LB, click "Edit" and then go to the Additional Apps tab. There you can set which version launches when clicked. 2: set up m3u files and import those instead of the roms for multidisc games. 

  9. I don't know if Launchbox can sort through this but some sets, like a Tosec set, zip up multiple versions of the rom in each zip. I recommend unzipping SNES anyway as it takes up no space, but open one of the roms in 7z and see if there is just one file in there or many. If there's multiple files I don't think the launchbox unzip feature will work. Edit: If you can't manually open any of the files in 7zip that usually means you didn't download the full files and will need to replace the set.

  10. Launchbox is designed to automatically resume the download task even after reopening, as you're finding out. I don't know of any setting to turn that off. Looks like you loaded up a big chunck of games (9000) so as far as I know your best bet is to hit cancel and try to wait until it can fully cancel. 

    • Like 1
  11. On 7/28/2022 at 2:15 PM, Corgana said:

    SteamLauncher stop working yesterday for anyone else? Totally crashes launchbox when I try to launch a game. Works fine when disabled. Haven't changed any settings that I'm aware of.

     

    On 7/28/2022 at 2:27 PM, Razor112 said:

    Yes, Yesterday steam client received a update. Vtables need to be updated. @Lahma needs to update those.

     

    Steam hasn't updated yet for me I guess, for whatever reason, and SteamLauncher is still working fine for me. But, there is an option in the SteamLauncher settings under the Misc tab to update the vtables. Not sure if it works or not as I can't test it, but its worth trying.

  12. On 6/26/2022 at 1:02 PM, Corgana said:

    @fromlostdays I'm curious, when you launch a WiiU game via SteamLauncher, do your controls work as normal (it's playable) or is Steam assigning it the desktop controller config? I can't help but assume the issues are related.

    Good question. I set up a desktop config called Disabled with no mapping a long time ago because it was confusing me at the time, and the controller doesn't work at all in Cemu when I launch with Vulkan. So it very well could be launching my empty desktop config. 

  13. 15 hours ago, thecouchleague said:

    Hello, thank you for responding and I appreciate your work. For whatever reason, I am still not seeing the SteamLauncher in the Tools drop down. Not exactly sure why still.

    If you send me a private message, I'll help you get all setup. Or you can reach out Lahma on Steam. It sounds to me like you're just not installing it properly, but personally I'd need some screenshots of your setup to see exactly what you're doing wrong.

    If I use my intuition and take a wild guess.... did you decompress the file before you put it in the plugins folder? :D

    Remember, download file from here: 

     Decompress using 7zip or winwar or whatever you like. After unzipping you will be left with a folder called "Steamlauncher"

    Put "Steamlauncher" folder in Launchbox/Plugins folder.

    Open launchbox / close and reopen launchbox if its already open.

  14. 18 hours ago, Lahma said:

    Just a thought... Where is your Cemu installation and roms in relation to your Steam installation and your LB installation (both @Corgana and @fromlostdays)? Like, is your Steam installed on your system drive (C)? How about LB? Is Cemu located on a different drive or possibly even a network share? How about your Wii U roms?

    Actually.. Let's try something else... Steam tracks each overlay injection attempt in a file located at "<Steam_Install_Dir>\GameOverlayRenderer.log" (also, look at the file "GameOverlayUI.exe.log"). Try renaming both of those files to "<original_filename>.OLD" and then try launching Cemu from Steam and starting a rom from within Cemu. After the rom is fully loaded, exit Cemu and then check the 2 new log files created. Now, rename those files to "<original_filename>.<CemuVulkan_or_CemuOpenGL>" (according to what rendered you had enabled in Cemu). Then, switch to the other renderer within Cemu, close Cemu, and then relaunch Cemu from within Steam and do the entire process again. Post those files on Pastebin and provide the URLs here. It might give us some additional information which could help track down the issue. If nothing else, we can compare my own log files in which the overlay is working with your own, in which it isn't.

    Firstly, for me those things are spread out over 3 drives. Steam is on the C Drive. Launchbox is on L Drive (SSD). Roms are on R Drive (Big internal HDD).

    Secondly, I did the requested process. Here's a the pastebin specifically to the Gameoverlayrenderer file for the Vulkan launch. (Note, you said log files, for me they are .txt files I'm not sure if that's different or matters): https://pastebin.com/hhLC5Cm5

    So, I do have the OpenGL version of both files, let me know if you need them. However, interestingly enough, when launching with Vulkan enabled in Cemu, Steam just doesn't create the "GameOverlayUI.exe.log" at all. I did OpenGL first, both files created no problem. When I switched to Vulkan Steam only created the GameOverlayRenderer file, no matter how many times I launched. 

  15. 32 minutes ago, thecouchleague said:

    I just downloaded this SteamLauncher program and added it to the Launchbox Plugin section. I went to properties and I noticed that the enable option at the bottom is not there.

    Can I confirm how to install this dll plugin again please?

    Download the plugin, and put the whole steamlauncher folder in the Launchbox/Plugins folder.

    Launch launchbox. Go to "Tools" and then "Steamlauncher Settings" and enable it from there.

    Done.

    On older versions of windows, you sometimes had to right click the actual DLL file for some plugins and click "unblock", but that went away a long time ago.

  16. 7 hours ago, JedExodus said:

    Ah bummer. I've also ran into issues with Citra and Steam overlay breaking recently. Thankfully due to the selective use feature @Lahmahas added to the plugin I can just disable SteamLauncher from running when I launch 3DS games until a solution is found. 

     

    Not ideal but I'm glad that I can at least toggle it off and keep the end experience seemless

    Citra has always been hit and miss with me, but it wasn't that the overlay just wouldn't come up. In Citra, if I bring the overlay up once, and then close it, somehow all of the buttons are jumbled. I have to just bring up the overlay again and close it, and for some reason that straightens everything out. Definitely odd behavior. Is that what you're seeing? 

  17. Can confirm is not the issue. I've tried with it on and off in my testing as well, it doesn't change anything in terms of Steam and Cemu. Someone was talking about that setting a long time ago .. somewhere .. which is how I knew to check. In fact, I had just left that setting turned off the whole time since. But thanks for trying to help!  

  18. 2 hours ago, Corgana said:

    @fromlostdaysAlso found this reddit thread describing the same problem. Seems it's a problem with CemU. I'll try OpenGL but last I tried, I get vsync and performance issues with it. Not sure why the graphics driver would affect controller inputs 🙃

    I just solved this little problem as well with OpenGL. Horrible screen tearing. I turned vsync off in Cemu and turned it on FOR Cemu via nvidia control panel, and it's working like a dream now. And I agree, it is curious. 

    Edit: just read that reddit threat and that sure could have saved me a lot of time. 🤣

  19. 16 hours ago, Lahma said:

    Hey @fromlostdays, just to be sure, I checked all my software versions and it looks like the issue likely has nothing to do with that. I too am using the lastest Cemu 1.26.2 (product version 1.26.2f), the latest LaunchBox 12.11, and the latest version of Steam. The overlay is working fine for me. Remind me again.. You said that when you manually add Cemu as a non-Steam shortcut to Steam that the overlay still doesn't work (even after you load a game in Cemu), right? Do me a favor and check these Steam settings and tell me if you have them set the same as me:

    image.thumb.png.62b0a8ff6d0e6e0cece2775412d43b7f.png

    Let me ask you a few more questions to see if we can't figure out this issue of yours.

    • Are you using Vulkan or OpenGL in Cemu?
    • Do you have any other software installed/running which might be trying to inject its own overlay (MSI Afterburner/Riva Tuner, Xbox Game Bar, Nvidia GeForce Experience, Discord, SpecialK, etc)?
    • ***BIG ONE*** Are you trying to run Cemu as administrator ('Run this program as administrator' checked in the 'Compatibility' tab in the cemu.exe file properties dialog) when Steam and/or LaunchBox are NOT running as administrator? (This will absolutely cause the overlay not to work as Steam can't inject its overlay into a process running with higher privileges than itself.)

    When you respond back with this info (and if none of this fixed your issue), I will see what else I can suggest that might be helpful in troubleshooting the issue. If worst comes to worst, I'd be happy to remote into your machine for a few min to see if I can resolve the issue (Teamviewer, Windows Remote Desktop, or whatever). Just let me know!

    WOWWWWWWWWWWWWW. 

    I've tried like every permutation of every setting of every version of every imaginary number physics equation to get this to work. haha. EXCEPT, switching from Vulkan to OpenGL... which I just tried and Steamlauncher worked perfectly. So do the various nonsteam games I have for cemu and zelda now. I'm quoting Corgana below so they get a notification in case this fixes it for them. Its not totally ideal because you can't do async shaders in OpenGL as far as I know, but it's good enough for me. Thanks as always Lahma. The weird part is... aren't you using Vulkan? What could cause Steam to freak out over a renderer like that?

    Let me go ahead and answer all your questions just in case its a compounding issue:

    1: Works in OpenGL, not in Vulkan

    2: I have Xbox Game Bar, Discord and GeForce experience, but AFAIK none of them are actively running... maybe they got a background process going I'm not aware of? 

    3: I tried every permutation of having Steam and or Cemu running as ADMIN, none works, so I set them all back to not running as admin. 

     

    10 hours ago, Corgana said:

    Let us know if you find an older version that works!

    As above, try checking to see if you're using the Vulkan renderer in cemu and switching to OpenGL.

×
×
  • Create New...