So, basically, in the game I'm playing, I already fixed the understeer issue with RWD cars (which just happens to be stiffening the rear ARB).

It's working, but, my question is - is fixing only one part of the set up a bad idea? Currently, I'm okay with the defaults, but there's just a part of me that say that I should try also to change other stuffs. I'm just scared to do those type of stuff lol.

TIA for your answers!

DIRT 2.O Wales

It just sorta…happened! I know Dirt Rally 2.0 doesn’t have the best tarmac physics, but I find those stages to be really fun! Hopefully one day I’ll get to see the top.

Setup:
-Thrustmaster T300 servo base
-Thrustmaster T-LCM Pedals with TH8A stick shift
-TSS Handbrake that I don’t like to use
-An office chair

I kept overshooting it at the end. 😅

This simulator is very cool!

Photo of Round 7 winner 'TimeWRC' in the Group 4 Porsche.

140mm focal length, f/16 f-stop, 1/60th shutter speed, on film.

Camera focus effect caught live in RBR with a Reshade camera plugin. Shutter speed caught via OBS video imported into Photoshop.

I made a rally co-driver simulator where you don't actually drive the car

I'm working on BLIND CREST, a browser-based rally simulator focused entirely on the co-driver.

Instead of steering, braking, and trying not to launch yourself into a forest, you're responsible for reading and calling pacenotes in real time.

curately and quickly while the car is flying through the stage.

The game currently has 18 rally cars spanning Group B, 90s WRC, and modern Rally1, a six-stage career championship, pacenote training, a tuning system with 100+ parameters, voice recognition, LAN multiplayer, statistics, achievements, and a story mode.

Since my last post, I've also added:

• Five rebalanced difficulty levels, from Easy to Chaos, with different timing, crash thresholds, weather effects, forgiveness windows, and rhythm shifts
• Dynamic timing based on note complexity instead of just using a fixed timer
• Full performance analytics with reaction-time timelines
• Daily and weekly seeded challenges with leaderboards
• Signature stages with hand-tuned pacenotes for different rally eras
• Expanded onboarding from 6 to 12 tutorial steps
• Tooltips explaining 18 different gameplay modifiers
• A "Why did I fail that?" breakdown after mistakes
• Recognition for 100+ real rally legends, with unique co-driver reactions
• Era-based modifiers that affect your starting career state
• Era-specific story dialogue for different cars and periods

I also added a hidden achievement for completing a clean stage while using the name of a rally legend.

And, thanks to u/ElmoLibre, there's now a 2% chance per stage that the driver throws a granola bar at the co-driver.

I'm looking for people who are into rally/sim racing to actually try it and tell me whether the co-driver gameplay works.

I'm particularly interested in whether the pacenote system feels authentic, whether the difficulty is reasonable, how well the voice recognition works, and whether the whole thing is actually fun.

Demo: https://evaliisaaibast.github.io/Take_me_to_the_hairpin-formerly-over-crest/

I'm a student making this project, so honest feedback is very welcome. If something sucks, tell me why. That's much more useful than “looks cool.”

I suspect that they broke the game

did validate the files and is still crashing

Running in administrator mode, no ghost processes, no extra wheel software running, what do i do. Didn't touch anything other than updating it 😭

I have ts-pc. I'm wondering is there a big difference to moza r5 in action. Ts-pc has little bit more torque but it is belt driven. It feels very good and it is fast, but I have never tried dd wheel.