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


  • Content count

  • Joined

  • Last visited


About mikeday

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. mikeday

    Trouble compiling Chocolate Doom

    Are you forgetting to run the packaging step after building? cd pkg/win32 make This will create zip files which should have the executables + all the dlls you need.
  2. mikeday

    Chocolate Doom not exiting properly

    I opted for the latest artifacts from the master branch. As I matter of good practice I wouldn't point people to artifacts associated with pull requests; the associated branch might be behind master and may contain unstable/unapproved code. In this particular case it's they're pretty much identical, but that definitely isn't true in general. (FYI, the branch that you grabbed from is staging for the next official release, which is mostly just working on getting the changelog up to date.)
  3. mikeday

    Chocolate Doom not exiting properly

    This is most likely an issue with midiproc, which has been removed in dev versions of Chocolate Doom. I suggest running a nightly build or getting a recent Github Actions artifact. (Go here, scroll to the bottom and download either MINGW32 for 32-bit or UCRT64 for 64-bit.)
  4. mikeday

    dsda-doom v0.27.5 [2023-12-03]

    If you're using the FLAC version of the musicpacks, try the OGG instead. You may be hitting this bug: https://github.com/libsdl-org/SDL_mixer/issues/511
  5. mikeday

    This is Woof! 14.5.0 (Apr 30, 2024)

    Re: MP3s not playing - If you're on Linux or otherwise building from source, libsndfile needs to be at least version 1.1.0 to support MP3 playback.
  6. mikeday

    This is Woof! 14.5.0 (Apr 30, 2024)

    Yes, through libsndfile.
  7. mikeday

    Doom II on Mac

    There are a number of source ports available on Homebrew including DSDA, Crispy, Chocolate, Woof and GZDoom.
  8. mikeday

    This is Woof! 14.5.0 (Apr 30, 2024)

    Is this a photo of your monitor, or a screenshot taken from your PC? If it's the former, I would guess that your monitor is having backlight issues.
  9. mikeday

    This is Woof! 14.5.0 (Apr 30, 2024)

    I observe the same issue with the weapon psprites. I think it might be dependent on monitor resolution. (I'm at 1920 x 1200)
  10. mikeday

    dsda-doom v0.27.5 [2023-12-03]

    Remove the “(1)” and the “ (2)” from your IWAD file names. In general you shouldn’t rename your WADs, as source ports search for them based on their official names.
  11. For the automatic SDL_Mixer looping, LOOP_END should equal nsamples. (nsamples in this scenario is defined as sample_rate * track_duration. You don't need to multiply this number by 2 for stereo.) I bet one could use a small Python script to automate calling oggz and updating the Vorbis comment with the LOOP_END tag. Might be good ChatGPT fodder. :) When I get some time I'll submit a PR to SDL_Mixer to handle the case where only LOOP_START is provided. It seems pretty straightforward to implement.
  12. If you're comfortable with command-line tools, you could always use something like oggz. I can't test this at the moment but it should be something like: oggz comment -c vorbis -o <new_ogg_file> <path_to_original_ogg_file> LOOP_END=<num_of_samples_in_file>
  13. You need LOOP_START and LOOP_END tags, or alternatively LOOP_START and LOOP_LENGTH.
  14. One small correction: it’s FLAC looping that has the crash, not OGG. And yes, it should be fixed in 2.8.0.
  15. mikeday

    Nugget Doom 3.1.0 (updated May 16th, '24)

    There is no smooth pixel scaling algorithm. When that option is enabled, the program asks SDL to enable bilinear filtering when scaling the intermediate buffer to your screen's native resolution. If that option is disabled, it requests to instead use nearest-neighbor. Normally this scaling and filtering is handled by your GPU. So my guess is your graphics hardware can't handle the load from OBS + Woof.