Fairshift never worked with the BRM for me - no 6th gear, ever. Fun thing to notice in the Long Night of the Ring. Coming from GPLShift, the timing for getting the gear in is different, so I'd suggest sticking with one of the programs and not switching back and forth. If I recall correctly it's that with GPLShift you have to have the clutch pressed as you put the gear in, whereas with Fairshift you can select the gear and then push the clutch pedal down.
One (or rather another) thing that spoils Fairshift for me is that the clutch becomes a digital trigger which, at 50% percent clutch pedal range, switches between neutral and whatever gear you're in, upsetting the car.
Does the developer race like this? Are they at the grip limit in curved braking zones (Rouen Hairpin, Monaco final corner, Monsanto T5, etc)?
I don't know how a two-pedal user could experience it for themselves, but maybe mapping the clutch to one of the pedals and going to a skidpad could work.

A few years ago I targeted my Ring PBs, did some testing on a dragstrip track ("1320"), looked at the speed graphs in GPLRA and merged the laps to one file.

If the EOLC forums were still online, I could point you to the post. Here are the replays and the two rank accounts, which basically were a decade-long experiment:

http://www.mediafire.com/file/0r6hxzbqq7...7-12-27.7z/file

http://www.mediafire.com/file/19ct55e7k7...parison.7z/file

http://gplrank.schuerkamp.de/php-pub/use...howDriver=16175

http://gplrank.schuerkamp.de/php-pub/use...howDriver=29101

My recommendation is to use GPLShift with a clutch_threshold of 5 or higher. GPLRA reports shorter upshift times, but that doesn't mean there's acceleration, since the clutch is disengaged (or slipping) for longer than the duration of the gear change.
Furthermore, in a race, you won't be able to do 20 laps without missing a gear if you shift like you would during hotlapping. If you miss it on an upshift, you'll lose 5 tenths minimum. If you don't realise it and smash the throttle, you'll blow an engine after 5 to 10 times. If you miss a downshift, you'll lose engine braking and struggle to make the turn.
Fairshift is the slowest option of all in hotlapping. It's closer to a level playing field than 0 clutch could ever be, but clutch settings of 5 to 9 in GPLShift will be closest to paddles. Bear with me if my memory serves me wrong here. I can't remember the exact setting either. It might not even matter; the main point is that the clutch should be mandatory when using GPLShift.
Standing starts are another can of worms.

I'd make the argument that a clutch_threshold of 9 is slower on the straights than paddles. I never quite got my head around whether or not there was a difference under braking, since auto-blip is disabled. Essentially, left-foot brakers use low brake biases and control rear wheel rotation by trailing throttle, heel'n'toers use higher brake biases (+2% or so) and can forego trailing throttle, but have control over the amount of throttle blip and can smooth out the clutch engagement, albeit there's no truly analog clutch in GPL. It's more like 5 or 7 steps of clutch modulation, which is still better than Fairshift's on/off neutral switch.

I'm all for fairness. I'm all for realism. Having the clutch pedal rendered useless takes the fun out of it, and pacewise it doesn't even match GPLShift at settings 5 to 9.

On a sidenote, I once mentioned the idea of a force feedback gear stick that would refuse to move out of neutral when you're grinding the gears. The Fairshift developer put it on the list of ideas, but I doubt there'll be customers. If there were, we would've have had this kind of thing in LFS, rF2 or AC.

Zum Umbenennen von Exen: Da gibt's eine Alternative. Indem man VROC über GEM startet, tauscht GEM die Exen auch automatisch aus. Insofern man GEM nicht wieder aufruft und nicht über den roten Knopf schließt, bleibt das auch so.
Ich weiß nicht, ob GEM damit zurechtkäme, wenn es eine Exe, die mit 60FPSv2 und Long-Track gepatcht ist, als Input bekommt und anhand dessen dann die Exe einer Mod, die mit einem der beiden Features inkompatibel ist, basteln soll. Es käme auf den Versuch an oder halt auf den Nutzer, der keine Mods fährt oder sich erinnert, dass er die Exen umbenannt hatte.


@Ranch Du könntest eventuell noch den GPL Patch Inspector befragen. Der untersucht die Installation unter anderem darauf, ob die Inis im richtigen Format gespeichert sind und ob der Bandwidth-Patch installiert ist. Zu finden ist der Inspector in GPLPS-Installationen im Ordner gpl\repository\Tools\GPLInspect\ oder hier: http://srmz.net/index.php?showtopic=2468
Randbemerkungen: Die Bandwidth-Settings an sich werden nicht überprüft, nur der zugehörige Programmcode. Wenn die Cars-Behind-Komponente beim BW-Patch nicht aktiviert ist, ist das okay. Und der Inspector kann GPL v1.3 von v1.2.0.2 nicht unterscheiden.



Bei einer GPLPS-Installation sollte standardmäßig alles i.O. sein. Ich schließe mich da allem, was bisher gesagt wurde oder in den geposteten Core.inis unter "Communications" und "Task" steht, an. Diese Inis stimmen da mit jener von GPLPS ohnehin überein.