Some kind of problem with anisotropic filtering?

[Sierra]

After about 3 foot away from where you stand the textures look as if they are not taking any effect from anisotropic filtering.

[CrunchyBiscuit]

Indeed. It's not working on an RTX 2070 Super either, not even when forced through the driver. It just looks like nearest-neighbor with regular mipmapping.

[Sierra]

Guess we'll just hope they read the forums, I don't know of any way to report bugs to this developer.

[ViRGE]

Okay, so it's not just me, then. I am seeing the same thing on an RTX 2080.

[NOBLE SIX]

Originally posted by Sierra:

After about 3 foot away from where you stand the textures look as if they are not taking any effect from anisotropic filtering.

Have you got pixelation turned up?

[DefectiveByDesign]

Originally posted by CrunchyBiscuit:

Indeed. It's not working on an RTX 2070 Super either, not even when forced through the driver. It just looks like nearest-neighbor with regular mipmapping.

The game is using bilinear mip mapping instead of trilinear. It also has no anti-aliasing enabled that I can notice.

If this was quake, the render command would be "gl_nearest_mipmap_nearest"

It should not be using mipmaps AT ALL in a fake software renderer with low res textures, let alone bilnear LOD. The lack of anti-aliasing also makes all imperfections stick out more.

I don't know if you can fix this by editing the Engine.ini, but if you can this would be really useful information to report. Also, I would recommend using ReShade to enable FXAA / SMAA.

Originally posted by Sierra:

Guess we'll just hope they read the forums, I don't know of any way to report bugs to this developer.

99% of fake Retro games, game devs do not care and ignore requests to fix graphic issues, or are outright hostile to people reporting them. "It's not a bug, it's a feature."

Unreal Engine itself has problems with rendering pixel graphics mode. A lot of problems are built directly into the engine. It's also the worst performing engine for retro games, with heavy CPU/GPU performance hit that don't make sense for the graphics. Modern systems won't notice, but you will on a steam deck or anything slower.

edit:
AFAIK, the user can't manually fix texture filtering. This is set in the unreal editor texture mode. So the game devs likely have bad defaults set for texture filtering.

I don't know if this will help, but maybe editing the engine.ini, add:
[SystemSettings]
r.FullScreenMode=1
r.MaxAnisotropy=16
r.DefaultFeature.AntiAliasing=1
r.PostProcessAAQuality=4
r.MipMapLodBias=-1

I am not experienced with tweaking UE4, so use at your discretion.

[makoto]

Hello! We're aware of this problem and we're working on it. We're sorry for the inconvenience

[CrunchyBiscuit]

Good news! Thanks for the heads-up.

[XDbored]

i couldn't get the texture filtering/LODs to work properly either, you have like 1.5m in front of you until it goes ♥♥♥♥♥♥, and then in 3m it gets even worse, and distant textures are just a mess, i would be worried that the problem is me forcing driver AF16 and engine AF16, but the AMD drivers say the AF16 is only for dx9 stuff, so probably just a game thing