Good day everyone!
I'm a complete newbie, for the first time I wanted to play DOOM on a computer, and when I learned that it was possible with the help of GZDoom I decided to try it)
I apologize for the crooked English, I don’t speak it, so I use a robot translator.
So I unpacked gzdoom-4-14-0-windows.zip and added IWADs to it here [REDACTED].
I launch it and play, but the picture looks like it was stretched from 64x64, literally)
Here are the screenshots - 1 - 2 - 3
The textures become normal only when point-blank, and even after a couple of steps you can’t even distinguish the letters on the walls, and the decals of the particles from the shots are clear and visible from afar..
I spent several hours fiddling with the settings, but nothing was fixed...
If anything, here is mine gzdoom.ini
I play fullscreen on a 1280x1024 monitor
Please tell me what I need to do?
Easy setup help
Moderator: GZDoom Developers
Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
-
FiLinX
- Posts: 3
- Joined: Sun Dec 22, 2024 3:18 am
- Operating System Version (Optional): Windows 10
-
Rachael
- Posts: 13884
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
Re: Easy setup help
Can you post a startup log?
You can get one very easy by starting the game, entering the console (~ on most systems, might be ; or ' on others), and typing "crashout" in the console. It should give you a file you can post here, that will contain a startup log.
You can get one very easy by starting the game, entering the console (~ on most systems, might be ; or ' on others), and typing "crashout" in the console. It should give you a file you can post here, that will contain a startup log.
-
Jekyll Grim Payne
- Global Moderator
- Posts: 1117
- Joined: Mon Jul 21, 2008 4:08 am
- Preferred Pronouns: He/Him
- Graphics Processor: nVidia (Modern GZDoom)
-
FiLinX
- Posts: 3
- Joined: Sun Dec 22, 2024 3:18 am
- Operating System Version (Optional): Windows 10
Re: Easy setup help
here is the log for that command - https://www.upload.ee/files/17551526/Cr ... t.zip.html
maybe share your gzdoom.ini? I would at least compare and check)
-
Rachael
- Posts: 13884
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
Re: Easy setup help
Just to rule out a driver issue, can you type "gl_texture_filter 0" in the console?
(Your previous entry was 4 according to your .ini you posted, in case you want to set it back after)
(Your previous entry was 4 according to your .ini you posted, in case you want to set it back after)
-
Rachael
- Posts: 13884
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
Re: Easy setup help
Thank you for letting me know but that actually doesn't solve the problem - what that did was eliminate one thing that I suspected could be a problem: I think your GPU, for whatever reason, is showing the lowest mipmaps as the actual texture, and it should not be.
This is likely a problem with the GPU's drivers, so there might be nothing we can do. Hopefully NVidia has already addressed and fixed this.
Info for other devs:
gl_texture_filter is 4, vid_preferbackend is 2, report in question comes from "GeForce GTX 550 Ti/PCIe/SSE2" with GL version "4.6.0 NVIDIA 391.35", not sure if there are other cvars that cause this effect but at least now we know the workaround.
This is likely a problem with the GPU's drivers, so there might be nothing we can do. Hopefully NVidia has already addressed and fixed this.
Info for other devs:
gl_texture_filter is 4, vid_preferbackend is 2, report in question comes from "GeForce GTX 550 Ti/PCIe/SSE2" with GL version "4.6.0 NVIDIA 391.35", not sure if there are other cvars that cause this effect but at least now we know the workaround.