Engine: Rendering graphical glitch

[edmundito]

Describe the bug
While playing An English Haunting, I noticed a graphical glitch in one of the rooms—a black bar with a blue pixel. I notified the creator (Postmodern Adventures), and they couldn't see it. They reviewed the sprites used for the room, and nothing unusual was found. Note that animation is playing in this part of the room, so this area is part of an object that animates:

I am running the game with an ATI (Now AMD?) Radeon 560; I wonder if that's the issue, as I've encountered some problems with this before.

AGS Version
3.6.0.54

Game
An English Haunting (I can provide a save game)

To Reproduce
Just stand in the room and watch.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
Game setup:

Desktop (please complete the following information):

• OS: Windows 10

[ivan-mogilko]

An English Haunting (I can provide a save game)

Yes please, provide a save. I have asked developers for a game copy a while ago, but I haven't played it through.

[edmundito]

@ivan-mogilko Here's a saved game that puts you right in the cave:

an-english-haunting_cave-glitch-save.zip

[ivan-mogilko]

I'm afraid I don't see this glitch either.

I have a nvidia card, but idk if it's related.

Do you know if anybody else with ATI card reported such problem for this game?

[edmundito]

This is why I suspect it is video card-related. I don't know anyone with an ATI card yet, But I will ask around... In any case, hopefully, a minor bug then.

[ivan-mogilko]

Could you also tell, does this happen in any display mode or in particular one (fullscreen, exclusive fullscreen, windowed)?

[edmundito]

I just tried all modes and all rendered (d3d9, ogl, software) and it's still there. I tried enabling sdl debug info in the console but nothing unusual other than:

SDL : ERROR: DEBUG: Couldn't open C:\TIMIDITY\TIMIDITY.CFG
SDL : ERROR: DEBUG: Couldn't open timidity.cfg

[ericoporto]

I just tried all modes and all rendered (d3d9, ogl, software) and it's still there.

If it happens in the software renderer I don't think it can be related to the video card.

I don't know if you are familiar with RenderDoc, but it can be used to inspect the textures by themselves, it works with the AGS OpenGL driver, you need to run the game from RenderDoc to be able to inspect it.

But anyway, if it happens in the Software Renderer my guess is it isn't that. If you can run the game on a build from the master and see if it reproduces the error it would be useful, also perhaps running it on your mac computer, and seeing if it reproduces there or not.

[ivan-mogilko]

Actually, yes, if it happens in software mode, then either this is actually a game bug, engine bug, or something else overlaying the game.

Because in software mode all the game is first drawn on bitmap using software blitting in ram.

[ivan-mogilko]

@edmundito can you clarify, do you see this glitch immediately after loading the save that you attached, or do you have to do something to make it appear?

Another thing, there are few test options in the engine. Try running the game with --nospr command, that will disable rendering of characters and objects. See if the glitch persists.