Jump to content
LaunchBox Community Forums

SentaiBrad

Members
  • Posts

    6,988
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by SentaiBrad

  1. lordmonkus said I got no problems updating, especially when there's a feature making the switch worth it but something in 1.3.2 and the FBA cores it was having some issues with NeoGeo. From the little time I spent at it it seems to want to default to one of the MVS bios files instead of the Unibios even after I told it to use the Unibios in the core options. Certain games weren't loading. So for now there is no compelling reason to make the switch, 1.3.2 has no features in it to make me switch. When they come out with the next point release with worthwhile changes like the difference from 1.2.2 to 1.3.0 I will make the switch and figure everything out. Have you tried updating the core specifically? Or Running portions of the Online Updater? As long as it's not a problem with this build or RA, it can probably get fixed in an update. The beauty of their new schedule though, you won't have to wait long for the next stable.
  2. lordmonkus said No problem on the edit to remove the mention of that site, I will keep that in mind in future posts. Yea, I've probably messed up and mentioned them before too, but I gotta try and keep us safe in the long run.
  3. LaunchBox might not be fully supported yet for all instances of how rom's are set up.
  4. Yea it's a cool idea that ultimately didn't really take off and is kind of left buggy. However, have you tried it with Higan? Higan is the continuation of Byuu's work. Also edited your post a bit to remove references to a specific rom site.
  5. lordmonkus said I had a little bit of a go at 1.3.2 last night to see if it was worth switching to. I got 3DO working but I had to switch my launchbox file to point at the actual iso image instead of the cue sheet but it did work. The one problem I did run into was NeoGeo using the FBA core because it was defaulting to one of the MVS bios and not using the Unibios and nothing I could do to fix it would stick. At the end of the end I just went back to using 1.3.0, the newer version has nothing important to make it worth the headache of changing. In the long run it will be more worth it to be updated. I am unclear with MAME related BIOS and what is good what is bad, but open up the FBA .info file in the info folder with Notepad++. This tells you the BIOS and File extensions they need. Sometimes this can be off as Mednafen PCE or SuperGrafx don't say they can load CCD files, even though they can. Maybe rename the BIOS you want to use with the BIOS it is looking for? I patched my TurboGrafx syscard3.pce BIOS so that it autoboots instead of needing to press a button.
  6. Names could have changed, or if you updated and didn't carry over your cores, configs, system folder and retroarch.cfg then you're missing Core files. You'll need to re-download them or carry them over. You'll also need to tell LaunchBox where the new RetroArch is located too. We've got a video on the channel about updating RA and everything to do in these scenario's when upgrading. If you did carry over, the files could have changed, file extensions could have changed (though honestly unlikely), BIOS could have changed. There's lots of stuff. If you've got the Core downloaded, the proper -L command in LB and the game is linked properly there really shouldn't be anything in your way. I've loaded up 1.3.2 just fine, so I have no clue. Just to be safe, I just tried loading some of the games from your console list and they loaded just fine. So something between LaunchBox, RetroArch and your set up is broken. This isn't necessarily a LaunchBox bug. A link (which is to say a file path to a rom, core, emulator or anything else that needs them) is broken somewhere.
  7. Yea we did work with him on a Giveaway and got him set up for those video's. He is a great guy. I haven't talked to him all that much but he's a cool person.
  8. I got my PhD in LaunchBox and a Masters in BigBox. I now teach them at a local University. xD Anyways, yea we have great community members who translated LB and BB a while ago. Some of them are even wanting to translate the new Database too. We're still always looking to translate in to new languages too. It's amazing we have dedicated enough users. I don't remember all of them off the top of my head but forum member Clive was our Spanish translator I believe.
  9. As to your edit that you made when I was making my post (I post fast sometimes...) More side bar details for Premium users is a great Idea too so you should vote on it: https://bitbucket.org/jasondavidcarr/launchbox/issues/264/allow-customizing-all-game-details-in You'd be surprised at the list when you start making searches in the BitBucket tracker. Make sure to filter by Open too.
  10. I think we have plans to expand the images for MAME a bit, more than likely at least to marquee and cabinets.
  11. DOS76 said Yeah it hides for me every time. @Walrus13 what version of Windows are you running as that may have something to do with it. Let's wait for them to respond about the first question. ;)
  12. We are replying at the same time. :P
  13. Antropus said The frequency doesn't seem to be the case. That would be absurd. I used to administrate a forum with over 30.000 people, so I doubt that would be the case. Every post that was flagged for moderation had a link attached to it, especially to "mega" or other websites. It has no problem with google drive, but if I post anything linked to mega it will be flagged. Frequency CAN be flagged if the forums see's that repeated replies from the same user over and over. It is an over zealous automatic sorter due to spam issues we were really having. Either way, in my second reply I did say that I saw that .nz was the culprit.
  14. Ok I see now too what the issue was. It is for some reason having to do with the .nz domain. So it has nothing to do with my suspicion about frequency. I'll see if we can't get that white listed so that you don't have to do anything special with your posts. In the mean time I'll try to keep an eye on it for you.
  15. Antropus The forum is assuming some of your posts are spam potentially because of the frequency of your replies. I would suggest trying to slow down the amount of replies you make at one time. I'll see if I can't get your previous 4 posts to show up. Edit: Antropus said Btw, there are at least 4 messages answering to your questions since yesterday that are STILL awaiting for a moderator to approve them... including my latest one. You're also more than welcome to PM me. I see a lot, but I can't see everything.
  16. DOS76 said What version of Demul are you using? I just launched Dolphin Blue and it hides the cursor for me when it opens. I'm using the 12-22-2015 build. Ooh, I didn't know that. Was it an option or did it do that on it's own?
  17. DOS76 said You could change the folder that Screenshots point to to the back box folder to make it a one time deal but wouldn't be something I'd want to do. I rarely flip the box using the context menu many of the images it is hard to read what it says anyway. Right next to the flip button is an image expand button, but even then it's borderline for size when reading.
  18. There isn't this option in LaunchBox, but the cursor doesn't exist in BigBox mode because it's primarily controlled with a controller or keyboard. However, you're more than welcome to suggest this as a feature in our BitBucket. Click Feature Request at the top of this page.
  19. Well you can't, unless you made them screenshots or fanart, but that would be ridiculous to have to do obviously.
  20. I thought you could, but apparently not: https://i.imgur.com/71b1fkO.png Should add it to BitBucket.
  21. tomf80 said My mistake on the batch file, I had put an extra dot in the filename. Working on a TV is difficult. It seems the problem was under the associated emulators tab, I didn't choose the preferred core, so nestopia was being called rather than fceumm. Can we get a debug checkbox that logs the exact command given to make troubleshooting these kind of things easier in the future? Thanks. For RetroArch specifically more so than other emulators, the name in the associated path and the name on the left hand side in RetroArch need to match so that it knows what core to load. So in this case Nintendo Entertainment System (NES) is the default name, so that would need to be the name used in both. Not sure what you mean here, but I got it working. Thanks. There is a System name on the left of LaunchBox and there is a System name for your consoles in the Associated Platforms list when editing RetroArch. Every emulator has the Associated Platforms list, this is where default is checked for when importing games and the default command line parameter is for using command line arguments like loading a core or config file for RA. The two names need to match. If you named your system NES during import, not only will you have some issues scraping for metadata (though you shouldn't, but you could) the name will not match the name in Associated Platforms. NES doesn't match Nintendo Entertainment System (NES). Honestly a debug box wouldn't really help here? LaunchBox won't know that you are trying to load a different core. It might know if the two names are different and could probably say something when importing your games, but there is a reason we have a default list of names and this being one of them. If you are intending to use a different core and download a different core, LaunchBox doesn't know this. In my tutorials this is something I do go over, making sure the names are right, making sure to download the cores you want to use then changing the name of the core name in the Default Command Line parameters.
  22. No you're fine. Just making sure they didn't come from a site that doesn't want them shared externally. If you found and compiled them all then thank you very very much for sharing them! I do greatly appreciate it.
  23. SentaiBrad

    Bezels

    DOS76 said I didn't do anything credit goes to @Drybonz You still had the answer. I have a lot of answers, but not always.
×
×
  • Create New...