Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

ChopBlock223

Members
  • Content count

    994
  • Joined

  • Last visited

About ChopBlock223

  • Rank
    Detail Obsessed Ritalin Enjoyer

Recent Profile Visitors

3204 profile views
  1. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Does the new 14.5.0 build include the fix from here, by the way?
  2. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Woof can use .ogg files for music tracks, but can it use .ogg files for sound effects?
  3. ChopBlock223

    Laz Rojas - an old Doomer in trouble.

    KICK HIS ASS!
  4. Fuck off janny, it wasn't that bad.

  5. Stoked to learn that Senator Joe Lieberman is dead. Fry in hell for all of eternity, you fucking leech.

  6. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Seems to work.
  7. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Same controller, did not happen in older versions.
  8. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Getting an odd behavior with analog sticks which I don't think was in older versions. I can move the stick around and that gives input for all directions, EXCEPT for straight left and straight right, it's completely dead and I get nothing. The weird part is that if I start movement with anything which isn't those directions, and then move the stick to those positions, then the input works just like normal (until I let go). Is this a matter of some setting somewhere, or is this a bug? Anyone else experience this? Was just using Woof v1.4.2.0, tried updating to v1.4.3.0, but it persists.
  9. ChopBlock223

    Laz Rojas - an old Doomer in trouble.

    Glad to see progress in your case!
  10. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Those are textbook slimetrails, they can happen sometimes when there's a lot of fine linedef detail tightly together (like the little pits you see on the ground), and usually where those lines aren't mostly 90 degrees or 45 degrees. You can spot a slimetrail on the zigzag bridge in the original E1M1.
  11. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Glad I could draw attention to and get a problem fixed. Looking forward to further developments of Woof, like always.
  12. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    I don't know how to calculate that value off hand, and that isn't a parameter or value described in the options. I switched to a 400% resolution scale, and that seems to fix it for me (I also told NVidia to actually use my dedicated GPU for rendering Woof, but that did nothing by itself). Still worth looking into what causes this though, and again, it seems to relate to translucency at distance (for the white pixel noise anyway). The little pale purple pixel lines on non-translucent graphics almost seem like they behave slightly differently, but it's harder to gauge. They are on the zombiemen corpses in the Doom 2 screenshot. Maybe this is an inherent issue with uneven resolution scaling, hence it shows at 300% but not at 400%. Like it wants to be power of two. This is interesting, I was on 300% when it happened, and then it stopped at 400%. I'm glad that someone can reproduce this, and that I'm not crazy or having a hardware problem. I guess I'll try and see what I get with different scaling when I get back to my computer, will I get them on the same values? Oh, that is VERY interesting. I had actually been using the vertical mouselook in Woof just now, not for aiming but for visually inspecting levels in software mode.
  13. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    Alright, here you have it happening with unmodified doom2.wad
  14. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    A work in progress. How would a demo help? Wouldn't it render fine on your end if you don't have this problem? I get the feeling that I can PROBABLY reproduce this with the stock game, I'll try that in a bit. I managed to catch a screenshot of it, it seems that it's more likely to happen at further distance away from the player, and that this goes for both original and new things. The Mancubus fireballs do this too. If I were to take an uneducated shot in the dark, I would suggest that it has something to do with translucency, maybe lighting and color too. When I look at items and static objects which are NOT translucent, they don't get all the white crap pixels around them, but what they do tend to get (at least temporarily), is little odd streaks underneath the sprites, and the color looks like that one shade of pale reddish-purple which iD used for transparency. I did not experience this in 14.0.0 or earlier.
  15. ChopBlock223

    This is Woof! 14.5.0 (Apr 30, 2024)

    I edited the config to turn it off, and it actually got more frequent. I can't get a screenshot because it seems to happen quickly.
×