Welcome, Guest.
Username: Password: Remember me

TOPIC: eduke32 Build Engine text+sprite draw issue

eduke32 Build Engine text+sprite draw issue 5 months 3 weeks ago #1

Been lurking for weeks, first time posting, sorry to say it's with a problem.

ReShade version
Game: Ion Maiden & Duke Nukem 3d on the eduke32 sourceport of BUILD engine Rendering with OpenGL

Issue: some text, most sprites, and occasional textures on models are not being drawn correctly. The perspective seems severely distorted as though stretched or smeared vertically.

The issue remains whether the post-processes are active or not, and after deleting the ReShade files from the game folder entirely.
Confirmed this issue does not appear on a clean install of the current version but appears after injecting ReShade.

I also tried running this version of reshade with Duke Nukem 3d on a different version of eduke32 and reproduced precisely the same problem.

Aside from this, there appear to be no other visual issues. Any idea what could be causing this?

Other Screenshots of the issue: - imgur.com/a/4zUoWk8

OPENGL32.log - pastebin.com/8JiLbWWS
maiden.log - pastebin.com/pq6Lg7KY

Running on
Windows 10 x64
Intel i5 4690k
The administrator has disabled public write access.

eduke32 Build Engine text+sprite draw issue 1 week 6 days ago #2

I'm getting the same issues, so it isn't just you. I've also tried older versions of reshade (2.x and 3.x), same deal.

It would be awesome to figure this out before the release of Ion Fury, up until now, I had assumed it would work correctly.

[EDIT] Forgot to mention: deleting or renaming the .dll fixes the issue for me, and I don't know why it persists for you (I didn't try Ion Maiden, my testing was all done on eduke32). I don't see how it could permanently alter the game, but you never know.

[EDIT2]Also, the issue only seems to happen when using the default and best setting of "classic" for the texture filter in the video options. Applying the blur filter fixes the issue, but makes the game unplayably ugly and blurry. Using filtered textures in polymer mode does not look anywhere as bad, and is the workaround I would recommend using for now, but some mods require polymost to function properly (like in my case) so this doesn't help everyone.

Now that we know it's related to texture filtering specifically, someone might have an idea on how to fix this.

[EDIT3] Well this will be one of the most edited post ever. Scratch most of what I said in EDIT 2, simply CHANGING the video mode and texture filter mode IN THE MENU will reset the sprites to what they should be. It seems like reshade is interfering with the game's launch, but changing those options will make it work totally fine as far as I can tell. Navigating the menu without text can be kinda hard if you don't know the menu by heart like I do, but you could launch the game without reshade, write down the steps etc... I assume everything I've just said also applies to ion fury, so although it may be a bit of pain, it should all work as expected when the game releases next week.
Last Edit: 1 week 6 days ago by themaxmeister.
The administrator has disabled public write access.

eduke32 Build Engine text+sprite draw issue 14 hours 24 minutes ago #3

Same here, with EDuke32. Changing the video mode actually only fixes most of the menu text, but not the sprites in-game for me. That is, with the Polymost renderer. With the "Polymer" renderer enabled, ReShade does not load at all (I did prefer the Polymost renderer though last time, for some reason).

EDIT: seems like crosire pointed out the problem on the other thread: reshade.me/forum/troubleshooting/5707-te...opengl-game-ion-fury

Whaddayasay if we (four already) teamed up and everyone takes like 50 or 100 and checks them through? :-)

EDIT 2: oh well, what crosire said could actually mean that there could be several numbers to be reserved since far more than one texture is being used by the game..? :-( I think I've had the same issue in Half-Life (WON), where several different textures would glitch out when ReShade shaders were loaded. Thankfully I could fix the problem by only loading the shaders after startup. With EDuke32, the glitches appear even before loading any shaders.

Fun fact: this is how it looks in Half-Life:

Xeon E3-1231 v3, MSI GTX 970 @1446/3903 MHz, 16 GB DDR3-1600
Last Edit: 14 hours 7 minutes ago by brazzjazz.
The administrator has disabled public write access.