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

Final Tear 3: Endless intro loop #1316

Ghabry opened this issue Dec 7, 2017 · 3 comments


Copy link

commented Dec 7, 2017

Name of the game: Final Tear 3

Start a new game and Choose "Skip intro". This will still show the (far too long) credits which shows the authors. Simply fast forward through it until you reach a yellow epilepsy-like (at least at 10x :D) thunderstorm scene. This one will loop infinitely after the next name is displayed.

Quote from 20kdc in the forum

Map 0719, “You will never disrupt < Intro pounder” is a night scene, just after the first bit of voice acting (which appears to be involuntary for the intro???). It’s driven by E2/Event talk, a parallel event.
After it’s done, it goes to Map0954, “MAP0954”, driven by E1/EV0001 (also a parallel event), which shows the “STEVIE V.D LAAR / PRESENTS” scene.
Map 0954 then goes back to Map 0719 for a sec, shows map, and then event execution stops there, because Map 0719’s event starts up again, and on EasyRPG Player it interrupts map 0954’s event.
I assume that on RPG_RT, it does not, and the map transition goes quickly enough that the intro lines don’t play, or alternatively, Map 0719 is the event that gets interrupted.


This comment has been minimized.

Copy link
Member Author

commented Sep 22, 2018

FYI: The fix for log.[in] does not fix this.


This comment has been minimized.

Copy link

commented Dec 14, 2018

This game uses DynRPG patches and also uses some modified headers while trying to test with plain RPG_RT (it returns invalid signature), so these headers should be restored and play with unpatched RPG_RT.exe to make sure DynRPG patches are not the problem.


This comment has been minimized.

Copy link

commented Mar 13, 2019

This is fixed in #1694

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.