Simwiki.net - Recent changes [en]

User:Shovas

Shovas — Wed, 06 May 2026 00:00:11 GMT

Scratchpad

← Older revision		Revision as of 00:00, 6 May 2026
Line 147:		Line 147:

	<pre><nowiki>		<pre><nowiki>
			==
			260505

			This might apply to GTR2:

			>>>
			Extra: Weather parameters in your GDB files:
			Instead of typing out numbers, you can type out predefined preset-words.

			Here's a list of them all:
			Conditions=Best is the same as Conditions=3.0
			Conditions=Nice is the same as Conditions=30.0
			Conditions=Clear is the same as Conditions=60.0
			Conditions=Overcast is the same as Conditions=65.0
			Conditions=Drizzle is the same as Conditions=73.0
			Conditions=Rain is the same as Conditions=85.0
			Conditions=Monsoon is the same as Conditions=97.0
			CONDITIONS GOES IN THE RANGE FROM 0 TO 100!

			TrackWetness=Dry is the same as TrackWetness=0.0
			TrackWetness=Damp is the same as TrackWetness=25.0
			TrackWetness=Wet is the same as TrackWetness=50.0
			TrackWetness=Soaked is the same as TrackWetness=75.0
			TrackWetness=Monsoon is the same as TrackWetness=100.0
			SAME FOR OnPathWetness AND OffPathWetness!
			WETNESS GOES IN THE RANGE FROM 0 TO 100!

			AmbientTemp=Hot is the same as AmbientTemp=32.5
			AmbientTemp=Warm is the same as AmbientTemp=26.25
			AmbientTemp=Medium is the same as AmbientTemp=20.0
			AmbientTemp=Cool is the same as AmbientTemp=13.75
			AmbientTemp=Cold is the same as AmbientTemp=7.5
			SAME FOR TrackTemp!
			<<<

			-Matty (AMS1 QOL Discord)

			https://discord.com/channels/968392089450737674/1499161523837210815/1501181902848000071

	==		==
	260108		260108

Sunshine and Moonlight

Shovas — Sun, 03 May 2026 23:29:23 GMT

Resources

