I dont know bout any one els but i am having probloms with video pov ...when I log into a game my video is all messed up, every thing seems like its stretched out and looks distorted. No matter what i have tryed nothing fixes the issue ..i have tryed restarting , going in options and messing with video settings there, i even reinstalled the game...and still i loged on and same thing long stretched out graphics....all my drivers are up to date, and i have a card that can def run this, 9800gt 1gig ram nvidia..so yeah....is any one els ahving this issue?? dose any one have a solution to the problom>? some one please help.....

I know from what you'be mentioned, however, did you make sure you are using the correct aspect ration for your monitor? 4:3/16:9/16:10. Did you mess with custom aspect ratios at all?

If you have messed with the config file in any way and need to reset to defaults for the most part on the graphics as far I know, just delete the brink cfg which is located "Steam/Userdata/"numbers"/22350/local/base/brinkconfig.cfg.

Uninstalling the game may have not fixed your config file. Give that a shot and get back to us,

nope like i said earlyer i went in and messed with all the options ...nothing.....ok i know its not just me...a friend of mine just said he is having the exact same thing happen to him...its on there end not mine.....and erasing the cfg file will not do anything, ...again some one please help....if you do not know a viable salution to this problom please dont post what you "think" might help....just post if you know what to do please...sigh..

If the problem only persists with the in-game videos then you can disable them by renaming the Assets folder in the following directory : ...\Steam\steamapps\common\brink\base\video .

I also have the same problem. I've tried with different weapons, different maps, restarted my computer and the game several times. Even tried Sinn3246's tip. None of this helped. Very annoying...and when you reload it distorts so you can see through your arm.
Does anyone have any tips on how to fix this? (Apart from the ones that were already submitted)--

I've found a solution for this. It seems as though he FOV (Field of View) was altered somehow. All you have to do is enable the console and then type "ui_fov 90" (Without the quotation marks) for it to become normal again. (At least I think that 90 was the default value) 70 is the lowest. To enable the console open steam, select Brink. Right click it and open properties and press "SET LAUNCH OPTIONS" and enter the following without the quotes "+com_allowconsole 1"

Hope this helps!

still nothing.....

um witch is it...you are telling us to type 2 dif things...?? what you said makes no sense at all....what are we supose to type? the first thing you mentioned ...the last thing? or both...i tryed doing this and nothing at all happened...hmmm?

ui_fov 70 is default and the least stretched. Maybe you could post a picture...it might be easier to determine what the problem is.

ok im done im sickend trying to mess with this video, its perma stuck in stretch mode...wow what a waste....im so pissed off i dont even care any more... i am uninstalling and using the disc as a coster for my beer..word to the wise bethesda...stick to making single player games, it what you do best...second....if your going to make a game 2 player...at least run it threw test and work out most of the bugs befor you release it..i feel so ripped off...you people will never get a nother dime of my money ever...thanks and good luck :verymad:

I'm telling you to enable the console and then type ui_fov 80 or another value.

Do this:

" enable the console and then type ui_fov 80 or another value. "

this is how to fix it, personally I like 90

Why don't you post what you've actually done and the steps you took and post a screen shot of your issue as well. It seems to be an aspect and/or fov issue. So post what you've done the steps you've taken to fix your issue.

And what I think is more of a theory and WILL work for some and others NOT, so don't jump on people who's suggestions that doesn't work, since they at LEAST tried to help you when we didn't have too.

Thank you
Sinn

dosent matter lol i am done with this game...good luck to all and have a nice day.

@ OP

They posted what they thought would work because you haven't provided a picture of what your actual problem is. How can anyone post a definitive fix if they don't know what it is they are trying to fix?

the ui_fov 90 does work....though, do you have to reset it everytime you launch?

If you create an Autoexec.cfg and add the line in, it would over write every launch, I'm sure if you were to also add/change it in the BrinkConfig.cfg it would also change it, I usually don't mess with the orig since you can break the game and usually deleting it would usually cause a "reset" to defaults. However I would rather create an Autoexec.cfg, add the line and use the BrinkConfig.cfg as reference if I wanted to test anything else out in that config. There are other lines as well that aren't in there if added would work, I'm trying to compile a list of them, though I believe there is one floating around somewhere, I'd google it. There is alright this http://www.rush-zone.com/downloads/gaming/brink.html that I've found that can help modify/optimize the game even farther and also includes a few extra options that you wouldn't normally find in the BrinkConfig.cfg and it also auto creates the Autoexec.cfg in case you're not familiar with it or just are too lazy, lol

Sinn

open console type in
seta ui_fov 90

should stay then

This too, though I'd still rather add that specific line to the autoexec.cfg, just me though, not a big deal however, even if you just used that line within the console in-game or in brinkconfig.cfg.

I don't usually recommend playing with cfg much for people unfamiliar, that one line will fix his problem without any other work or explanation

Yeah, I can understand, that is why if I am asked, that I would suggest that you never modify the brinkconfig.cfg and just create and add the lines to autoexec.cfg. That way you can at least delete either the lines or the autoexec.cfg file all together to correct your mistakes. But yes, "seta ui_fov 90" should fix his issue.