9 replies to this topic

[-Halcyon-]

Why do you make us edit text files on staple options that plenty of other free games (or any FPS for that matter) like Planetside 2 include directly in the game options?

I just don't understand these kind of decisions.
How much more non-user friendly could you guys make the game UI?

Something as basic as a FOV setting should have it's own slider bar in the video options.
Making your users edit text files...that's just amateurish.

Edited by Halcyon201, 29 April 2014 - 04:59 PM.

[-Halcyon-]

I just discovered that you can't just edit the user.cfg file because in my installation it didn't even exist.

So new players are expected to create a new config file and edit in the code themselves to get these features?
Jeez PGI you guys really blow at the UI.

[Jabilo]

These options need to be in the main menu, with film grain, cockpit glass and DoF.

ASAP

[Troutmonkey]

UI in general is a mess, but asking people to edit .cfg files for basic stuff like this? Yeah that's a new level of crap.
It would be like asking Windows user to change there wallpaper via cmd prompt, not cool.

[Duncan Longwood]

Wasn't UI 2.0 supposed to fix all this crap? So what was the step forward that justifies the months of having a horrible mechlab? I'm not seeing it.

Edited by Duncan Longwood, 30 April 2014 - 04:01 PM.

[DeadlyNerd]

Apparently, they've probably integrated fov setting so deeply into the start up code that they can't find it. Maybe they should try Ctrl+f, but that's just my blundering of heretical nonsense.

[Durant Carlyle]

Many games have required the manual editing of configuration files to access certain settings. MW:O's not the first, and they certainly won't be the last.

[thisisxerxes]

It's really common that as a developer (especially if you're working in two-week sprints or something), once you've finished a cool new feature (even if that feature is being able to turn another off), you just want to get it out there to the userbase as quickly as possible, and sneak it into an upcoming release. Sure, it might need some config file tinkering to enable, there might not be any final UI to support it, but at least it's in.

I suspect if we wait a few more weeks these will show up in the UI.

[Cest7]

They've stated it allows an unfair advantage for multi monitor users and removed it....

[DeadlyNerd]

thisisxerxes, on 30 April 2014 - 09:04 PM, said:

It's really common that as a developer (especially if you're working in two-week sprints or something), once you've finished a cool new feature (even if that feature is being able to turn another off), you just want to get it out there to the userbase as quickly as possible, and sneak it into an upcoming release. Sure, it might need some config file tinkering to enable, there might not be any final UI to support it, but at least it's in.

I suspect if we wait a few more weeks these will show up in the UI.

The field of view adjustment has been present since closed beta. In what universe is few more weeks 2 years?