rebtd7/FF13Fix

1.5.1 breaks hunts texts

danilo-bc opened this issue · 9 comments

I'm playing on linux on a gtx 1650 and the latest DXVK and NVidia stable drivers. To use 1.5.1 I added d3d9 to Wine DLL overrides and I confirmed the game is using the fix by changing the game's framerate (and the game running higher than 60fps)

Release 1.4.6 works fine, with OCCASIONALLY breaking text boxes, but restarting the game fixes it (it can be identified by not having the text box describing the previous actions of the team during a Load Game screen, so it's easily identifiable).

On 1.5.1, however, hunt texts always show up cut out like shown. From 1.4.6 to 1.5.1 the main change for me is the menu performance, it's much better in the current version.

Ignore the black rectangle on the left, that's from my poor screenshotting skills.
huntbug

What resolution you use? This can be related to one pixel offset in viewport fix i have added.

I'm using 1920x1080, 60 fps ingame framerate, 120fps monitor.

Disabling SetScissorRect patch fixes some of those so this is definitely something with scissor fix, investigating.

Fixed in e15529e

@rebtd7 can you create new release/hotfix?

Release 1.5.2 includes the commit above, let us know if the issue is fixed

There are still plenty of broken text boxes.

This is the minimap on the mission list
stillbug1

This is the new hunt text
stillbug2

This is the text on the loading screen
stillbug3

All these are not apparent on 1.4.6

I just restarted the game and all the screenshots I've just shown are fixed. I don't understand this type of "time-variance". Maybe switching from 1.4.6 to 1.5.x leaves broken pre-compiled shaders which affect these parts?
EDIT: this issue may be singular for my use case where I'm testing between these two versions AND I'm on linux playing with Proton+SteamPlay+D9/DXVK. Again, I'm positive I'm using the provided d3d9.dll because the framerates are way better and configurations apply accordingly.

So this is fixed by 1.5.2? Please close issue if it's fixed.

I didn't want to close at first because it required two game runs and may be unstable, but it all seems fixed! It's a pretty minor inconvenience.

Thanks a lot!