OrdinaryMagician/swwmgz_m
OrdinaryMagician/swwmgz_m
1
Fork 0
Code Activity

README update, a couple other things, and more partial progress on the Visual Thinker migration.

Browse source
This commit is contained in:
Mari the Deer 2025-04-28 10:08:05 +02:00
commit fb835a478f
7 changed files with 68 additions and 85 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -54,21 +54,25 @@ Recommended settings are as follows:
- **Textures:** Filtering set to either "`None`" or "`None (Trilinear)`". Textures are meant to be chunky.
- **Post-processing:**
- Bloom is recommended at minimum, FXAA should be fine as well.
- Only enable SSAO if you have beefy hardware, it's expensive *(though it doesn't look that great)*.
- Only enable SSAO if you have *REALLY* beefy hardware, it's expensive *(though it doesn't look that great)*.
- It is not advised to use VKDoom's tonemap filters, as they can cause glitches with some visual effects.
- For other post-processing, use [MariFX](https://git.marisa.pw/OrdinaryMagician/marifx_m) *(shameless self-plug)*.
- **Lighting:**
- Dynamic lights must be enabled, or you'll be missing out on a lot.
- It's advised to use "`Classic`" sector lighting, as other modes may over-brighten weapon models.
- If affordable by the hardware, raytraced shadows are recommended *(don't use the "precise" options unless you have a 30xx series card or higher)*.
- With RT shadows, keeping the shadow quality at "`Nearest`" is recommended. That setting has a much higher performance hit when not using regular shadow mapping.
- "`GPU (Per-pixel)`" sprite lighting is also recommended on high-end hardware, though do note that this may cause performance issues on slaughtermaps *(I mean, that's kind of expected)*.
- **Audio:**
- Increasing sound channels to their maximum limit is advised.
- HRTF is not recommended, it may result in excessive CPU usage.
- HRTF is not recommended, it may result in excessive CPU usage and lower quality full-stereo SFX.
This was verified to run smoothly on the Steam Deck *(rarely if ever dips below 60 FPS in combat unless playing geometrically dense maps)*. Still, it is not really possible to bind *ALL* controls beyond the bare essentials, *(this might be addressed in the future)*, and setting up VKDoom itself on the Deck is complicated as well, but the devs are working on that, [last I checked](https://bsky.app/profile/vkdoom.bsky.social/post/3lgarbh5phs2s).
This was verified to run smoothly on the Steam Deck *(rarely if ever dips below 60 FPS in combat unless playing geometrically dense maps)*. Still, it is not really possible to bind *ALL* controls beyond the bare essentials, *(this might be addressed in the future)*, note that for the time being, VKDoom has to be installed on the Deck through an [unofficial flatpak repo](https://github.com/fpiesche/flatpak-builds).
*(Testers are welcome for narrowing down more precise hardware requirements)*
*(If you're going to be playing slaughtermaps with this, these specs and settings may not be enough, duh)*
---
## The Demolitionist