-
Posts
457 -
Joined
-
Last visited
-
Days Won
15
AstroBob last won the day on February 13
AstroBob had the most liked content!
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
AstroBob's Achievements
-
Please also add your support and follow our feature request for this, to be notified of any updates. 🔗 Support for Linux operating systems
-
The unexpected error is back again in the moderations
AstroBob replied to Arthurcoutinho600's topic in Troubleshooting
Yes, there have been some updates to the game pages on the database. Expect more details on these to arrive soon, but you should be seeing images load a lot faster, along with some other quality of life improvements. Sorry for the issues there, and let us know if you notice these errors again in the future. -
Can't install DOS games with latest version of LaunchBox (13.19)
AstroBob replied to St_Eddie's topic in Troubleshooting
Hi Folks, Just wanted to let you know, today we released a patch version (13.20) which contains a fix for this issue. The DOS importer should now be working properly as expected. You can see the full changelog here. Thanks for bearing with us there. Cheers, -
The unexpected error is back again in the moderations
AstroBob replied to Arthurcoutinho600's topic in Troubleshooting
Hi there, Thanks for the report here, there was some maintenance on the database yesterday, which could have contributed to this. Can you confirm If you're continuously seeing these moderation errors today? Cheers, -
If you go to Tools > Edit > Platforms, select WiiU and then click on the 3D Model Settings tab, do you have any ovveride set there? Also, does this affect any WiiU games, or just that specific one?
-
I wouldn't be surprised if it's not treating those shortcuts as game files, hence why it isn't picking anything up to be removed. I've added that to the scoped feature though, since you're right, it shouldn't just be able to scan for added shortcuts but remove them by running the scan for deleted ROMs as well
-
For sure, it's certainly possible. There are many ways we could go about this, another being using the fbneo core, since a lot of those sets also don't require any dependencies. We're continuing to iterate on the NAS functionality so I wouldn't be surprised if we come back to this in the future, but can't say which approach we would go with.
-
Hi there, Thanks for the report here. We've actually been hunting down an issue for a while now that sounds similar to this. I tried to run the same repro steps as you but unfortunately, I couldn't reproduce the behaviour. If you can reliably reproduce the issue, would you mind recording a quick screen recording outline so I can ensure I'm following your steps 100%. That, and please let me know what LaunchBox version you're using. Cheers,
-
Thanks, one thing you could try here is temporarily moving the directory it's referring to outside of LaunchBox to see If it resolves the error. It's possible something in that tmp directory has become corrupted so take a backup of it, remove it and see if that resolves the error.
-
Hi Folks, Happy to report we finally have an implementation for .RVZ scanning! 🙌 This is available in our latest beta for 13.20 GameCube games in the .RVZ will now be able to scan correctly for achievements, and achievement badges will now show for any matched games. If you're keen to give this a try you can join the latest beta, otherwise you can expect this in 13.20. Cheers,
- 21 replies
-
- 3
-
-
-
- gamecube
- retroachievements
-
(and 2 more)
Tagged with:
-
Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this.
-
Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this.
-
13.19 Dolphin doesn't launch fullscreen anymore
AstroBob replied to jevcleem's topic in Troubleshooting
Hi Folks, Just to let you know this, issue has now been addressed internally and will be available in the next version of LaunchBox (13.20). An early beta is available of this version which contains this fix, which you are welcome to try out below: 🔗 https://forums.launchbox-app.com/topic/89482-launchbox-1320-beta-thread/ Otherwise, you can expect to receive this fix in 13.20. Thanks for bearing with us there, and apologies for any issues due to this. -
HI there, Thanks for the report here. I'm looking into a potential issue where .chd files don't appear to be getting recognised by the importer. Could you please walk me through your exactly import steps (including what files you have in the directory you're trying to import). If it's easier, you can also share a screen recording, but I'm most curious to see what is the structure of the directory your trying to import, and which import steps your following to get them into LaunchBox. Please let me know and we'll try to get you sorted. Cheers,
-
Hi there, I've split this out into its own topic since that thread was specifically with Big Box, and if you're not using Big Box it would be good to keep this separate. To investigate further, could you please confirm the following? Steps to reproduce: Please describe the full steps you took to encounter this error. Consistency: Are you able to reproduce this error reliably, or does it occur sporadically? Error details: Are any errors shown, and if so please attach to this thread When did the issue start? Let us know when you first noticed this issue occurring. Screen recording: If possible, providing a screen recording of the issue in action would greatly help our team narrow down the cause. Let us know, and we’ll work on getting this resolved for you.