No CMSS allowed

What would be the point of that?

Everyone will tell you to not do it (or trolls will tell you to do it).

But why don't you just make a different sens for each weapon in your cfg instead?

i have already changed different senses, i know want different dpi, or whats the equivalent of dpi to sense?

500 dpi = 2 sense? ( i dno its just example )

???
dpi*sens=cm/360
1000dpi * 1 sens = 500 dpi * 2 sens

what dpi = what sensivity? EG: (500 brown = 200 green * 1000 brown = 400 green) ??

a = your IQ
1000 dpi * 2.5 sens * a = 0

i think 650 green brownies

wtf :D

dpi = dots per inch
(dpi * sens) / 2.54 = cm / 360 .. isnt it?

dpi*sens=/=cm/360

new_sens = old_sens * (old_dpi / new_dpi)

I don't know why but sens 2 with DPI 800 feels different than sens 4 with DPI 400

indeed it does feel different and i get different cm/360 on each setup

What's happening there is that the mouse is likely not using the exact DPI it says it is.

Of course it does. Different DPI values feel different.

E=mc^2

different senses, fovs, stuff for each weapon are overrated

dpi is a driver option not a game option, or something a game event can trigger.
you could scale your sensitivities by changing m_cpi, but your mouse hardware settings will remain unchanged.

also, nice troll.

?

The game cannot change your DPI.

so could it actually be done with the logitech software?

say, when i press r (my rail bind) my dpi changes to what i want, then if i press anything else it goes back to the other dpi?

try

bind r "weapon 7; m_cpi 400; r_showimages 1"

It's possible, but I'm not sure the game will still see the button you chose for a dpi switch as a mouse button anymore.

The other issue is even if it does, a lot of times what the drivers offer is just to switch between available dpi values, not specific ones. So like you'd press a button 4 times and it would go 800-1600-3200-400. Wouldn't just be the one you wanted exactly.

It's possible that it offers a switch of profiles or somet in which case you could select a specific DPI, but it would have to do that _and_ also be seen as a button in the game, seems like quite a long shot.

i have a dpi switch and can change to any dpi?

https://www.youtube.com/watch?v=oX6q_KYdqkg

bind r "quit"

should work perfectly.

using third party software = BAN

I use Paint to draw some dicks (it calms me down). Am I in danger zone?

ohhhh you're getting there buddy boy

Nice job with hacking world championship :)))

Ok if you're not trolling.
It is not currently possible with anything currently available within QL, and it's not something i can ever see them attempting to implement as it would require specific code for each and every mouse driver.

And it's a silly idea.

You could conceivably do this by forcing a config write on every weapon change (on the assumption it doesn't to this already), and using 3rd party automation software to scan that file for a change, and then trigger an event that your mouse driver can pick up (eg a key combination if you can set a key combination for different dpi's ). This would likely cause in game lag from disk i/o during play every weapon change.

Or you would have to write some hook code to actually read when the weapon changes in QL occur, and then trigger the driver. This would have to be updated every QL update, and you run the risk of it being falsely detected as a cheat.

Either way it's a silly idea.

You have some mouse with a physical button to switch DPI's on the fly. (Abyssus for exemple)

That would require some dexterity though

Abyssus wouldn't be so great, DPI switch is on the bottom.

That's why it would require some dexterity tho

bind e "sensitivity 5; weapon 5"
bind q " sensitivity 8; weapon 8"

It's a very dumb idea btw.

that's not dpi.

what difference does it make?

DPI/CPI is sensor accuracy, how many samples it's taking per inch, and sensitivity is a multiplier for that data.

Some people don't like the jitter it can cause from increase sensitivity to some surfaces and shaky hands.

