I have found that i am doing worse in CS with my new better mouse

A while back i bought a new mouse because i thought the one i was using was holding me back.... well today i have found that my inferior spec'd mouse is superior purely because my brain is trained with it.. used it for years.

I was using a Microsoft Express mouse.. it's as cheap as cheap can get, and my new mouse is a 1000hz 8D from James Donkey which is superior in every manner, however observing some recent videos i did of my gameplay and mouse control.... i am doing worse.

When i got to MG2 rank i went with the new mouse... now i find myself struggling to pull off the things i used to do aim wise.

Here is the cheap mouse.



Now i wonder myself why the heck i even bought a new mouse :(

People if you are not doing great, take a break from the game, or perhaps learn new tactics, i should never have dropped my MS mouse...

Just thought i would share this as my first post/topic ever :P

I guess it will just take time to get used to the new mouse ;)

I will order a new mouse as well after finals, but I think playing with the same sensitivity afterwards should be quite the same. And I hope to improve (currently LE).

I think that was the problem for you, the change in sensitivity.

1 Like

Well i am going back to my MS mouse, it's not aim that was my problem, mostly game sense and no premade team.

Why don't you keep the better mouse then?

I have noticed that in some situations my mouse has tracking issues (for example 180 degree turn), thats why a better mouse can help. And a good and large mousepad.

I've never used either mouse but I'm sure once you put the same hours in on the new mouse you'll be fine.
Are you using raw input with acceleration off in CS:GO settings?
There is even a windows mouse setting that you want to make sure is disabled.

I like the compilations, I'm a sucker for CS:GO and banging tunes. Please take my advice with a pinch of salt though, as I'm only GN3/4 level :)

Well... obviously.

Its like switching from qwerty to dvorak. your going to be crap at it until you get used to it then its better than the original.

2 Likes

No accel of any kind, Windows is set to 6, and no precision.
In game with new mouse i use 1600DPI 2.9, and with old mouse 1.92 in game (no dpi)

2.9 at 1600 DPI is quite high. I use 1.3 at 800 DPI at Full HD. I would try to lower it, you will be more accurate in the long run.

1000 Hz is often slower than 500 Hz, because of hardware limitations.

Try your mouse at 500 Hz.

There have also been some issues lately with CS and some driver changes and updates that have caused mouse-related anomalies, like unsollicited sens switching in-game.

A standard mouse polls at 125 Hz, and that's a bit slow for CS even on a 60 Hz monitor. In CS, you usually want to double up the Hz from output to input, so e.g. 60 Hz monitor, 120 fps, 250 Hz mouse, or 120 Hz monitor, 250 fps, 500 Hz mouse poll rate. By default there is an fps cap at 250 I think, but it's generally useful to set it for 999 to get the shortest possible timing for the frames that are put out. Setting this may solve minute latency issues that look like mouse latency issues, but are really timing discrepancies.

If you play with a tick rate of 128, you need at least 128 fps minimum, or you're better off sticking with 64 tick rate.

CS is just one of those real PC games with special requirements for competitive play... for entertainment purposes though, it's all not that important in my opinion...

1 Like

Cool information, because I run mostly old AMD hardware, my CPU cannot keep a steady 200FPS at all times, however it can stay above 130, 128 tick servers I do sometimes play to warmup on, there is always some really weird stuff in CS in 64 tick and especially lately, where I feel like I was seen way before I was updated from the server.

Like people have inhuman reflexes at my same rank, I have now demoted to MG1 because of this.

I don't know man. If you want to move to the new mouse I would give it a lot of time. I got lucky when I started playing CS:GO, I have two nearly identical mice with the only difference being a few grams of mass and the mouse pad they use. With my DPI at 400, Sens at 3.5 (I think) and refresh rate at 500Hz, I've gotten to Nova 4. Mind you I've only had the game a few months and BF4 and similar are more of my type of game.

Somethings I recommend is capping your framerate at something that your rig can run with zero framedrops. I currently have my laptop set up at 60 FPS (HD4600, sad little thing), and my desktop capped at 70 FPS. I felt that when I capped it and turned off v-sync, responsiveness and predictability rocketed up. Yes, I get screen tear, but who cares, my mouse does what I ask it to do and there is zero stutter.

You were right on the money. It's all muscle memory. I find that I adjust the game sensitivity based on my mouse.

Though, a higher DPI mouse will have better tracking over most surfaces, it doesn't always evenly play out with the game sensitivity.

Nice, my setting is only 2.14 @ 400dpi. I do prefer low sensitivity.
I'm sure you will get used to it with more play.

That's true, CS:GO has become a lot worse in the last year or so. There are definitely problems with the simulation engine. It's really clear to see those problems, especially if your opponents fire 3-4 bullets simultaneously, you know that your simulation has been lagging out big time, but the system doesn't show it, netgraph doesn't show it, etc...

I'm running it on an FX-6300 @ 4000-4300 GHz for the moment, a Phenom II X4, my backup system, would probably have better single threaded performance and might squeeze out a couple more fps, but I'm totally happy with my fps for the moment, which is always between 200 and 300 in CS:GO in 1080p. A CS:GO pro team I'm very familiar with, uses the latest and greatest Intel octocores, and get about the same fps. The difference is in the tweaking. On an AMD system, you would typically get the best performance by setting the thread count to the CPU core count in the launch options, whereas on an Intel CPU, you would get the best results by setting the thread count to the total thread count minus one core (two threads). It's pretty amazing in my opinion that the difference in fps is greater by manipulating the thread count in the launch options, than by adding a shit ton of processing power (core per core, a modern Intel will have about 50% more ppc than an AMD core, and the Intel has 8 cores/16 threads, whereas the AMD only has 6 cores/6 threads, so that means that the Intel has twice the processing power of the AMD).

The good news is that we're approaching the end of CS:GO, and that the successor - properly optimized for linux instead of nerfed for linux - is around the corner. In the mean time, the competition is dead anyways, and now that the NA teams are also going to be checked for drugs, and C9 will have to do without Adderall, the commercial support for pro CS:GO competition is going to fall back also, so the whole scene will experience a total refresh in my opinion, making more space for the next installment of CS to gain momentum, something that CS:S for instance never had. What remains is the entertainment value of the game, and in my opinion, those software bugs, cheaters and general obnoxiousness of the recently added hype crowd to the scene, are annoying, but they're not that bad for the general entertainment value of the game. Even with all of the bugs, the stupid Valve policies and the corrupt MLG scene, CS:GO is still one of the best PC games, not as good as 1.6, because 1.6 was a game changer, but there aren't all that many games you could spend thousands of hours playing without developing a profound resentment for the game at hand... CS:GO is still CS, the version with extra lard and useless trimmings, but it's still CS.

1 Like

Strange how that would change how you do at Computer Science lol

I have put in -novid and -threads 4 commands in startup options, I am on Windows 10 Pro now BTW so I will now see how it works.

More of the 7770 is used but it's not really any better, more stutters than anything else.