seriously? in 2024/5 we have zoomed in fov for ultrawide?

[Khser]

wtf is this? seriously who the ♥♥♥♥ in 2024/5 makes a game with a zooming fov for ultrawides? do i have to split my monitor just play a game because devs were so lazy to create adjustable fov?

edit: i am not even talking about 16:9 limited videos/CUTSCENES THAT INCLUDE BLACK BARS ON TOP AND BOTTOM

[Sleepy]

That's rough. I hope they'll release a patch for that because I'd love the game to fit my 32:9 monitor

[Khser]

Originally posted by Sleepy:

That's rough. I hope they'll release a patch for that because I'd love the game to fit my 32:9 monitor

for anyone interested here is the comparison (moon is not visible on any of the 32:9 ones, barely visible on 110 fov);


32:9 with 32:9 aspect ratio;
https://steamcommunity.com/sharedfiles/filedetails/?id=3369178085


32:9 with Auto aspect ratio:
https://steamcommunity.com/sharedfiles/filedetails/?id=3369178192


16:9 with Auto aspect ratio:
https://steamcommunity.com/sharedfiles/filedetails/?id=3369178293


32:9 with Auto aspect ratio and 110 FOV (closer to actual image but still VERY limited)
https://steamcommunity.com/sharedfiles/filedetails/?id=3369178453

[reese]

Adding this line "[/script/engine.localplayer] AspectRatioAxisConstraint=AspectRatio_MaintainYFOV" Engine.ini file fixes it for most UE5 games (It did in Palworld for exemple) but I can't find this file in the config files! (.\AppData\Local\Stalker2\Saved\Config\Windows)

[Duchenkuke]

thats a typical unreal engine issue

[YangDou]

Originally posted by reese:

Adding this line "[/script/engine.localplayer] AspectRatioAxisConstraint=AspectRatio_MaintainYFOV" Engine.ini file fixes it for most UE5 games (It did in Palworld for exemple) but I can't find this file in the config files! (.\AppData\Local\Stalker2\Saved\Config\Windows)

Create it, and make it read only. It works for some UE5 games. Otherwise you will need to use Unreal engine unlocker (UUU) for it.

[Duchenkuke]

I am a 32:9 User as well and this is not acceptable. But as I said, it is a typical issue with almost every unreal engine game. I got the same issue with Ready or Not for Example.

Once the download is finished, I will take a look

[reese]

Originally posted by YangDou:

Originally posted by reese:

Adding this line "[/script/engine.localplayer] AspectRatioAxisConstraint=AspectRatio_MaintainYFOV" Engine.ini file fixes it for most UE5 games (It did in Palworld for exemple) but I can't find this file in the config files! (.\AppData\Local\Stalker2\Saved\Config\Windows)

Create it, and make it read only. It works for some UE5 games. Otherwise you will need to use Unreal engine unlocker (UUU) for it.

This works, but if you change your FOV afterwards it breaks and you need to restart the game.

[Tornadium]

Originally posted by reese:

Originally posted by YangDou:

Create it, and make it read only. It works for some UE5 games. Otherwise you will need to use Unreal engine unlocker (UUU) for it.

This works, but if you change your FOV afterwards it breaks and you need to restart the game.

Which INI file did you add this to?

I can't find an Engine.ini anywhere.

[Célestin]

Originally posted by reese:

Originally posted by YangDou:

Create it, and make it read only. It works for some UE5 games. Otherwise you will need to use Unreal engine unlocker (UUU) for it.

This works, but if you change your FOV afterwards it breaks and you need to restart the game.

Can you explain step by step ? One line or two ? Brackets ? Full path for file ?

Thank you very much!

[Khser]

Originally posted by Célestin:

Originally posted by reese:

This works, but if you change your FOV afterwards it breaks and you need to restart the game.

Can you explain step by step ? One line or two ? Brackets ? Full path for file ?

Thank you very much!

i tried it:

went to AppData\Local\Stalker2\Saved\Config\Windows and created a new file called Engine.ini and then saved the text there, nothing happened.

also i noticed that my character is shooting from his hand;

https://steamcommunity.com/sharedfiles/filedetails/?id=3369190270

[Khser]

update:

tried Engine.ini, DefaultEngine.ini, GameUserSettings.ini and nothing works.

[The Crusader 39]

Originally posted by Khser:

update:

tried Engine.ini, DefaultEngine.ini, GameUserSettings.ini and nothing works.

Easily my biggest disappointment with the game. Not generating a functional engine.ini is a huge miss fire on their part. There's so much the end user can pull off with strings of texts but that's not an option now.

[NitekPL]

I really. I mean REALLY wish that unreal engine dies as soon as possible. This engine is the blight of gaming.

[Khser]

well we have found a workaround, by we i mean @Frehgin;

instead of trying to create/edit Engine.ini check the AppliedSettings.ini and there is a setting called "FieldOfView" which can be 110 if you use the ingame settings. but if you modify the file it can go up to 170 (higher than that it is impossible to see) we found out that 130-135FOV for 32:9 is very similar to 90 on 16:9. so you can try that. ill check it and post a screenshot in a few minutes

120 FOV
https://steamcommunity.com/sharedfiles/filedetails/?id=3369230809

125 FOV
https://steamcommunity.com/sharedfiles/filedetails/?id=3369229939

135 FOV
https://steamcommunity.com/sharedfiles/filedetails/?id=3369228801

[Luke]

FOR EVERYONE HAVING THIS ISSUE

This FOV problem fixed itself for me at a certain point in the game, not long after the introduction sequence. By the looks of the screenshots, you guys are at the very beginning. I'll add a spoiler section below roughly explaining the point at which it fixed itself for me.

If you REALLY don't want minor early-game spoilers, then it happened for me after I spoke to the guy when you first start throwing bolts into anomalies. So, the first true dialogue interaction.

So, at the third location where you use the scanning device on the anomaly, you get knocked out. You wake up, someone finds you, I can't remember his name. But after you throw the bolts through the anomalies, you go and speak to him. At this point, upon exiting the dialogue menu, the vertical FOV scaling fixed itself.

I hope this solves your guys problem. Cheers.