Opened 13 months ago

Closed 13 months ago

Last modified 13 months ago

#13914 closed defect (fixed)

SCI: PQ2: Pixel Artifacts after clicking on top menu bar

Reported by: antoniou79 Owned by: sluicebox
Priority: normal Component: Engine: SCI
Version: Keywords:
Cc: Game: Police Quest 2


This is on 2.6.1 stable and also on current 2.7.0git from master HEAD on Windows 10 x64, with the GOG version of the game. OpenGL graphics mode.

Step to reproduce:

  1. Start the game
  2. In the first screen (Sony is in his car) move the mouse cursor to the top of the screen on the menu/Score bar and click on it -- it doesn't matter if you select a menu option or not.

What happens:

  • Pixel artifacts appear on the top left of the screen (see screenshot), overlapping with the menu/Score bar. These pixel artifacts look like they belong to the next screen (when Sony is outside his car, in the Police HQ parking lot), but they still overlap with the top menu there.

What should happen:

  • These pixel artifacts should not appear, at least not while inside the car.

On DosBox (used by default when running the game from the GOG launcher), there are not artifacts there.

I have not checked whether this issue persists in other screens of the game.

I tried the default settings for the game and also the "use RGB rendering" but the issue persists.

Attachments (1)

scummvm-pq2-00002.png (26.1 KB ) - added by antoniou79 13 months ago.

Download all attachments as: .zip

Change History (4)

by antoniou79, 13 months ago

Attachment: scummvm-pq2-00002.png added

comment:1 by sluicebox, 13 months ago

Awesome! This is (at least) a pic drawing bug; we are not drawing the tree in room 1 accurately. A quick comparison against other reputable resource viewers shows them drawing in wrong in different ways. Not a big surprise given recent discoveries in SQ3 first-room inaccuracies.

Last edited 13 months ago by sluicebox (previous) (diff)

comment:2 by sluicebox, 13 months ago

Owner: set to sluicebox
Resolution: fixed
Status: newclosed

Fixed in: f779535e3e9c4f9e89963fd26fd8d182aaa75f1c

Good news: I blew it! This is a regression from drawing fixes I did in March: 44b6050915ed6012f9e2e14c8ffa81d9e366529d

SQ3 picture 4 was also affected in the same way.

This PQ2 picture is a great test case, as it was also affected by the inaccuracies I was fixing back then. It's now drawn correctly for the first time!

comment:3 by antoniou79, 13 months ago

Yes, I can confirm it works here too.

Thank you for fixing this so quickly!

Note: See TracTickets for help on using tickets.