p bizzy Posted February 24 Posted February 24 Anyone able to replicate symlinks still not working? This would mean either I would need to stay on 13.18 -- or move my launchbox instalation off the NVME to the HDD where my rom rom collection is, which would probably offset any new performance improvements and then some.
Fursphere Posted February 24 Posted February 24 On 2/24/2025 at 12:40 AM, p bizzy said: Anyone able to replicate symlinks still not working? This would mean either I would need to stay on 13.18 -- or move my launchbox instalation off the NVME to the HDD where my rom rom collection is, which would probably offset any new performance improvements and then some. Expand Is this because of launchbox's insane desire to use relative pathing for everything? I wish they'd disable that, or at least give you a choice. Relative pathing is super annoying.
TheNewClassics Posted February 26 Posted February 26 One other thing I've noticed with the recent betas is that the release year is only showing up for some games in Big Box; it looks to be sporadic. I'm using the Game Discovery Center
ToniBC Posted February 27 Posted February 27 On 2/26/2025 at 1:11 PM, TheNewClassics said: One other thing I've noticed with the recent betas is that the release year is only showing up for some games in Big Box; it looks to be sporadic. I'm using the Game Discovery Center Expand I have the same problem, there is a problem with the release date, if the date is complete (01/01/1990), it is shown in the game information, but only the release year, but if the database only shows the release year (1990), nothing is shown. It happens on all platforms, it may be related to the change in the database, which only detects the complete date format and not just the year.
C-Beats Posted February 27 Posted February 27 For reports on release year not coming through see here:
Vader Posted February 28 Posted February 28 (edited) @faeran Launchbox will not automatically update my version of mame its stuck on version .256 while the latest version is .274. Please help Edited February 28 by Vader
C-Beats Posted February 28 Posted February 28 On 2/28/2025 at 5:38 AM, Vader said: @faeran Launchbox will not automatically update my version of mame its stuck on version .256 while the latest version is .274. Please help Expand This is intentional. To use MAME and it's ROMs correctly your MAME version should match the version of MAME your rom set was built against. It's not like most emulators where the version doesn't matter and you always want the newest one.
Fursphere Posted February 28 Posted February 28 On 2/28/2025 at 5:38 AM, Vader said: @faeran Launchbox will not automatically update my version of mame its stuck on version .256 while the latest version is .274. Please help Expand Latest version is actually .275
Vader Posted February 28 Posted February 28 On 2/28/2025 at 2:58 PM, Fursphere said: Latest version is actually .275 Expand ahh good catch. I was writing this post last night close to midnight and was half-asleep.
Fursphere Posted February 28 Posted February 28 It just came out. I was just teasin' ya. Unless you're crazy like me, there is no need to update MAME on a regular basis. If there is a new playable game you want, or a new core feature of mame that you're interested in, that's when you upgrade. And as always, use clrmamepro to make sure your current rom set matches your current mame.exe
launchretrogirl2562 Posted February 28 Posted February 28 On 2/28/2025 at 4:11 PM, Fursphere said: It just came out. I was just teasin' ya. Unless you're crazy like me, there is no need to update MAME on a regular basis. If there is a new playable game you want, or a new core feature of mame that you're interested in, that's when you upgrade. And as always, use clrmamepro to make sure your current rom set matches your current mame.exe Expand clrmamepro is more for the experienced user. I've been using Romvault for upgrading pretty much the last 20 mame releases without any issues. It is much more user friendly and is updated on a regular basis. Once you set it up once, next times it's just a question of downloading new dat's, importing them, scanning and fixing the files. All through the UI. https://www.romvault.com/
Undertherainbow Posted February 28 Posted February 28 There is a problem with LB and BB in this update for me. They both get stuck in memory on exit. 1
Fursphere Posted February 28 Posted February 28 On 2/28/2025 at 5:18 PM, Undertherainbow said: There is a problem with LB and BB in this update for me. They both get stuck in memory on exit. Expand I've been having this same issue, but honestly just thought my PC was being a piece of crap. Maybe there is a bug. 1
Undertherainbow Posted February 28 Posted February 28 On 2/28/2025 at 5:21 PM, Fursphere said: I've been having this same issue, but honestly just thought my PC was being a piece of crap. Maybe there is a bug. Expand Nah. I am using 9700X cpu. Its quite new. Problem is not on your side. I noticed by accident. 1
Drybonz Posted March 2 Posted March 2 On 2/28/2025 at 5:33 PM, Undertherainbow said: Nah. I am using 9700X cpu. Its quite new. Problem is not on your side. I noticed by accident. Expand Yeah, this is real. I reported it back in the 13.19 beta thread. 1
xX-Delirium-Xx Posted March 5 Posted March 5 bigbox keeps randomly freezing up on me while I'm scrolling through my games since the update saved the log when it happen if that helps Debug 2025-03-04 09-42-01 PM.logFetching info...
faeran Posted March 5 Author Posted March 5 For people wanting to follow the Big Box freezing issue can do so from its ticket here: https://launchbox.featurebase.app/p/known-issue-big-box-freezes-after-being-left-idle-on
Drybonz Posted March 5 Posted March 5 My comments above weren't related to Big Box... I never use it... so maybe two separate issues?
faeran Posted March 5 Author Posted March 5 On 3/5/2025 at 7:03 PM, Drybonz said: My comments above weren't related to Big Box... I never use it... so maybe two separate issues? Expand Yeah, yours sounds like a different issue. The difference between the Big Box freezing issue and yours is that the freezing issue appears to be a global issue regardless of environmental conditions that everyone can experience, where yours does appear to be based on some kind of undetermined environmental factors where not everyone is experiencing it. For people where it's happening, it sucks, but it's one of those things that's not happening for the majority of individuals and is hard to replicate. It's good enough to open up a ticket over on our new ticketing system though where we can track it and discuss troubleshooting steps.
p bizzy Posted March 6 Posted March 6 On 2/24/2025 at 1:53 AM, Fursphere said: Is this because of launchbox's insane desire to use relative pathing for everything? I wish they'd disable that, or at least give you a choice. Relative pathing is super annoying. Expand Probably, but I like the relative pathing for portable use. But now after 13.19 it doesnt work, so im stuck on 13.18. I wonder if just the current working directory needs to be set since I did see some updates to the syntax for .NET9
Recommended Posts