Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RoboCop versus The Terminator screen flickers strobes during game play #439

Closed
ghost opened this issue Oct 4, 2018 · 11 comments
Closed

Comments

@ghost
Copy link

ghost commented Oct 4, 2018

RoboCop versus The Terminator screen flickers strobes during game play

@ghost
Copy link
Author

ghost commented Oct 4, 2018

on older versions this game is fine. i have a feeling its irq timing

@lordpeluca
Copy link

In the official version 1.56.2 that is in releases there are no blinking problems ...

Maybe fixing the blink problem of daffy duck has caused the same in the robocop vs terminator?

@ghost
Copy link

ghost commented Oct 5, 2018

broke here
e3216ec

@ghost
Copy link

ghost commented Oct 5, 2018

Here's what I see:

--- IRQ Timer HC:36 VC:31 set 357378 cycles HTimer:0 Pos:0000->0010  VTimer:1 Pos:031->031
*** IRQ


$80:9683 A9 20       LDA #$20                A:C242 X:0000 Y:00FF D:0000 DB:80 S:01F0 P:eNvMXdIzc HC:0486 VC:031 FC:37   V .n.    HT:10 VT:31 C:357378
$80:9685 8D 09 42    STA $4209  [$80:4209]   A:C220 X:0000 Y:00FF D:0000 DB:80 S:01F0 P:envMXdIzc HC:0498 VC:031 FC:37   V .n.    HT:10 VT:31 C:357378
--- IRQ Timer HC:516 VC:31 set 1374 cycles HTimer:0 Pos:0000->0010  VTimer:1 Pos:032->032


$80:974A A9 81 00    LDA #$0081              A:96B5 X:0000 Y:0000 D:0000 DB:80 S:01F0 P:eNVmxdIzc HC:0040 VC:032 FC:37   V .n.  L HT:10 VT:32 C:357378
$80:974D 8D 00 42    STA $4200  [$80:4200]   A:0081 X:0000 Y:0000 D:0000 DB:80 S:01F0 P:enVmxdIzc HC:0058 VC:032 FC:37   V .n.  L HT:10 VT:32 C:357378
--- IRQ Timer HC:76 VC:32 set 268435455 cycles HTimer:0 Pos:0000->0010  VTimer:0 Pos:032->032
--- IRQ Timer Enable HTimer:0 Pos:0010  VTimer:0 Pos:032


$80:9750 A9 A1 00    LDA #$00A1              A:0081 X:0000 Y:0000 D:0000 DB:80 S:01F0 P:enVmxdIzc HC:0088 VC:032 FC:37     .n.    HT:10 VT:32 C:268435455
$80:9753 8D 00 42    STA $4200  [$80:4200]   A:00A1 X:0000 Y:0000 D:0000 DB:80 S:01F0 P:enVmxdIzc HC:0106 VC:032 FC:37     .n.    HT:10 VT:32 C:268435455
--- IRQ Timer HC:124 VC:32 set 357378 cycles HTimer:0 Pos:0000->0010  VTimer:1 Pos:032->032
--- IRQ Timer Enable HTimer:0 Pos:0010  VTimer:1 Pos:032
$80:9756 80 11       BRA $11    [$9769]      A:00A1 X:0000 Y:0000 D:0000 DB:80 S:01F0 P:enVmxdIzc HC:0136 VC:032 FC:37   V .n.    HT:10 VT:32 C:357378


========  missed irq @ VC:032 FC:37 ===============


--- IRQ Timer HC:24 VC:32 set 357374 cycles HTimer:0 Pos:0000->0010  VTimer:1 Pos:032->032
*** IRQ
$00:964B 5C 4F 96 80 JMP $80964F[$80:964F]   A:0004 X:FFFE Y:0002 D:0000 DB:80 S:01FB P:envmxdIzC HC:0084 VC:032 FC:38   V .n.  L HT:10 VT:32 C:357374

Haven't compared against bsnes.

@bearoso
Copy link
Collaborator

bearoso commented Oct 5, 2018

We need to allow enabling IRQ to trigger the IRQ instantly as long as VTIMER was rewritten.

I'll have to see if OV2's alternate fix for this issue doesn't have the same problem.

@OV2
Copy link
Collaborator

OV2 commented Oct 5, 2018

For RoboCop it seems to be enought to change it back to S9xUpdateIRQPositions(true); in 4200. Psycho Dream still works because of the check for a change in the byte value.

@bearoso
Copy link
Collaborator

bearoso commented Oct 5, 2018

That's simple enough. Fixed in e543702.

@ghost
Copy link
Author

ghost commented Oct 9, 2018

Thanks again guys!!

@ghost ghost closed this as completed Oct 9, 2018
@niuus
Copy link

niuus commented Jan 10, 2019

Hey guys!. How would i go implementing this fix to a 1.52 codebase? Is it possible?
https://github.com/niuus/Snes9xRX

@bearoso
Copy link
Collaborator

bearoso commented Jan 10, 2019

That could be difficult because it would probably break other games. You'd end up having to supplant the entire IRQ code.

@niuus
Copy link

niuus commented Jan 10, 2019

Oh, that's a shame. Thanks for the answer, bearoso.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants