ZDoom

Graf Zahl wrote:Prepare to buy some new hardware soon. This sounds like some component in your system is coming close to the end of its lifespan.

Fixed by replacing the sound card. Shouldn't have questioned the above response.

@mods pls close the thread

Hi. GZdoom 4.4.2 OpenAL on Creative X-Fi Titanium, 44100 Hz. I always used "Linear" interpolation before and the game sounded as it should for me. Now it sounds more "crispy" -- almost like there's no interpolation, forcing me to use Cubic mode, which I don't like. Tested in previous version (3.x.x ...

Seems fixed in latest GZdoom 4.4.2.

What about these? Still an infringement? screen.jpg If not, download whitecross.wad I'd stick with the original design -- it just seems most minimalistic and simple, unlike the ones provided above which don't really fit the visual style of the game -- despite being realistic. It's basically just ...

Tried Attaching debugger to Process. Checked twice -- freeze occured when trying to use some kind of EFX (according to code), which is a common thing in PSXDOOM TC maps (Reverb). Still not sure what particular Effect might be causing this -- when I played, Reverb seemed to work fine. Maybe I'll ...

You can also use some kind of emulated OpenGL, like Mesa: https://www.mesa3d.org/
Used it with some success on a laptop with faulty GPU, where installing Drivers only made things worse.

Where do you open this file? Latest GZdoom creates INI with non-usual line break format which Windows Notepad doesn't understand. Try using Notepad++. Here's where you need to add this line: <...> vid_aspect=0 vid_vsync=true vid_defheight=480 vid_defwidth=640 vid_rendermode=0 vid_maxfps=200 win ...

try adding this to gzdoom-username.ini:

vid_rendermode 0

Built debug openal32 successfully using cmake-3.14.0-rc3-win64-x64 GUI vs2019 project https://drive.google.com/open?id=1iVHjvC6DdflqP-Ijr7WlK4iUxvSuv6Zt Problem reproduced. Im afraid I don't have enough experience to see what's going on. Is that where these "hints" are supposed to be? [imgur]https ...

This time GZdoom Crashdump was created: https://drive.google.com/open?id=1R5_eYXBgibD_7RT2P9VstuuQ3QRB9nLe I don't have the debug symbols for the openal32.dll ************* Path validation summary ************** Response Time (ms) Location Deferred cache* Deferred srv*https://msdl.microsoft.com ...

Freeze now appears randomly, or doesn't appear at all First, it crashed after changing some options, including switching OpenAL device from Default to "OpenAL Soft on SB X-Fi (B)" and performing writeini shortly thereafter (sorry -- no dump) When Sound Device was Default, don't remember encountering ...

Actually the sound card is the only old component (besides few hard drives). Thanks for the guess. Makes sense because it's OpenAL device. Still haven't tried with No sound. Tried the following instead: Deleted all Configs Played clean doom2.wad fine Played doom2+psxtc.pk3 fine Played doom2+psxtc ...

The system is less than a year old, CPU and motherboard released less than 9 months ago. Are you really sure? What Component should I replace?

Maybe there's some kind of Debug mode in gzdoom? How can I collect Verbose logs or something? I cannot even get to "Send GZdoom crash report" stage.

As a quick check, could you please try to enable VSync? Also, why do you use legacy/vintage build with quite modern hardware? VSync was enabled during previous attempts -- I disabled it (that's why it's off in the config), but it didn't make any difference. The problem occured regardless of VSync ...

Great tc! i am sometimes running Skulltag server with it