Project

General

Profile

Actions

Emulator Issues #7689

closed

Cannot Choose Computer Skill Level in Multiple Exhibition Matches in Mario Power Tennis

Added by PEmu about 10 years ago.

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

0%

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

Description

Game Name?

Mario Power Tennis

Game ID?

GOME01

What's the problem? Describe what went wrong in few words.

When playing multiple exhibition matches in Mario Power Tennis you cannot choose the computer character skill level after the first match.

What did you expect to happen instead?

I expected to be able to choose the computer player skill level in every match.

What steps will reproduce the problem?

  1. Launch Mario Power Tennis.
  2. Choose Exhibition.
  3. Pick character and choose Singles.
  4. Pick the computer character and choose skill level.
  5. Pick the first choise for court (Peach Dome) and select Standard play mode.
  6. Start match.
  7. Pause game and change the camera to dynamic if you want to be able to see properly (the default camera is currently broken in Dolphin).
  8. Finish the match.
  9. Select Back to Main Menu.
  10. Repeat these steps starting at #2.
  11. When you get to choosing the computer character skill level it will now automatically select Intermediate without accepting any user input.

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?

4.0.2, 4.0-3367, 4.0-3376, 4.0-3393.

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

Yes. 4.0.2.

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)

Windows 8.1 64 bit
Intel Core i7-2600K
GeForce GTX 580

Actions #1

Updated by JMC4789 about 10 years ago

  • Status changed from New to Accepted

Accepted. Can you find when this behavior started?

Actions #2

Updated by PEmu about 10 years ago

Yeah I will try to hunt down the revision that broke it.

Actions #3

Updated by JMC4789 about 10 years ago

I have 2826 as wokring and 3239 as broken, narrowing down further.

Actions #4

Updated by PEmu about 10 years ago

Works in 3149. Still narrowing it down.

Actions #5

Updated by JMC4789 about 10 years ago

Working 3162, working 3194

Actions #6

Updated by PEmu about 10 years ago

Works in 3039.

Actions #7

Updated by JMC4789 about 10 years ago

3214 works. I'm thinking it's Carry Optimizations! that broke it.

Actions #8

Updated by JMC4789 about 10 years ago

JIT Carry Optimizations was indeed the culprit. Fiora broke it.

How it makes the difficulty auto-select after one try, I really don't know.

4.0-3230 is the culprit. You're kinda going the wrong way on your bisect.

Actions #9

Updated by PEmu about 10 years ago

Yeah I just noticed that, haha, was getting my info mixed up. I guess I don't need to keep looking now.

Actions #10

Updated by JMC4789 about 10 years ago

Yup, we got it anyway, I'll find the subcommmit that broke it.

Actions #11

Updated by PEmu about 10 years ago

Should this be marked as Regression as it didn't happen in 4.0.2?

Actions #13

Updated by JMC4789 about 10 years ago

  • Status changed from Accepted to Fix pending
  • Regression set to Yes
  • Milestone set to Current

it should be but it was fixed quickly so I was lazy.

Actions #14

Updated by JMC4789 about 10 years ago

  • Status changed from Fix pending to Fixed
Actions

Also available in: Atom PDF