pcsx2 icon indicating copy to clipboard operation
pcsx2 copied to clipboard

[BUG]: Dynasty Warriors 2 / Shin Sangoku Musou - Garbage on post character selection screen with software rendering.

Open HeroponRikiBestest opened this issue 4 years ago • 9 comments

Describe the Bug

After choosing a character in Dynasty Warriors 2 / Shin Sangoku Musou, if you are using software rendering, the following screen is garbage. It displays properly with hardware/OGL rendering.

Reproduction Steps

With software rendering on, get past the opening fmv (skip it with start, watch it all, doesn't matter) and choose any more. After you choose a character, the battle intro screen in question will play.

Expected Behavior

I expected the post-character-select screen to be displayed properly on software rendering.

PCSX2 Revision

PCSX2 1.7.0-20210817085737 - compiled on Aug 17 2021

Operating System

Linux (64bit) - Specify Distro Below

If Linux - Specify Distro

Linux Mint 20

CPU

AMD Ryzen 7 PRO 4750U with Radeon Graphics

GPU

Uses an iGPU, see cpu

GS Settings

No response

Emulation Settings

No response

GS Window Screenshots

Software rendering: image Hardware (OGL) rendering: image

Logs & Dumps

While I was unable to get log dumps here, I did get log dumps when I tested the game in Dobiestation. I will post them here in case they are useful.

0x00005555555b6484 in GraphicsInterface::request_PATH(int, bool) () (gdb) bt #0 0x00005555555b6484 in GraphicsInterface::request_PATH(int, bool) () #1 0x00005555555eaedc in VectorInterface::process_data_word(unsigned int) () #2 0x00005555555ec266 in VectorInterface::update(int) () #3 0x00005555555744bf in Emulator::run() () #4 0x00005555555d2ac3 in EmuThread::run() () #5 0x00007ffff6e8c9d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007ffff6db4609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #7 0x00007ffff698e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Additionally, if this is also useful, Refraction mentioned that they suspected "Vif0 is trying to access the gif".

I'm sorry I couldn't provide logs from PCSX2; even after turning on everything nothing showed up. If there is anything additional I can do to get logs, please let me know.

HeroponRikiBestest avatar Aug 17 '21 18:08 HeroponRikiBestest

Forgot to add gsdumps initially. dumps.zip

HeroponRikiBestest avatar Jan 12 '22 09:01 HeroponRikiBestest

heres an updated GS dump , issue 4673.zip

SW mode is mostly the same image

HW mode is getting like SW mode image

Mrlinkwii avatar Apr 06 '23 10:04 Mrlinkwii

Should the GS:Hardware tag be added too, then?

HeroponRikiBestest avatar Apr 07 '23 08:04 HeroponRikiBestest

@HeroponRikiBestest the game is very odd , if you boot in HW and never change renderer its fine , but if you boot in hw , change to software and back before the screen its glitched in hw , from what i can see

Mrlinkwii avatar Apr 07 '23 09:04 Mrlinkwii

Ah, ok, so its possible nothing has actually changed?

HeroponRikiBestest avatar Apr 07 '23 11:04 HeroponRikiBestest

All I can say the game is doing odd stuff :S

Mrlinkwii avatar Apr 07 '23 11:04 Mrlinkwii

This happens in hardware too now. It's caused by a blur effect this screen has. I made this a while ago to disable the blur effect, which looks nicer than the bug: (For ntsc-u version) patch=1,EE,002C8668,word,00000000

It just nops a function that I believe is responsible for the effect.

Maybe devs can investigate the bug easier if they know where the blur function is located in code now.

michaelx333 avatar Feb 06 '24 20:02 michaelx333

This happens in hardware too now. It's caused by a blur effect this screen has. I made this a while ago to disable the blur effect, which looks nicer than the bug: (For ntsc-u version) patch=1,EE,002C8668,word,00000000

It just nops a function that I believe is responsible for the effect.

Maybe devs can investigate the bug easier if they know where the blur function is located in code now.

Can you test if this is any better?

patch=1,EE,00201984,word,00000000

ghost avatar Feb 06 '24 21:02 ghost

This happens in hardware too now. It's caused by a blur effect this screen has. I made this a while ago to disable the blur effect, which looks nicer than the bug: (For ntsc-u version) patch=1,EE,002C8668,word,00000000 It just nops a function that I believe is responsible for the effect. Maybe devs can investigate the bug easier if they know where the blur function is located in code now.

Can you test if this is any better?

patch=1,EE,00201984,word,00000000

Seems pretty much the same as mine.

michaelx333 avatar Feb 06 '24 21:02 michaelx333