← Older revision		Revision as of 23:29, 3 May 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== What is Sunshine and Moonlight? ==		== What is Sunshine and Moonlight? ==

	~~todo~~		* ''Moonlight allows you to play your PC games on almost any device, whether you're in another room or miles away from your gaming rig.''
			* ''Moonlight (formerly Limelight) is an open source implementation of NVIDIA's GameStream protocol. We implemented the protocol used by the NVIDIA Shield and wrote a set of 3rd party clients.''
			* ''You can stream your collection of PC games from your gaming PC to any supported device and play them remotely. Moonlight is perfect for gaming on the go without sacrificing the graphics and game selection available on PC.''

			[https://moonlight-stream.org/]

			== Resources ==

			* Homepage: https://moonlight-stream.org/
			* Download: https://moonlight-stream.org/

	== Guides ==		== Guides ==

3DSimEd

Shovas — Sun, 03 May 2026 19:19:49 GMT

Tips and Tricks

@@ Line 443: / Line 443: @@
 -Driver59
 </nowiki></pre>
 == Issues ==

Sunshine and Moonlight

Shovas — Sun, 03 May 2026 18:54:05 GMT

Created page with "== What is Sunshine and Moonlight? == todo == Guides == === First Steps Setting Up A Game To Stream Successfully === These steps assume your Sunshine-Moonlight streaming is already setup and operating fine. # Start the game on the host with any controllers and peripherals it will eventually need when streaming #* At this step, you are just testing the game starts with your peripherals locally fine before trying over streaming, to make sure everything on the host end..."

New page

== What is Sunshine and Moonlight? ==

todo

== Guides ==

=== First Steps Setting Up A Game To Stream Successfully ===

These steps assume your Sunshine-Moonlight streaming is already setup and operating fine.

# Start the game on the host with any controllers and peripherals it will eventually need when streaming
#* At this step, you are just testing the game starts with your peripherals locally fine before trying over streaming, to make sure everything on the host end is fine.
# Configure the game's display, graphics, audio, control, and other settings locally
# Play a bit of the game to ensure your controllers and other settings are operating okay
# You should now be ready to stream

''Note: These steps are a work in progress and I may add more steps over time.''

'''Notes:'''
* Locally I use a Microsoft Xbox Core controller but, when streaming, at the TV I use an [[NVIDIA Shield]] with a PS5 Controller.
** So, I test with the Xbox controller locally and usually that's enough to ensure the PS5 controller will work through the Shield (at least when running through Steam and using the Steam Input controller compatibility option)
** Steam Input controller compatibility works so well I actually import GOG games to Steam and launch them from Steam just to get access to Steam Input compatibility

'''Gotchas:'''
* '''Interfering Software'''
** [[Special K]], [[RTSS]], or other similar software may interfere with a game starting up. You'll have to fix those so the game starts okay locally before you can stream.

'''More Details:'''
* There's a lot more details over here: [[NVIDIA_Shield#Moonlight_PC_to_Shield_Streaming]]
** I started documenting Sunshine and Moonlight over there before I created this page
** Eventually, I'll probably move it all here

Main Page

Shovas — Sun, 03 May 2026 18:44:20 GMT

Sim Hardware

← Older revision		Revision as of 18:44, 3 May 2026
Line 162:		Line 162:
	** [[NVIDIA_Shield#Moonlight_PC_to_Shield_Streaming\|Moonlight PC to Shield Streaming]]		** [[NVIDIA_Shield#Moonlight_PC_to_Shield_Streaming\|Moonlight PC to Shield Streaming]]
	* Handbrakes, Button Boxes, Shakers, Fans, Dashboards		* Handbrakes, Button Boxes, Shakers, Fans, Dashboards

			== Sim Software ==

			* [[Sunshine and Moonlight]] - Stream from almost anything to anything else over lan or wifi. A console killer PC-to-TV solution. Compatible with PC/Mac/Linux/Android.

	== Sim Clothing ==		== Sim Clothing ==

RFactor 1

Shovas — Sat, 02 May 2026 00:38:23 GMT

Hacking

@@ Line 177: / Line 177: @@
 * [http://www.tirewall.net/mh-rf2/archive/isi_mod_tut/index.html rFactor Modding Documentation] - "This is basically a backup of the old and, unfortunately, incomplete official ISI rFactor modding tutorial."
 * [https://meetme.bplaced.net/rF2_onlineTools/rF2GGeninfo/tbc_slipcurve_gen.php rF2 and rF1 TBC Slipcurve Generator] - Interesting slip curves, might be useful for various isiMotor sims
 == Cheats - Unlocks ==

Need For Speed Hot Pursuit Remastered

Shovas — Fri, 01 May 2026 17:17:26 GMT

Game won't launch (Special K or RTSS prevents launch)

← Older revision		Revision as of 17:17, 1 May 2026
Line 4:		Line 4:

	* '''tl;dr''' Completely exit Special K and/or RTSS before starting the game for the first time. After the first time, it appears to be okay to run Special K and I guess RTSS.		* '''tl;dr''' Completely exit Special K and/or RTSS before starting the game for the first time. After the first time, it appears to be okay to run Special K and I guess RTSS.
			* '''Workaround:''' [[Special_K#Disable_Special_K_Per_Game]]

Special K

Shovas — Fri, 01 May 2026 03:26:02 GMT

@@ Line 41: / Line 41: @@
 ** Doesn't have anti-cheat so it's not that
 ** I assume it's something like [[RTSS]]'s 'detection level' that can conflict with some games
 == Troubleshooting ==
 === SDR Image Looks Washed Out (Not related to HDR) ===

Main Page

Shovas — Fri, 01 May 2026 03:25:39 GMT

Sims

← Older revision		Revision as of 03:25, 1 May 2026
Line 22:		Line 22:
	** [[BeamNG.drive]]		** [[BeamNG.drive]]
	** [[BMW M3 Challenge]]		** [[BMW M3 Challenge]]
			** [[Burnout Paradise]]
	** [[Copa Petrobras de Marcas]]		** [[Copa Petrobras de Marcas]]
	** [[Dirt Rally 2.0]]		** [[Dirt Rally 2.0]]

NVIDIA Shield

Shovas — Wed, 29 Apr 2026 14:15:45 GMT

Troubleshooting

← Older revision		Revision as of 14:15, 29 April 2026
(3 intermediate revisions by the same user not shown)
Line 40:		Line 40:
	==== Even later, now pushing 4K60 on the same hardware ====		==== Even later, now pushing 4K60 on the same hardware ====

	* I have since upgraded from 1440p to 4K and I'm now streaming 4K native at 60fps using ~~80Mbit~~/sec bandwidth with virtually flawless framerates and frame pacing		* I have since upgraded from 1440p to 4K and I'm now streaming 4K native at 60fps using 40Mbit/sec bandwidth with virtually flawless framerates and frame pacing
	* I was experiencing multi-second stutter, that I think the move to 4K introduced, but since moving from the '''Smoothest''' Frame Pacing to the '''Balanced With FPS Limit''' Frame Pacing, I believe that issue is solved or at least much improved now. It was really harming my experience in V-Rally 4 and WRC 9 but now it is virtually flawless.		* I was experiencing multi-second stutter, that I think the move to 4K introduced, but since moving from the '''Smoothest''' Frame Pacing to the '''Balanced With FPS Limit''' Frame Pacing, I believe that issue is solved or at least much improved now. It was really harming my experience in V-Rally 4 and WRC 9 but now it is virtually flawless.
	* Setting '''HEVC/H.265 codec''' was required after upgrading to 4K to avoid maxxing out the 3080 encoders and suffering performance problems		* Setting '''HEVC/H.265 codec''' was required after upgrading to 4K to avoid maxxing out the 3080 encoders and suffering performance problems
Line 235:		Line 235:
	* Try [[Special K]] if you're using [[RTSS]]		* Try [[Special K]] if you're using [[RTSS]]
	* You may experience better framerate limiting and better framepacing for a smoother visual fluidity experience		* You may experience better framerate limiting and better framepacing for a smoother visual fluidity experience
	* Special K can also enforce refresh ~~ratess~~ which RTSS cannot do. This may help for some video games.		* Special K can also enforce refresh rates which RTSS cannot do. This may help for some video games.

	==== 4K May Require HEVC/H.265 Over H.264 ====		==== 4K May Require HEVC/H.265 Over H.264 ====
Line 289:		Line 289:

	=== Troubleshooting ===		=== Troubleshooting ===

			==== RTSS (RivaTuner Statistics Server) Framerate Limiter May Be Causing Stuttering ====

			* '''tl;dr''' Try [[Special K]]'s framerate limiter, or the limiter in the NVIDIA Control Panel, and see if it provides a smoother stream
			* See [[#Special K may provide a better experience compared to RTSS]]

	==== Potential Fixes for Stuttering After Narrowing Down To Host Differences Between Games ====		==== Potential Fixes for Stuttering After Narrowing Down To Host Differences Between Games ====

Need For Speed Hot Pursuit Remastered

Shovas — Tue, 28 Apr 2026 02:30:24 GMT

Created page with "== Troubleshooting == === Game won't launch (Special K or RTSS prevents launch) === * '''tl;dr''' Completely exit Special K and/or RTSS before starting the game for the first time. After the first time, it appears to be okay to run Special K and I guess RTSS."

New page

== Troubleshooting ==

=== Game won't launch (Special K or RTSS prevents launch) ===

* '''tl;dr''' Completely exit Special K and/or RTSS before starting the game for the first time. After the first time, it appears to be okay to run Special K and I guess RTSS.

Main Page

Shovas — Tue, 28 Apr 2026 02:29:09 GMT

Sims

← Older revision		Revision as of 02:29, 28 April 2026
Line 35:		Line 35:
	** [[Le Mans Ultimate]]		** [[Le Mans Ultimate]]
	** [[Live For Speed]]		** [[Live For Speed]]
			** [[Need For Speed Hot Pursuit Remastered]]
	** [[PISTA Motorsport]]		** [[PISTA Motorsport]]
	** [[Project Cars]]		** [[Project Cars]]
Line 45:		Line 46:
	** [[rFactor 2]]		** [[rFactor 2]]
	** [[Richard Burns Rally]]		** [[Richard Burns Rally]]
			** [[Rush Rally 3]]
			** [[Rush Rally Origins]]
	** [[Shift 2 Unleashed]]		** [[Shift 2 Unleashed]]
	** [[Test Drive: Ferrari Racing Legends]]		** [[Test Drive: Ferrari Racing Legends]]

User:Shovas

Shovas — Thu, 23 Apr 2026 13:48:58 GMT

Notepad

← Older revision		Revision as of 13:48, 23 April 2026
Line 106:		Line 106:

	<pre><nowiki>		<pre><nowiki>
			==
			260423

			Tips for publishing mods or tools that help users onboard more easily:
			- Remember to keep it as simple as possible or or regular users will be overwhelmed and won't know how to approach it
			- If I can make some suggestions, I would rework the forum post with a brief description of the problem it solves, a brief point form overview of how to get it and run it, and a brief point form overview of how to use it, a more complete point form how to (maybe split up into major functionalities with screenshot thumbnails for illustration), and the bonus would be a tutorial video
			- Although I don't always follow my own advice on Simwiki, I'm always trying to ease users into something by starting them out with the biggest win with the smallest upfront cost, and then introduce them to more advanced usage. That's the idea behind leading with an overview and then diving in to bigger sections after.
			- Lead with download links, too, it's what end users are looking for. It always bugs me when I'm looking at a car/track mod and the link is hidden at the bottom or in between screenshots.

	==		==
	250823		250823

Development.txt for SHO Competition AI

Shovas — Fri, 17 Apr 2026 01:54:47 GMT

← Older revision		Revision as of 01:54, 17 April 2026
Line 1:		Line 1:
			* Development.txt from [[SHO Competition AI]] (V14)
			* Included here to make the AI tuning details openly accessible on the web

	<pre><nowiki>		<pre><nowiki>
	SHO COMPETITION AI		SHO COMPETITION AI

SHO Competition AI

Shovas — Thu, 16 Apr 2026 14:51:30 GMT

Download

← Older revision		Revision as of 14:51, 16 April 2026
Line 12:		Line 12:
	* [https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])		* [https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])
	* [[README SHO Competition AI.txt]] - Putting online to make the AI tuning details openly accessible on the web		* [[README SHO Competition AI.txt]] - Putting online to make the AI tuning details openly accessible on the web
	* [[Development.txt for SHO Competition AI]]		* [[Development.txt for SHO Competition AI]] - Many valuable testing details about various AI tuning parameters

	== Discussion ==		== Discussion ==

Development.txt for SHO Competition AI

Shovas — Thu, 16 Apr 2026 14:50:53 GMT

Created page with "<pre><nowiki> SHO COMPETITION AI DEVELOPMENT Version 14 (2022-06-20..2023-06-11) - DONE: [Location AIW RaceRatio] Imola RaceRatio is tuned too high. I couldn't pass one car in 10 minutes even after setting better-than-qualifying PBs multiple times. - [README] Removed instructions to set tuned AI Realism (Aggression) value. No need to have a tuned value here anymore. Users can set their own Aggression according to their own preference. - DONE: [PLR] Reconsider Psycho..."

New page

<pre><nowiki>
SHO COMPETITION AI

DEVELOPMENT

Version 14 (2022-06-20..2023-06-11)

- DONE: [Location AIW RaceRatio] Imola RaceRatio is tuned too high. I couldn't pass one car in 10 minutes even after setting better-than-qualifying PBs multiple times.

- [README] Removed instructions to set tuned AI Realism (Aggression) value. No need to have a tuned value here anymore. Users can set their own Aggression according to their own preference.

- DONE: [PLR] Reconsider Psychotic AI realism? Not sure it'll help, maybe I'm just too slow for some faster AI. Initial with Timid and Angry vs Psychotic didn't seem to affect qualifying laptimes. Try this after last change...

- DONE: Checked Magny-Cours National with GT cars on Real Aggression. AI were competitive and behaved fine.

- DONE: Checked Imola with GT Cars and Angry Aggression. AI were just as competitive as always.

- DONE: Update README instructions and PLR references to tuned AI Realism value

- DONE: [Location AIW RaceRatios] Check AIWs with RaceRatio < 1.0 (seems odd). Barcelona GP 2003 (FIXED), Oschersleben 2003 (FIXED), Magny-Cours National (FIXED), Anderstorp South (FIXED)

- DONE: Barcelona GP 2003: Seems I used an incorrect RaceRatio that didn't match what was in the tuning spreadsheet.

- DONE: Check Barcelona National: OK. Q: 1:06.886. It's okay now with the proper value from the spreadsheet.

- Was RaceRatio=1.021493813 <-- didn't match spreadsheet RaceRatio=1.1025

- DONE: Oschersleben 2003: OK. PB: 1:23.209. 12th to 8th in 8 laps (10min).

- Was RaceRatio=0.997172531 <-- Didn't match spreadsheet RaceRatio=1.07625

- DONE:: Magny-Cours National: OK. PB: 0.53.540, Q9, 9th until half way (lap 12 or so) when I got lucky with an accident and got to 4th place, that was hard to keep pace with and 5th and behind kept up really close.

- Was RaceRatio=0.997172531 <-- Spreadsheet: 1.07625

- DONE: Anderstorp South: OK. PB: 0:46.553, Q15, 15th to 9th in about 10mins. Could be better but it's okay for now.

- Was RaceRatio=0.990947441 <-- Spreadsheet: 1.06953125

- SCRATCH: Passing too many at Barcelona GP 2003 (33 to 17 after 4 laps). Related to Aggression change from Psychotic to Real? Trying again on Psychotic...no, doesn't seem like it: 9th to 4th in 3 laps on Psychotic.

- SCRATCHED: Doesn't seem to be about Aggression. Fixed with RaceRatio changes above.

- DONE: AI are too strong right off the start as if they don't have to deal with cold tires. Bring back ColdBrain params?

- DONE: RaceColdBrainMin back to RCD original values (instead of all just 1.00). Original values varied between about 0.93 to 0.98, most being 0.94 to 0.96 from what I can see.

- Done: RaceColdBrainTime=45 (previously 0, default 120)

- DONE: Test RaceColdBrainTime=45. May need to change it if it feels off in an actual race.

- Honestly, hard to tell the change here, but I'm happier to be back to or closer to default values.

- [MOD] Renamed MODS\SHO Competition AI\Release Notes.txt to Releases.txt

- [Experiment] Investigated AI Max Load (AI aggression / chance of attempting passes) might be a helpful AI tweak in the future to liven up AI
- Experiment 1: GT's 2004 at Spa 2004
- 0.1 (min): 2:11.911
- 31,500: 2:12.764
^ https://github.com/dbkblk/race07-smartai
- 40,000 (default): 2:12.715
- 1,000,000 (!?): Slower (2:22, +10sec vs 0.1)
- 10,000,000: (2:21)
- 100,000,000: Same
- 1,000,000,000: (2:20)
- 10,000,000,000: (2:21)
- Experiment 2: GT's 2004 at Valencia National
- 0.1 (min): AI1: 1:10.247 (AI100), SB: 1:10.215), Q: 1:10.215, P: 16, ...
- Lot more crashes (mistakes?), a lot more going wide
- 31,500: AI1: 1:10.221 (AI102), AI1: 1:09.839 (AI106), SB: 1:10.100, Q: 1:10.268, P: 21, ...
- Far more normal vs 0.1, far less going wide (none?), less crashes
- https://github.com/dbkblk/race07-smartai
- 40,000: AI1: 1:09.437 (AI100), SB: 1:10.356, Q: 1:10.356, P: 18, ...
- Similar to 31,500
- 80,000: AI1: 1:09.300 (AI110), SB: 1:10.003, Q: 1:10.003, 14, P: ...
- Result:
- Performance: AI Max Load seems like a universal version of AIW RaceRatio. It can increase or decrease an entire field's performance.
- Behaviour: Lower AI Max Load values increase crashes (mistakes?) and going wide while higher values decrease crashes (mistakes?) and going wide
- Updated GTR2 Glossary

- [README] Fixed incorrect Composure value in the manual installation step 2b for Composure. Not a problem if you never used the manual install steps.

Version 13 (2022-06-16..2022-06-20)

- [Testing] Further testing of V13-test2's Composure tuning

- OK: GT 2003: Specials GT's 2003, Chrysler Viper GTS-R, Zuhai GP 2004, AI 100 [SB: 1:30.572, Q: 1:30.572, P: 14, F: 16 (crashed; got up to 8th)]
- OK: GT 2004: Specials GT's 2004, Ferrari 575, Valencia GP 2004, AI 104 [SB: 1:30.032, Q: 1:30.032, P: 14, F: 8]
- OK: NGT 2003: Specials NGT's 2003, Porsche GT3-RS, Imola GP 2004, AI 100 [SB: 1:53.450, Q: 1:53.450, P: 22, F: 16]
- OK: NGT 2004: Specials NGT's 2004, Porsche GT3 RSR, Oschersleben GP 2004, AI 100 [SB: 1:28.404, Q: 1:28.404, P: 6, F: ]

- [MOD] Corrected accidental copy&paste references to "SHO GTR2 XD Style SimHub Overlays"

Version 13-test2 (2022-04-15..2022-06-16)

- [Composure] Increasing Composure in V13-test1 resulted in undesirable retuning of RaceRatio for what seemed like every track. Instead, try a universal decrease of RaceRatio to retain it alreacy custom values from V12. The mistake in V13-test1 was resetting to default RaceRatio and simply adding a static percentage to it thus losing the custom tuning of V12. Instead, this version retains the custom tuning and just decreases the AI performance by tuning AIW RaceRatio with a universal value which will keep the custom tuning of V12 and hopefully prevent having to retune from scratch for each track.

- Problem: Can no longer keep pace with AI who you qualified close to after V13-test1's Composure increase

- Theory: Increased Composure in V13-test1 also increased general AI performance (ie. AI more confident more of the time so they perform better on the whole)

- Experiment: Reduce AI performance by decreasing RaceRatio ideally by a universal amount (ex. -2%)

- Result: OK. Main tests feel decent. I think we're back to V12 quality AI performance with V13-test1's Composure enhancements.

- Testing:

- OK: Specials GT 2004, Lamborghini Murcielago R-GT, Monza GP 2003, AI 96 [Q: 1:45.036, P: 20]

- OK: Specials NGT 2003, Porsche GT3-RS, Valencia National, AI 119 [SB: 1:14.996, Q: 1:15.259, P: 24, F:19]

- OK: Specials NGT 2004, Ferrari 360 Modena, Oschersleben GP 2004, AI 102 [SB:1:29.387 , Q: 1:29.479, P: 18, F: 17]

- OK: Specials GT 2003, Lister Storm, Oschersleben B Course, AI 100 [PB: 0:59.540, SB: 0:59.540, Q: 0:59.540, P: 19, F: 10]

- [License] Added Creative Commons Attribution Non-Commercial License. README updated. License details:

SHO Competition AI © 2021 by Shovas is licensed under Attribution-NonCommercial 4.0 International: http://creativecommons.org/licenses/by-nc/4.0/

SHO Competition AI © 2021 by Shovas is licensed under CC BY-NC 4.0: http://creativecommons.org/licenses/by-nc/4.0/

- [MOD] Split out README Plans section to MODS\SHO Competition AI\Plans.txt

- [Composure Testing] Checking more tracks after V13-test1's Composure + RaceRatio change. This was just testing more tracks using V13-test1's changes - not actually making any new changes here.

- Scratched: I didn't like this approach as it was resulting in effectively retuning every single track again.

- OK: GT 2003: Specials GT's 2003, Chrysler Viper GTS-R, Zuhai GP 2004 [PB: 1:31.000] [Q: 1:31.650]
- Passed 1 lap 2, passed 1 lap 3, passed 1 lap 4, passed 1 lap 5, P20 by lap8/10min, staying with pack ahead, pack behind staying close, couldn't quite pass pack ahead, P23 to P20 by 15min
- OK: GT 2004: Specials GT's 2004, Ferrari 575, Valencia GP 2004 [PB: 1:29.880] [Q: 1:30.795]
- Passed 1 lap 2 (P12), passed 1 lap 3 (P10), crashed back to P27 lap 3, passed 1 lap 3 (P26), passed 2 lap 5 (P24), passed 1 lap 6 (P23), crashed back to P28, quit, pack ahead and behind good
- Observation: Cars far back in the field are very competitive even if you qualified much further ahead then them. Not sure if really realistic or good or bad. When you crash back at least you have some hard racing left to do.
- Theory: They gain Composure from passing you and start doing perfect laps?
- NGT 2003: Specials NGT's 2003, Porsche GT3-RS, Imola GP 2004 [PB: 1:51.690] [Q: 1:53.667]
- OK: Passed 1 lap 3 (P22), caught up to pack (lap 9), could have passed more but crashed lap 9 (P25)
- NGT 2004: Specials NGT's 2004, Porsche GT3 RSR, Oschersleben GP 2004 [PB: 1:29.003]
- Passed 1 lap 3 (P14), crashed lap 5 but was keeping up and could have passed in a few laps

- Other Tests:
- G3 2003: BMW Z3 at Imola GP 2004 [PB: 1:57.826]
- G3 2004: Viper Competition Coupe at Brno GP 2004 [PB: 2:07.114]
- GT3 Cup 2003: Porsche 911 GT3 Cup at Donington GP 2004 [PB: 1:36.027]
- NGT 2004: Specials NGT's 2004, Ferrari 360 Modena, Anderstorp GP 2003 [PB: 1:33.953]
- ...

- NGT 2004: Specials NGT 2004, Porsche GT3-RS, Anderstorp South [Q: 0:49.800]
- NOK: P14 to P4 by lap 8 (5min)

Version 13-test1 (2022-03-08..2022-04-14)

- [Oschersleben GP 2004] Tuning RaceRatio to Qualifying performance as I couldn't keep up

- Problem: AI drive faster when they're ahead of you and slower when they're behind you. This results in AI being harder to catch up to when you're behind them even when you qualified ahead of them. It also results in AI falling farther behind when you pass them than they should even though they qualified ahead of you. Ideas: RCD Composure(?), PLR Player Car Equal(?), PLR AI Max Load(?), ...

- Theory: AI Composure results in AI feeling more confident (faster) when ahead of you versus less confident (slower) when behind you

- Experiment: Try bisection searching Composure

- Reminder: AI Speed Ahead/Behind (Composure) is not the same as keeping up with AI (RaceRatio). AI keeping close to you (Composure) is okay but if you can't keep up to qualifying neighbour positions than you need to tune RaceRatio.

^ I don't think increasing Composure is increasing AI performance (ie. RaceRatio) but AI performance does feel off now.

^ Theory: Higher Composure is making AI more confident more of the time. When they have higher confidence level (when they are ahead of you) they are faster but when they have a lower confidence level (when they are behind you) they are slower.

- Result:

- OK: Specials GT 2004, Lamborghini Murcielago R-GT, Monza GP 2003 [Q: 1:44.912, P: 15]

- DONE: Retuned RaceRatio as I wasn't keeping up to qualifying neighbours

- DONE: +2.5%: Good

- OK: Specials NGT 2003, Porsche GT3-RS, Valencia National [Q: 1:15.079]

- SCRATCH (will try tuning RaceRatio): Note: No RaceRatio tuning here because it's where I tuned Composure

- TODO: +2.5%: Good

- OK: Specials NGT 2004, Ferrari 360 Modena, Oschersleben GP 2004 [Q: 1:29.698]

- DONE: Retuned RaceRatio as I wasn't keeping up to qualifying neighbours

- DONE: +2.5%: Good

- OK: Specials GT 2003, Lister Storm, Oschersleben B Course [Q: 1:00.184]

- DONE: Retuned RaceRatio as I wasn't keeping up to qualifying neighbours

- DONE: +2.5%: Good

Version 12 (2021-12-20..2021-12-20)

- Changes section renamed to Release Notes and moved to MODS\SHO Competition AI\Release Notes.txt

- Development section moved to MODS\SHO Competition AI\Development.txt

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT 2004, Lister Storm, Spa GP 2004 [Q: 2:16.763]

- OK: Specials NGT 2003, Porsche GT3-RS, Valencia National [Q: 1:15.602]

- OK: Specials NGT 2004, Porsche GT3-RS, Valencia Long [Q: 1:55.763]

Version 11 (2021-12-18..2021-12-19)

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT 2004, Lamborghini Murcielago R-GT, Monza GP 2003 [Q: 1:45.072]

- OK: Specials NGT 2003, Ferrari 360 Modena, Monza Junior [Q: 0:55.124]

- OK: Specials NGT 2004, Ferrari 360 Modena, Oschersleben GP 2004 [Q: 1:29.799]

- OK: Specials GT 2003, Lister Storm, Oschersleben B Course [Q: 0:59.295]

Version 10 (2021-12-16..2021-12-17)

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT 2003, Ferrari 575 GTC, Dubai Club [Q: 0:59.034]

- OK: Specials GT 2004, Ferrari 575 GTC, Dubai International [Q: 1:32.053]

- OK: Specials NGT 2003, Porsche GT3-RS, Dubai National [Q: 1:25.707]

- NOK (AI Broken): Hockenheim National

- NOK (AI Broken): Hockenheim Short

- OK: Specials NGT 2004, Nissan 370Z, Magny-Cours GP 2003 [Q: 1:42.790]

- OK: Specials GT 2003, Lamborghini Murcielago R-GT, Magny-Cours National [Q: 0:53.381]

Version 9 (2021-12-09..2021-12-16)

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT 2003, Chrysler Viper GTS-R, Anderstorp South [Q: 46.977]

- OK: Specials GT 2004, Chrysler Viper GTS-R, Barcelona National [Q: 1:07.780]

- OK: Specials NGT 2003, Ferrari 360 Modena, Brno GP 2003 [Q: 2:04.554]

- OK: Specials NGT 2004, Ferrari 360 Modena, Donington GP 2004 [Q: 1:33.949]

- OK: Specials GT 2003, Ferrari 550 Maranello, Donington National [Q: 1:04.227]

Version 8 (2021-12-01..2021-12-09)

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT's 2003, Porsche 911 GT2, Dubai GP 2004

- OK: Specials GT's 2004, Maserati MCI2, Spa GP 2003

- OK: Specials NGT 2003, Porsche GT3 RS, Enna GP 2003 [Q: 1:42.085]

- OK: Specials GT's 2003, Saleen S7-R, Oschersleben GP 2003 [Q: 1:23.554]

- OK: Specials NGT 2004, Ferrari 360 GTC, Estoril GP 2003 [Q: 1:41.992]

- OK: Specials GT 2004, Chrysler Viper GTS-R, Monza GP 2004 [Q: 1:45.828]

- OK: Specials NGT 2003, Porsche GT3-RS, Imola GP 2004 [Q: 1:53.128]

- OK: Specials NGT 2004, Porsche GT3-RS, Magny-Cours GP 2004 [Q: 1:41.862]

Version 7 (2021-11-29..2021-11-30)

- Problem: (Continued) Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result:

- OK: Specials GT's 2003, Lister Storm, Barcelona GP 2003

- NOK: Specials GT's 2004, Lamborghini Murcielago R-GT, Hockenheim GP 2004: Broken; Cars go around at pit speed; Even happens on my vanilla install; Not sure what's up;

- OK: Specials GT's 2004, Lamborghini Murcielago R-GT, Zuhai GP 2004

- OK: Specials NGT 2004, Nissan 350Z, Brno GP 2003

- Investigate: Do a proper bisection Search on AI Max Load to find the behaviour and the optimum point as I still think the AI get better of AI-Player collisions (ie. it effects them less than you)

- Experiment: Bi-section search AI Max Load

- Result: NOK: I had this wrong. AI Max Load isn't about collisions. It seems to have to do with AI aggression and chance of attempting passes. Might be interesting but for later.

- Experiment: Investigate Car HDC "AI Torque Stab" as I think this has to do with weight

- Result: NOK: Less than 1.0 had problems while 1.0 acted basically realistically but not sure I could tell a different between 1.0 and 1.25 (the default). So to preserve progress with AI performance tuning in races I'll just let this be for now and return to it if the need arises.

Version 6 (2021-11-25..2021-11-29)

- Problem: Cars are off qualifying pace by too much in race sessions. Results in passing too many who were faster than you in qualifying.

- Theory: Track AIW RaceRatio is not representative of AI's qualifying performance

- Experiment: Adjust Track AIW RaceRatio to better represent qualifying performance

- Result: OK - Not perfect but much, much better than default.

- Specials NGT's 2004, Porsche GT3 RSR, Anderstorp GP 2003: OK

- Specials NGT's 2003, Ferrari 360 Modena, Valencia GP 2004: OK

- Specials GT's 2003, Chrysler Viper GTS-R, Donington GP 2003: OK

Version 5 (2021-11-25..2021-11-25)

- Investgate: "AI to AI Collision Rate" (Default 20, V1 40) might be impacting AI in some way. Like perhaps 40 is too complex and results in wonky AI decisions. So try a bisection search to understand how it's effecting AI.

- Experiment: Bi-section search and note observations

- Result: NOK: It's not obvious going above the default (20) actually helps. So leave it at 20 for now.

- 1 (Min): Oddly not as bad as you would think. Yes they touch a little bit more on starts and first corner but after that it's a touch once in a while not the wreck fest you would expect.

- 40: This is my usual. They seem fine but you still get those start and T1 collisions. Not sure if other values would improve upon this but it's worth a try.

- 20: Fine, I guess. A number of touches on start and T1 but nothing crazy.

- 10: Definitely more touches on start and T1. So I guess more is better.

- 30: Less touches than 10 definitely

- 40: Weird. Plenty of touches with GT's at Valencia GP 2004, messy T1, sometimes full or near stoppages at T2. Maybe there's something up with too much of this param.

- 20: Definitely better (not saying it's perfect but better) on start and through T1

- 30: Pile up T1 the first time, second and third starts definitely slowdowns T1 and T2

- Problem: V3 Pyschotic AI Realism=2.0 results in AI ramming you from behind if you're too slow in a braking zone or corner for example but it's not really realistice

- Theory: AI Realism is too high causing AI to act more aggressive than is realistic

- Experiment: Lower AI Realism to lower AI aggression which should lower the frequency of ramming due to being slower than AI

- Result: OK: Seems like an improvement in sportsmanship

- OK: Specials GT's 2004, Ferrari 575, Valencia GP 2004

- 0.7 (Timid); Specials GT's 2004, Ferrari 575, Valencia GP 2004; Less abrupt maneuvers in straight lines where they might have side contact; Seem to run wide when you're on the inside to avoid hitting you; Maybe(?) not using full throttle (I'm overtaking cars on wide open straights I don't think I should be); They do still pass, though, when they have a clear opening, but they don't force tight passes;

- 1.35 (little bit more than Angry=1.30): This is called "Psychotic" in-game but it's very close to Angry (1.3); AI are behaving; They don't give up spots too easily; No big contacts yet; Best AI fell behind 6sec+ by mid-race but this is probably due to something else (eg. Track AIW QualRatio vs RaceRatio - problem logged)

- 1.675: Qualified first but decided to run second first lap then discovered the leader was very hard to pass in a race-worthy fashion (a good thing); Third really kept up nicely within 0.5sec; No real reckless driving to speak of; Positive experience overall, would be nice to get even more competitive with them;

- 1.8375: Passed a few but they became difficult after a while; A good improvement I think; I think I'll move on as this feels like a point of diminishing returns.

- OK: Specials NGT's 2004, Porsche GT3 RSR, Oschersleben GP 2004

Version 4 (2021-11-21..2021-11-24)

- Problem: AI fall too far behind when passed / AI never catch up after passing big pileups with AI that are definitely better than you (same root cause?) but AI that you didn't pass keep ahead of you and very competitive

- Theory: Talent RCD Composure levels too low result in loss of composure after pass and they fall behind

- Experiment: Increase Talent RCD Composure levels to reduce loss of composure after pass so they keep up

- Result: NOK: Hard to tell if there's a difference. Composure effect is very subtle or not doing anything at all.

- Test 1 (Composure=1.0): Specials NGT's 2004, Porsche GT3-RS, Imola GP 2004 / Passing cars fell behind by 1-2 seconds but seemed to be able to keep it to just 1-2 seconds / Oddly smooth T1/L1 but did notice minor errors before T1 / Boring AI?

- Test 2 (Composure=0.5): ~ / Passed a pileup, I guess they caught up

- Test 3 (Composure=0.25): ~ / Hard to say...

- Test 4 (Composure=0.001): ~ / Hard to say again...

- Test 5 (Composure=1.0, again): ~ / Just so difficult to tell if there's any change...

- Theory: Talent RCD MinRacingSkill default is too low allowing drivers to decrease in skill by an unrealistic amount (ie. 10%)

- Experiment: Increase Talent RCD MinRacingSkill to see if skill level is causing the issue when they fall behind

- Result: NOK: Once I understood MinRacingSkill + Composure and how they worked together I started tuning Composure instead (see next Theory).

- 1.0: Definitely seemed like they were 100% skill the entire time / not sure if that's absolute or relative to their own RCD parameters like Composure or RaceAbility etc

- 1.0 + Composure=1.0: Felt like they were losing composure more but they kept up after 10sec or so
- 0.0 + Composure=1.0: lol 2-3 incidents before T1 and 1 immediately after T1 / So yeah MinRacingSkill=0.0 and Composure=1.0 means basically no skill at all at times
- 0.0 + Composure=0.0: Okay, so Composure=0.0 seems to be perfect composure / Even though MinRacingSkill=0 (bad) the AI never felt like they lost their skill / So Composure = 0-100 it seems and MinRacingSkill = 0.0-1.0
- 0.90 (Default) + Composure=0.005: ...

- Theory: Talent RCD Composure default is too high (0=Perfect) causing AI to make too many mistakes and cost them time

- Experiment: Lower Talent RCD Composure so that AI make less mistakes and cost less time

- Result: OK: I think this is a decent starting point. Can come back to this later after tuning other areas.

- OK: Specials GT's 2004, Ferrari 550, Monza GP 2004; Past a few too many peopl for my liking, 11 or so, but at some point the AI got good enough and it became more and more difficult to make up spots. I think AI who had fallen far behind started catching up again after a while. If other results are OK then maybe this will have to be a starting point for a release now and improvements later.

^ Note: Ferrari 550 seems overpowered. It was overtaking everybody on straights and seemed faster through corners.

- OK: Specials GT's 2004, Ferrari 575, Valencia GP 2004; Passed 5 within a few laps and then the AI really started to put up a fight; The guy behind kept to within 1.0-1.2sec mostly.

- OK: Specials NGT's 2003, Porsche GT3-RS, Imola GP 2004; Intense race actually. Again, made up 7 spots or so starting from 17th is a little too easy than I would like but what can you.

Version 3 (2021-11-21..2021-11-21)

- Problem: AI too nice, too easy to intimidate them to let you pass (

- Theory: AI Realism too low (Default 1.0 "Real") resulting in "timid" Aim

- Theory: Talent RCD related? Aggression or Composure?

- Experiment: Bisection search AI Realism (Max 2.0)

- Result: OK; Seems like a positive change. Might have to review later if I notice too many crashes or pileups, though.

- OK: Specials GT's 2004, Ferraro 575, Valencia GP 2004

- OK: Specials NGT's 2004, Porsche GT3-RS, Imola GP 2004 [Q: 1:53.605]

- One big pile up, seems I heard Crew Chief mention more crashes than I would expect. Might be a side effect of "Psychotic" AI

- Note: This might be causing more crashes and pileups. Might have to back it off if I find it's too much of a problem.

- Problem: Still seeing slow cornering in some scenarios / tracks. Eg. GTs 2003 at Anderstorp GP 2003. Note I'm not sure I saw problematic slow cornering in other test cases. It might be Anderstorp is an outlier and requires a more specific track fix (eg. AIW lines).

- Theory: AI Corner Grip causes AI to think they don't have enough grip on corners to go faster

- Experiment: Increase AI Corner Grip to allow AI to use more grip which should allow faster cornering

- Result: Cornering speeds seem fine at tested tracks.

- OK: Specials GT 2004, Lister Storm, Zuhai GP 2004

- OK: Specials NGT's 2004, Porsche GT3-RS, Imola GP 2004

Version 2 (2021-11-20..2021-11-21)

- Problem: AI slow off green, slow first lap, etc. (ie. ColdBrain params)

- Theory: ColdBrain effect resulting in sub-optimal AI behaviour

- Experiment: Disable ColdBrain effect in Talent RCD files

- s/RaceColdBrainMin\s*=\s*(-?[\d\.]+)/RaceColdBrainMin=1.00 // DEFAULT=\1 /
- s/RaceColdBrainTime\s*=\s*(-?[\d\.]+)/RaceColdBrainTime=0 // DEFAULT=\1 /

- Result: OK; AI seem to be full speed immediately which is what I wanted.

- Note, only for Race session. ColdBrain still at default for Qualifying which is fine since you can time accelerate there. Might want to consider it for Qualifying later though just so you don't even have to do that.

- Problem: AI still sometimes braking early but also sometimes seems good (GTs 2003 at Anderstorp GP 2003)

- Theory: AI Brake Power and Brake Grip values causing AI to think they have to start braking earlier

- Experiment: Increase AI Brake Power and Brake Grip to allow AI to stop later

- Result: OK; AI braking points seem okay. Might be a little late to be realistic but it makes them competitive. Might reconsider later.

Version 1 (2021-11-19..2021-11-20)

- Tuning UserData PLR AI Brake Power and AI Brake Grip params for alleviating early braking by AI

- Tuning UserData PLR AI Corner Grip param to alleviate slow corner speed by AI
</nowiki></pre>

SHO Competition AI

Shovas — Thu, 16 Apr 2026 14:50:24 GMT

Download

← Older revision		Revision as of 14:50, 16 April 2026
(One intermediate revision by the same user not shown)
Line 11:		Line 11:

	* [https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])		* [https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])
	* [[README SHO Competition AI.txt]]		* [[README SHO Competition AI.txt]] - Putting online to make the AI tuning details openly accessible on the web
			* [[Development.txt for SHO Competition AI]]

	== Discussion ==		== Discussion ==

README SHO Competition AI.txt

Shovas — Thu, 16 Apr 2026 14:46:17 GMT

Created page with "* README from SHO Competition AI (V14) * Included here to make the AI tuning details openly accessible on the web <pre><nowiki> SHO COMPETITION AI GTR2 AI improvements for original content cars and tracks "For God so loved the world that he gave His one and only Son, that whoever believes in Him shall not perish but have eternal life." - John 3:16, Holy Bible. Visit selah.ca/free-gift to learn more. Overview: 1. Introduction 2. Install/Uninstall 3. How To Play..."

New page

* README from [[SHO Competition AI]] (V14)
* Included here to make the AI tuning details openly accessible on the web

<pre><nowiki>
SHO COMPETITION AI

GTR2 AI improvements for original content cars and tracks

"For God so loved the world that he gave His one and only Son,
that whoever believes in Him shall not perish but have eternal life."
- John 3:16, Holy Bible. Visit selah.ca/free-gift to learn more.

Overview:
1. Introduction
2. Install/Uninstall
3. How To Play Against AI
4. Tips
5. Notes
6. Known Issues
7. Open Issues
8. Testing Notes
9. Plans
10. Releases
11. Development

#
# 1. Introduction
#

SHO Competition AI Video Demonstration:

https://www.youtube.com/watch?v=pCGGOEvH4YE

SHO Competition AI is a GTR2 mod for original content cars and tracks that aims to improve the racing experience by creating greater racing immersion and realism by improving AI driver performance.

*Please see "README SHO Competition AI.txt" as it contains helpful details on install/uninstall, tips, questions, known/open issues, testing notes, changes, and development notes. You might be reading this file right now: I've included this note here for easy copy&paste to places like Race Department download descriptions

The main goals of this mod include:

- [Fix Stock AI Flaws] Improving obvious AI flaws on-track such as early braking, slow cornering, bad starts/first corners/first laps, and unrealistic crashes or collisions that all result in race performances that don't accurately represent qualifying performances

- [Improve Qualifying vs Race Performance] Furthermore, race performance should more closely reflect qualifying performance. With original GTR2 AI, you could start from the back of the field and win quite easily. Instead, the aim here is to ensure you have good, hard racing battles with opponents that qualified with similar laptimes. As such, if you qualify top 5 you might have a chance to win, but if you qualify top 10, it should be very difficult to win outright. That's just realistic. Again, the upside is good, hard battling with AI you are competitive against.

- [Keep Unique AI Personalities] Maintain original AI personalities and relative performance levels as much as possible to keep AI varied and interesting and allow rivalries to form between player and closely matched AI

Here is the latest version and changes (see Section 10 Release Notes for older versions):

Version 14 (2022-06-20..2023-06-11)

- [Tracks] Re-tuned Imola GP 2004 as it was too difficult to pass.

- [Tracks] Re-tuned some tracks that had suspicious AIW RaceRatio < 1.0 values (probably due to mis-copy&paste from spreadsheet). Tracks tuned included: Barcelona GP 2003, Oschersleben 2003, Magny-Cours National, Anderstorp South

- [Game] Aggression is now free for users to change according to preference in-game. This was the PLR AI Realism parameter.

- [Talent] Reset Talent RCD RaceColdBrainMin back to original values and RaceColdBrainTime to 45 (seconds). This was to alleviate the issue where AI don't act like they have cold tires like you right off the start and just act like they're at 100% performance instantly. This also returns a little bit more personality back to the AI as retaining as much AI personality as possible is an important goal of this mod.

- [README] Removed instructions to set tuned AI Realism (Aggression) value. No need to have a tuned value here anymore. Users can set their own Aggression according to their own preference.

- [README] Fixed incorrect Composure value in the manual installation step 2b for Composure. Not a problem if you never used the manual install steps.

- [MOD] Renamed MODS\SHO Competition AI\Release Notes.txt to Releases.txt

What does SHO stand for?

SHO is the first three letters of my username (Shovas) but also happens to be an acronym used by Ford, which stands for "Super High Output", so I feel is an appropriately fun acronym for a sim racing mod :)

Why is it called "Competition"?

The aim of my improvements is always to improve the experience for a competition context, like racing real humans or racing AI, as opposed to say just hotlapping. It's hard racing where you really have to have the best simulation to really raise the immersion and experience. That means my changes might feel better or worse for some depending on what you want but I'm always trying to be better in "competition", hence the name.

Credits

Thank you to GTR233, Von Dutch, GTR2 Reborn, SimBin, and others for assistance, input, reference, help, and inspiration in the making of this mod!

License

See MODS\SHO Competition AI\License.txt for full details.

SHO Competition AI © 2020 by Shovas is licensed under Creative Commons Attribution-NonCommercial 4.0 International. This license requires that users give credit to the creator. It allows reusers to distribute, remix, adapt, and build upon the material in any medium or format, for noncommercial purposes only. This license does not to third party materials included and used with permission: Third party materials reserve all rights.

View the full license here: http://creativecommons.org/licenses/by-nc/4.0/

You don't have to ask permission for legitimate uses. You just have to give credit.

I think this provides clarity and is a nice compromise that maintains modding freedom while protecting the people that made them from losing credit to their work and against people who would cut out authors from profit from copying it.

Contact

You can reach me, Shovas, on Race Department, European Endurance Center (EEC), F1 Classic, Trackaholics, Sim Racing Mirror Zone, eSport-Racing.de, Festbierbude.de, Koelschbierbude.de, or Altbierbude.de, or @shovas on Twitter, or my website Selah.ca.

#
# 2. Install/Uninstall
#

Notes:
- Simulation mode in-game is assumed.
- This mod assumes all other configuration params are set to default values where/when relevant. In other words, mixing with other AI mods or tweaks is not recommended and may not work well.

Steps:
1. UserData PLR Edits
2. Talent RCD File Updates

# Install

1. Edit UserData\User.PLR(*) and use the following parameter values
- Make a backup of your PLR in case you want to uninstall

Required:

AI Brake Power Usage="0.99625"
AI Brake Grip Usage="0.99437"
AI Corner Grip Usage="0.96500"

*Rationale for each param change can be found under the Notes section.

2a. Copy&Paste the \GameData\Talent\ folder into your GTR2 \GameData\ folder and allow it to overwrite the \Talent\ folder

...or...

2b Edit your GTR2 GameData\Talent *.RCD Files, load in Notepad++ or other editor, and make the following Regular Expression changes:

- Find: RaceColdBrainMin\s*=\s*(-?[\d\.]+)
- Replace: RaceColdBrainMin=1.00 // DEFAULT=\1
^ Include trailing space
- Find: RaceColdBrainTime\s*=\s*(-?[\d\.]+)
- Replace: RaceColdBrainTime=0 // DEFAULT=\1
^ Include trailing space
- Find: Composure\s*=\s*(-?[\d\.]+)
- Replace: Composure=0.12890625 // DEFAULT=\1
^ Include trailing space

3. Copy&Paste the \GameData\Locations\ folder into your GTR2 \GameData\ folder and allow it to overwrite the \Locations\ folder

- There's no real manual way to edit these files as each track is tuned with its own specific parameters (eg. RaceRatio)

# Uninstall

1a. Replace your UserData\User.PLR file with your backup

...or...

1b. Edit these default values back into your PLR:

AI Brake Power Usage="0.98000"
AI Brake Grip Usage="0.97000"
AI Corner Grip Usage="0.93000"
AI Max Load="40000.00000"
AI to AI Collision Rate="20"

2a. Extract MODS\SHO Competition AI\ORIGINALS\Original RCD Files.zip and Copy&Paste the \GameData\Talent\ folder into your GTR2 \GameData\ folder and allow it to overwrite the files

...or...

2b. Edit GameData\Talent *.RCD Files, load in Notepad++ or other editor, and make the following Regular Expression changes:

- Find: RaceColdBrainMin\s*=\s*(-?[\d\.]+) // *DEFAULT=(-?[\d\.]+)
- Replace: RaceColdBrainMin=\2
^ Include trailing space
- Find: RaceColdBrainTime\s*=\s*(-?[\d\.]+) // *DEFAULT=(-?[\d\.]+)
- Replace: RaceColdBrainTime=\2
^ Include trailing space
- Find: Composure\s*=\s*(-?[\d\.]+) // *DEFAULT=(-?[\d\.]+)
- Replace: Composure=\2
^ Include trailing space

3. Extract MODS\SHO Competition AI\ORIGINALS\Original AIW Files.zip and Copy&Paste the \GameData\Locations\ folder into your GTR2 \GameData\ folder and allow it the \Locations\ folder

- There's no real manual way to edit these files as each track is tuned with its own specific parameters (eg. RaceRatio)

#
# 3. How To Play Against AI
#

General:

- Run all sessions with default setups to avoid 'gaming' the system with for example better tires or less fuel weight than AI (I'm not exactly sure what GTR2 is doing for session specific setups, though).

^ This guidance might change in the future as I discover how it affects AI behaviour

- Always start new class/car/track combos at 100% and tune from there

- Don't take chances with the AI you wouldn't take with a human. This will enhance your experience, improve immersion, and stop you 'gaming' the race by abusing AI short-comings

Practice:

- Get Race Ready: Run laps until you're at race-level comfort with the track (ie. run multiple, qualifying-speed, incident-free laps). If you end up going much faster in the race you won't get a competitive, close, hard racing AI experience this mod intends to achieve.

Qualifying:

- Don't Skip Sesssion: Time Accelerate Instead: Do not skip the session, use time acceleration, instead, to ensure all AI get a time in. Failure to do this may result in random grid positions because some AI have not got a qualifying time in.

- Optimum Track Conditions: Go ahead and qualify immediately but be aware the track will not be warmed up or as rubbered in as it will be later in qualifying. You can often achieve better laptimes later in qualifying. Use time acceleration to go to 10-20 minutes left in qualifying and you'll have a well warmed up track that is rubbbered in and now you'll be able to achieve better laptimes.

- Save Time Finding Good AI Level: If you're too fast or too slow (ie. not the position you want to be) then note your time and run qualifying again with a different AI level using time acceleration. Compare your time against the AI and see if your time would lie where you like to qualify. Change the AI level if you're unsatisfied and repeat. You don't have to actually put in qualifying laps until you see you're at the right AI level.

- AI Level Increments And Their Effect On Laptime (not exact, probably wonky):
- 80-90: 0.5sec increments
- 90-100: 0.25sec increments
- 100-110: 0.2sec increments
- 110-120: 0.1sec increments

Race:

- Wait For Green: Jumping the Green Flag is easy and can get you an unfair advantage. Wait for it and you should accelerate realistically with the AI instead of getting ahead of them.

- Don't Pass Early: Do not try to pass too many people on the first corner or first lap. The AI is still wonky and gets jammed up on the first lap when everybody is all together so do yourself a favour and work with it. You'll be in the correct position, AI competitiveness-wise, after the first few corners or maybe the first lap, and you'll have a much better race.

^ Personally, I find it necessary not to pass at all the first lap, just maintain the position, to avoid 'gaming' the race and moving up too quickly to be realistic

#
# 4. Tips
#

- Be Race Ready: Practice until your are race ready for best race results.

- Optimum Track Conditions: Time accelerate 10-20 minutes in Practice and Qualifying to allow the track to heat up and the AI to rubber in the track so that it's at its fastest when you start driving.

- Avoid Qualifying First: You might have good results but, so far in developing this mod, I find you will probably stay ahead of the AI the entire race which means it won't be very fun. Try qualifying in the top 3 or top 5 and I think you'll have a much better race. This is something I hope the Open Issues will address in the future.

- Aim For Close Qualifying Laptimes: Aim to compete with AI who are about 0.1-0.2sec faster than you. These AI should give you a good battle. Much faster and they will pull ahead and much slower and they will fall behind.

#
# 5. Notes
#

UserData PLR Notes:

AI Power Calibration // Disallow game adjusting AI using various available parameters (power, gearing, fuel) in order to get a baseline so AI calculations can be done reliably. This may also be the param that causes AI to use less than full throttle for AI < 95. Need to confirm.
AI Additional Fuel Mult // Adjust to make sense of AI Brake Power/Grip Usage and AI Corner Grip Usage
AI Brake Power Usage // Increase/Decrease when AI brake too early/too late before corners
AI Brake Grip Usage // Increase/Decrease when AI brake too early/too late before corners
AI Corner Grip Usage // Increase/Decrease when AI are slower/faster around corners than they should be
AI Max Load // Reportedly affects AI aggression in some way...
AI to AI Collision Rate // Higher values increase AI situational awareness. In theory, they won't collide so much, but it doesn't seem to make it better when you increase it.
Vehicle Specific AI Setups // Reduce testing variables by avoiding custom AI setups (0)
AI Realism // Make the AI more aggressive, try to pass more. 0.70=Timid (Min), 0.85=Clean, 1.0=Real, 1.3=Angry, 2.0=Psychotic (Max). This value is preserved in saved sessions. So your PLR value will be overwritten by the saved value if you continue a saved session.

Talent RCD Notes:

Composure:
- Can't find GTR2 description of this param so getting pointers from games in the gMotor engine lineage
- rF1 Studio 397 (2010): "The lower the number, the higher the frequency of "intentional" mistakes (if AI Mistakes is > 0 in the playerfile). If AI Mistakes in the playerfile is set to 0.0, then the AI drivers never make mistakes. *cough* Well, mistakes that the programmer planned. "intentional" mistakes are things like, taking a turn too wide, or missing a breaking point. Increasing composure also decreases the time between bad driving zones. (also affected by the playerfile variable AI Limiter, see MinRacingSkill below)"
^ https://forum.studio-397.com/index.php?threads/rcd-talent-file.52996/
- AMS1 / Reiza (2016): "The lower the number, the higher the frequency of simulated driving mistakes from AI. It depends on 'AI Mistakes' parameter on your PLR file. Reiza uses 66-98 range. If in doubt, stick it with 90."
^ https://forum.reizastudios.com/threads/anyone-got-info-on-rcd-player-files.2941/

#
# 6. Known Issues
#

These are issues which are known to exist in the current version of the mod but are believed to be unfixable due to various reasons, such as hard-wired AI implementation, etc.

- AI Start Slowness: AI tend to be slower than you would expect off the green (start of the race). It helps to wait just a moment longer for them to get up to speed and then go for better race results.

- AI First Corner Jam: AI tend to jam up in the first corner, slowing everything down more than you would expect in real life. It helps to be less aggressive and let them get sorted out through the first few corners for better race results.

- AI First Lap Slowness: AI tend to be slower for half or more of the first lap. It helps to let them get sorted out for half the lap and then start to push after they speed up for better race results.

- Mixed-Class Wide Class Spread: In mixed-class races, per-class qualifying laptimes are spread out wider than they should be. Optimal would be < 2sec, preferably 1sec, which is the case in Single-Class races, but in mixed-class it seems to be about 4sec for 10 GT AI (20 AI total), 6sec for 15 GT AI (40 AI total), 7sec for 20 GT AI (60 AI total). For best results, use more AI rather than less. For example, prefer 40+ AI to 20 or less in mixed-class racing so there's enough of each class. Still, it's a known issue and can't be totally resolved as far as I can see, at this time.

# 6.1 GTR2-specific Known Issues

- [GTR2] Broken AI (pitlap speed around entire track) at Hockenheim GP 2004

- [GTR2] Broken AI (pitlap speed around entire track) at Hockenheim National

- [GTR2] Broken AI (pitlap speed around entire track) at Hockenheim Short

#
# 7. Open Issues
#

N/A

#
# 8. Testing Notes
#

Common Testing Parameters:
- 10am PRAC, 9am QUAL, 1pm RACE, AI 100, 30 AI, Rainfall None (20C^)

Main Tests:
- GT 2003: Specials GT's 2003, Chrysler Viper GTS-R, Zuhai GP 2004, AI 100 [PB: , SB: , Q: , P: , F: ]
- GT 2004: Specials GT's 2004, Ferrari 575, Valencia GP 2004, AI 100 [PB: , SB: , Q: , P: , F: ]
- NGT 2003: Specials NGT's 2003, Porsche GT3-RS, Imola GP 2004, AI 100 [PB: , SB: , Q: , P: , F: ]
- NGT 2004: Specials NGT's 2004, Porsche GT3 RSR, Oschersleben GP 2004, AI 100 [PB: , SB: , Q: , P: , F: ]

Other Tests:
- G3 2003: BMW Z3 at Imola GP 2004 [PB: , SB: , Q: , P: , F: ]
- G3 2004: Viper Competition Coupe at Brno GP 2004 [PB: , SB: , Q: , P: , F: ]
- GT3 Cup 2003: Porsche 911 GT3 Cup at Donington GP 2004 [PB: , SB: , Q: , P: , F: ]
- NGT 2003: Specials NGT's 2004, Ferrari 360 Modena, Anderstorp GP 2003 [PB: , SB: , Q: , P: , F: ]

Bad:
- G2 2004: Specials G2 2004, BMW M3 GTR, Estoril GP 2004 [PB: ...] / Bad experience as each car is not BoP adjusted (balance of power)
- G2: BMW M3 GTR at Hockenheim GP 2004 [PB 1:40.468] / Bad experience as each car is not BoP adjusted (balance of power)
- G2 2003: Specials G2 2003, Chevrolet Corvette C5-R, Barcelona GP 2003 [PB: 1:41.454] / Bad BoP between cars, cars too stratisfied

Broken:
- Hockenheim GP 2004/National/Short: AI drive around track at pitlane speed all the time

Notes:
- Ferrari 550 seemed over powered. Can outpace anyone on straights and can go through corners faster.

Rules For Optimizing Location AIW Race Pace (ie. RaceRatio)
- Goal: Tune AI speed to reflect relative performance as compared to qualifying. So, for example, an AI who qualified ahead of you should be difficult to pass.
- Goal: It is okay to pass AI after Lap 1. Don't tune to the point you can't pass anybody, that's no fun. You want to allow some passing but only what's realistic. I would say +/- 5 positions movement would be realistic.
- Goal: Aim for a race pace where the user can pass ~5 AI after 10min in a 20min race. This isn't necessarily realistic but it does provide time and pace for good, hard battles.
- Do NOT pass first lap. Maintain position.
- Push at full race pace immediately on Lap 2
- Show no mercy: Take a gap if it's safe. For example, if an AI routinely takes a corner wide then go for the inside if you know you can do it safely.
- Don't pass under yellow as I think AI won't pass under yellow (besides passing the crashed AI(s))
- Around Lap 3 the AI seem to slow down a bit and they get competitive appropriate to their qualifying times (ie. you can keep up and try for passes)
- After Lap 6 you should have a pretty good idea of field competitiveness
- Aim to pass 1-5 AI in the first half of a 20 minute race (at least 1 for fun factor but no need to pass more if you're keeping up with a pack - that's the fun itself)
- Aim to pass up to 5 (but preferably less) AI in the last half of a 20 minute race
- Increase RaceRatio if you can pass > 5 AI within 10 minutes of a 20 minute race
- Decrease RaceRatio if you can't even maintain your qualifying position (ignore "hero" AI that jump ahead in Lap 1, they abuse the AI like a human).
- It's okay if you pass a number of AI but come up on an AI that just outpaces you and there's no way to catch up. That's realistic.
- It's normal if you find yourself with no one around you after a while. This happens in real races where you pass who you can and then those ahead are faster than you and get farther ahead while those behind you are slower and fall farther behind.

#
# 9. Plans
#

See MODS\SHO Competition AI\Plans.txt

#
# 10. Releases
#

See MODS\SHO Competition AI\Releases.txt

#
# 11. Development
#

See MODS\SHO Competition AI\Development.txt

</nowiki></pre>

SHO Competition AI

Shovas — Thu, 16 Apr 2026 14:45:23 GMT

Download

← Older revision		Revision as of 14:45, 16 April 2026
Line 10:		Line 10:
	== Download ==		== Download ==

	[https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])		* [https://www.mediafire.com/file_premium/gy6ping4pxj3iwx/SHO_Competition_AI_V14.zip/file Click here to download] ([https://archive.org/details/sho-competition-ai-v-14 Alternate])
			* [[README SHO Competition AI.txt]]

	== Discussion ==		== Discussion ==

GTR2

Shovas — Thu, 16 Apr 2026 14:24:27 GMT

Safety car comes out based on accident severity

← Older revision		Revision as of 14:24, 16 April 2026
(One intermediate revision by the same user not shown)
Line 2,883:		Line 2,883:

	GTR2 is deeper than you might think: This is a section for trivia about the things you might not know even if you’ve been using GTR2 for a long time.		GTR2 is deeper than you might think: This is a section for trivia about the things you might not know even if you’ve been using GTR2 for a long time.

			==== Safety car comes out based on accident severity ====

			* I'm assuming the FCY is evaluated by accident severity and the SC always comes out for FCY

			<pre><nowiki>
			it is triggered by evaluated accident severity. Threshold is configurable in .plr file. Some tracks have issues around SC, one issue is where xfinish object does not match .aiw s/f point. But on most tracks you will see SC in front of the grid after everyone catches up.

			-The Iron Wolf on Simwiki Discord https://discord.com/channels/1260036892703854652/1269815958072201216/1494341550153531493
			</nowiki></pre>

	==== Modern GT Classes vs 2003-2004 GT Classes ====		==== Modern GT Classes vs 2003-2004 GT Classes ====

Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin

Shovas — Thu, 16 Apr 2026 01:02:13 GMT

Installation

← Older revision		Revision as of 01:02, 16 April 2026
(2 intermediate revisions by the same user not shown)
Line 161:		Line 161:
	'''Requirements:'''		'''Requirements:'''
	* Steam GTR2 or [https://www.racedepartment.com/threads/modernizing-gtr2-with-the-crew-chief-gtr2-enhancements-plugin.250134/post-3598884 HQ Anniversary Patch compatibility options]		* Steam GTR2 or [https://www.racedepartment.com/threads/modernizing-gtr2-with-the-crew-chief-gtr2-enhancements-plugin.250134/post-3598884 HQ Anniversary Patch compatibility options]

			'''Overview:'''
			* Choose only one to install: Latest CCGEP, Beta CCGEP, or Crew Chief
			** You'll get CCGEP regardless of which you pick

	'''Latest CCGEP Install:'''		'''Latest CCGEP Install:'''
Line 197:		Line 201:
	*** See also [[Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin]]		*** See also [[Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin]]

	'''Is CCGEP It Working?'''		'''Is CCGEP Working?'''
	* CCGEP should generate '''Plugins\ccgep.ini''' in your GTR2 folder when you start and exit GTR2		* CCGEP should generate '''Plugins\ccgep.ini''' in your GTR2 folder when you start and exit GTR2

V-Rally 4 is Special

Shovas — Sun, 12 Apr 2026 22:32:20 GMT

More of the V-Rally 4 Feel - Kylotonn's Other Official WRC Games

← Older revision		Revision as of 22:32, 12 April 2026
(One intermediate revision by the same user not shown)
Line 44:		Line 44:
	This had, apparently, been done before in the Dirt series(?) but people disliked it in that game because it was "barren" and didn't feel like the handcrafted experience of the main tracks. V-Rally 4, on the other hand, takes the same handcrafted tracks and almost imperceptibly adjusts them with road blocks, hay bails, fences, and ribbons to direct you along new routes.		This had, apparently, been done before in the Dirt series(?) but people disliked it in that game because it was "barren" and didn't feel like the handcrafted experience of the main tracks. V-Rally 4, on the other hand, takes the same handcrafted tracks and almost imperceptibly adjusts them with road blocks, hay bails, fences, and ribbons to direct you along new routes.

	I guess this explains why, after 200 hours across PS5 and PC (PS5 133h then moved to PC ~~94h~~), I'm still experiencing new track variations. It feels natural.		I guess this explains why, after 200 hours across PS5 and PC (PS5 133h then moved to PC 112h), I'm still experiencing new track variations. It feels natural.

	V-Rally 4 truly does generate random routes easily and instantly, as demonstrated in this Quick Play Track Selection menu screenshot showing '''Random track: 199927'''. I've seen up to <strike>38,000</strike> <strike>98,000</strike> 199,927 and there's probably more. This is for a single location. Multiply that by all the locations and it becomes obvious you could go a huge amount of time and never repeat the same, exact route.		V-Rally 4 truly does generate random routes easily and instantly, as demonstrated in this Quick Play Track Selection menu screenshot showing '''Random track: 199927'''. I've seen up to <strike>38,000</strike> <strike>98,000</strike> 199,927 and there's probably more. This is for a single location. Multiply that by all the locations and it becomes obvious you could go a huge amount of time and never repeat the same, exact route.
Line 140:		Line 140:
	I started in campaign mode and haven't even touched Quick Play mode yet. Campaign mode starts you off easy, with slower but more approachable cars. You are then guided through how to earn more, research and develop upgrades, and then buy those upgrades for your cars. This was how I learned the game and it may have helped give me a positive reception over just diving in the deep end of Quick Play mode.		I started in campaign mode and haven't even touched Quick Play mode yet. Campaign mode starts you off easy, with slower but more approachable cars. You are then guided through how to earn more, research and develop upgrades, and then buy those upgrades for your cars. This was how I learned the game and it may have helped give me a positive reception over just diving in the deep end of Quick Play mode.

	I saw a video recently of a guy who was proud to have put 21 hours of gameplay into V-Rally 4 and he loved it and knew it really deeply. I just checked and I was surprised to see I've put in over 200 hours across PS5 and PC (PS5 133h then moved to PC ~~94h~~). I had no idea I had put that much in. It's a testament to how good and engrossing the game is.		I saw a video recently of a guy who was proud to have put 21 hours of gameplay into V-Rally 4 and he loved it and knew it really deeply. I just checked and I was surprised to see I've put in over 200 hours across PS5 and PC (PS5 133h then moved to PC 112h). I had no idea I had put that much in. It's a testament to how good and engrossing the game is.

	== People Are Giving V-Rally 4 A Second Look ==		== People Are Giving V-Rally 4 A Second Look ==
Line 173:		Line 173:
	* Notes on my experiences with the WRC games:		* Notes on my experiences with the WRC games:
	** WRC 5 is a little too basic and graphically dated. The physics and sense of motion and movement don't feel as engaging as later WRC entries.		** WRC 5 is a little too basic and graphically dated. The physics and sense of motion and movement don't feel as engaging as later WRC entries.
	** WRC 6 came out in 2016 before V-Rally 4 (2018) but ~~is the best experience out of the box compared to other WRC games (~~not ~~compared to V-Rally 4)~~		** WRC 6 came out in 2016 before V-Rally 4 (2018), it's a good improvement on WRC 5 but not as good as 7+
	** WRC 7 came out in 2017 should be technically better		** WRC 7 came out in 2017 should be technically better, although, to be honest, it doesn't quite feel as polished, even if it does feel like a robust, solid, dedicated rally game
	** WRC 8 came out in 2019, a year after V-Rally 4, and is the one I'm interested in. Unfortunately, while it is playable on the PS5, you have to purchase it in the web browser, not on the PS5 itself, and something about contrast and colour grading and shadows (which appear very black) appears slightly buggy on PS5. Try setting HDR on the PS5 to 'When Supported' (ie. automatic) in case you have forced it on like I did--it helps a little in the shadows. It's playable and could be enjoyable, to be honest, it's just the graphics seem weird.		** WRC 8 came out in 2019, a year after V-Rally 4, and is the one I'm interested in.
			*** PC: No issues on Steam, as I recall, maybe slightly off with contrast and colour grading.
			*** PS5: Unfortunately, while it is playable on the PS5, you have to purchase it in the web browser, not on the PS5 itself, and something about contrast and colour grading and shadows (which appear very black) appears slightly buggy on PS5. Try setting HDR on the PS5 to 'When Supported' (ie. automatic) in case you have forced it on like I did--it helps a little in the shadows. It's playable and could be enjoyable, to be honest, it's just the graphics seem weird.
	** WRC 9: This finally clicked with me and I'm having a really good time with it now. Not too hard to dial in controls and all that. Good fun once you find a difficulty level you're competitive with.		** WRC 9: This finally clicked with me and I'm having a really good time with it now. Not too hard to dial in controls and all that. Good fun once you find a difficulty level you're competitive with.
	** WRC 10: ~~Got this but haven't played it too much yet. But all these~~ WRC ~~games have the Kyloton/Bigben DNA and you'll feel at home~~.		** WRC 10: Solid WRC experience.
	** WRC Generations is a good experience and is more technical/simulation than V-Rally 4. Generations feels like the pinnacle of the ''simulation'' aspect of the Kylotonn WRC games (not ~~to say~~ it's the ~~best game overall~~, ~~though)~~.		** WRC Generations is a good experience and is more technical/simulation than V-Rally 4. Generations feels like the pinnacle of the ''simulation'' aspect of the Kylotonn WRC games but not the pinnacle of the games for enjoyment, it just doesn't feel like Kylotonn WRC, anymore.
			** WRC 2027
			*** After EA's WRC didn't go so well, it looks like Nacon/Kylotonn has the license again. Looking forward to trying this out.

			'''Notes:'''
			* I've limited my WRC installs to just WRC 9 and 10, having at least tried all of them, briefly. WRC 9 and 10 provide the peak Kylotonn WRC experience, to me.

	'''Quirks:'''		'''Quirks:'''
Line 228:		Line 235:
	* If you hit a road sign or other debris it will occasionally “ride” your hood until flung off		* If you hit a road sign or other debris it will occasionally “ride” your hood until flung off
	* 50h in and I don’t think I’ve ever repeated a track route in campaign mode		* 50h in and I don’t think I’ve ever repeated a track route in campaign mode
	** Now over 200 hours across PS5 and PC (PS5 133h then moved to PC ~~94h~~) and routes still feel fresh due to randomization		** Now over 200 hours across PS5 and PC (PS5 133h then moved to PC 112h) and routes still feel fresh due to randomization
	* In cockpit mode, your co-driver sways with the g-forces		* In cockpit mode, your co-driver sways with the g-forces
	* In cockpit mode, your feet are fully animated on the pedals		* In cockpit mode, your feet are fully animated on the pedals
Line 255:		Line 262:
	** Unsure if this affects non-rally events		** Unsure if this affects non-rally events
	** Practice becomes necessary. Zero mistake tolerance. Handbrake mastery required.		** Practice becomes necessary. Zero mistake tolerance. Handbrake mastery required.
	** After 200 hours across PS5 and PC (PS5 133h then moved to PC ~~94h~~), I can only comfortably enjoy 1 and 2 star rally events		** After 200 hours across PS5 and PC (PS5 133h then moved to PC 112h), I can only comfortably enjoy 1 and 2 star rally events
	* Randomize All feature for rally events doesn't randomize everything possible		* Randomize All feature for rally events doesn't randomize everything possible

Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin

Shovas — Sun, 12 Apr 2026 11:49:38 GMT

Improved Frametimes using both CCGEP DXVK Framerate Limiter and RTSS RivaTuner Statistics Server Framerate Limiter

← Older revision		Revision as of 11:49, 12 April 2026
(2 intermediate revisions by the same user not shown)
Line 159:		Line 159:
	=== Installation ===		=== Installation ===

	* <span style="color: DarkOrange; font-weight: bold;">Requires:~~</span>~~ '''Steam GTR2~~'''~~ or [https://www.racedepartment.com/threads/modernizing-gtr2-with-the-crew-chief-gtr2-enhancements-plugin.250134/post-3598884 HQ Anniversary Patch compatibility options]		'''Requirements:'''
			* Steam GTR2 or [https://www.racedepartment.com/threads/modernizing-gtr2-with-the-crew-chief-gtr2-enhancements-plugin.250134/post-3598884 HQ Anniversary Patch compatibility options]

	'''Latest CCGEP Install:'''		'''Latest CCGEP Install:'''
Line 267:		Line 268:

	See [[GTR2#Perfect Mirrors]] for full setup details for improving resolution, view distance, level of detail, and fixes for visual glitches in mirrors		See [[GTR2#Perfect Mirrors]] for full setup details for improving resolution, view distance, level of detail, and fixes for visual glitches in mirrors

	~~==== Simplified CCGEP Plugin Files Setup ====~~

	* '''tl;dr''' Manually copy&paste d3d9.dll and Plugins\CrewChief.dll, either from Crew Chief's folder or discord betas, and put them in your GTR2 root folder.
	* Crew Chief, itself, is not actually necessary, it's just an easy way to get the GTR2 Enhancements Plugin (CCGEP) files.
	* We can simplify setup for GTR2 by grabbbing the CCGEP files it contains (d3d9.dll and Plugins\CrewChief.dll) and manually copy&pasting them into the GTR2 folder
	* That's all. CCGEP is just those two files. If you don't want Crew Chief, you don't need to use it or start it. CCGEP will still work with GTR2.

	==== Improved Frametimes using both CCGEP DXVK Framerate Limiter and RTSS RivaTuner Statistics Server Framerate Limiter ====		==== Improved Frametimes using both CCGEP DXVK Framerate Limiter and RTSS RivaTuner Statistics Server Framerate Limiter ====

	* '''tl;dr''' Set both the Framerate Limit in RTSS for '''GTR2.exe''' and the '''d3d9.maxFrameRate''' setting in '''dxvk.conf''' for framerate limiting and stable framepacing provided by RTSS's limiter		* '''tl;dr''' Set both the Framerate Limit in [[RivaTuner Statistics Server]] (RTSS) for '''GTR2.exe''' and the '''d3d9.maxFrameRate''' setting in '''dxvk.conf''' for framerate limiting and stable framepacing provided by RTSS's limiter
	** RTSS's limiter may be all that's required and I may update this in the future but for now I want to simplify confounding variables		** RTSS's limiter may be all that's required and I may update this in the future but for now I want to simplify confounding variables
	* Background:		* Background:
Line 289:		Line 283:

	'''Alternatives:'''		'''Alternatives:'''
	* [~~https://gitlab.com/Kaldaien/SpecialK~~ Special K] appears to be a popular, open source~~, dll-injectable~~ alternative with similar quality framerate and framepace options		* [[Special K]] appears to be a popular, free, and open source alternative to [[RTSS] with similar quality framerate and framepace options, and much more
	** [https://wiki.special-k.info/ Special K Wiki]

	'''CCGEP DXVK Framerate Limiter with and without RTSS Framerate Limiter:'''		'''CCGEP DXVK Framerate Limiter with and without RTSS Framerate Limiter:'''

Crew Chief GTR2 Enhancements Plugin

Shovas — Sun, 12 Apr 2026 11:44:54 GMT

Discord

← Older revision		Revision as of 11:44, 12 April 2026
(One intermediate revision by the same user not shown)
Line 19:		Line 19:
	== Discord ==		== Discord ==

	* ~~Find~~ the Discord link on the [https://thecrewchief.org/showthread.php?2012-Crew-Chief-GTR2-Enhancements-Plugin-Setup-Instructions-Known-Issues-and-Changelog&p=8180&viewfull=1#post8180 Homepage]		* CCGEP Discord: https://discord.gg/zSdSwqHvx9
			* Or find the Discord link on the [https://thecrewchief.org/showthread.php?2012-Crew-Chief-GTR2-Enhancements-Plugin-Setup-Instructions-Known-Issues-and-Changelog&p=8180&viewfull=1#post8180 Homepage] if the direct link breaks

	== Manual ==		== Manual ==

Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin

Shovas — Sun, 12 Apr 2026 11:43:01 GMT

Installation

Show changes

Crew Chief GTR2 Enhancements Plugin

Shovas — Sun, 12 Apr 2026 11:24:47 GMT

Homepage

← Older revision		Revision as of 11:24, 12 April 2026
Line 16:		Line 16:

	* [https://thecrewchief.org/showthread.php?2012-Crew-Chief-GTR2-Enhancements-Plugin-Setup-Instructions-Known-Issues-and-Changelog&p=8180&viewfull=1#post8180 Homepage]		* [https://thecrewchief.org/showthread.php?2012-Crew-Chief-GTR2-Enhancements-Plugin-Setup-Instructions-Known-Issues-and-Changelog&p=8180&viewfull=1#post8180 Homepage]

			== Discord ==

			* Find the Discord link on the [https://thecrewchief.org/showthread.php?2012-Crew-Chief-GTR2-Enhancements-Plugin-Setup-Instructions-Known-Issues-and-Changelog&p=8180&viewfull=1#post8180 Homepage]

	== Manual ==		== Manual ==

CCGEP Manual

Shovas — Sun, 12 Apr 2026 11:20:32 GMT

Redirected page to Crew Chief GTR2 Enhancements Plugin#Manual

New page

#REDIRECT [[Crew_Chief_GTR2_Enhancements_Plugin#Manual]]

GTR2

Shovas — Sun, 12 Apr 2026 11:14:54 GMT

Fix for Dedicated GPU not available to set in GTR2Config.exe

← Older revision		Revision as of 11:14, 12 April 2026
Line 208:		Line 208:
	===== Fix for Dedicated GPU not available to set in GTR2Config.exe =====		===== Fix for Dedicated GPU not available to set in GTR2Config.exe =====

	* tl;dr Set the preferred GPU for '''GTR2.exe''' and '''GTR2Config.exe''' to the dedicated GPU in the '''Windows Display settings''': This enables '''GTR2Config.exe''' to show the dedicated GPU and you can now select it		* '''tl;dr''' Set the preferred GPU for '''GTR2.exe''' and '''GTR2Config.exe''' to the dedicated GPU in the '''Windows Display settings''': This enables '''GTR2Config.exe''' to show the dedicated GPU and you can now select it
	* [https://steamcommunity.com/app/8790/discussions/0/770811663800708027/#c770811663800877579 Original Link] - User describes how they solved being able to select their dedicated NVIDIA GPU instead of their integrated AMD GPU in '''GTR2.exe'''		* [https://steamcommunity.com/app/8790/discussions/0/770811663800708027/#c770811663800877579 Original Link] - User describes how they solved being able to select their dedicated NVIDIA GPU instead of their integrated AMD GPU in '''GTR2.exe'''

Modernizing GTR2 with the Crew Chief GTR2 Enhancements Plugin

Shovas — Sat, 11 Apr 2026 20:16:00 GMT

Windows Automatically Blocks Crew Chief DLLs (Unblock in DLL Properties)

← Older revision		Revision as of 20:16, 11 April 2026
(3 intermediate revisions by the same user not shown)
Line 275:		Line 275:

	=== Gotchas ===		=== Gotchas ===

			==== Windows Automatically Blocks Crew Chief DLLs (Unblock in DLL Properties) ====

			* '''tl;dr''' In the GTR2 folder, on '''d3d9.dll''' and '''Plugins\ccgep.dll''': Right-click > Properties > Security: Unblock
			* Windows may automatically block some files, including Crew Chief DLLs, because they 'came from another computer' ie. you downloaded them
			* So you may have to remove the block
			* This is possibly more likely to happen if you are, for example, copying GTR2 to a new folder

			<gallery>
			windows-dll-properties-unblock.jpg\|
			</gallery>

	==== CCGEP AVX2 vs Non-AVX2 Versions for Old CPUs ====		==== CCGEP AVX2 vs Non-AVX2 Versions for Old CPUs ====