Homebrew Homebrew game Chrono Trigger - Switch port

[josete2k]

Then this issue shouldnt be new. I described the levels you need to achieve general stability in prior posts.

fixed_timestep = 0 fixes it

I'll try with OC

Post automatically merged: Friday at 10:21 PM

Tested: 1581 MHz cpu and 691 MHz GPU in handheld 720p

It works much better, yes

 

[ppkantorski]

All my work is on GitHub. I'll draft a PR soon. For now users can test this version out. Lots of improvements and changes from the last version I shared. See the config.ini for options. You can also checkout the README here for details.

For the field / map zoom, it is only recommended right now to use values of 2.0 (default) and 1.75. 1.5x zoom still needs more work to get all the alignments corrected, as well as 1x zoom. Other zoom values will create weird visual pixel glitches, like the default behavior.

The remove mobile ui patch has also been enhanced to remove touch buttons, back / exit buttons in the equipment and settings menu, etc. And I have also included a patch (on by default) to align text and icons a tad cleaner in the equipment menu as well.

Users can also map buttons. The right joystick is currently set in the config.ini to mirror the left joystick. Users can currently program zl, zr, plus, and minus to be any other recognized game button (A, B, X, Y, L, R).

I've also relinked the text ctp patch generator here for easy access, but nothing in its code has changed. This should be the final release version imo for what i wanted this version to include. I can still try to get 1.5x zoom working properly at some point, but it will take me more time.

 

[josete2k]

Thanks!!


The OC is still needed for the fixed_timestep, I assume...

I don't know if it's mentioned in the readme.

 

[ppkantorski]

Thanks!!


The OC is still needed for the fixed_timestep, I assume...

I don't know if it's mentioned in the readme.

OC is needed even for fixed timestep off, I'll make note of it. Ideally you should keep it on if you can imo. From my personal testing performance is about the same with it on and off. If you delete the config.ini it will regenerate a new one. Some of the settings are still going to be hidden / suppressed from being written.

 

[josete2k]

OC is needed even for fixed timestep off, I'll make note of it. Ideally you should keep it on if you can imo. From my personal testing performance is about the same with it on and off. If you delete the config.ini it will regenerate a new one. Some of the settings are still going to be hidden / suppressed from being written.

OK, i'll test again...

The run speed decreases a lot without OC... I have an oled and all ports are working "fine" at stock clocks

 

[ppkantorski]

OK, i'll test again...

The run speed decreases a lot without OC... I have an oled and all ports are working "fine" at stock clocks

if you want to compare it to other ports, use v1.0.1 as your baseline. Then compare this version to v1.0.1.

fixed_timestep is ensuring right now that it runs synced to the expected frame rates, which may be why you noticed it being faster with it off as the frame rate dips. Overall i say people should experiment with it on and off to their preferences. If oc is high enough, it does hold some benefits to being on. I'll run some more tests.