damageinc86

Right, but do you still have to put them in the fanart folder right? I was saying it would be nice to have a "standalone" folder that LB made just for start up screens, and leave fanart out of it altogether, unless you checked a box to add it to the folders that it looked in.

Oh,...how do you do that? Can you just put an image in a folder and it will use it?

This is why it might be nice to have a startup screen background image folder. So that way it wouldn't look in the fanart folder, but there instead, and you could just throw whatever image you wanted/needed to in there.

Yeah I would like to eventually move away and have LB take care of everything, and hopefully that ends up being a user-friendly point-and-click type experience like most everything else is. I think I've been using RL for about 5 years now, and so far it hasn't actually broken down like a car or anything, leaving me up that creek lol. So far, the only thing needing attention has been the module for Cemu not having kept up with the new name for their window, so It can't grab it to focus on currently for fades. But everything else has worked. Some things take a little more tweaking than others, but it's just clicking around boxes and changing values, so again, no need to know scripting for me. I would say that the average user would definitely be intimidated, but I'm not advanced to the point of understanding how to compile scripting, just mildly advanced I'd call it, and I can understand where to click and what boxes to type in, etc. Launchbox is the best frontend ever, and most likely will continue to be, but for the things that jason doesn't see the need for, or doesn't want to tackle, like bezels and the handling of keymapping profiles for you, I can stick with RL which already has it tackled. I remember when startup screens (fades) were considered something not worth thinking about since RL already devoted all their time to implementing that. But now we have startup screens, so I'm betting someday all these little things will make there way in here. I've thought about making a tutorial video for some key things you might want to setup in RL, maybe someday I'll get around to it. The few times I've gotten in trouble, I could just switch over to LB and use an emulator directly from there if I needed to. Even if you use RL for only a few systems, you can always rely on LB for a system that you might be having issues with otherwise, and just launch it through there straightforward if you are done messing with something like a bezel or whatnot.

Yeah that's my point though. Even the simplest scripts, I wouldn't know how to make from scratch. It would take someone showing me what to type like that in order for me to be able to make it function. I wouldn't have the first clue on how to link antimicro/joy2key with anything in launchbox off the top of my head. So just clicking a button in RL to bring up joy2key and having it link it up to the game itself is a frickin' godsend for people like me. I'm sure I could be taught, and could be shown, but lacking anyone just grabbing me randomly and transferring their knowledge to me out of nowhere, this has given me that functionality. The RA controls thing is just that it is a little bit quicker to run through it using mednafen, and I really like that. The other point about RA was that if you happened to use anything different than RA, it is useful to have RL put bezels on those other emulators (mednafen, ppsspp, and maybe a few others for me) so that you have overlays/bezels on as many systems as you can for a more uniform look. There was no script .bat stuff for me to type out at all to get it to point the .iso image to my virtual drive software either, it is all point and click for that, which is just helpful for me. It doesn't look that bad to pull off in LB either, so that's a minor difference in that I wouldn't even have to make a .bat file using RL. I know it's getting less and less useful to the average person, but those were just the things that make it an integral part of my setup. And those few things are very important to me personally, so I will have to wait for the future to see if LB ever adds those types of things in a point and click style of integration. I'm hoping someday to not have to have the middleman of RL. But for now, I still need it.

MAn, retroarch can just get itself all weird sometimes. I always have to keep a copy of an original config because even when saving core overrides only, somehow it has kept overlays from previous cores and applied them to the next for example. I've kept a clean download handy to start fresh several times. Once you do like 4 or 5 systems it just seems to want to implode on itself and get wonky with certain things. Hopefully mednafen can someday cover even more systems because that emulator just flat out works.

I gave up on citra. It seems to have stopped opening, like, ever. Even re-downloading a fresh copy of it. My citra-qt won't open.

Can't you just use the TAB key to bring up the menu and change the game's screen aspect ratio in there? I swear I've done that before.

mine is damageinc86. I hardly have any steam games, but I love playing risk of rain 1 and 2 with other people. I just got killer queen black also, that's a fun multiplayer one.

