Jump to content

Jakura

Members
  • Posts

    9
  • Joined

  • Last visited

About Jakura

  • Rank
    New Member
    New Member

Recent Profile Visitors

236 profile views
  1. I did notice something different with the DEH Extra patch when testing in a couple different source ports: the plasma rifle's frames are uneven, sort of stuttering when holding down the fire button. The last vsmooth patch from Scuba Steve has perfectly even frames in comparison. At first I thought this was an anomaly, but after messing around a bit I realized the "stuttering" matches vanilla, non-modded behavior. I grabbed the decorate version of the Extra patch, and it fixed the problem in GZDoom; but I haven't yet figured out a fix for DSDA/other source ports, if there is one.
  2. Thank you (and @DreadWanderer) for the answer, I've learned something new! I'm currently using dsda-doom, so I'll give the DEH Extra patch a spin. I was using one of your previous patches before, so thank you as well for your additions to the mod.
  3. While comparing past and current builds, I noticed that from v0.26.2 to v0.27 (and prevailing to v0.27.5, used in the examples below) there was a change in OpenGL's lighting that resulted in a brighter overall image, where v0.26.2 and earlier builds were closer to Software (especially in the shadows, such as in the doorway to the left). Software v0.27.5: OpenGL v0.26.2: OpenGL v0.27.5: The fake contrast and light fade options were introduced with v0.27, but I have them set to their defaults of "Normal" here and changing either doesn't bring the image closer to earlier versions/Software. I recall reading in a previous thread that the ongoing goal is to make Software and OpenGL modes essentially indistinguishable, with priority on the latter; so I'm curious if this was an intentional shift. Edit: I realize it might be a little difficult to tell with the screens I chose, so here's a link to Image Comparison Slider for quick and easy comparison.
  4. I apologize for bumping a year-old thread, but I enjoy this mod quite a bit and wanted to ask about something I only just noticed. As far as E1M1 is concerned, every instance of the player gibs (first screenshot, no mods) has been replaced with the zombieman/shotgunner gibs (second screenshot, mod enabled). Assuming this applies universally, is this intentional behavior? I've read through this thread and didn't see any mention of sprite changes beyond weapons, so I was a little surprised.
  5. I was just about to post the same (or similar) "dilemma", though in my case for Win10 (16:9, 1080p). In a way, I've already "solved" it - in 32-bit video mode spectres are practically invisible, and lowering the setting results in a drastic increase in visibility. The examples below (32-bit and 8-bit, respectively) are from Hell Revealed, but it's the same effect in any WAD/map that test. Strangely, when the screen flashes red due to picking up berserk or taking damage in 32-bit mode, they become more visible. Does anyone know the reason behind this, or if there's another way to tweak the fuzziness? It's more a curiosity than a problem.
  6. Thanks for the reply. I think I might've caught wind of that while doing my own research, so I'm glad to have it confirmed. I'm not an expert when it comes to configuration, so I never found my own solution.
  7. After playing around it some more, that does seem to be the case - I guess I just never noticed it before (or I was using ports that altered the behavior, more likely). Thanks for the answer, I know it was a novice question.
  8. Is it normal for sounds to cut out, or not happen at all? For example, when fighting the monsters that appear after obtaining the red key in MAP02, the super shotgun has moments where it makes no sound when firing. I've never had this issue with a source port before (including Chocolate DOOM), so I'm unsure what the issue could be.
  9. I have an issue where the music skips/repeats for a moment a few seconds after looping (using an .OGG music pack), present in both an old build I was using and a fresh install of the latest build. Everything else seems to function properly, and I haven't found this issue with other source ports. Is this more likely to be a problem with the port/how I've set it up, or with my PC/Windows?
×
×
  • Create New...