nipkownix / re4_tweaks

Fixes and tweaks for the "UHD" port of Resident Evil 4
zlib License
346 stars 32 forks source link

Incomplete screen display #408

Open leon861107 opened 1 year ago

leon861107 commented 1 year ago

Validation

Describe your issue here (drag+drop ZIP to attach it)

hello!

After upgrading 1.8

Incomplete screen display

nipkownix commented 1 year ago

Not sure what you mean, sorry. Could you show us a screenshot?

Alvarden15 commented 1 year ago

They are probably referring to this issue: with the latest version installed, if the game is on fullscreen mode and you set the game's resolution to a lower value than your screen display, the game will be displayed as if it was on Windowed (this didn't happened with older versions). I'm sending you a screenshot as proof (i edited some parts for privacy): re_tweaks_latest_version_bug

Note: I also have RE4HD V1.1 installed.

leon861107 commented 1 year ago

20221229202708_1

leon861107 commented 1 year ago

不知道你的意思,对不起。你能给我们看一张截图吗? 20221229202708_1

Alvarden15 commented 1 year ago

Ah, ok. It's a different type of problem.

nipkownix commented 1 year ago

@leon861107 What you're showing is a side effect of using Remove16by10BlackBars. You can disable that option in dinput8.ini if you wish.

@Alvarden15 Pretty strange issue in your image. Haven't been able to reproduce it. Does turning UseVulkanRenderer off gets rid of the issue for you? Might be some quirk with Vulkan on your computer/setup.

Alvarden15 commented 1 year ago

@nipkownix No, unfortunately, the issue still persist. VtSKcED2oY Just in case you need my specs, there they are: GPU: GTX 1650 4GB CPU: Intel Core i5-10400F RAM: 16 GB The game is stored on HDD.

I'll try to downgrade and see what happens.

Alvarden15 commented 1 year ago

@nipkownix Ok, a quick update. I managed to fix the issue: after downgrading and then upgrading again, the game was shown on fullscreen again (it turned out i skipped some files from another mod i was using and caused the issue, sorry).

But now there is another problem, the font of some words are too big suddenly (this only happens on the menu, thankfully, but still). Not sure if anyone else had it too: 20221230115120_1

leon861107 commented 1 year ago

@leon861107您显示的是使用 .如果您愿意,可以在 中禁用该选项。Remove16by10BlackBars``dinput8.ini

@Alvarden15你的图像中存在非常奇怪的问题。无法重现它。关闭会为您解决问题吗?可能是您的计算机/设置上的 Vulkan 的一些怪癖。UseVulkanRenderer

OK, the problem has been solved. Thank you very much

InsideCat02 commented 1 year ago

But now there is another problem, the font of some words are too big suddenly (this only happens on the menu, thankfully, but still). Not sure if anyone else had it too: 20221230115120_1

Now that you mention it, I have this problem too. (It also happens similarly with the "LOADING..." text) but these bugs for me happen specifically with the RE4 HD Project. The "PRESS ANY BUTTON" text is far larger than it should be, on top of again, the "LOADING..." text. None of this happens if I'm not using the RE4 HD Project.

nipkownix commented 1 year ago

The font issue is caused by a missing .ini file. See here: https://github.com/nipkownix/re4_tweaks/issues/414

leon861107 commented 1 year ago

There is no problem with the previous version of 16:10, including the resolution in the game. Now when it is disabled, there are black edges on the top and bottom

---Original--- From: "Bruno @.> Date: Fri, Dec 30, 2022 11:21 AM To: @.>; Cc: @.**@.>; Subject: Re: [nipkownix/re4_tweaks] Incomplete screen display (Issue #408)

@leon861107 What you're showing is a side effect of using Remove16by10BlackBars. You can disable that option in dinput8.ini if you wish.

@Alvarden15 Pretty strange issue in your image. Haven't been able to reproduce it. Does turning UseVulkanRenderer off gets rid of the issue for you? Might be some quirk with Vulkan on your computer/setup.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Alvarden15 commented 1 year ago

The font issue is caused by a missing .ini file. See here: #414

Thank you! That actually fixed it.