I feel like launchbox might eventually catch up someday in terms of matching it feature to feature. But for me, it's not there yet. I know we have startup screens now, but I like the simple fade screens I can make in RL by just dropping a wallpaper image in a folder for either a system or game specific, and that will show up as my background for the now loading text. I absolutely need the keymapping feature in RL, because it is so easy for me to use. Just have to point RL to joy2key.exe, go to the keymapping tab, find the game, and then it opens joy2key for you and you do your keymapping, save it and close, and from then on out, everytime that game is launched RL launches that profile for you. No ahk stuff to figure out or any xpadder stuff that always went wonky on me. It just works. A must have for PC games that don't see every controller, or play well with anything past the first two xbox360's i have plugged in. Or games that straight up don't see any gamepads even though they have a gamepad options screen in them lol. Or for keyboard only games. I just love the way it handles keymapping. And of course, bezels. I know so many people use retroarch with most of their systems, but I use mednafen for nes, snes, saturn, playstation, genesis, master system, turbografx16, and virtual boy. I have sega cd on retroarch though with some nice shaders, so I have since dabbled with moving genesis and master system over and using the crtgeom shader with overlays on that. My main reason for using mednafen for as much as I can is because of the on-screen control mapping. I enjoy not having to go into a menu and then a sub-menu, and then a sub-menu of that, in order to map my controls, should they ever need it again. Having it on-screen is super quick and easy. Since I do have my handhelds and a few consoles running through retroarch with their respective shaders/overlays I also want to have mednafen with it's overlay (bezel in RL's case) so that the entire setup looks more uniform. Bezels have been a pain at times in RL for sure, but once it's done, it's basically done. Looks great and works great. Retroarch does handle overlays/bezels better, but if you use anything other than retroarch, it's nice to have the option to also have bezels on those emulators to help the entire collection look uniform. One other thing is that on the odd PC game that looks for a disc to be in the drive, you can point RL to your virtual drive software, and then edit the PC module settings for the specific game to point to the .iso image, and it will mount it in that drive for you when you launch the game. I wouldn't know how to go about that using scripts or anything else, so it's very cool to just be able to point RL to that, and have it do the work for me. The modules can be annoying sometimes. If I ever update the modules using the built-in updater, I will then have to go back into my mednafen module and add the system names "SNES homebrew, NES homebrew, Genesis Homebrew, etc." because they don't have my naming convention included in the module system type. I also have to go down some lines to add it somewhere else as well. Someone had to make a custom redream module on the forums so we could launch through redream. So they could sure use a little more active development and whatnot over there. But other than that, my modules still launch everything I need. Dolphin, Cemu, launches retroarch fine as well, PCSX, etc. So far I've only had to ever add the new redream module. Everything else has always launched the other emulators just fine for about the last 4 or 5 years. There are a few cumbersome moments when dealing with the PC games modules settings, and some other settings. But all in all, it really isn't that bad. Of course, I have been dealing with it since it first came out and was still called hyperlaunch. It was absolutely daunting as a beginner. I had never even used a frontend before, so using that as well was very hard to get right. Basically, you have a lot of learning to do if nobody shows you around to get your bearings. I have helped a few people from the launchbox forums using teamviewer, and it was way easier to just show them on their screen what to do, than trying to explain it in text. Once they saw what I was doing, they could easily jump in and set up systems themselves. If anyone is curious about setting it up I am always happy to help out with it.

If you are just wanting to take some games from that collection and add them to yours, then just use the standard add/import function in launchbox and have it use those files.

That's odd. There should be text for every entry, even in the quick menu.

That's weird. I've left all my WiiU directory structures alone, so the file was hidden down a few levels and launchbox had no trouble accepting that as the rom file.

Is there a feature that allows you to adjust the size of your box front images (or any other image that you have chosen as the display image) in launchbox for one platform and have it applied to that platform only? For example, I'd like to have bigger N64 box images using the slider in the lower right hand corner,...and bigger ms-dos box images, but once I do that, the other images for all platforms are the same size and end up being way too huge for my liking. It would be useful to apply sizing options on a per-platform basis.

