Vader
Members-
Posts
129 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Vader
-
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
-
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 20231212_124604.mp4
-
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?
-
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.
-
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.
-
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.
-
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.
-
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.
-
Awesome. Glad I could be of help.
-
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.
-
@Stavros7575 and @ArquebusX 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.
-
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.
-
It seems to be working for me, as well. I will update if I notice something different.
-
Same here. Hopefully admins will fix this asap.
-
How to get daphne emulator to play on launch box for android.
Vader replied to ActionBackPack's topic in Android
Watch the video I posted. It explains it all there. -
How to get daphne emulator to play on launch box for android.
Vader replied to ActionBackPack's topic in Android
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. -
How to get daphne emulator to play on launch box for android.
Vader replied to ActionBackPack's topic in Android
No problem. If you get stuck on anything let me know. -
How to get daphne emulator to play on launch box for android.
Vader replied to ActionBackPack's topic in Android
Ok, I have managed to get dahpne running on android in past, but it is very tedious to setup and there are limitations. First I would recommend that you view this video : Know that you will have to use retroarch and an unofficial daphne core to get things running. The video will explain which website you will have to go to, to get that core and how to install it on retroarch. For a bit of background, at one time, someone was working on a retroarch core for daphne, but after 2 updates they stopped development, and the core was abandoned. The official core that was left behind had major bugs and was deemed unusable (most notably there were issue with the game audio not playing). However, the first update of the core worked fine with only some minor limitations, as result, someone was able to find that original core later on and posted it to the website noted on the video. Because of this, make sure that once you have the core installed that you disable core updates for that one core or else retroarch will try to update it to the 2nd update which will break functionality. On another note, there is another core being worked on for daphne called dirksimple. This core is a much simpler setup than the daphne core, however it is my understanding that it only plays dragons lair, while the daphne core mentioned above should play other daphne game such as dragrons lair two, space ace etc. Though I will admit that I did not test any other game with the daphne core except dragons lair. The one issue that I did have was that the core would not exit properly and would just hang at a blank screen. Hope this helps -
How to get daphne emulator to play on launch box for android.
Vader replied to ActionBackPack's topic in Android
@ActionBackPack Do you already have Daphne running on your phone or do you need help with that as well? -
Thats probably what I will do. Thanks for your help.
-
Yea, that is what I noticed. I was just experimenting to see how LB works with regards to clones and merged roms as I am trying to find ways to reduce the size of my mame roms. Especially since a full mame rom set can be over 70 gigs in size. Thank for your help
-
@Retro808 Thanks for your reply. What I am attempting to do, is import one merged mame rom, which has the clones imbedded within the zip file. However, LB does not seem to be able to pick up clones within the zip file on an individual basis. However, like you mentioned, If I use split roms of the same game and select each clone individually along with the parent rom, then the clones will be imported without issue. I was kind of hoping that LB for windows would work similarly to LB on Android, as LB for Android does pick up clones within a merged rom, when imported individually. Hopefully this makes sense.
-
@Jason Carr Not sure if this is a bug or just how lauchbox is supposed to work but I did notice something weird about how Mame rom files are imported. For example, right now I am using a full merged Mame rom set. If I import this whole set, launchbox will import clones appropriately without issue. However, If I try to install one game individually from this same set using the import rom file option, clones for that particular game will not import, no matter what options I select at import. Alternatively, if i use a split rom version of this same game, then the clones will import properly. Please advise.
-
I can confirm that the recents list issue on BigBox seems to have been fixed with this update. So far, no additional random games are being added to the recents list. However, there seems to be a small issue in that games that were added to the list prior to this update, cannot be deleted via the reset recent games option. As a result, only games added after this update can be deleted. Therefore, Is there another way to remove these games, so I can start fresh? Thanks