Jump to content
LaunchBox Community Forums

Tsik

Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Tsik's Achievements

8-Bit Processor

8-Bit Processor (3/7)

8

Reputation

4

Community Answers

  1. So, after much fiddling around it seems that the problem was not some kind of setting or arrangement nor anything to do with codecs. I finally reach to the conclusion that the problem is some kind of memory/performance issue. Not trying to say that is LaunchBox is "heavy" as a software because I said before that both my PCs are old enough to give reasons for those type of problems from now on... guess things are evolving ๐Ÿ˜ฅ The only way I manage to make the startup video play every single time is by starting it as soon as windows starts and immediately after logging in. Or by putting a BigBox shortcut into the windows startup folder. Well is this some kind of solution? ...No, but I know at least that the software is working as intended, and perhaps in the future something will change regarding the software's performance but until then is more likely that I 'm going to need new PCs! ๐Ÿ˜ So I'm marking this as a solution for anyone who might be reading this in the future. Thanks ๐Ÿ™‚
  2. Ok, baby steps with this one,๐Ÿ‘ถ I manage to make the BigBox logo to show up by removing the video folder entirely and let it create an new empty one. It looks like if there is a startup folder with a video inside, the logo won't show even if it is enabled in the BigBox options. If the startup folder is empty the logo will show up. But the main problem still remains (no video playback during startup) with slash logo set to off... Every other video (Platform or Game) show up nicely. I even try and reinstall DirectX. ๐Ÿค”
  3. Or because its the first core for the platform in the associated cores list...? Never the less as Joe said, this may be a bug for reporting. I'm glad I was able to help.๐Ÿ˜‰
  4. @JoeViking245 Hi, for me (and I hope this is because of the 'early access' stage of the function) the saves are showing only with some cores, e.g for FCEUmm core the saves and badge showing fine but with Messen (NES) although the [game].srm files are there in "RetroArch\saves\N.E.S\Mesen\[game].srm the saves window is empty and the badge is not there. On the other hand if I "force" import a save file it automatically puts it in "RetroArch\saves\N.E.S\FCEUmm\[game].srm" folder. Notice that I have RetroArch setup to save game files in both Parent_Directory\Core_Name enabled. Also in the saves window the emulator info line shows only (fceumm_libretro) even thought I use the messen core as default core for the NES platform. See picture below using the messen core as default core for the platform after forcing import a save file. Only this way the Game Saves and badge are shown when messen core used.! The 'Save States' show no problem as I leave the RetroArch default setup as to where the files are stored regardless of Parent_folder nor Core_name. [RetroArch\states\[Game].srm] Hopefully this clears the landscape for the current state of the Game saves function. ๐Ÿ™‚ @keironD2012Of course I suppose you already have the 'Enable Save Management' box ticked in the LaunchBox Options. I didn't test if that is the case with any other core. Can you please tell what is your particular case scenario and the problem you encountered. Thanks.
  5. Ok, so here is another one of those "StartUp Video not working" issues ๐Ÿ˜’ I have this issue a couple of versions back (I can't remember how far back) but finally I am at a position to try to address this issue (spoiler alert: I haven't) ๐Ÿ˜ I have done a fresh LaunchBox installation with only one test/dummy game file just for this purpose, I have my video file (.mp4 format about 20sec in length) in "LaunchBox\Videos\Startup\BigBox_Video.mp4", I have disabled the 'Show StartUp Splash Screen' option from BigBox (I think I read somewhere in the forums that this might conflict, which by the way does not show up either even if is enabled!), I tried both WMP and FFmpeg video engines, Nothing else is changed from the settings after installation. After all I hope I didn't miss anything... Oh, I my rig(s) are "a bit" old running win10 with the better one running on an i5-6500 CPU @ 3.20GHz, 8,00 GB RAM and an AMD Radeon (TM) R7 370 Series (2 GB) graphics but everything else works fine including all the platform and game videos. I have attached below a debug file for reference. Any information needed 'ill be happy to share. Thanks in advance. ๐Ÿ™‚ Debug info 2025-10-22.log
  6. Thank you, that looks pretty nice! ๐Ÿ˜„
  7. Hello there, if i understand correctly the programmers "name" you are talking about is "Itizso" and in his "itch.io" page has made a LOT and GREAT handheld simulations of Nintendo's "Game & Watch" titles alongside others (check here). Of course LaunchBox is capable of using links as launching path by just adding the url in the 'Launching tab' > as 'application path', and it will use the systems default browser. In fact i use his page in my personal Launchbox installation. Of course it will work the same for individual games but you have to press the 'play' button on the page for the game to load. I hope I helped you. ๐Ÿ˜ƒ
  8. That's very good news! ๐Ÿ˜„ I'm glad I'd helped you found your solution! ๐Ÿฅณ Game On! ๐ŸŽฎ
  9. Hey, I hope I caught you.! You don't have to uninstall anything, first did you uncheck the the 'Extract Roms' boxes from the Platform assoc. window? (this option is 'off' by default) You can install Launchbox a second time in a separate temporary location just for testing. When I am doing test with beta releases for example i temporary rename my current installation folder to let's say "Launchbox [Bauckup]" and then reinstall an other instance in the same Location as before or in another folder, After testing just delele the LaunchBox-test folder and rename "LaunchBox [Backup]" back to "LaunchBox" everything will be back to normal. Remember Launchbox is made that it is completely system independent and DRM free so you can have as may installations as you want in the same machine. I' am pretty sure that your problem does not associated with your Launcbox version because i am using the latest 13.19 in my Win10/11 PC without any problems.๐Ÿ™‚
  10. Oh wait... I just saw that the 'Extract Roms' boxes for all your platforms are ticked !!! If your rom file is in .chd format this option is not needed.! It is only used if the rom file is .zip compressed.๐Ÿ™‚
  11. Sure why not ๐Ÿ˜€, I play all my Saturn games with Beetle Saturn (mednafen_saturn_libretro) [including Astal] and Kronos (Kronos_libretro) for STV, Yabause and YabaSanshiro are a bit outdated and are not recommended as it says here and here. Mednafen is indeed a fork Beetle Saturn (Libreto Link). (Skip the --appendconfig...cfg part above as it doesn't matter, keeping only the default -f) Now lets take it from the start using only 'Beetle Saturn' shall we? ๐Ÿ™‚... Let me ask some questions (assuming your paths in LaunchBox are correct): - Was the problem about freezing or not booting the game (loads to Bios only)? - Does the problem occurs in all of your Saturn games or just Astal? (If you have any other than that..) - Did the bios files needed for Beetle Saturn are the correct? (look in the core info for the md5) - Did you try to remove the Beetle Saturn config options (Beetle Saturn.opt) file from the config folder in order to reset the options? (I use all the default ones) - What version of RetroArch/Core are you using? As the last step try a temporary fresh installation of Lunchbox/Retroarch in another location and import your game/s just for that System.
  12. Actually the ..\ is not there just for visual, its there for "relativity" or "portability" reasons meaning that your system (LaunchBox) is independent of the drive letter that its installed (if lets say you have installed it in a external hard drive G:\ considering the relative paths between LaunchBox and the files used). If the system throws an error like this then there is definitively something going on with the way you installed everything and i mean the installed locations/paths or something like this. In Post 2 i noticed that the paths don't match: the "ARCADE" part is missing from LaunchBox and the 'Sega Saturn' part perhaps has more than once space between the words! Again use the browse button in the emulator edit window and point to the actual RetroArch.exe file (no adding anything by hand) and also the in the launching section of the game edit to point to the actual rom file where your rom .chd "lives", this ensures that the paths used are pointing correctly to the files they suppose to. If Retroarch is installed inside LaunchBox\Emulators it must be like this: The ..\ part is automatically added by Launchbox only if the emulator is installed outside the Launchbox directory. Also in the game edit window in the Launching tab the path will be something like this: (Notice that I'm using one space between '\Sega Saturn\' and no '\Astal (USA) (3S)\' folder but that's just me, you can leave those if you want ๐Ÿ˜)
  13. Hello there Ipman559 I assume that the game is loading through RetroArch as stand alone, it looks like your paths are messed up... > Retroarch path should start with something something like ..\ > Rom path should be something like ..\ Please take the time and re-browse for the files both Retroarch.exe and the Rom file and test again. *(I say re-browse using the "Browse" button and not just edit the path so that Launchbox could auto-compensate the paths correctly as they should be) > Also un-tick the box "attempt to hide console window" in Retroarch edit.
  14. I also recently stumble into a Dependencies issue myself in Windows 10 Hatari_Libretro Retroarch core where the Dependencies Missing error pops up although for that core everything works fine through Retroarch standalone and the core information seems to have no missing TOS images and Launchbox "Dependencies Files" tab in the Emulator Edit window says no "Dependencies Files Required" ! If press the "Play Anyway" button the game works fine. I also looked in the "Beta Testing (13.19)" thread and nothing seems to be addressing this issue.
  15. OK, Reporting back from version 13.17 Everything now works perfect.!!! Thank you all. The best community ever.! ๐Ÿ˜ƒ ๐Ÿ˜„
×
×
  • Create New...