Updated the messenger (markdown)

GabeEddyT 2019-06-09 05:13:29 -04:00
parent 36c3e6ce69
commit 882f33fa40

@ -1,8 +1,59 @@
# On canary build #2342
Being 2D, this game runs relatively well, maintaining at least 30-40 FPS in most scenarios; Dipping in performance on level transitions and when many enemies are on the screen at once.
As for graphical glitches: The initial (tutorial) area is monochrome (on a GTX 1070, white and black; on a Radeon R9 380, white and yellow), but areas afterward are colored fine.
# Performance
Being 2D, this game runs relatively well, maintaining at least 30-40 FPS in most scenarios; Dipping in performance on level transitions and when many enemies or moving objects are on the screen at once.
# Graphics
The initial (tutorial) area is monochrome (on a GTX 1070, white and black; on a Radeon R9 380, white and yellow), but areas afterward are colored (relatively) fine.
<details>
<summary>Ninja Village screenshots</summary>
![black and white tutorial](https://i.imgur.com/teDtDZm.png)
# On canary builds #23432359+
The game can spontaneously hang on a black screen (like a loading screen, except it happens abruptly in the middle of play; not when loading is actually meant to occur), rendering it unplayable. This will happen regardless of `asynchronous GPU emulation`. The only difference is, during the hangup, `async` will cause the game to speed up past the set limit; whereas leaving this setting unchecked keeps the game locked at 100% speed.
>Ninja Village on a GTX 1070
![yellow and white tutorial](https://i.imgur.com/wDhStiN.png)
>Ninja Village on an R9 380
</details>
## Contrast issues
At some points it's more noticeable than others, but *The Messenger* appears to have contrast issues, with some shades of colors only appearing as black. Noticeable on the Messenger himself in his 8bit form.
<details>
<summary>Images of the 5th boss</summary>
![suses](https://i.imgur.com/RDugE5k.png)
>Suses has noticeable black spots all over his body; Colos has a black eye.
![correct-suses](https://vignette.wikia.nocookie.net/the-messenger-2018/images/3/35/Colos_%26_Suses.png)
>How Suses and Colos are supposed to look.
</details>
# Physics Quirks
There is unintentional behavior causing the player to "slip" off of walls and remain stationary on horizontally moving platforms. Especially detrimental at [a specific point](https://youtu.be/3p-hKJNJ64s?t=360) in the game where the player is supposed to ride a platform with just enough room to duck under a long row of spikes: Halfway across, the player will be stuck in place while the platform continues to move from under their feet. Given that you're meant to stay crouched to not touch the spikes, the player is unable to move to readjust themselves and therefore falls to their death. The only way to clear this gap is to purposely damage oneself on the spikes before the halfway point, using the resulting invincibility frames to continue riding the platform to the other side.
# Softlock on canary builds #23432372+
The game can spontaneously hang on a black screen (like a loading screen, except it happens abruptly in the middle of play; not when loading is actually meant to occur), rendering it unplayable. This will happen regardless of `asynchronous GPU emulation`. The only difference is, during the hangup, `async` will cause the game to speed up past the set limit; whereas leaving this setting unchecked keeps the game locked at 100% speed.
## Workaround
If you're [building the emulator](https://github.com/yuzu-emu/yuzu#building) from the [Yuzu canary source](https://github.com/yuzu-emu/yuzu-canary), you can merge in changes from [FernandoS27's softlocks branch](https://github.com/FernandoS27/yuzu/tree/softlocks).
```bash
# Assuming you have the canary repo cloned, add a new remote for the fork
git remote add a_fork https://github.com/FernandoS27/yuzu.git
git fetch --all
# Then merge the changes in
git merge a_fork/softlocks
```
Otherwise, you can run the game on [canary 2342](https://github.com/yuzu-emu/yuzu-canary/releases/tag/canary-2342).
# Potential softlock after the first part of the game
<details><summary>After beating the eighth boss... (spoilers)</summary>
After defeating Barmathazel, and watching a cinematic, the player is returned to the shop. After a few interactions with the shopkeeper, the player is asked to change back into their normal clothes...
</details>
After which a bug occurs whereby the player will become invisible—still able to move, jump, and use abilities—but unable to interact with anything or progress. Making matters worse, the game doesn't save at any point leading up to this, so returning to the main menu in hopes of fixing this bug will make you face the boss again.
## Workaround
Minimize and maximize Yuzu, and the player becomes visible, allowing them to continue.