How do i change FOV and dramatically lower mouse sensitivity

(Atavax) #1

I’m new to splash damage games, so i’m guessing its pretty common knowledge with people experianced with the developer, but is there key or combination of keys for a console and a list of commands for said console somewhere? looking speficially to increase FOV and to lower mouse sensitivity far more then the primitive slider in options allows.

(Ino) #2

I’d like to know that too, even though I’m not even able to play right now :smiley:

I thought Splash Damage knew how important a good mouse input is for FPS (probably the most important part) and wasn’t to worried because of idTech 4. But hearing more and more people complain that mouse stutters/has accel and does not go low enough is terrible. If I’m not able to play with my 35cm/180° sens this game will be dead for me. Also: Why doesn’t every developer implement raw input these days? Valve did, and it’s a blast.

(murka) #3

To open console, press ctrl + alt + ~(key left of 1). To make it open with ~ key only, write com_allowConsole 1.

To change sensitivity, the cvar is sensitivity i hope, as it was that in etqw.
To change fov, use cvar g_fov (range 70-110).

For a full list of cvars, type htmlCvars which show up as a nice html file in mydocs/splashdamage/brink/…(somewhere, dunno exactly as i don’t have brink).

Also this game does use raw input and any acceleration/slugishness you might feel is a weirdness with the engine. Mouse just does feel sluggish when fps is below 60. At 120fps it should feel very smooth.

(Ino) #4

Well, as I said I can’t even play it myself right now cause I’m in europe. But if BRINK allows the usual idTech 4 console commands everything is fine for me. But how do you know when you don’t have it yourself?

Also thumbs up for raw input, if this is true I’m happy :smiley:

(Atavax) #5

thank you so much… i think the minimum sensitivity on the bar is 1… ideal for me is around 0.15… so it was more then 5 times what i like…

(murka) #6

Download brink dedicated server and do htmlcvars in console :slight_smile:

(Ino) #7

so you either have a mouse with a lot of DPI or you play with a sens that’s even much lower than mine. In Quake I play with 0.5 which equals to 35cm/180° on a 1800 DPI mouse.

(system) #8

g_fov has been changed to ui_fov

[QUOTE=SRS-Kap;295830]Hi all,

This issue has been addressed and will be with you via an update very shortly.

Once you recieve the update, the cvar for changing fov is now ‘ui_fov’ rather than the previous ‘g_fov’.

On a side note, there is no aim assist on the PC version at all. :)[/QUOTE]

(JeP) #9

The update is not out yet I think. Last night it wasn’t.