@hitm4k3r @Dockxys
Still not taking away from the post above which is absolutely valid, and the lack of movement in this area of rF2 since release is frustrating. But while there's a workaround available it's worth helping to make it work because, well, there's the workaround or nothing.
On the Gearshift
releases page, grab the Grind_default.wav file, then go down to release 1.5.27 and grab the 2 .exe files. Put all 3 files somewhere accessible and safe.
Here's mine under a folder in rF2, hadn't grabbed the .wav file yet:
View attachment 41239
Then you want to run 'Configurer' , which will appear with nothing set:
View attachment 41240
Select your shifter controller, then for each of your gears (including Reverse) click the corresponding button, select the gear on your controller, then press Ok. It should show the button number. If it doesn't pick it up, wait a second or two after selecting the gear before hitting Ok. If it still doesn't work, check you've selected the correct controller.
Then do the same for the Clutch controller, hit Select clutch, press your clutch pedal, and hit Ok. Again it should show the axis number.
Then, for the moment, change Clutch bite point to 50. Hit Save configuration.
Here's what mine looks like at this point (note I have different controllers for gears and clutch):
View attachment 41241
You should have a gearshift.ini beside the other files now (from hitting save), and it should look something like this if you open it:
View attachment 41242
You can close the Configurer and its command window now.
It's now ready to test outside of the game, just to make sure it's configured correctly and adjust if necessary.
To do that, run Gearshift.exe. A command window should appear confirming the configured controllers and its status, so then open a Notepad window to test. Like this:
View attachment 41243
Now, time to see what it does. Without pressing your clutch, move the gear stick into gear. You should hear a 'grinding' (if you have the .wav file) and see zeroes appearing in notepad as long as you leave the stick in gear. Like so:
View attachment 41244
If you don't see any zeroes appearing, the clutch may be backwards (it's expecting up to be down, and vice versa). In that case, open up the gearshift.ini and change
reversed to 1 like this:
View attachment 41245
(Note: not 'reverse' - that's an error on this build of gearshift. Ignore that one)
Save that file, then restart gearshift (close the window, then run it again). You should now get the expected behaviour. Depending which way is which you may need to press and release the clutch once to get things in the right state.
At that point, you will find that if you press the clutch all the way before engaging a gear, nothing happens. If you don't press the clutch you'll get the grinding (and zeroes), at which point you'll need to centre the stick and re-engage the gear with the clutch pressed in order to avoid more grinding when you release the pedal. (just pressing the clutch pedal will stop the grinding - but you're now pressing the clutch and would have no power applied to your wheels. Release the clutch and the grinding will return. So you need to centre the stick at some point...)
I set the clutch bite point to 50 initially as it's best to avoid any potential deadzone when setting it up; at this point you'll probably want to adjust it. 50 is pretty forgiving, almost to the point of making the whole process a waste of time. I ended up around 90 which means I need the clutch nearly fully down to successfully engage a gear, and this also matches the way the game works (the bite point is very low on the pedal). If you had to reverse the clutch you may need lower values instead - I'm not sure which way it works. Just experiment a little with Notepad while gearshift is running.
If you've got to this point, you're just about all set. You can go into rF2, assign Numpad 0 to the Neutral control, and drive with the shifter knowing you can't get away with cheating (I highly recommend testing that it's actually operational when you first jump in the car in a session - throw it in gear without a clutch and confirm you have grinding. A few times I did a number of laps and then realised I'd forgotten to run it...).
You can of course choose a different control for it to press for Neutral, and configure rF2 to the same control. Again for initial testing purposes the default Numpad0 works well. If you can't get some other key to work it's something about that key, rather than the program, as long as you got Numpad0 working first.
It's not perfectly realistic: you can't rev match, it doesn't know what the current car can and can't do. Tony did talk about adding some support for different drivetrains but I imagine the lack of data you can get from the game makes this unappealing. It would absolutely be much much better for the game to handle this itself and have some vehicle parameters that help define the behaviour, but if you actually want to use a shifter properly this is what we've got right now. And having it 'right now' is, in rF2 terms, a pretty good thing.