Driving Stick Behind Slow Drivers... Tips?


Recommended Posts

I just purchased my second car, a 2002 Mazda Protoge5 which has a manual transmission. My first car on the other hand was an automatic, so my experience with standard trans is very low at this point, so I'm looking for a few good tips.

So I'm still playing around with starting in first gear and getting a smooth acceleration, but for the most part I'm ok with it; the odd time however, I have rough start. Now, I've run into a few situations where I'm stopped at a red light with one car ahead of me, and when the light turns green, the driver ahead of me starts moving EXTREMELY slowly and keeping at an incredibly low speed with little to no acceleration, seriously, they only drive at about 10 km/h for a good 30 sec. Now, what I want to know is, what's the best way to drive stick in a situation like this without having the car jerk around a bit? The reason I ask is because I can't seem to get a smooth accel since I'm not able to give it too much gas. Any tips?

Stick = gears?

Rule of thumb is always pull away in first, then move to second and upwards as the ride demands.

In such a situation, I would generally go to second, but my car has a nice level or torque and can deal with it.

However, you can't get a smooth accelleration in first? Why?

One thing you can do, which is really dependent on how much torque your car has, is to start in 2nd gear. Another thing you can do, but isn't really good for your clutch, is to "slowly" let off the clutch until you feel it starting to slip, then give it a "little" bit of gas to keep it from stalling. Since you're starting out, I'd go to an empty parking lot or street and practice for a while (not good to stall in traffic). Once you get comfortable with the clutch, and knowing when it starts to grab (this will be different for every car), you'll be able to do this comfortably. Manual transmission cars can go slow too :)

Stick = gears?

Rule of thumb is always pull away in first, then move to second and upwards as the ride demands.

In such a situation, I would generally go to second, but my car has a nice level or torque and can deal with it.

However, you can't get a smooth accelleration in first? Why?

Well I can get a smooth acceleration when I'm starting at what I considder a normal speed. But when I'm going too slow, let's say while behind one of those slow drivers, it feels a bit rough.

One thing you can do, which is really dependent on how much torque your car has, is to start in 2nd gear. Another thing you can do, but isn't really good for your clutch, is to "slowly" let off the clutch until you feel it starting to slip, then give it a "little" bit of gas to keep it from stalling. Since you're starting out, I'd go to an empty parking lot or street and practice for a while (not good to stall in traffic). Once you get comfortable with the clutch, and knowing when it starts to grab (this will be different for every car), you'll be able to do this comfortably. Manual transmission cars can go slow too :)

Yeah I could go in second in situations like that but you sometimes don't know if the driver is a slow one or not, so usually I'm in first. Beyond that, and I don't know if this is good, bad or just the way my type of car is, but the clutch seems to need some good level of precision to get a smooth accel. Other standard cars I've driven have been a bit more... I don't know, forgiving. I guess maybe the "bite point" (as I've heard it's been called) is a bit bigger on the other cars I've driven. Mine, on the other hand, seems to have a smaller bite point, so I'm not used to it fully. A friend of mine took it for a spin when I first got it and mentioned that the clutch is sensitive, and even he made it jerk around a bit.

I dunno, maybe I just need a little more practice. Again, I'm okay for the most part, except when accelerating slower than I'm used to.

Like IceBreakerG said, torque plays a big role here. Civics produce barely any torque, so with my car it's possible to crawl very slowly on 1st gear. If you have something like a TDI with much more torque, just playing with the clutch (although slippage is bad) is more than enough to move in traffic.

Either you use and burn more the clutch, but stick closer to the car in front which I think is bad

or leave some space, burn less clutch, but have more people cutting you over because you're letting them in.

When im in situations like these, usually I tend to get angry, but being my 2nd year driving a stick everyday, I can tell you give them enough space and then go, as you get to 2500 shift to second and keep your foot close to the clutch.

The jerking your talking about happens in some cars because of the torque and in first you cant just give it gas and slowly let off, youll get rough / jerkiness. I learned that the 2nd day of driving my car and had to figure out what to do. Basically learn your car, its gonna become second nature too you. As soon as that happens your naturally know when to shift, when to put it in neutral and ride, when to keep a slow accelration / foot REALLY close to clutch, etc.

