[GoldSrc] Add raw input toggle in menu like in Source games.

[DarkDefender]

Now that raw input is not on by default it would be really helpful for players that doesn't know this exists to have a raw input toggle in mouse settings like in source games.

[zp]

They may as well.

Remove the auto-aim option from the mouse tab, because almost every server runs sv_aim 0 anyway rendering this option pointless, and replace it with a raw input toggle for people that are unaware of the cvar.

[AndreiRomania]

Raw input is useless becose most PRO players use -noforce or since the shitty update they used.

[Safewood]

@AndreiRomania Most actually additionally used a program called RInput, which is Raw Input for HL1 games. What's your point anyway?

[AndreiRomania]

the only INPUT that worked was the old 1 with -noforce

that is why CS 1.6 was on the top 5 games on steam and the dysfunctional CS:S and CS:GO are below 5.

[r3n4m3]

@AndreiRomania what are u talking about?

[AndreiRomania]

r3nam4 => Not sure if stupid or just retarded ? ( how much time do you play cs and since when ? )

I play 8 - 10 h a day on my free time.

and i Play CS since the BETA stage 0.1 and 1.0 ( 1999 - 2000 )

These former commands: -noforcemaccel -noforcemparms -noforcemspd were implemented by a really SMART guy to remove mouse acceleration successfully.

Now they are replaced with this raw input ( update ) you call witch does not make it GOOD in fact the opposite.

Let me enlighten you what these commands DO and why the SHOULD never be REMOVE.

http://h3llrz3r.wordpress.com/2006/06/03/counter-strike-16-mouse-acceleration-and-settings/

Right click the steam icon on your taskbar -> Play Games -> Right click Counter-Strike -> Properties -> Launch Options.

The following three commands are the most used commands you will find in a users launch options. Luckily, they have a direct correlation to your mouse so you get to learn all about them right now.

invokePan("bannerid:43", "rectangle");

noforcemaccel – reverts to desktop mouse acceleration settings. For the most part (when it comes to gaming and precision accuracy) mouse acceleration is a fickle feature. The noforcemaccel command will make sure Half-Life does not try and manage mouse accel when it is disabled in your windows options. When to use? When mouse acceleration is disabled on your desktop and you want the same results for your in game experience.

noforcemparms – reverts to desktop mouse button settings. What does that mean? Usually when you start up Half-Life (or in this case Counter-Strike) your mouse configuration will switch to application mode, allowing the assignment of keys already assigned to your desktop (like mouse3). This variable turns that feature OFF. There is really no benefit to this command, and in actuality it is quite buggy at times. When to use? When you are experiencing difficulty with button assignments. A part from troubleshooting this command has no practical use, despite popular belief.

noforcemspd – uses desktop mouse speed settings. Noforcemspd forces Half-life to use whatever speed settings you have applied to your desktop via mouse properties. Whatever the value, Half-Life will use it as guidance. When to use? When you want your out of game speed to set the bar for your in game sensitivity. Think of sensitivity as a speed (de)amplifier.

[r3n4m3]

Am I understand you correctly, do you want to remove the acceleration via that launch options?

[AndreiRomania]

Yes, the only way the WORK before the update

[DarkDefender]

If you read what the launch options does in the text you pasted you should know that "noforcemparms" is useless so that is rightfully removed.

The other two are for using the windows settings for speed and acceleration of the mouse pointer. If you truly want no mouse acceleration it is raw input that you want as it bypasses the OS when reading how you move the mouse.

If you want to use the setting of your mouse that your OS has then you just turn raw input off.

[r3n4m3]

-noforce commands remove acceleration from windows, it is true.

But I see that you, along with all your experience, still don't know that these Launch Options do not remove negative acceleration that is present in the game because of used input method. Smart people see this disease and create Direct and Raw input, which means that the data come from the mouse directly to the game without going through unnecessary errors introduced by the operating system, as well as the game itself.

And now I ask the question, what don't you like in Raw Input?

[AndreiRomania]

let me put it this way thousand people see this as a problem becose it generates positive and negative acceleration problems.

I have Mouse editor Oscar that came with the mouse with a MACRO for turnin 180* with 1 click.

I set my ingame sens to 1.5 prior to update ( -noforce ON ) then after the update seme settings the mouse did not move 180* it moved 200* with the same mouse sens witch is 1.5.

Now i got 1.35 sens in game to close match the prior 24.02.2013 sens 1.5 that i had.

Simple it moves just not RIGHT.

Same users with Steelseries, Inteli 3.0 , razer , zowie, logitech report THE SAME PROBLEM.

Gameplay before update http://www.youtube.com/watch?feature=player_detailpage&v=NJrgzA7JvEA#t=97s

Now the mouse does not have the same response time with the same settings as before this update.

[DarkDefender]

If you had disabled the mouse acceleration in windows before then you just have to play with 1.35 instead of 1.5. I don't really see the problem here.

[r3n4m3]

When using raw input game gets mouse data bit to bit.

If you find a issue, then create a topic with a detailed description of the settings that you have used before, and using, which version of the game were seen problems.

Will also need information that you can make after reading this https://github.com/ValveSoftware/halflife#reporting-issues, and specify on what equipment you did all these things, including the mouse.

[r3n4m3]

I also want to assure you that in the event that everything is set up correctly, there is no positive or negative acceleration.

[AndreiRomania]

When using raw input game gets mouse data bit to bit. Really?

It does not do this.

noforcemspd – uses desktop mouse speed settings. Noforcemspd forces Half-life to use whatever speed settings you have applied to your desktop via mouse properties. Whatever the value, Half-Life will use it as guidance. When to use? When you want your out of game speed to set the bar for your in game sensitivity. Think of sensitivity as a speed (de)amplifier.

[r3n4m3]

If u have issues with getting data bit to bit from ur mouse, create an issue via this https://github.com/ValveSoftware/halflife/issues/new, and follow the requirements mentioned above.

You should to understand, this is not a forum, if you have a problem, create topic for it.

And stop nagging in every topic, it will not help to other people and to you too.

[MaximilianKohler]

Hmm, I wonder why this was closed without an answer... zp's suggestion was good.

[zp]

@MaximilianKohler He added an option in the mouse tab of the options menu.

[MaximilianKohler]

Oh, cool!

[johndrinkwater]

If an issue is closed and the milestone field is all green, it means its been fixed!