Crispy Doom • Hacker News Board

Re: Crispy Doom

#11

Post by ASalazarMX » Mon, Jan 10, 2022, 10:01 PM UTC

theevilsharpie wrote: post #9

some-guy wrote: post #6

I'll have to give this a try. Maybe it's a nostalgia thing, but Doom feels "wrong" at higher resolutions and hardware-accelerated texture smoothing. In the past I usually set GZDoom to a 720p resolution with software rendering while disabling up/down mouselook. This to me is the best of maintaining a "classic" Doom feel while still supporting widescreen.

Simply disabling texture filtering would go a long way toward keeping the game looking the way the developers intended, without disabling hardware acceleration, widescreen, or other quality of life improvements.

Same with retro emulators. Smooth, blended pixels just feel wrong.

Re: Crispy Doom

#12

Post by theevilsharpie » Mon, Jan 10, 2022, 10:03 PM UTC

gkhartman wrote: post #10

I'd love to try this, but but I tend to get motion sick playing doom. It seems to be one of the few FPS games that I can't handle for more than a couple minutes at a time.

Older "2.5D" game engines (like vanilla Doom and the BUILD engine) use a number of tricks to simulate a three-dimensional scene that can be disorienting, especially when your player-character is looking up or down, crouching, leaning, or otherwise not looking directly straight.

Modern engines like GZDoom or eDuke32 have full-fledged 3D renderers, rather than the quasi-3D renderers of old. If you don't get motion sickness playing modern games, then playing Doom on an engine with a modern renderer might be helpful.

Re: Crispy Doom

#13

Post by optymizer » Mon, Jan 10, 2022, 10:08 PM UTC

S33V wrote: post #4

I find it slightly weird that a product that's characterized by its attention to resolution and crispiness has no images/video or obvious links to such in their README.

I was irked by this as well. I suspect that if GitHub allowed people to copy-paste images directly into README.md we'd see more images in the description of such projects (not sure if they've added such features since the last time I wrote a README.md).

Re: Crispy Doom

#14

Post by omn1 » Mon, Jan 10, 2022, 10:17 PM UTC

optymizer wrote: post #13

S33V wrote: post #4

I find it slightly weird that a product that's characterized by its attention to resolution and crispiness has no images/video or obvious links to such in their README.

I was irked by this as well. I suspect that if GitHub allowed people to copy-paste images directly into README.md we'd see more images in the description of such projects (not sure if they've added such features since the last time I wrote a README.md).

They did actually. You can paste an image into a Markdown file with cmd/ctrl+v.

Re: Crispy Doom

#15

Post by makeworld » Mon, Jan 10, 2022, 10:19 PM UTC

Seems like this is an improvement from Chocolate Doom, but GZDoom already does this.

Re: Crispy Doom

#16

Post by bombcar » Mon, Jan 10, 2022, 10:25 PM UTC

gkhartman wrote: post #10

I'd love to try this, but but I tend to get motion sick playing doom. It seems to be one of the few FPS games that I can't handle for more than a couple minutes at a time.

Doom was honestly not made to be played on the massive screens we have today I feel, and without adjusting for that, you're gonna have a bad time.

Re: Crispy Doom

#17

Post by gavinray » Mon, Jan 10, 2022, 10:30 PM UTC

omn1 wrote: post #14

optymizer wrote: post #13

Earlier quoted context omitted.

I was irked by this as well. I suspect that if GitHub allowed people to copy-paste images directly into README.md we'd see more images in the description of such projects (not sure if they've added such features since the last time I wrote a README.md).

They did actually. You can paste an image into a Markdown file with cmd/ctrl+v.

Or drag-and-drop an image into a README or any other form of text on the site (PR description, issue comment, etc)

Re: Crispy Doom

#18

Post by bhelyer » Mon, Jan 10, 2022, 10:42 PM UTC

umvi wrote: post #5

seph-reed wrote: post #2

I would love to see some video recording of this.

Seems like YouTube has a few showcases. Honestly I can't tell a big difference between Crispy Doom and, say, GZDoom. https://youtu.be/5e9jBlDYfW0

The point of Crispy is to be closer to vanilla than ports like GZDoom, Zandronum, PRBoom, etc, but still remove some static limits (that custom maps need to work) and increase the render resolution (which GZDoom etc do, but vanilla and ports like Chocolate Doom don't).

Basically it's Chocolate Doom (which is essentially 1994 Doom, but it builds and runs on modern systems), but a little more easy to use and a little more compatible.

Re: Crispy Doom

#19

Post by toast0 » Mon, Jan 10, 2022, 10:48 PM UTC

some-guy wrote: post #6

I'll have to give this a try. Maybe it's a nostalgia thing, but Doom feels "wrong" at higher resolutions and hardware-accelerated texture smoothing. In the past I usually set GZDoom to a 720p resolution with software rendering while disabling up/down mouselook. This to me is the best of maintaining a "classic" Doom feel while still supporting widescreen.

I played a doom port recently that had up/down mouselook and aiming. Very wrong.

Re: Crispy Doom

#20

Post by uxp100 » Mon, Jan 10, 2022, 10:51 PM UTC

gkhartman wrote: post #10

I'd love to try this, but but I tend to get motion sick playing doom. It seems to be one of the few FPS games that I can't handle for more than a couple minutes at a time.

Maybe it's the head bob?