If I can make a video ill show you what I mean. Took me a while to figure it out, but the ONLY person i knwo that drives a stick and does what I did is an employee at my mechanics shop. He told me it was the easiest way to "crawl" in any stick. Only time you shift to second is depending on your car and how fast it reaches 2500 or shifting point.

Me, ive driven a few beamers/vws/mazdas etc. They all basically do good in first till you get to 2200 then if you shift to second, second handles everything in these cars.

DO NOT START IT IN SECOND or Slip it. Or plan on saving up money for a Clutch.

I think it has been well covered already, but the best solution in my book is to let some more room develop between you and the car ahead. The downside there is that you sometimes get a car to cut you off in between, but really so what. That costs you maybe 20 seconds in your travel time. If 20 seconds is worth the stress and the increased use of the clutch then ride that clutch and suck right up to that car in front of you.

I do look at clutches a bit different than most. The clutch is a wear item. It is designed to wear out and be replaced. You don't burn out a clutch anymore than you burn out your brakes. You can use both of those items up faster by abusing them though.

If you want to keep the clutch floored the whole time in traffic, I think that wears out the throwout bearing. You're better off just putting it in neutral if you think you won't be moving for a while.

Thank you for knowing what you're talking about. A lot of people argue that having it in neutral is hard on the transmission. I have no idea where this argument stems from, but it is nonsense.

With enough practice, you can drive stick at walking speed from a dead stop, without slipping the clutch, no matter how much horsepower or torque your car has.

No one can just tell you how to drive stick, you must practice and develop the coordination and pedal control.

Practice makes perfect.

+1 for the parking lot idea.

Thank you for knowing what you're talking about. A lot of people argue that having it in neutral is hard on the transmission. I have no idea where this argument stems from, but it is nonsense.

Yeah it's because those people mix up automatics with manuals. I forgot why it's bad on an automatic, but they probably assume that it's also stressful on a manual transmission.

Just don't let off the clutch all the way.

Once you get good at it, you'll never want to go back to an automatic. At least, I never do.

Yeah,

There you go. Ride the clutch all day!!

Might as well try and ride the brakes all day also, once you get it going!

Let's burn 'em all up!!

This is one time where practice does make perfect.

I'll never buy another automatic again, except for maybe a winter beater.

My first car, back in 1976 was a stick, and I've had (at least) one since. Currently have Ford Ranger and Jeep TJ that are sticks.

Love 'em!!

i've recently bought my first automatic..

won't be going back to manual if i can help it :D

i can see your point, manual can be a pain especially on up/downhill starts. you shouldn't have to ride or 'tease' the clutch if you are competent at driving manual, that's just silly.

As others have said, you just need to practice more... you'll get used to driving in any situation soon so that you don't even think about what gear you're in and just "do it" naturally. Find yourself an parking lot and just practice low speed driving such as this.

Pulling away slowly from traffic lights should be nothing more than lightly building the revs, letting the clutch out till it's fully engaged and just gently resting your foot on the throttle.. the car should almost pull itself along at the slowest speed without any throttle input from yourself and then as the slow mover up front gets their act together, just gently onto the throttle, build up the revs and into second and off you go :)

Once you get good at it, you'll never want to go back to an automatic. At least, I never do.

Try driving a flatbed truck with $30,000 worth of windows and other building materials on it, where you have to deal with hills that have red lights on top, and traffic.

You will change your tune real quick and learn to avoid certain places.

I learned to drive stick 18 years ago. It's been nearly 6 since I've driven stick and I don't miss it one bit. Though I did enjoy it.

i've recently bought my first automatic..

won't be going back to manual if i can help it :D

i know, after driving manual/stick for such a longass (10+yrs) time, especially in such congested roads such as the ones i have to deal with, i dont want a damn thing to do with it. automatic ftw. i went from driving a civic lx stick to a magnum rt auto.. im in heaven!

as for being behind some tourist, downshifting and mashing the gas worked well for me.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!