Jump to content
LaunchBox Community Forums

Zombeaver

Moderators
  • Posts

    4,018
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by Zombeaver

  1. So, I realized after making the above, that I'm a complete moron... Dungeon Explorer II is a Turbografx CD game, so I'm going to have to modify that one to be for Turbografx CD and make a new one for the 16. Ugh...
  2. Despite an exceedingly generic sounding title, Dungeon Explorer II is actually pretty great and has a really badass cover. Normal: Sketch:
  3. That's definitely odd. I just tested both of the things you mention and I'm not experiencing them on mine. Are you running any AV software? Maybe try adding your Launchbox folder to its whitelist if so. You might also want to try turning down your RAM cache size in Tools -> Options -> System -> RAM Cache since it looks like BB is straining your system a bit.
  4. It was banned in Europe. Many credit it as the spiritual precursor to the Manhunt series.
  5. Hell yeah, I did a speedrun.
  6. Well, for MAME games it does - you can tell it to ignore duplicates during import. That's specifically for MAME though. The likely reason that it's able to do that though is because those games all have predefined, static rom file names; so it knows what to look for. That's not the case at all for other systems though so it will take in whatever you supply it - if you supply it with 15 copies of the same game, it's going to put them all in there unless you remove them - how exactly is it supposed to know which of those 15 is the right one? They could be named "Super-Awesome-Fun-Time", "Boogerland", and "Suckville II Turbo" - most emulators don't care what the rom file is named, they'll still run so long as it's a legitimate rom that it can read - which means Launchbox doesn't care either. This wouldn't be a problem if people didn't just grab the nearest gigantic-turbo-mega-pack-of-every-game-ever that they get there hands on and did a bit of curating with their collections. It's your collection, so put in what you want, but if you don't want all the junk maybe don't download a bunch of junk. If you drag in 10 files and they're all named "Mary Kate and Ashley: The Revenge" and the only difference between them is that 2-10 have like [a] [b] [!] [a2] or some other junk at the end, it's not going to know which one of these you actually want to use. The easiest way to deal with this would probably just be to use Windows search in your rom folder and specify what you want to look for (like [!] for example, which indicates that it's a "good dump") and cut them out into another folder, delete the rest, and then paste them back in and import; this is assuming of course that you've got [!] roms for every game, which may or may not actually be the case, but the point is you can use this to pull out files with a specific tag in them if you know what you're looking for.
  7. On the final page of the import wizard (when it shows a table of game names on the left and rom files on the right) just select any lines that are duplicates that you want to get rid of and hit the "delete" key. It'll remove them from the import.
  8. Yep, these are included in Retroarch via the Online Updater menu. Just hit "Update CG Shaders" and "Update GLSL Shaders" and it'll download/update them all. When you open up a core just go to Quick Menu -> Shaders -> Load Shader Preset -> CG Shader or GLSL Shader folder -> and then dig through the various categorized subfolders. "CRT" is probably where you'll want to start. Note, however, that the shader above is in the "CGP" folder and is only in the CG Shader folder.
  9. I looked at the CRT-Easymode-Halation shader in Notepad last night - it's actually pretty short. It's only 5 passes. I can't recall which one was for the bloom by memory (and there weren't any comment lines in the file) but I'm pretty sure one of the passes had "bloom" in the name. CRT-Royale-Kurozumi on the other hand is practically a novel. It's insanely massive. I don't actually know if simply swapping out pass 10 would even work because based on my testing it's affected by more than just that pass. Passes 2-4 and 8-10 all affected it. It's probably actually pass 2 that would be the one to change because all of the subsequent ones seem to involve various types of blur being applied to the bloom.
  10. I just wish there was a way to use the bloom from Easymode-Halation - it's the only one that actually looks very good to me because it's noticeable but unobtrusive. The way it blends with the surrounding area just looks so much better. I'm tempted to try swapping in the bloom shader file from it into Kurozumi. I don't even know if that'll work or if it'd look any good, but it's worth a shot I guess. I like this edit more than the default but I don't want to just get rid of the bloom entirely, which this nearly does.
  11. Yep, this was one of the earliest requests for Big Box. Hopefully it'll be implemented because I've got more than a few descriptions that just get...
  12. No problem! Yep, it's the little things like that that'll get ya
  13. Admittedly the arcade version is a little better given the somewhat toned-down nature of the TG16 port but it's still pretty solid. I'd normally make a point to decry censorship designed to avoid the public faux-outrage that always crops up around video game violence...but it was probably as much for hardware limitation reasons as anything else. Normal: Scanlines: Normal - Version 2: Scanlines - Version 2:
  14. Retroarch gives us tons of cool shaders to work with; so many that it can be a bit overwhelming and hard to know where to begin or what will suit your needs best. I thought it would be useful to create a thread for discussing various Retroarch shaders where people could show examples of specific shaders and potentially provide tips and tweaks for others. @lordmonkus, continuing our previous tangent on the subject, I messed around a bit with CRT-Royale-Kurozumi to see what I could do to tone down the bloom effect. It turns out quite a few of the passes have an impact on this effect. Passes 2-4 and 8-10 all directly affect it. I messed around with all of them for a while and ended up settling on a simple adjustment of pass 10 - "crt-royale-bloom-horizontal-reconstitute" by changing it to a scale of 2x. No more ugly gray smears! Default: Adjusted: Setting Changed:
  15. Having NeoGeo as a separate platform is perfectly normal. I do that as well. After upgrading to 6.7 the problem I was having with arcade platforms has been resolved. Basically it was using the wrong cores/configs between the platform in my library and the "associated platform" in the Retroarch emulator entry - "CPS-2" games were using the core and config I had entered for "Arcade". I thought maybe this is what you were experiencing. You can post screenshots of your Retroarch emulator entry screens (Emulator Details and Associated Platforms) and we can take a look. The main points to examine are: 1. Is LB's path to Retroarch correct? 2. Is the name of the "associated platform" in the Retroarch emulator entry identical to the platform name in your game library? 3. Is the name of the core dll file in the Retroarch emulator entry correct, and formatted as -L "cores\[core name].dll"? 4. Is the path to the rom correct in the launcher tab?
  16. I can confirm that after upgrading to 6.7 official the problem I was experiencing above has been resolved. Everything seems to be routed correctly now between CPS-1, CPS-2, NeoGeo, and Arcade for me. I have custom configs for two of them and when launching associated games it's launching the correct core with the correct custom config, and the ones that don't have custom configs are launching the correct core and just show "retroarch.cfg". That's a relief...
  17. Try changing your Arcade platform association in your Retroarch emulator entry to fb_alpha_neo_libretro and then launching it the game in the Neo Geo platform (I know, it doesn't make any sense, just test it to see what happens). Mine were all kinds of screwed up when I was testing last night. Take a look at this post.
  18. Welp... now I'm a little concerned. I was under the impression that the last beta/6.7 was going to fix this. I'll be home in about 20 minutes to test...
  19. Hmm. Have you closed out and reloaded LB? It prompts you on a new session. According to the Launchbox twitter 6.7 was put out about 2 hours ago.
  20. Are you sure you're not just on 6.7 official now? Because it should be out and fixed now. I've never touched Lightspeed and it was misdirecting cores for CPS-1, CPS-2, and Arcade prior.
  21. I'm willing to bet it's the same issue that's reported in that thread and has been fixed as of the latest beta. What version are you using currently? If you're not on the newest beta, Jason should be releasing the next official version at some point today which should fix your issue.
  22. It's a Vizio E371VA. It's a 37" 1080P TV and I sit about 2' away from it. I also have an E55-C1 in my living room which is a nicer TV; also 1080p. I can see the "bloom" there as well, although it's not very obvious sitting across the room on my couch. Both are thoroughly calibrated. I don't think it has anything to do with the resolution to be honest. That's something that certainly has an impact on scanlines looking correct, but that isn't my issue with either one. Higher resolution isn't going to make Kurozumi suddenly have gradation on its phosphor bloom. It's still going to look like a white smeared Photoshop brush...on a 4k image! *the sound of a crowd going "Ooooh" can be heard in the distance* If anything, that'd probably make it more noticeable. Sitting 2' away from a 40ish inch TV, at any resolution, with bright colors on top of a dark background...you're gonna see it. Meanwhile CRT-Easymode-Halation also has phosphor bloom but looks perfectly fine in that same scenario. I found this post by hunterk over at Retroarch about editing CRT-Royale-Kurozumi and noticed this: // Blur all colors more than necessary for a softer phosphor bloom? static const float bloom_excess_static = 0.0; // range [0, 1] That sounds like it has potential. I may try messing with that. We should...probably just start a "The Big Bag-O-Shaders Thread" ...thread. Haha
  23. Jason Carr said MAME does provide the option to have a button combination close itself out, so you can customize the MAME config to handle it with the same buttons instead. Ah! I didn't even think of that! I'll give that a shot. That should work via Steam Link since the controller inputs themselves all seem to register. Jason Carr said ...you can't simulate any keypresses for it... I didn't realize this - I bet that's actually why keyboard presses via Steam Link don't work. It's actually the only emulator that I've used that's exhibited that behavior so I knew there had to be something weird with it. Thank you!
  24. So this one was a bit similar to Amiga in that it's using artwork that I've always been really fond of, and I just didn't think the normal techniques that I've used on many of these would be all that beneficial. I decided that if I was going to do alternate versions that I'd make the alterations more dramatic than normal. I uh... kinda went nuts with it You've got plenty of options! Normal - Unfiltered: Scanlines - Unfiltered: Normal - Filter Style 1: Scanlines - Filter Style 1: Normal - Filter Style 2: Scanlines - Filter Style 2: Normal - Filter Style 3: Scanlines - Filter Style 3:
×
×
  • Create New...