Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Zombeaver last won the day on April 24

Zombeaver had the most liked content!

Community Reputation

1,768 Excellent

About Zombeaver

  • Rank
    128-Bit Self Aware
  • Birthday September 1

Recent Profile Visitors

9,868 profile views
  1. Iron Assault has now been added to Zomb's Lair.
  2. Gothos has now been added to Zomb's Lair.
  3. I forgot to mention it in here, but I've started a Discord server for Zomb's Lair. Anyone interested is welcome to join. I discuss upcoming projects I'm working on, take requests, talk about the tools I use to make the packages, and just blather on about old games in general You can find it here.
  4. Master of Dimensions has now been added to Zomb's Lair. This marks the 50th package available on Zomb's Lair! It's been a long road, and I look forward to the next 50. I've got plenty more in store. More to come soon!
  5. That'll work. I basically just wanted to make sure that increasing the input scale to 4x wasn't going to have a significantly negative impact on performance. Seems as though it had a positive one, oddly. That would be my guess, yes. That's highly unlikely. If anything, that would add more overhead. 98 is almost never warranted/beneficial over 95 for the purposes of emulating these games. That's significantly more likely. With that said, I don't really plan on changing that. The BIOS for the FIC VA-503+ isn't actually included with PCem by default either.
  6. Did some testing for the upcoming package with some interesting results. To my hand/brain, OpenGL 3.0 seems to actually reduce input latency slightly over the options, and this is improved further by making a few additional changes. I'm not certain whether or not these have any additional performance impact though. There is none for me, but I'd be curious if there is on your hardware @D-TurboKiller. Try setting the renderer to OpenGL 3.0 and then going to Video > OpenGL 3.0 Renderer > Input Stretch Mode > 4:3 and then Video > OpenGL 3.0 Renderer > Input Scale > 4x. This feels noticeably better to me than just using Auto. I'm not certain if that input scale setting increases hardware requirements though. From the upcoming package:
  7. Well, this is fortuitous. I was looking for an easy way to swap out the PCem settings in the launcher for more than just the renderer settings - it's easy enough to swap out any one value doing what I've always done which is essentially making multiple versions of a config and then making .bats that replace the used config with another with slightly altered settings. I've done this for DOSBox, Retroarch, and other things. This is no problem so long as you're only changing one value and don't need to toggle different things separately - like say a combination of the renderer and CPU speed. At that point that method wouldn't really work unless I made a separate .bat and separate config for every possible combination of those (which isn't going to happen). But I just came across the rather eloquently named FART - Find and Replace Text. It's a command-line tool for replacing text in files. This is perfect because now, rather than replacing the entire config with another, I can replace specific strings of text with another, so I can make changes to specific settings independently via command-line. Another gadget to throw into the tool belt.
  8. Understood, and I didn't really take it that way just explaining the logic behind what's there and how I get there. It's a process. I know that in a lot of cases the settings used are higher than "what's needed" as a bare minimum but there's still a reason for it. I do know of a couple though that I specifically intend to revise some settings for in an update like Biosys (which was my first use of PCem and I wasn't as well versed with it at the time). Thanks. I try to make it as easy as I can. I'm not always able to eliminate disc-swapping, but I try to when I can. Some games make that easier to do than others. That's part of the issue, for sure. There's nothing you can really do about that. But if you go from say a Windows 95 environment in PCem and then go to a Windows 95 environment in DOSBox, same screen resolution, same sensitivity settings, there's a noticeable difference (for me anyway). PCem is certainly still usable though. I should be able to do that. Yes, sometimes it can be beneficial to force various options through the Nvidia control panel as opposed to a game's own implementation of them. I've experienced similar things with Nvidia hardware. I don't know about Fast Sync specifically, my card doesn't support it (GTX 780), but that wouldn't shock me.
  9. Point and clicks are some of the worst culprits of noticeable input latency because you're constantly moving a mouse cursor. It's very noticeable to me even going from the most ideal settings for reducing it in PCem to DOSBox. It's basically always there in PCem, and then there are various changes that can be made that will only make it worse (like enabling vsync, which seems to do very little in PCem to begin with... other than increasing input latency). In any case, my point in all this is that I already make a conscious effort to do what you're asking. If you need to dial down settings more for your hardware, okay. I already do that to begin with until I reach a point that I'm seeing some sort of performance impact (minor, in some cases, to be fair). If someone came to me with questions about what changes they could make to cater to weaker hardware, I'd have no issue assisting with that. But my point is that the settings I use aren't just arbitrary. I won't go as far as to say that tweaks shouldn't be made in some cases (I have a few early ones in particular that I know I need to adjust), but in many cases they're dialed in where they are for a reason; and some people's hardware won't be sufficient. I don't mind switching over to OpenGL 3.0 in theory, if that's going to prove beneficial (although I don't know how comfortable I am with assuming that that's going to be ideal across all hardware/software as opposed to Auto), but only if it's not going to negatively impact the input latency.
  10. I'm using a 6 year old PC with an i7 4770k without issue so I'd say there's more than likely a deeper issue on your side; the presence of Wine seeming to be the most probable culprit. In all honesty I ordinarily dial back the CPU speed for the final release. Emulating a Pentium 200 runs at full speed for me. I ordinarily dial it down until the game runs slower in some way/at some point. I even try to ordinarily take a look at the system requirements as listed on the box and aim around the recommended (not the minimum) hardware. Sometimes I'll go a little above if I can notice a difference in load times or performance. The settings I use though, by and large, are not that demanding to be completely honest with you. None of these are intended to be used on Linux/Wine so I can't guarantee how well or if any of them will work in that setting, and I'm not going to cater to that. About the best I can do is get it to an "about right" value and tell people to make adjustments if necessary for their hardware (it's easy enough to do). There are a few that I intend to go back and make a few tweaks to, and that might include speed settings but, again, emulating a P133 is not particularly outlandish (even on relatively ancient hardware like mine). I've seen several packages from The Collection Chamber that use a P166 with 128MB of RAM. I do wish that PCem's tools for tweaking performance were as robust as DOSBox's. I always use "cycles = max limit [#]" for the DOS stuff which is extremely useful since it essentially means "as fast your PC can handle but no more than [x]" which gives you an upper limit to prevent problems from running too fast while simultaneously not locking it into an arbitrary fixed speed that the host might not be capable of reaching (which is essentially what you're stuck with for PCem). Unfortunately, there's no equivalent to that in PCem currently. I'll take a look at this again, but my recollection of using OpenGL 3.0 as the renderer was that it increased the input latency a bit (which is already worse in PCem than it is in DOSBox). Will have to experiment some.
  11. It saves to the inis folder in your PCSX2 folder. I think you can change this in the settings file in the configurator plugin folder.
  12. Mummy: Tomb of the Pharaoh has now been added to Zomb's Lair.
  13. The Day The World Broke has now been added to Zomb's Lair.
  14. It should also be noted that if you're going to do that, you should make sure you use the update that I posted a couple pages back, because the core options changed (because I'm using @Pixelpiper's core now). This is what's going to be used in all future releases so it would invalidate your new option files if you tried using then after updating to the next version.
  15. No, it's done through the core options. If you change it there, it will change it for anything that doesn't have an existing core option (.opt) file for them. To change it per-game, you would change the value and then use the top option in the list to save a core option for the currently loaded game only. This creates an .opt file that's named after the game in config\Vice x64. These essentially work as overrides except they're specifically for core options. Be aware, however, that the vast majority of these games are designed for PAL. The only games that are setup to use NTSC are ones that specifically require it (few and far between). In some cases it will work for both, but I can't guarantee it.
  • Create New...