Vader
-
Posts
111 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by Vader
-
-
10 hours ago, faeran said:
Can you confirm how many files you have left in your arcade folder?
I actually deleted the folder so I don't have an accurate count of files. But If I had to guess I would say about 4 to 5 thousand files.
-
57 minutes ago, Retro808 said:
What rom set (merged, split, non-moerged) are you using and how many files did you remove?
With the full set importer LB is looking to the folder you have the full set in and is looking to ensure it has a certain number of files in it. If it does not meet that requirement you get that error. I remember a post stating there is a file cut off and if you have anything less than that it will not work with the full set importer. I think the file cut off limit is based on the Mame set.
It's a merged set. I did remove quite a bit of roms, as I wanted a set that did not have extra's such as playchoice, casino, mahjong. etc. I went this route because I wanted to have clones, might have to switch to a split set and import using regular import.
-
Can you guys look into this? I am trying to import a mame romset and I get this error. I am for the most part using a full mame romset, but some roms were removed to reduce space. . I used to be able to import semi-full sets, but now I can't
Thanks
-
I also noticed an issue where big box crashes when loading from launchbox. Screen just turns black and I have to exit out via task manager.
Thanks
-
1 hour ago, Belmont said:
I'm sure you guys know, but https://gamesdb.launchbox-app.com/ is dead (maintenance?)
I guess that explains why I can't scrape images. I'm trying to import a new game but am getting the following error scraping images. I guess i'll have to wait until its fixed.
-
2 hours ago, faeran said:
The search window is a theme specific thing. It's because you are using an out-of-date theme. You can go into the theme's View folder and delete the old Keyboard view file and that should fix it, or you could use the author's updated version of the theme.
Like I mentioned in the beta thread, I tested this across a number of scenarios, but was unable to recreate it. I should have a laptop with those low specs to test on if I can find some time. I'll see if I can break it like you are seeing.
As a follow-up I removed the arcade platform and installed an NES platform. The issue persists with this platform, as well.
-
1 hour ago, faeran said:
The search window is a theme specific thing. It's because you are using an out-of-date theme. You can go into the theme's View folder and delete the old Keyboard view file and that should fix it, or you could use the author's updated version of the theme.
Like I mentioned in the beta thread, I tested this across a number of scenarios, but was unable to recreate it. I should have a laptop with those low specs to test on if I can find some time. I'll see if I can break it like you are seeing.
Thank you, deleting the keyboard view file fixed the issue with the on-screen keyboard. However, the other issue still exists. I just copied my build to a mini pc that I have, and the same issue occurs there too.
Note, I am using a full mame romset only, no other platforms have been installed yet. To reproduce trying scrolling back and forth and then stop on any letter. It seems worse on cover flow views. Also, I am using a keyboard. I have not tried it with a controller yet.
Basically, it seems like the images can't keep up with the search by letter widget.
-
@faeran @Jason Carr Here is the latest info that I have on the issue.
As I mentioned before, I am having an issue with the search by letter widget on bigbox. No matter what theme I use, any time I open up the widget to search by letter, the letter seems to not match the game selected. For example, If I scroll to the letter P, I will get a game that starts with the letter M. See example on the screenshot below.
.
I have tried several different troubleshooting steps, such as reinstalling Launchbox, moving my roms to the same drive that lauchbox is installed on and removing other programs that I thought might be causing a conflct. Nonthing seems to work.
Also I just noticed that If I select the magnifying glass to search for a game I get a full screen, on-screen keyboard that is useless, see screenshot below.
This has now become a deal breaker for me. Please look into this.
My system:
HP Envy x360 Laptop
8 gb of memory
256gb ssd hd
-
22 minutes ago, faeran said:
It's possible it's always been like this. Hard to say, but we'll look into it.
For your first one there, it's possible that's how it's always worked. If your list doesn't contain a game with the letter you have landed on, the game it remains on is the one that came before it. It's also possible you may be experiencing some lag with it, causing some errors with where you are landing, but I just did a quick test on my slow mechanical hard drive build across a number of themes, but things seem to be working as expected.
Your second point is also as expected. It populates itself first with either recently added games or recently modified (I can't remember which one at this moment), to make sure something appears there right away. Then your recently played games will quickly take over.
Thanks for the reports.
Here is a short video showing what is going on with the search by letter widget. Sorry for the wonkiness of the video, I was trying to record with one hand and run bigbox with the other.
Thanks
-
19 hours ago, faeran said:
Beta 5 is out with some further fixes to this morning's beta:
- Improvement: The new Xbox login will now automatically attempt to re-authenticate you when your token has expired
- Fixed: Button mappings not working when navigating a manuals from the Pause Menu
- Fixed: Incorrect RetroAchievement header in LaunchBox's Default theme's expanded overlay
- Fixed: Crash caused in Big Box's Platform Categories section, when entering into a category using certain themes
We are hoping that this brings us close to a release candidate here, with an official release pending shortly after. All feedback with this beta is greatly appreciated.
Don't know if this is beta related, but I found couple of issues that I think are worth noting:
1. There seems to be an issue with the search by letter option on big box. I have tested this on several themes, and all seem to have the same issue. When scrolling through the letters on the search by letter widget, sometimes the letter you stop at does not match the game shown. For example, if I stop on the letter "A", the game I get is Cabel, instead of an "A" lettered game. Etc. Below are screenshots showing this error on 4 different themes. This seems to happen while fast scrolling threw the letters.
2. To see if this issue was related to my install of launchbox, I re-installed launchbox from scratch. After doing so, I noticed that the search by letter error still existed but at same time I noticed another error. This time, on the recent games section of the default big box theme, I noticed that there was one game already on the list, even though I have not played any games with this build yet (see 5th screenshot). Also, while the other boxes remained un-populated (no box art), if you click on any of the other "empty" boxes, it takes you to a game anyways. This list is supposed to be clean, isn't it?
-
6 hours ago, skizzosjt said:
I think you meant to quote the OP rather than me
But, am I missing something here? we're in the Android section of the LB forums and everything I read says NTFS is not compatible with Android
if the OP was using LB/BB on Windows I would agree that NTFS certainly makes the most sense. But I do not understand the NTFS recommendation for use with Android? Yes, NTFS will work on the Nvidia Shield, but if a user is on an Android device when trying to access the Shield, I would believe the NTFS drive will not be recognized by LB on the Android device due to the incompatible file system.
You are correct, I quoted the wrong person. But anyways, I agree that NTFS should not work on android devices, but when I plug in my usb drive formatted in NTFS it works and is recognized on my shield. It's a PNY 500gb usb drive.
-
59 minutes ago, skizzosjt said:
what format are you formatting the USB drive to within Windows? if the shield is asking that when the device gets plugged in it is because you are using an incompatible format for the Shield
Shield's website says it can use FAT32, exFAT, NTFS, and HFS+ which would cover the vast majority of users.
however, I know diddly squat about android, so for all I know, the issue lies here.....
quick goggle suggests android devices can use FAT32, EXT4, EXT3, and exFAT
based on that, I would suggest using FAT32....exFAT being a distant 2nd choice. but it suggests NTFS would not work with android and that is the common format type for Windows now-a-days and potentially what you have been trying to use. don't use EXT4 and EXT3.....I don't know squat about them either, other than they are not going to be compatible between your devices.
It's actually kinda a pain in the ass to format as FAT32 in windows now-a-days since it's such an old/deprecated file system (windows 98 era if I'm not mistaken) and isn't an option given anymore on disks over 32GB.....which your 128GB is surely larger than that. you will need to make use of some 3rd party tool or maybe do some work-around tricks. Perhaps if you create a 32GB (or smaller) partition on the 128GB disk is will allow you to format it as FAT32. then you can expand the partition to the whole 128GB disk. just a theory, no idea if that would work or not. either way, you likely formatted the 16GB one as FAT32 and everything works, but the 128GB one is likely NTFS and will work fine in Windows but will not work in the android ecosystem
The usb drive I am testing with is a 500gb drive formatted in NTFS. My shield recognizes it, as is, without any modifications. I would recommend that you format your drive in exfat or NTFS. Below is a screenshot showing the drive being recognized by Launchbox on my shield.
-
2 hours ago, Elhora said:
What i mean is Launchbox doesn't see the USB Key.
The USB Key is seen by all my Shield emulators (Retroarch, msx.emu, Lemuroid, etc....) and programs (Kodi, File Manager, etc.) but NOT by Launchbox. When i click on Import games, the only storage i see is the 16Go drive of the Shield, not my 128Go USB Key.
The Key has been formated on my Shield when i plugged it, and the ROMS have been put on it via network with FX Manager. It seems that just Launchbox doesn't see my USB Key
I know what you mean. It's possible that the issue is that launchbox does not recognize usb drives formatted by the shield. I have used drives formatted in windows and those have been recognized by launchbox on the shield. You might want to try that.
-
On 11/4/2023 at 5:20 PM, Elhora said:
Hi everyone
I'd like to know if it's possible (or if there is something special to do) for Launchbox installed on an Nvidia Shield (version 9.1.1 33.2.0.157) to look for games located on an external USB key ?
I've put all my roms there, i can see my usb key from within many application on my Shield, but not within Launchbox... that makes me perplex.
Yes, you can. Go to the hamburger menu, select "import games". From there, select "folder of games to import" and if the shield has picked up your usb drive correctly, you should see two folder paths on the "select this folder" screen. One of these paths should be to your usb drive. If your usb drive is not shown on the list, then you might have an issue with the drive itself, such as formatting etc. Hope this helps.
-
1 hour ago, C-Beats said:
As you've been told several times, most of the delay you're complaining about isn't the program being slow, it's a UI animation in play put there by the theme designer. Changing the theme would drastically change your experience. Not saying there isn't room for improvement in either application, but a lot of what you've complained about in the past you already have ways of opting out of.
I think we are all here to help Jason and the developers make Launchbox and Bigbox the best it can be. I don't know how many times Merovingio has brough this issue up but looks like it's gotten to the point of frustration. I do agree with him that there seems to be some scrolling lag on Launchbox which looks like it has to do with how the images are rendered. I have switched themes and have noticed similar results with other themes. For me Bigbox seems to render images better as there is hardly any lag. However, I haven't added any videos yet, so we'll see if anything changes after those are added. Keep up the good work.
-
1
-
-
1 hour ago, ArquebusX said:
Update - I have learned about side-loading! And I've gotten it to work just as you suggested. Thank you!
Awesome. Glad I could be of help.
-
18 minutes ago, ArquebusX said:
I'm able to get the mame 2003 plus core to work (matched up with LaunchBox), but the standard mame one (which I'm assuming is matched to the standard mame libretro core in Launchbox) is giving me a black screen. I don't know that it matters - 2003+ seems to be working fine.
If you are using the 64 bit version of retroarch, you need to use the mamearcade_libretro_android.so core, for 32 bit i believe it is mame_libretro_android.so core. Also, make sure you have the correct core downloaded inside retroarch. Depending on which version of retroarch you have.
-
Have you tried checking to see if retroarch is setup properly on launchbox for android? You can do this by going into the arcade platform and selecting the 3 vertical dots on the upper right side. There you will find an option that says emulator settings, select this option and you will see the emulator options for that platform. Makre sure that the default emulator matches the retroarch version you have installed. Next make sure you have the correct default core. Finally, you can select verify configuration, this will let you know if you setup retroarch correctly. If you get an error, then something is set up wrong, and you will have to check your setting again. Mine is working on my cell phone so if you still have issues, let me know.
-
14 hours ago, C-Beats said:
All themes have Platform/Game Details reload on item selection. That being said Default does have quite a few transition animations that occur that others don't that would increase the time it takes to load in. Those time are static though and shouldn't be changing with a change of drive.
I could be wrong, but I know that SSD's have different read/write speeds depending on the model, so it's possible that @Retrogamer4423 ssd's are running at different speeds. This could account for the differences in load speeds that he is experiencing.
I too have noticed a little bit of lag when scrolling though the games on Launchbox. I also noticed that when using an xbox controller to scroll though the games that Launchbox will continue to scroll even I stop making motions with the controller.
-
1 hour ago, C-Beats said:
@goin3d @Beforedeth @Vader Can you update to the latest beta and let us know if you're stilling having the issue with your options window not opening correctly? We believe it to be resolved in this latest push and would love to have confirmation as such from some users who were experiencing the issue.
It seems to be working for me, as well. I will update if I notice something different.
-
1 hour ago, goin3d said:
With the latest beta I am unable to access the Tools>options menu. When I attempt to there is a box popping up behind the Launchbox app for EA Play login, but that box cannot be focused, nor can the main LaunchBox window. The only way to access Launchbox again is to force close it. I've attached a screen shot of what the mouseover of the LaunchBox app icon looks like in the windows task bar when this happens.
Same here. Hopefully admins will fix this asap.
-
4 hours ago, ActionBackPack said:
So how do I go about getting the right retroarch and then how do I install the daphne core into the app so that it sees it?
Watch the video I posted. It explains it all there.
-
2 hours ago, ActionBackPack said:
Which version of retroarch has the Daphne core?
Retroarch does not come with the daphne core built in because it is not being developed anymore. That is why you have to go to the website noted in the video, download the core and install it manually in Retroarch.
-
8 hours ago, ActionBackPack said:
Thank you. I'll give it a try.
No problem. If you get stuck on anything let me know.
LaunchBox 13.11 - Beta Thread
in Beta Testing
Posted
He is correct, my original list had 3408 roms, which didn't import. I then used a split romset which had close to 8000 files and that worked. So I guess there is a threshold of some kind.