Jump to content
LaunchBox Community Forums

C0ntrA

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by C0ntrA

  1. That was a good post. But the issue with wheel scrolling can't be swept under the rug like that. I have a specific "other front-end" that has literally zero issues with scrolling through my thousands of game titles. Calling it an "Nvidia Shield limitation" is a poor excuse. Honestly it's the primary issue that I am struggling to get past, especially with no attention from development, and excusing it that way does not help the situation. I'll repeat, other front-ends do NOT have this issue. Cutting down your library so that Launchbox won't freeze and freak out while force closing your application is not a viable "resolution". Now I am no app developer (I am a business man and an investor of businesses), but if I was to hazard a guess. The issue may be to do with the "image downloading" when entering a selected system. Is there not a way to have those images saved so that any time after the fact, a user can simply have those images locally stored and saved so that there is no "download" process involved every time? Excuse my assumption that the images download every time if that is not the case. But that in of itself seems to be a potential problem then. Something to do with the images and data scraping process/downloading most likely. My other front-end...let's call it "Turbospun" has ZERO issues with lag caused by scrolling through thousand of titles. No front-end is without issues, but being that front-ends are for mostly convenience and aesthetics, the current state of Launchbox and it's wheel issue seems to be a MEGA problem that is becoming "acceptable" by those who may not realize that ain't normal... If Launchbox and its team aspires to be "top-dawg" of Android front-ends, it's time to both recognize and DEAL with that very obvious issue. Otherwise, Launchbox is going to have to settle for about "third place", falling behind products that don't create a "hassle" when trying to find a game to play while enjoying the visuals and convenience of an expected and professionally designed front-end.
  2. That would be nice, other front ends have that option, or at least one that I know of. Perhaps it's already on the agenda?
  3. Those are getting added.
  4. Isn't it safe to assume that all this will eventually resolve as LaunchBox for Android matures? Especially when the community can add to the database. This is still "being developed"; No reason to assume every little detail is going to be 100% just yet. The ability to select which emulator I need to run the game with at the selection wheel is why I am committed to Launchbox Android at this point.
  5. LB Android is being developed again, still work to be done, and that's the point of this thread Glad you got it figured out though!
  6. Could be variable depending on the system being emulated etc. But the basics to look for would be the title for the game/file name, and an example of that would be something like say...Super Nintendo for example. So let's say you just downloaded Super Mario World (of course because you own it *cough*), the file would look something like SMW.sfc ,SuperMarioW.sfc, or SuperMarioWorld(USA).sfc...etc etc, looks clean and such right? Yes. But you could find one like SuperMarioWorld(J).sfc...Now that would be the japanese version and Launchbox will identify it with the japanese super famicom title and boxart; the game itself will also of course be the japanese version when played. Anyway, to test this. Find one of your problem games in Launchbox, then exit and try to find that rom in your storage, now look at the file name. If you notice something like what I had posted above, you should be able to "rename" that file so that Launchbox will see it as the region of your preference. Sounds like you are newer to this scene, as far as front ends and emulation goes. I am as well! Sure I have played with emulators back when they were a new thing, but it's not until you try to make things pretty (ie front ends) that your journey for emulation expertise starts! I have only been at it for about a month now, and due to my frustrations with other less than user friendly front ends, I have obtained a lot of learned knowledge along the way, as will you. Welcome to another hobby
  7. Did you check all your roms in question via your storage drive? There are no additional characters following their names such as "j/eu" etc? I would think that you could simply rename the ones that aren't correctly identified in Launchbox. Again...I haven't read the entire thread, so I am not sure if you had done this already. I mean, just because a downloaded set states NA only, doesn't mean it won't have its potential issues.
  8. Excuse my ignorance as I haven't read the entire thread... But it sounds to me like you have other rom versions in your set (other regions). I assume this because I recently scanned all of my snes roms (NA/USA) and everything looked correct. I then scanned my super famicom roms under snes (since we don't have a famicom section) and the process seems to have altered "some" of the NA titles to japanese...(I assume that perhaps I had japanese versions of those NA games and because I scanned following NA, the japanese titles had overwritten the NA ones where applicable because it was scanned more recently (after snes). Not a huge deal really, but hopefully it's in the agenda to add categories for the "funky stuff" like famicom etc. Or another solution could be to allow a user to select which version of a title in their library to show under the wheel. I assume your friend tried with the exact same rom set as you? Side note: Why no scummV yet?
  9. I see it's been 2 days... But anyway, you need to set that up in Dolphin natively first. Otherwise "select" might be the default button to bring up the menu that allows you to quit.
  10. Of course! That's why we are here, because Jason and the Launchbox team are developing a premium front end, and we are providing feedback to hopefully help assist in its success! It's my primary Front End even now, for good reason. It's clean, versatile, and looks amazing as an Android TV setup (my individual use).
  11. I think an "expectation" for smooth scrolling is there because of experiences with other front ends using the exact same hardware. If a person experiences this already, it's not a far stretch to wish for the same result under a new front end. Of course every front end has its quirks and such, that's the reality. But again, some categories slow down even to the point of force closing Launchbox, some don't. The most likely reality is that this has something to do with the way Launchbox is currently built, rather than storage speed limitations, again referencing the fact that other front ends don't suffer this anomaly. Other than that though, this front end is performing quite well.
  12. Also experiencing it here. Only a select few consoles seem to suffer the slowdown in the wheel. SNES is one example I personally notice the most. Using an ssd as adopted (where I moved my Launchbox folder to). I think it's something more than "just drive speed", it makes no sense as it doesnt affect every game category.
  13. No that is not accurate at all lol. Toilets are NOT free and readily available for people to obtain at any given time...Also toilets are TANGIBLE items that have a manufacturing cost etc. Anyway, was only trying to help, and forgive me for even remotely mentioning the forbidden "hard drive" subject. Won't happen again
  14. I wasn't "promoting" anything...I was being truthful of my avenues. Prob should have kept it to myself yes. Just like a good 50% of the users in here are doing just now I am sure. Brutal honesty has always been a curse of mine.
  15. OP, if you haven't got your issue resolved yet. Maybe look at my thread as I found a solution for my situation that is similar to the one you were experiencing.
  16. Update 3: Seems that I was able to get Neogeo to work within Launchbox by scanning the Neogeo game library through the Arcade category... I can play my Neogeo games through the Arcade selection in Launchbox by selecting the FBNeo core from within Arcade to run them. They also work on Mame_current but with terrible audio stutters. So I lose my ability to have my Neogeo games nicely organized on their own, but really Neogeo games are arcade games anyway so meh. I guess it is not much of an issue anymore. So it's as "resolved" as it's going to get for me.
  17. Update 2: Well it seems that only a minority of the NeoGeo games work when trying to launch from Launchbox using either Retroarch 32bit or Retroarch Plus. So I guess my battle ain't over quite yet.
  18. Update: After re-scanning the NeoGeo library, I was promted with a request to download Retroarch. This lead me to assume that the FBNeo core within the Launchbox selection is default set to launch from within Retroarch 32bit. Tested afterward through Launchbox and most titles eventually worked through Launchbox>Retroarch>FBNeo, not Launchbox>Retroach Plus>FBNeo (even though Retroarch Plus > FBNeo works just fine). Possibly something to be addressed in a future update? I suppose my focus is more narrow than most, as I stick to Retroarch and Retroarch Plus for my emulator platforms. I did this so that my "Bezel project" program continues to work while within LaunchBox.
  19. All my other systems work just great so far. Everything from Coleco to Ps1. Initially Arcade was giving me issues but I resolved it. Neogeo is the stubborn one here. I initially allowed the files to unzip etc before realizing that was not the thing to do, so I reinstalled and started from scratch after moving my Launchbox folder to internal storage (to help with menu scrolling/crashes from slowdown). Come to think of it, the "google issue" can't be related...Otherwise my other systems wouldn't work right? Especially Arcade. So perhaps something to be looked into by development? That...or I am the only one with this issue and it is something ridiculously small that I have been overlooking?
  20. It's from the playstore. I wanted simplicity and updates etc. Again though, the thing is that the games work fine using FBNeo core in Retroarch. The problem is through LB, as something is preventing it from working. Same rom files, same core, no worky... So I guess what you are saying is that it's some sort of LB and playstore Retroarch plus compatibility issue in regard to Neogeo? Or more specifically FBNeo core? I would prob rather wait for a future update of Launchbox and just play Neogeo games through Retroarch natively while crossing my fingers that it gets fixed eventually. I am 42 and I only consider everything up until dreamcast/saturn/ps1/N64 to be retro, and Retroarch Plus from the playstore runs all of that on my Nvidia Shield perfectly fine. I may dig around a bit more to try to fix it, but I am pretty sure it's got to be something goofy, most likely to do with the google barriers.
  21. Well no...Still looking for possible solutions as to why it isn't working. Kind of outta ideas over here.
  22. After a bunch of messing around, I have been able to get everything working so far except NeoGeo. If I launch a Neogeo game through Retroarch Plus using the FBNeo core, it works no problem. But it's when I try to run Neogeo games through launchbox that I will get a message on screen (seemingly through retroarch as my bezels show etc) stating something along the lines of "rom files such and such...missing etc" or even a black screen. Things I have tried: -Moved Launchbox folder to internal storage from my external HDD where it defaulted itself. -Deleted everything and re-scanned about 3 times over. -Tried all the various core options from within Launchbox when trying to run Neogeo games. -Tried replacing bios files within the Retroarch system folder. Again, it's very odd as the rom files themselves are perfectly fine as they run through Retroarch Plus natively. I am only using Retroarch Plus 64bit version from the playstore, no other emulators etc.
  23. I notice the same thing that OP has been (I have a TON of games). I was thinking of trying to move the launchbox folder from the external drive (where it defaulted to) and moving it to internal storage. External has my roms of course, but is an HDD, as to my adopted internal storage being an SSD. Will try tonight and see if it helps.
×
×
  • Create New...