Project

General

Profile

Actions

Emulator Issues #6745

closed

Fire Emblem: Radiant Dawn doesn't respond to input

Added by xemnasdp about 11 years ago.

Status:
Fixed
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? Fire Emblem: Radiant Dawn

Game ID? RFEE01

What went wrong? After loading, the game doesn't respond to input.

What did you expect to happen instead? After loading, the game responds to input.

What steps will reproduce the problem?

  1. Load the game and press A button.

Which versions of Dolphin did you test on? 4.0-263

Which version of Dolphin used to work? 4.0-127

What are your PC specifications (example: Operating System, CPU and GPU)? Windows 7, Core i5 2500K, AMD Radeon HD 7870

64 or 32 bit Operating System? 32-bit

64 or 32 bit Dolphin? 32-bit

Actions #1

Updated by MayImilae about 11 years ago

Very little information. Are you using the GCPad, Emulated Wiimote, or Real Wiimote? What revision EXACTLY broke it?

Actions #2

Updated by xemnasdp about 11 years ago

I'm using GCPad. It has been broken since 4.0-143. The x86 builds between 4.0-143 and 4.0-127 are broken (separate issue).

Actions #3

Updated by MayImilae about 11 years ago

EXACT. You are asking other people to fix stuff for you, the least you can download some builds from the site and try them all. You only have a narrow range so it wouldn't be that hard. I've done it a hundred times myself.

Hint: it's likely 4.0-238, it's the only obvious GCPad change in that range. Test it and the builds around it, and keep trying builds until you can find "X-XX3 works and X-XX4 is broken".

Actions #4

Updated by xemnasdp about 11 years ago

4.0-143 doesn't work and 4.0-127 does work. I can't try the x86 builds between 4.0-143 and 4.0-127 because they are broken (something about XMM0 processing which is a separate issue).

Actions #5

Updated by parlane about 11 years ago

Why are you running a 32bit operating system ?

Actions #6

Updated by MayImilae about 11 years ago

4.0-137 is available in 32bit, and so is 4.0-141 and 4.0-142. Try them, that should at least narrow it down some more.

https://dolphin-emu.org/download/list/master/5/

Actions #7

Updated by xemnasdp about 11 years ago

parlane, when I built my PC, I was in a hurry and my previous PC had only 1 GB of RAM. I didn't think of the difference between 32-bit and 64-bit back then.

I tried 4.0-137, 4.0-141, and 4.0-142 and I got a black screen so I couldn't test whether it was working. 4.0-143 corrected the XMM0 processing and it didn't respond to input.

Actions #8

Updated by MayImilae about 11 years ago

Calling the troops. Let's see what they think.

4.0-134 = rf6c0fb7bbe6f

Actions #9

Updated by thetoerk about 11 years ago

I have same problem. I know that the problem already exists in Dolphin 3.5

Actions #10

Updated by JMC4789 about 11 years ago

When all else fails, Blame Billiard.

Actions #11

Updated by kostamarino about 11 years ago

No issue here with 64 bit dolphin. Seems to be a 32 bit dolphin issue.

Actions #12

Updated by Sonicadvance1 about 11 years ago

So for some reason fastmem is affecting 32bit even though it isn't supposed to?

Actions #13

Updated by parlane almost 11 years ago

  • Status changed from New to New
Actions #14

Updated by JMC4789 about 10 years ago

  • Status changed from New to Fixed

This was actually fixed (the bug in fastmem writes), but we don't support 32bit any more, so, yay.

Actions

Also available in: Atom PDF