Just wondering if a BF Rep could take the time to list some of the limitations of the editing of the config file 'settings'.
The listed below are the ones I'm interested in, It would be great if you could expand on what they do and whether they are allowed to be edited and to what extent.

[Sound]
SpeakerCount=

[Graphics]
Bloom=
HSAO=
MSAA=
Aniso=
RenderAheadLimit=
Fov=

cheers in advance

I'm more concerned about the changing of bloom from true to false, like if it's a legal edit.
Usually i wouldn't have a problem with this, but because it's been left out of the game menu, i thought i would just double check.

To save you some time, no EA reps read or respond here. Sorry.

Kinda ironic, been through 3 customer service reps and they all said post here ^^
Oh and i've seen Zerk around so kthx.

Because they don't know, they are hoping the community can help you. I can say that usually if you change your configs PB will kick you. Changing the bloom might be one that would get you. Bloom is in there for a reason to balance gameplay, and keep snipers from dominating maps at great range like they did in previous games. Changing this would give you an unfair advantage over those that don't have it turned off. PB doesn't usually take to kindly to that. Same as turning off grass, decals, fluff and flare, etc. I could be wrong with this one, but I would change those at your own risk.

They really should post something somewhere about that lol
ZERRRRRk read this

battlefield.XamotDB wrote:Because they don't know, they are hoping the community can help you. I can say that usually if you change your configs PB will kick you. Changing the bloom might be one that would get you. Bloom is in there for a reason to balance gameplay, and keep snipers from dominating maps at great range like they did in previous games. Changing this would give you an unfair advantage over those that don't have it turned off. PB doesn't usually take to kindly to that. Same as turning off grass, decals, fluff and flare, etc. I could be wrong with this one, but I would change those at your own risk.

I've had bloom off since beta and haven't been PB kicked....

I'm pretty sure that if it's in that config.ini file it's safe to change it. Mostly since I have changed them all at one point or another and haven't been kicked.

would be good to get an official reply, after all Vincent from support claimed

"We are listening and we read everything that is posted on our Battlefield: Bad Company 2 forums. We are committed to providing the best play experience possible and working hard to ensure that we solve these problems as soon as possible. We promise to keep you updated and, in the meantime, we thank you for your patience."

Please, fix Vsync!! It does not work in my PC, nor in game setting neither in the my documents settings.

Ive adjusted everyone of those settings and have no issues with PB or kicks. If it doesnt change the way the game functions,but rather how it looks,its not a cheat.

battlefield.rysheK wrote:Just wondering if a BF Rep could take the time to list some of the limitations of the editing of the config file 'settings'.
The listed below are the ones I'm interested in, It would be great if you could expand on what they do and whether they are allowed to be edited and to what extent.

[Sound]
SpeakerCount=

[Graphics]
Bloom=
HSAO=
MSAA=
Aniso=
RenderAheadLimit=
Fov=

cheers in advance

To clairify a bit for you. Bloom set to false takes that extreme brightness outta some maps.
HSAO,i have no idea and keep it off.
MSAA-multi sample anti aliasing. Set it to 1x-2x-4x-6x-8x-16x,but it doesnt work atm.
ANSIO-antrhoscopic filtering-leave it or set it to 8x or max 16x on most cards
Renderaheadlimit-this tells your cpu to render 2 frames ahead of your graphics card,set this to 0 at this is optimal,you want your card to render more.
FOV-field of view-set this to 78 for 16:9 ratio monitors and 74 for 16:10 monitors to optimize your view on screen.
hope this helps.

Cheers man ;D

still would be good to get the official word on legality; i've been chasing for the past 24 hours ^^

cem_ea_id.NameAlreadyUsed wrote:Ive adjusted everyone of those settings and have no issues with PB or kicks. If it doesnt change the way the game functions,but rather how it looks,its not a cheat.

It can technically be , not a cheat, but a leg up. Earlier games really allowed you alot of leeway in adjusting game settings.

Take a game like Armed Assault. Turning the resolution and AA high, but turning everything else to the lowest possible settings would give you a significant advantage over someone playing with everything maxed out.

i.e. removing grass, shadows, particle effects, sun glare, postprocessing etc etc. All of these deal with altering vision in some manner. Ive known plenty of players as long as ive played fps games online, that would knock down effects, and detail to nothing to gain an advantage over those that use all the effects.

Yeah, hence why i want an official response..

My understanding in discussing this with an admin at a ranked server provider is from the response:
"Currently EA does not have PB checking for configuration file violations, and there are not even any 'defined' yet.
Should EA decide to limit these, I would suspect players would be advised. In any case, configuration violations generally are kicks, not bans, allowing you to remedy the offense. Let me know if you need more info."

PB can and will detect these, it is up to the server admins (EA certified providers) to set these, and there are no
checks done at this time.

Most 'tweaks', or things like key macro programs will at worst get you a PB kick, it is generally only identified outright cheats/hacks that result in a PB ban. These are controled by Evenbalance, so that rogue admins can't set things up and get players banned for reasons they deem. An out of control admin could set up artificially ridiculous configuration or file MD5 restrictions, but at worst it would kick players, not ban them.

Hope this helps.