Yup. Maybe I'm tired of seeing certain platforms for a while, and just want to have a smaller setup, but definitely don't want to have to re-import and everything when I decide to bring it back. Just another useful option.

I would think anything that helps with naming things correctly and spitting out useful files would be welcomed.

So i'm starting a new build and my motherboard now has onboard bluetooth. so I'm thinking of adding my 8bitdo controllers. I still have all my wired controllers plugged in (mayflash GC adapter, two snes gamepads, two playstation gamepads, and two xbox360 power-a controllers). Soooo, big question is, once you pair the 8bitdo and map the controllers, then turn off the 8bitdo and turn it back on,...does the emulator still have the right controller order in mind when it starts looking for it? Don't know how bluetooth works with controller order in windows. Do things get switch around during power on/off like it would when you unplug a wired controller? Even more curious about using two bluetooth for two player games and then turning them off and on again. Still haven't ever really seen anybody fully deal with this and report back results. I might just end up doing it and checking, but just wanted to see if someone might know already.

Yeah having to do per game override seems like a pain. Guess we suffer for it haha. I still primarily use rocketlauncher for my bezels, but that's just because it's "grandfathered in" to my system as I was already 100% set up with it before launchbox came along. In that system, you just have to have the correct parameters set in an ini file (which would be the same for every one if you had a uniform set) and put it in a folder with the same naming convention as the games and it will display. I usually stick to system wide bezels, with the occasional per-game bezel when there is cool artwork that I like.

It must have saved the overlay to the main config. I had this happen a bunch when I was trying to do custom overlays for all my handheld systems. Retroarch would just randomly pick one system and save the overlay as being on in the main config. Even though I had turned save on exit off, and saved a core override everytime. It was just a weird glitch type thing. That meant it would have the previous system's overlay on top of the next system's overlay (e.g., sega saturn bezel on top of the dreamcast bezel; could see both). So I ended up having to make a good main config that was clear and just a base setting, and make a copy of it so that once I was done saving all the core overrides, I could then delete the original config and rename the copied one back to the main name and it would have clear settings and stop putting a previously saved override on top of the next system I loaded. Maybe if you just turn save on exit option off you will get lucky and it will not save the previous overlay everytime you exit.

I have: Mario Bros., Zelda, Mega Man, Metal Slug, a bunch of "best of" arcade genres (Fighters, golden age, Schmups, etc.), Pac-Man (includes all pac-related games), Nintendo black box collection, top 100 and top 50 for most of my consoles, and I think that's about it.

Ohh damn I was searching for stuff about big box controller mapping and that sort of answered my question as well. I was curious if with the more recent updates you could select a controller, then go edit the mappings, then select a different controller, then go edit ITS mappings, so on and so forth. So that for each controller you could have buttons you chose for it to control bigbox. Currently, I have my xbox R3 click to start a game, but that button number is different on my SNES usb controller, and also different on my gamecube controller, etc. So I have to push buttons until for example, I remember that whatever button number that is, corresponds to a different button on a different controller. Because bigbox seems to just apply the first button mapping you do onto every other controller, regardless of where that button happens to physically be, and whether you want it to be that button on a different controller or not. Hopefully someday we get controller specific mappings to navigate bigbox, so that we can pick up any controller, and have mappings that make sense for each one depending on the buttons on the controller.

I think someday it will handle everything artwork and streamline look related. Right now though it is either retroarch or rocketlauncher for bezels. Those are the only two programs that can handle it right now that i'm aware of. Well, besides the MAME bezels for arcade games that you can use natively within mame.

I've had some luck by filtering the youtube search results for gameplay down to 2 minutes and under setting and then refreshing the search. When it's that short, usually people are doing legit gameplay real quick. Some trailer creators are getting better at jumping into it quicker and showing more gameplay.

I just made a platform for each of my homebrew/romhacks. SNES Homebrew, NES Homebrew, etc. etc. Took a little bit of time, but not too bad.