Fluid 135 Ride 1

I was able to get a good beating in on the WB F 135 fork today attached to the Curtlo, which from now on shall be referred to as "The Tractor."

I took Little Granite Trail (37) to its end, turned left on 39, turned left on 38 back to 37 and out.

For those that don't know, this is a 20 minute steep climb (barely ss able by me at 32:21), 1 minute descent, 5 minute climb, 3 minute steep, very techy descent at moderate speed, followed by about 20 minutes of flowy trail to trail 39.

As always, the Tractor climbed right up, over the water bars, etc. An extra inch of fork height made no difference at all. The first steep descent made is abundantly clear that running the fork without any air preload was a bad idea. It simply dove way into travel under braking and stayed there. I added about 10 psi, and that seemed to control it. Lesson learned. Use the coil to soak up the little chatter, add air to control dive, and bottom out. Sag is not really a good measure of how to set the fork up, it needs to be ridden. After adding air, all I can say is that the front end seemed very quiet compared to the Reba. No drama, just went where I pointed it without fussing, soaked stuff up nicely. Some stiction, but still early in break in so forgivable.
Again, quiet is the word I would use; not sure why.

Interestingly, I have noticed that the problem I had with not being able to get the front end up with the other Fluid 130 is now totally gone. I can manual off a wheelie drop/water bar at will, with no hesitation. It must have something to do with how the fork rebounds, and I depend on that rebound to lift the front. I also had no problem with the Reba BTW.

Trail 39 is one of the most difficult technical trails around these bits. Not fun technical, just survive type technical. I am happy to get through it without crashing (which I did twice today(how can you go OTB on a bike with a 46" wheelbase?)). Luckily, it is so overgrown, cactus ridden, rocky, rutty, and tight, that speeds remain low, so the crashes are more semi-controlled falls off the bike (hopefully not into a cactus). The fork handled this section fine. Steered where I wanted it, didn't dive too much, gave me the BB clearance I love for this sort of work. It has no bad habits at low speed techy stuff, which is the one skill I do have on a bike. In this sort of situation, Maverick's claim that torsional stiffness in unimportant to a MTB fork is proven to be total rubbish. Going slow over rocks and obstacles puts lots of stress on steering, especially in torsion. No bad habits on the WB.

On 38 I have the option of the less techy smooth moto trail climb, or the uber techy hike a bike climb. Of course, being on the Tractor, I took the tech option. I am still amazed at what I can get up with this bike. It is honestly ridiculous.

Finally, the downhill to the car. Five solid minutes of steep, smoothish trail interrupted by water bars to hop/drop.

Sold.

The fork performed in a freaking amazing fashion on this descent, and I honestly beat the crap out of it, bashing into logs, whatever. The only time I have had a better time on this descent was on a bike too small for me with 170mm of travel. The Tractor is XC-ish compared to that bike, but that is how I ride. I was going as fast as I should ever go in relative safety. I don't need or want more.

So, the initial impression is favorable. It performs as advertised. I hope this thing performs in the long haul, and doesn't break my heart....again.

I also feel very affirmed in some of the design choices I made on the Tractor: Too long head tube...perfect. Too long Chainstays...check. Funny looking frame with loads of stand over....I used all of it multiple times. Too long top tube.....here I really think I did mess up. I think it would be better at least an inch shorter. Oh well, it is a learning process, and I have learned that I like smaller bikes given the choice.