Open GoogleCodeExporter opened 9 years ago
Can confirm this bug still present in version 2.0. Often, after triggering the
scene change on a particular set of vines, going back to those vines again will
not trigger the scene change. (Although not necessarily. The vines in level 2,
Angry Aztec, are particularily bad for constantly triggering scene
changes/resets)
As to the severity of the bug, many sections of the game require vines to
complete plot elements, thus rendering the game uncompletable for the time
being.
Original comment by matthewd...@gmail.com
on 13 Jan 2014 at 2:59
Please try this: use a current build of mupen64plus-core and set CountPerOp
from 0 to 1. You may need to change this back when you play another game
Original comment by s...@narfation.org
on 22 Jan 2014 at 9:08
Yeah I've noticed that on the first introduction of CounterPerOp, but i could
only test for a few mins and while it didn't happen, I was reluctant to rule it
out completely. Will do some extensive testing tonight.
Original comment by davidro...@gmail.com
on 23 Jan 2014 at 9:11
Done some testing now, pretty safe to say that setting counterop to 1 fixes
this issue (it also seems to fix the spiking textures - so double yay) i've
jumped around 30 times on and off those without it happening once, on counterop
= 0 the fourth try was enough
Original comment by davidro...@gmail.com
on 23 Jan 2014 at 5:22
Ok, the current git (hg not used anymore, please switch to
https://github.com/mupen64plus/mupen64plus-core ) repo now contains the
CountPerOp=1 for DK64 (even when you set it to CountPerOp=0 in your config).
This autoconfig per ROM feature can be disabled again by setting CountPerOp=2
in your config file.
Original comment by s...@narfation.org
on 23 Jan 2014 at 5:35
Original issue reported on code.google.com by
davidro...@gmail.com
on 5 Sep 2013 at 10:18Attachments: