Fix timing regression affecting ES_LAUNCH.
Scheduling an event for zero cycles in the future actually means zero cycles with new timing changes, but the code for IPC ACKs was depending on it meaning "soon". Fixes #9511. I'm not at all confident this is actually right... but it seems to work.
This commit is contained in:
parent
b7795044bb
commit
36f01e141d
|
@ -223,7 +223,7 @@ void GenerateAck(u32 _Address)
|
|||
ctrl.Y2 = 1;
|
||||
INFO_LOG(WII_IPC, "GenerateAck: %08x | %08x [R:%i A:%i E:%i]",
|
||||
ppc_msg,_Address, ctrl.Y1, ctrl.Y2, ctrl.X1);
|
||||
CoreTiming::ScheduleEvent(0, updateInterrupts, 0);
|
||||
CoreTiming::ScheduleEvent(1000, updateInterrupts, 0);
|
||||
}
|
||||
|
||||
void GenerateReply(u32 _Address)
|
||||
|
|
Loading…
Reference in New Issue