Results 169 comments of illusiony

@cirquit might be interested in this new solution, but I still am having trouble on how to calculate frame rate from it. Also found that gray scale is quite limiting...

It was discussed in https://github.com/cirquit/trdrop/issues/70#issuecomment-756535297

Not sure where to comment, they used float for resolution in comics, try that.

editing front buffer broke it ![image](https://user-images.githubusercontent.com/37698908/172076060-1883d3aa-38cd-4e91-b617-cc947b5a5c02.png)

~~to be more specific, height value (hightlighted in green)~~ nope, w + h is affected ![image](https://user-images.githubusercontent.com/37698908/172076505-93db85b2-36c1-4793-814a-09ce9807d3e4.png)

doubt I will get a response, if anyone has working debugger, set memory breakpoint at `0x81669310`, `0x81669314`, and `0x81669318` during startup for me.

Until we get working homebrew software debugger, it's not possible for now. Simplified code: ```yaml # gravity rush 1.00 # front # UI + front = this breaks comics+ui stuff...

960x544 UI only: ![image](https://user-images.githubusercontent.com/37698908/173716739-01e70262-dc59-495a-9b1c-9cde33af37e6.png) ![image](https://user-images.githubusercontent.com/37698908/173716753-12db1ccf-eaaf-484a-b13b-15774ca53bbe.png) 960x544 internal rendering + 720x408 UI (doesn't break UI but outputs at only 720x408 with downsampled 544p frame): ![image](https://user-images.githubusercontent.com/37698908/173716929-352f3f8b-b385-4c55-b8a5-504501fa6a35.png)

@Ivanim13 That is what the third image is.

@delon5 I don't know much syntax about it. Besides its not very useful as the patch is still broken and nothing more than a novelty