ZDoom

I just wanted to thank everyone keeping GZDoom up to date for always releasing a Mac version. Having the plethora of WADs and mods available to play on my Mac is not taken for granted. I hope it will continue to be maintained far in the future as new mods/games/features come out that can use future ...

It seems to be this issue . Although, I have no idea why VKQuake works fine. Can you set vid_nativefullscreen CVAR to true and restart GZDoom to check if it changes something? Hmm that didn't seem to affect it at all. Here's a clip of what it looks like for me, in slow motion though so it comes ...

_mental_ wrote: ↑Sat Nov 12, 2022 2:47 pm What renderer are you using, OpenGL or Vulkan?

I'm using Vulkan, but it still occurs with every other renderer.

This stutter was still occurring in Monterey, even late version. Vsync does not have this issue in VKQuake. I’m really just curious as to what’s causing it, because the new Resident Evil 8 port runs smooth as butter on my Mac.

Hello! Title says it all. I have reported this issue before but wasn't (and am still not exactly) able to nail down a cause of what it could be. Simply put, turning on vsync causes some very noticeable frame stuttering at any frame rate and well under what my Mac can max out at. In DOOM II, I ...

There is a good chance this would be fixed by switching to the raw mouse input from the game controller API in macOS. Unfortunately my mac mini from late 2014 refuses to upgrade itself to a version of macOS with this API, so I can't even test this theory. Perhaps some developer with newer mac ...

Alright, so I posted about this a few days ago and I'm now 100% sure this is a bug with GZDoom and is no fault of the hardware I'm using. No matter if I use the ARM or Intel version of the game, there is a noticeable stutter that happens only when moving the mouse. This stutter does not occur if I ...

You can use autoload<tab> in the console to see the command completion for all the autoload commands. You can use cmd+I on the GZDoom icon from within the Apps folder to enable Rosetta mode (but you probably already know that) - it's very useful to see if a certain crash still happens with the ...

Try setting the value "autoloadlights" to true in the console. Thank you so much! That worked beautifully once I restarted the game. Is there any other tricks for MacOS I should know to get the most out of the engine similar to this console command? I appreciate the thorough response and ...

Regardless of what hardware renderer or software renderer I use, I can't seem to get dynamic lights to work on MacOS. At this point, I'm sure this has to be a bug because dynamic lights work just fine on my PC with the exact same settings enabled. Imp fireballs glow on my PC and do not glow on my ...

Alright, I was able to capture the bug on video recording my monitor in slow motion so everyone can see what my eyes are seeing. I also recorded my Windows PC to offer a reference. The game is running at a perfectly smooth 100 FPS on both machines (my monitor's refresh rate) with vsync turned on ...

Just to rule things out, Andrew67100 - are you running with any mods? Usually I do, but to isolate the problem I tried just running the vanilla DOOM 2 WAD and the problem still persisted. It's soooo so slight, and I almost thought I was going crazy when I noticed it, but having my Mac and PC ...

Unfortunately this seems to me to be a hardware limitation. The dead giveaways are that it happens more often with a higher refresh rate, and that it's more noticeable with vsync on. Classic symptoms of the hardware working at its limits, such that if GZDoom has to do more work than usual in a ...

It's hard to notice on a 60 Hz display, but at higher refresh rates, I'm getting a very slight stutter that I believe has something to do with how GZDoom interprets mouse movements in relation to MacOS, but I'm not sure. Using the exact same mouse (Logitech G305) and same G Hub software on both my ...