End of the day it just feels different, if you set m_cpi correclty in QL (as razer driver 'sensitivity' does alter dpi with razer mice for example then you don't have to change your sensitivity to get exactly the same cm/360 it does the job of working out the changes for you.

mouse at 6400dpi, m_cpi 6400, sensitivity 18 = 20cm/360
mouse at 450 dpi, m_cpi 450, sensitivity 18 = 20cm/360 but very slightly different feel.
Caused by the software interpolation of the mouse data, and how the hardware is coping reading the surface you're on at whatever speeds you're physically moving the mouse over that surface, some mice fail badly at some dpi's and high speeds as well.


high sensitivity players (say, under 15cm/360) tend to favour high DPI.
low sensitivity players (I've heard of anything up to 80cm/360) tend to favour low dpi.

what practical difference does it make?

Different DPI values feel different is the practical difference, even if the cm/360 is the same.

That's only true in severe cases. Check with enotusmouse test to check the exact dpi on the value you use and check the max tracking speed at that dpi.

e.g the abyssus at 450cpi is bad.
Most newer mice are fine.

They do feel different.

I can definitely tell the difference between 400 and 800 dpi.

I hope you changed the sensitivity ingame according to that dpi change

i have tested several mice lately with that program and its not giving correct values for the dpi at least

yea, but in this case it would be probably like RL at sens 4, RG at sens 2 and LG at sens 3 or something.
so he needed it like RL at 800DPI, RG at 400DPI and LG at 600DPI, but he could just use 800DPI for everything, and change the sens instead.
that shouldn't be a too dramatic change in feel.

Of course his idea is quite crazy.

Entertaining it on its own objective merits and whether or not it is possible.

I just want it to be clear though that dpi does not equal sens. Sens 4 at 400 dpi will feel different than sens 2 at 800 dpi, even if the cm/360 is identical.

I use 800 dpi and use 13.8cm/360 because that's the sensors native dpi and it works well. Just use the native dpi and leave it alone... Also I don't know why you'd ever bother using m_cpi
Just go here http://www.mousesensitivity.com/ and put numbers in.

There are a lot of people who use lower sens than 80cm/360. A tribe player sebacious who uses 300+cm/360 and a lot of the snipers use 100+cm/360

Hahaha 300cm/360? Fucking unbelievable.

these guys play with Ra$ta Yanushevsky certified rug surfaces for optimal tracking and comfortable meter-long sweeps

because if you use m_cpi then if you change mouse, and the mouse has a different dpi, then you just have to set the m_cpi to that dpi and you will have the same turning circle.

Also it means that your sensitivity is a value that has instant meaning comparing it to others without having to break out a calculator.

That's the whole point of m_cpi's existence really.

what do you aim to achive with this?

read this:
regurge.at/ql/lorfa

remember there will be a test

from my config, I guess you need only to add sensivity cvar to each weapon.

// Weapon binds

set xhair1 "cg_drawcrosshair 2" // GT, LG, MG, PG, CG
set xhair2 "cg_drawcrosshair 9" // Everything else

set pos1 "cg_gunz -2; cg_gunx 2; cg_guny -4; cg_drawgun 2; cl_mouseAccelOffset 0" // GT
set pos2 "cg_gunz -10; cg_gunx -10; cg_guny 3; cg_drawgun 2; cl_mouseAccelOffset 0" // Everything else apart from SG + MG, except LG
set pos3 "cg_gunz -10; cg_gunx -10; cg_guny 3; cg_drawgun 0; cl_mouseAccelOffset 0" // SG
set pos4 "cg_gunz -2; cg_gunx 2; cg_guny -4; cg_drawgun 2; cl_mouseAccelOffset 1" // MG
set pos5 "cg_gunz -10; cg_gunx -10; cg_guny 3; cg_drawgun 2; cl_mouseAccelOffset 2" // LG

set _GT "weapon 1; vstr pos1; vstr xhair1; vstr wdownreset; vstr wupreset"
set _MG "weapon 2; vstr pos4; vstr xhair1; vstr wdownreset; vstr wupreset"
set _SG "weapon 3; vstr pos3; vstr xhair2; vstr wdownreset; vstr wupreset"
set _GL "weapon 4; vstr pos2; vstr xhair2; vstr wdownreset; vstr wupreset"
set _RL "weapon 5; vstr pos2; vstr xhair2; vstr wuplock"
set _LG "weapon 6; vstr pos5; vstr xhair1; vstr wdownlock"
set _RG "weapon 7; vstr pos2; vstr xhair2; vstr wdownreset; vstr wupreset"
set _PG "weapon 8; vstr pos2; vstr xhair1; vstr wdownreset; vstr wupreset"
set _BFG "weapon 9; vstr pos2; vstr xhair2; vstr wdownreset; vstr wupreset"
set _NG "weapon 11; vstr pos2; vstr xhair2; vstr wdownreset; vstr wupreset"
set _ML "weapon 12; vstr pos2; vstr xhair2; vstr wdownreset; vstr wupreset"
set _CG "weapon 13; vstr pos2; vstr xhair1; vstr wdownreset; vstr wupreset"

set zoomon "+zoom; bind * vstr zoomoff"
set zoomoff "-zoom; bind * vstr zoomon"

bind "c" "vstr _GT"
bind "e" "vstr _MG"
bind "r" "vstr _SG"
bind "mouse3" "vstr _GL"
bind "MWHEELUP" "vstr _RL"
bind "MWHEELDOWN" "vstr _LG"
bind "SPACE" "vstr _RG"
bind "q" "vstr _PG"
bind "5" "vstr _BFG"
bind "1" "vstr _NG"
bind "4" "vstr _ML"
bind "3" "vstr _CG"

bind "mouse1" "+attack"
bind "*" "vstr zoomon"
bind "g" "dropweapon"
bind "h" "dropflag"