PCSX.GPU.takeScreenShot() returns wrong data or dimensions (or both) in 24bpp mode

Open

#1,209 opened on Feb 5, 2023 1 comment 0 reactions 0 assignees View on GitHub

Dominant language: C++
Stars: 994
Forks: 151
Avg merge: 1d 15h
Merged PRs (30d): 18

Description

### Describe the bug

In redux, the display and vram in 24bpp show the same image
![from_redux_display_and_vram](https://user-images.githubusercontent.com/34957530/216825544-2f06c76d-7e2e-48ed-aff2-5b746fe8b3ac.jpg)
but the output from lua looks corrupted (black chunk at the top) and things that look like misc left over things from the vram:
![what_is_sent_via_lua](https://user-images.githubusercontent.com/34957530/216825583-3ae7f9ad-4907-4253-b713-9d32e5f01a91.jpg)
![evidence of something funky](https://user-images.githubusercontent.com/34957530/216825709-d45eb4e3-558f-4336-be94-bbd40e0178a7.jpg)

### Expected behavior

Expect a 640 x 480 RGB888 data.

### Steps to reproduce the bug

Meh...
https://youtu.be/yubF-K4KI6I

### Operating System

Win11

### PCSX-Redux version

Version: 13139.20230130.2.x64
Changeset: 26d0a78307c1ea69e0529a3d8c940018e6cfa8d1
Date & time: 2023-01-30 14:03:57

### CPU model

AMD 3700X

### GPU model & Drivers

NVIDIDA GeForce GTX 1650 Super/PCIe/SSE2 Version 3.2.0 NVIDIA 516.94

### BIOS version

SCPH7502

### Options

- [ ] Dynarec CPU
- [ ] 8MB
- [ ] OpenGL GPU
- [X] Fastboot
- [ ] Debugger

### Iso checks

_No response_

### Logs

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

PCSX.GPU.takeScreenShot() returns wrong data or dimensions (or both) in 24bpp mode

Description

Contributor guide

Assessment

Get new issues in your inbox