Experienced Forum User, Published Author, Former player
Joined: 9/4/2012
Posts: 9
To call the end of the game, the game logic certainly needs to use initial function (and not just for that what I see). The feature you can found in the rom address: 0x91AC (but exist exceptions?). For this:
https://feos-tas.googlecode.com/svn/trunk/DJ-stuff/Movies/bt_improve_ends.fm3
and for MESHUGGAH video, function launched "game end" in the level 3 instantly. Not exactly is known cause of this sudden call.
Experienced Forum User, Published Author, Former player
Joined: 9/4/2012
Posts: 9
Radiant wrote:
TASVideoAgent wrote:
Yes?
Yes.
I carefuly analyze step by step the game code.
As all this information will be clearly (for all), I describe them "clearly"
(I'll try to do it so that everyone can understand what is really happening here).
Experienced Forum User, Published Author, Former player
Joined: 9/4/2012
Posts: 9
MESHUGGAH wrote:
So I have two questions.
1. Did you optimize both the section after spawning the correct object and destroying it and also optimize the length of cutscenes?
2. Did you tried using the reset button? I tested it many times and everytime I had the conclusion that it's not properly emulated (both fceux and bizhawk), not to mention the 513 bug which also a problem.
1) Not fully understand your question, but when it comes to optimizing, I only did it in order to not wait until the object "end of level" (ID = 0x7f) disappears through out of time range (Timer = 0xff equal max range).
2) I tested. I don't know what bugs you mean about?, but I think that I know emulator, which complies with the seeming "console reset" (I haven't checked it).
Here you have an exception if you're interested? see this:
https://feos-tas.googlecode.com/svn/trunk/DJ-stuff/Movies/bt_u-lvl3_3489.fm3
Experienced Forum User, Published Author, Former player
Joined: 9/4/2012
Posts: 9
Please do not forget the main thread!
We are doing everything, to every person on earth could understand what happened here (step by step, as you need).
Most important in this movie "is not" a assignment to the category, is only what really happened in the game code between the 3493 and 3494 frame.
If we have to explain the assembler code, we'll do it.
At the moment, we know that:
* "Created player" in 12th slot, cannot be manipulated (modified) too much (in the sense that "it" cannot be killed, for example - is best, when "it" is not touched by something or for glitch). "The parameters must be stable".
* In addition to what Feos wrote, we know that the "Introduction" (is what's going on before you press the start button), has an impact on the "Game End" event (It can reduce the value and the game starts normally).
Now, we are working on a faster end of the game (not just using the level 3 glitch).
Experienced Forum User, Published Author, Former player
Joined: 9/4/2012
Posts: 9
To summarize, we know for sure that:
* Object with ID equal to 1, 2 or -1, -2 (player 1 or 2) is the cause of the end of the game.
* We know also that the bug is performed only at level 3.
* The object must be thoroughly prepared in the 12th slot.
* The environment is of little importance, and so the game is over (in theory, in practice you should make a little help for the game), even in the first level frames.
We don't know whether to blame it the level 3, or it isn't the 12th slot yet.