Mouse sensitivity reset

(Breo) #1

I’ve changed the sensitivity of Brink to 0.727
But when I play the campaign mode the sensitivity will change automaticly to 1 when I start a mission :mad:

(Ino) #2

I have exactly the same problem, I’ve set my sens to 0.5 via autoexec, yet it always resets itself to 1 each round. My workaround for that was binding “sensitivity 0.5” to a key, but that can’t be the solution.

Please SD fix the sensitivity reset! And even better: allow us to enter a value for sensitivity in the menu, right now you can’t go lower than 1 with the menu. That must really be a pain in the arse if you have a high DPI mouse. I use a 1800 DPI Deathadder and a sens of 1 is far to high for me to feel comfortable.

(Breo) #3

That’s the reason why it always change back to 1 :frowning:

(Ino) #4

Can we get a short reply by someone from SD about this? I don’t want definit answers now, just something like “it’s intentional, deal with it” and then me going QQ or something like “we’re looking into it” and me going :smiley:

(Ino) #5

(Ino) #6

I will bump this to infinity and beyond…

Also: why is the cvar for the sensitivity ratio while zoomed in locked? can someone explain the reason behinnd this? It completely ruins all the scope attachments for me because sensitivity goes much too low while zooming in.

(McAfee) #7

I don’t have one of those mouse with one billion, gajillion, fifillion,
shabba-doodle-ooly-million, sha-ming-gommy-shlay million…DPI

But wouldn’t it be logical that they provided a compatibility mode
while still taking advantage of the DPI?

eg: the driver scales the input before the apps.

(Ino) #8

[QUOTE=McAfee;324124]I don’t have one of those mouse with one billion, gajillion, fifillion,
shabba-doodle-ooly-million, sha-ming-gommy-shlay million…DPI

But wouldn’t it be logical that they provided a compatibility mode
while still taking advantage of the DPI?

eg: the driver scales the input before the apps.[/QUOTE]

I don’t use one of those either, I use my trusted good old Deathadder with 1800 DPI. I have a G500, but when I used it I played all games with 1600 DPI.
High DPI don’t even offer you any advantage, that’s just marketing. I would use my DA with 450 DPI if there weren’t problems with the maximum speed with lower DPI than 1800 (see the ESReality mousescore for reference)

But we should not need to scale our mousespeed in drivers when the engine is perfectly capable of mousesensitivities below 1. They just need to get rid of the reset. And while they’re at it they should get rid of the locked sensitivity multiplicator while zooming in.

(BMXer) #9

I have this problem too. I had to bind a key to set my sens because it resets to “1” after every round.

Its simply just one more thing SD failed to correct when they PORTED BRINK FROM THE XBOX TO THE PC.

Brink = console port = sad

(Zarlor) #10

I had mine set to .5 as well, but now I have to use like 500dpi on my mouse because is goes back to 1.

Oh well, it doesn’t bother me because the game doesn’t feel right anyway. I thought it would at least feel like ETQW because it is based off of idtech4, but now we know why we’ve been told Brink’s-Not-ETQW. It feels like they took the engine that was ported to the consoles for ETQW and ported it back to the PC. Maybe they didn’t do that, but it feels like that new Wolfenstein did a bit -like it was run through the wringer.

Maybe if I can get more fps in the game it’ll feel better. I keep hoping there will be some magic driver update or patch and only time will tell. I hope SD will unlock more graphical cvars which will actually improve performance. Aside from AO and shadows it seems like all of the other variables INCLUDING lowering my resolution in game provide negligible performance improvements. There must be something like the depth of field that is forced on which really kills the performance.

I like the game and I play it every night and I know SD is working on upcoming improvements. Maybe we’ll all sit back and chuckle about the day when all anyone ever played were lights with carb9s.

(Breo) #11

I still need to adjust this setting at start of a map.
Is it possible to execute a command (sensitivity) automatically after loading the map?

(EnderWiggin.DA.) #12

http://www.splashdamage.com/forums/showthread.php?t=28975
I don’t think this is limited to just sensitivity. I don’t think autoexec.cfg fiels are working correctly.

@BREO.
I think you could try this.
Create a file in \Steam\userdata\some random number\22350\local\base called sens.cfg
in the NOTEPAD file sens.cfg type “seta sensitivity #” where #= the number you want. Save the file.

Start the game and open the console with CTRL+ALT+~
Create a keybind in the console like this:
bind “kp_enter” “exec autoexec.cfg” “” “default”
If I wrote that correctly (not guaranteed), the file sens.cfg should be executed when you press enter on the keypad.

(Breo) #13

EnderWiggin that works :smiley: but still, after loading another map it’s back to 1 :tongue:

(EnderWiggin.DA.) #14

yeah, sorry. I don’t know if there is a fix for the problem. I was just trying to make it easier for you to change the sensitivity. I wasn’t clear.

(AltoKnallo) #15

[QUOTE=Breo;345522]I still need to adjust this setting at start of a map.
Is it possible to execute a command (sensitivity) automatically after loading the map?[/QUOTE]

try this

10chars

(Mustang) #16

@AltoKnallo
Doesn’t work (testing with m_pitch)

(AltoKnallo) #17

[QUOTE=Mustang;345678]@AltoKnallo
Doesn’t work (testing with m_pitch)[/QUOTE]

unfortunately, just tested it with “seta sensitivity 0.815”. obviously the reset to 1 happens after the mapscript exec.

(HugePinball) #18

Then add a wait command.

(Breo) #19

Unfortunatly wait will not work, all the commands will be executed b4 loading the map.
Everything that supposed to be set after the load screen will be skipped.

Allthough I’m not sure if I test it properly :0

“wait 30” = 1 second? I tried “wait 300” for 10 seconds without any luck.

(HugePinball) #20

[QUOTE=Breo;345832]Unfortunatly wait will not work, all the commands will be executed b4 loading the map.
Everything that supposed to be set after the load screen will be skipped.
[/QUOTE]
Hmm… it seems that commands called in this manner (automatically on map loads) aren’t being buffered, otherwise it would work. All the commands are being called immediately, even those after any wait command. If you manually exec the same config file from the console line, they are buffered and execute after the wait like you’d expect. Don’t know if there’s any way around this.

Btw, the parameter for wait is supposed to be frames, so at 30fps “wait 30” should be 1 second.