Project

General

Profile

Actions

Emulator Issues #12648

closed

Mario Party 7 End of Turn Frame Buffer Issue with Cheat code

Added by savagejacek20 over 2 years ago. Updated over 1 year ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

[Mario Party 7]

Game ID? (right click the game in the game list, Properties, Info tab)

[GP7E01]

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

[bd367c67fca5d93e581a43d1f61f4514]

What's the problem? Describe what went wrong.

[When playing both by myself and with people via netplay, whenever a character's turn ends, the game lags. I am using top end hardware with OpenGL on an RTX 3080 and with friends with similarly powerful builds. I first thought it was my friend, then I tried it by myself and discovered it was lagging on my system too! His system seems to not be affected, unlike mine. I have entirely purged shadercaches in "User > Cache > Shader" and to no avail. Changed from OGL to Vulkan to no avail. Toggled Ubershaders to no avail. I believe this a regression of some sort. I tested Mario Party 6 and it runs fine. Mario Party 7 didnt have this bug last month so its definitely something pertaining to an update.]

What steps will reproduce the problem?

[Start a game of Mario Party 7 in Neon Heights (could be all maps as well, only tested Neon). After Bowser places his orbs, the game will lag WHENEVER a character's turn begins and/or ends. This was tested using OpenGL.]

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

[5.0-15007]

Is the issue present in the latest stable version?

[Yes, 5.0-15007]

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

[5.0-15007]

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

What are your PC specifications? (CPU, GPU, Operating System, more)

[Ryzen 9 3900X, 32GB RAM, 1TB SSD, RTX 3080, Windows 10 Pro Build 2004]

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[[[[https://www.twitch.tv/videos/1132809899]]]]

Actions #1

Updated by savagejacek20 over 2 years ago

Found out it was due to a Gecko Code:

04198524 48000018

Using this code hides the "CPU" logo under everyone's name, but seems to introduce this weird bug. It however, was not a bug until a recent update. Idk how important this info is but hope it helps!

Actions #2

Updated by savagejacek20 over 2 years ago

By dumping and erasing the "CPU" texture, this makes the bug avoidable, but seems hacky

Actions #3

Updated by JMC4789 over 2 years ago

  • Subject changed from Mario Party 7 End of Turn Frame Buffer regression on NVIDIA? to Mario Party 7 End of Turn Frame Buffer Issue with Cheat code
  • Status changed from New to Questionable

Please bisect to an exact Dolphin build that causes the issue.

Actions #4

Updated by savagejacek20 over 2 years ago

Testing on older builds and this comes up:
"Invalid read from 0x00000c9f, PC = 0x80198544"
as well as:
"Invalid read from 0xd723debd, PC = 0x80198544"
"Invalid read from 0xd723dfcd, PC = 0x80198544"
"Invalid read from 0xd723e0dd, PC = 0x80198544"
"Invalid read from 0xd723e1ed, PC = 0x80198544"
"Invalid read from 0xd723e2fd, PC = 0x80198544"
and way too many more to count. They all have "0xd72#####" in them. Literally hundreds if not thousands of these errors are thrown.

Tested as far back as 14344. It might just be my bad memory and it just being a bad code. My apologies for the waste of time.

Actions #5

Updated by JMC4789 over 1 year ago

  • Status changed from Questionable to Invalid

No problem.

Actions

Also available in: Atom PDF