Simwiki.net - Recent changes [en]

Project Motor Racing

Shovas — Sun, 23 Aug 2026 15:54:00 GMT

Gotchas

← Older revision		Revision as of 15:54, 23 August 2026
(One intermediate revision by the same user not shown)
Line 247:		Line 247:
	=== Inputs not responding while calibrating ===		=== Inputs not responding while calibrating ===

	* '''tl;dr''' Calibrate from wheel device for wheel inputs and separately calibrate from pedal device for pedal inputs. Pedal inputs will not respond when calibrating from wheel device.		* '''tl;dr''' Calibrate from wheel device for wheel inputs (ignoring prompts for pedal inputs) and separately calibrate from pedal device for pedal inputs. Pedal inputs will not respond when calibrating from wheel device even though it prompts you (I don't know why).
	* You can assign controls across multiple devices but Calibrate won't work or won't ~~appear to work when you use it~~.		* My wheel and pedals are separate devices. When I use the Calibrate function on the wheel, it also prompts for pedal inputs but I can't see my pedal inputs during calibration. When I use the Calibrate function on the pedals, the pedal inputs respond as expected.
	* My wheel and pedals are separate devices. When I use the Calibrate function, I can't see ~~either~~ my ~~pedals or wheel responding to~~ inputs during calibration.
	* I feel like I'm wrong about this and there's some subtlety I~~'m missing.~~
	* It's confusing nonetheless
	* Okay, this is probably when you use ~~Calibrate from~~ the ~~wheel device as opposed to using~~ Calibrate ~~from your pedal device. When calibrate is used from~~ the ~~wheel device~~, ~~it goes through your wheel and then your pedal inputs, and~~ the pedal inputs ~~don't respond. When you use calibrate from your pedal device, it only goes through your pedal inputs and, in my case, they~~ respond as expected.

	== Troubleshooting ==		== Troubleshooting ==

GTR2

Shovas — Sun, 23 Aug 2026 13:49:52 GMT

Wheel/Pedals not working - GTR2 3 USB Device Limit

← Older revision		Revision as of 13:49, 23 August 2026
Line 3,721:		Line 3,721:
	** You can either disconnect as many devices as you can, or you can use tools like [[Devreorder]] or [[USBDeview]] to reorder, hide, or disable your USB devices so that game picks up wheel/pedals.		** You can either disconnect as many devices as you can, or you can use tools like [[Devreorder]] or [[USBDeview]] to reorder, hide, or disable your USB devices so that game picks up wheel/pedals.
	** It is important to get wheel/pedals to work directly in the game, as for buttons that are not working there’s a workaround ([[Joy2Key]] or [[AntiMicroX]]), but wheel/pedals need to be detected directly by the game.		** It is important to get wheel/pedals to work directly in the game, as for buttons that are not working there’s a workaround ([[Joy2Key]] or [[AntiMicroX]]), but wheel/pedals need to be detected directly by the game.
	* Once you have pedals/wheel recognized by the game, you may find that the game does not detect some of your shifters/buttons ~~etc.~~		* Once you have pedals/wheel recognized by the game, you may find that the game does not detect some of your shifters/buttons because you have too many
	** To work this around, use one of the many tools available to map button presses to keyboard presses, then assign keyboard keys to various game actions. I personally use [[Joy2Key]]. There is also [[AntiMicroX]].		** To work this around, use one of the many tools available to map button presses to keyboard presses, then assign keyboard keys to various game actions. I personally use [[Joy2Key]]. There is also [[AntiMicroX]].

Project Motor Racing

Shovas — Tue, 18 Aug 2026 13:27:38 GMT

Inputs not responding while calibrating

← Older revision		Revision as of 13:27, 18 August 2026
Line 252:		Line 252:
	* I feel like I'm wrong about this and there's some subtlety I'm missing.		* I feel like I'm wrong about this and there's some subtlety I'm missing.
	* It's confusing nonetheless		* It's confusing nonetheless
	* Okay, this is probably when you use Calibrate from the wheel device as opposed to using Calibrate from your pedal device. When calibrate is used from the wheel device, it goes through your wheel and then ~~you~~ pedal inputs, and the pedal inputs don't ~~responsd~~. When you use calibrate from your pedal device, it only goes through your pedal inputs and, in my case, they respond as expected.		* Okay, this is probably when you use Calibrate from the wheel device as opposed to using Calibrate from your pedal device. When calibrate is used from the wheel device, it goes through your wheel and then your pedal inputs, and the pedal inputs don't respond. When you use calibrate from your pedal device, it only goes through your pedal inputs and, in my case, they respond as expected.

	== Troubleshooting ==		== Troubleshooting ==

Optimized Graphics Settings

Shovas — Mon, 17 Aug 2026 04:42:56 GMT

Graphics Settings Impact

← Older revision		Revision as of 04:42, 17 August 2026
Line 122:		Line 122:
	** '''Mirrors'''		** '''Mirrors'''
	*** GPU, Vram, Framerate, frametimer, judder		*** GPU, Vram, Framerate, frametimer, judder

			=== Common Graphic Settings With Significant Impact ===

			* '''Shadows'''
			* '''Global Illumination'''
			* '''Anti-Aliasing'''
			** 4x is good enough with 1440p or 4K. Beyond 4x AA is very much diminishing returns and not worth the cost.
			* '''Volumetric Clouds'''
			** See [[Assassin%27s_Creed_Odyssey#Persistent_severe_stuttering,_hitching,_or_freezing]]

	== Graphics Performance Engineer ==		== Graphics Performance Engineer ==

Assassin's Creed Odyssey

Shovas — Mon, 17 Aug 2026 04:40:15 GMT

← Older revision		Revision as of 04:40, 17 August 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	* '''Troubleshooting~~'''~~		__TOC__
	** '''Persistent severe stuttering, ~~freezing~~, or ~~hitching'''~~
	*** '''tl;dr''' Disable hyperthreading in the BIOS for a big ~~improvement~~ to ~~frametime consistency~~		== Troubleshooting ==

			=== Persistent severe stuttering, hitching, or freezing ===

			* '''tl;dr''' (1) Disable hyperthreading in the BIOS, (2) Volumetric clouds medium or lower, (3) set Ultra Low Latency + disable Multi Frame Sample AA in NVIDIA Control Panel
			** First, disable hyperthreading in the BIOS for a big reduction in multisecond freezing. This takes the game from interolerable to tolerable but still not great.
	*** Yes, must be done in the BIOS, in my experience. Just setting a CPU affinity to real P-Cores (ie. not hyperthreading cores) was not enough.		*** Yes, must be done in the BIOS, in my experience. Just setting a CPU affinity to real P-Cores (ie. not hyperthreading cores) was not enough.
	*** I ~~tried many supposed fixes~~ and ~~tweaks~~ from the ~~Steam Community forums~~ for the game ~~and nothing worked until~~ I ~~tried this~~		*** I'm wondering if hyperthreading isn't a net loss for games, anyway. Newer CPUs are removing hyperthreading in favour of real P-cores and E-cores so why not disable hyperthreading. Probably helps with older games more, too, as they're even less aware of threading intricacies.
	*** Theory: ~~Games optimized~~ for ~~consoles may not be hyperthreading~~-~~aware and so may have compatibility issues~~		** Second, lower Volumetric Clouds in-game to medium or lower. This seems to be the main graphics setting that affects stuttering/hitching/freezing. This takes the game from tolerable to acceptable.
			*** I figured it would be some problem setting in-game but it's always hard to find the exact one. Luckily, I saw a random post on reddit that gave me the idea to try it. I think I've heard about performance with volumetric clouds in other games, too, so it makes sense.
			** Third, set Ultra Low Latency and disable Multi Frame Sample AA in the NVIDIA Control Panel for AC Odyssey (you may have to add the game by hand). This takes the game from acceptable to mostly enjoyable.
			** There are some remaining microstutters, maybe 1-2 ms-level stutters every 30-60 seconds, maybe less, but the whole experience is so much smoother. Even things like going to the map, inventory, abilities, or other menus feels much better.
			* System: 12700KF/32GB/3080
			* [[Optimized_Graphics_Settings#Image_Terms\|Terms: Stuttering, Hitching, Freezing]]

			'''Notes:'''
			* Limiting CPU affinity to P-cores, or first 4 P-cores, did not seem to show a net positive improvement, so I left it unrestricted
			** Interesting observation: Limiting to first 4 P-cores resulted in higher GPU usage while still capped at 60fps ie. higher GPU usage for no extra benefit. Letting it use all the CPU cores again lowers the GPU usage to between 70-90% on average.

Project Motor Racing

Shovas — Sun, 16 Aug 2026 18:58:38 GMT

Gotchas

← Older revision		Revision as of 18:58, 16 August 2026
(One intermediate revision by the same user not shown)
Line 242:		Line 242:

	* In this [https://www.youtube.com/shorts/ki4KuFigChw video short] they talk about some of their AI tech being used in [https://youtu.be/5XsOCZUIuvs?si=_pp8eBmB8lEgLQZq&t=1177 Williams Racing Lap of Legends 'real vs virtual race' TV program] where they have virtual cars, controlled by AI, race around a real Silverstone		* In this [https://www.youtube.com/shorts/ki4KuFigChw video short] they talk about some of their AI tech being used in [https://youtu.be/5XsOCZUIuvs?si=_pp8eBmB8lEgLQZq&t=1177 Williams Racing Lap of Legends 'real vs virtual race' TV program] where they have virtual cars, controlled by AI, race around a real Silverstone

			== Gotchas ==

			=== Inputs not responding while calibrating ===

			* '''tl;dr''' Calibrate from wheel device for wheel inputs and separately calibrate from pedal device for pedal inputs. Pedal inputs will not respond when calibrating from wheel device.
			* You can assign controls across multiple devices but Calibrate won't work or won't appear to work when you use it.
			* My wheel and pedals are separate devices. When I use the Calibrate function, I can't see either my pedals or wheel responding to inputs during calibration.
			* I feel like I'm wrong about this and there's some subtlety I'm missing.
			* It's confusing nonetheless
			* Okay, this is probably when you use Calibrate from the wheel device as opposed to using Calibrate from your pedal device. When calibrate is used from the wheel device, it goes through your wheel and then you pedal inputs, and the pedal inputs don't responsd. When you use calibrate from your pedal device, it only goes through your pedal inputs and, in my case, they respond as expected.

	== Troubleshooting ==		== Troubleshooting ==

GTR2

Shovas — Fri, 14 Aug 2026 14:47:42 GMT

Tip: Adjust Wheel Rotation by Car and Steering Lock by Track

← Older revision		Revision as of 14:47, 14 August 2026
(5 intermediate revisions by the same user not shown)
Line 921:		Line 921:
	==== Field of View (FOV) ====		==== Field of View (FOV) ====

	GTR2’s default FOV (field of view) shows you a large amount of your cockpit but it’s not realistic and can be a disadvantage in terms of judging speed, distance, and general timing. You will almost certainly be faster with correct FOV because you’ll be better able to judge speed, distance and timing.		* GTR2’s default FOV (field of view) shows you a large amount of your cockpit but it’s not realistic and can be a disadvantage in terms of judging speed, distance, and general timing.
			* You will almost certainly be faster with correct FOV because you’ll be better able to judge speed, distance and timing.
	Need convincing? Try watching this [https://www.youtube.com/watch?v=AbbxkX7kS_M classic Empty Box video] on why you would adjust your field of view.		* Need convincing? Try watching this [https://www.youtube.com/watch?v=AbbxkX7kS_M classic Empty Box video] on why you would adjust your field of view.
			* If you use HQ Anniversary Patch your FOVs will be updated for you, and you probably won’t need to change anything, but otherwise you can do so manually in the '''GTR2\UserData\defviews.cam''' file as described here.
	If you use HQ Anniversary Patch your FOVs will be updated for you, and you probably won’t need to change anything, but otherwise you can do so manually in the '''GTR2\UserData\defviews.cam''' file as described here.		* If you find you need to, tweak the field of view somewhat wider than default.
			* As a good rule of thumb, you want your field of view to include your driver-side mirror and about half of your rear-view mirror.
	If you find you need to, tweak the field of view somewhat wider than default.		* For those with head tracking, such as TrackIR, Tobii, or VR, bring your FOV so that you can see half of your driver-side mirror and half of your rear-view mirror, since you can move your head around to see the mirrors in full.

	As a good rule of thumb, you want your field of view to include your driver-side mirror and about half of your rear-view mirror.

	For those with head tracking, such as TrackIR, Tobii, or VR, bring your FOV so that you can see half of your driver-side mirror and half of your rear-view mirror, since you can move your head around to see the mirrors in full.

	===== Field of View (FOV) Reference Table =====		===== Field of View (FOV) Reference Table =====
Line 951:		Line 947:

	===== Field of View (FOV) Calculators =====		===== Field of View (FOV) Calculators =====

			'''FOV Calculators:'''

	* https://dinex86.github.io/FOV-Calculator/		* https://dinex86.github.io/FOV-Calculator/
	* https://andyf.me/fovcalc.html		* https://andyf.me/fovcalc.html

	The old projectimmersion.com fov calculator is sadly defunct but I'll keep the example here to give you a point of reference for whatever calculators remain, as they all put out the same values.		'''Old Project Immersion FOV Calculator:'''
			* The old projectimmersion.com fov calculator is sadly defunct but I'll keep the example here to give you a point of reference for whatever calculators remain, as they all put out the same values.
	The Project Immersion.com FOV calculator is a handy site to calculate your correct FOV from the size of your monitors and how far away you sit. The '''“vFOV%”''' value it calculates a factor which should be applied against the default '''vFOV''' value in the '''GTR2\UserData\defviews.cam''' file:		* The Project Immersion.com FOV calculator is a handy site to calculate your correct FOV from the size of your monitors and how far away you sit. The '''“vFOV%”''' value it calculates a factor which should be applied against the default '''vFOV''' value in the '''GTR2\UserData\defviews.cam''' file:

	<pre><nowiki>		<pre><nowiki>
Line 967:		Line 965:
	</nowiki></pre>		</nowiki></pre>

	ProjectImmersion.com says my GTR2 vFOV% is 40% so that means I should change 62.0 to 40.0. Try it out. I adjusted mine from the suggested value. You probably will, too.		* ProjectImmersion.com says my GTR2 vFOV% is 40% so that means I should change 62.0 to 40.0. Try it out. I adjusted mine from the suggested value. You probably will, too.
			* Note! Select Race 07, GTR EVO (vFOV%) from the FOV Type drop-down for use with GTR2.
	Note! Select Race 07, GTR EVO (vFOV%) from the FOV Type drop-down for use with GTR2.

	==== Seating Position ====		==== Seating Position ====

	While not as important as FOV, one thing I've found handy is setting FOV about right and then using seat adjustment to bring the seat forward until the bottom edge of my screen is about in the center of the onscreen steering wheel. In other words, I move in until I can see only the top half of the brand logo in the center of the wheel).		* While not as important as FOV, one thing I've found handy is setting FOV about right and then using seat adjustment to bring the seat forward until the bottom edge of my screen is about in the center of the onscreen steering wheel.
			* In other words, I move in until I can see only the top half of the brand logo in the center of the wheel).
	Combined with FOV, this gives a decently immersive cockpit field of view experience, in my opinion.		* Combined with FOV, this gives a decently immersive cockpit field of view experience, in my opinion.

	==== Wheel Rotation and Wheel Lock ====		==== Wheel Rotation and Wheel Lock ====
Line 989:		Line 986:
	===== Tip: Adjust Wheel Rotation by Car and Steering Lock by Track =====		===== Tip: Adjust Wheel Rotation by Car and Steering Lock by Track =====

	'''tl;dr''' Set your steering lock so that your hands never come off the wheel in any corner on the circuit.		'''tl;dr''' Set your steering lock so that your hands never come off the wheel driving through any corner on the circuit.

	'''Notes:'''		'''Notes:'''
Line 3,077:		Line 3,074:
	This is as close to perfect mirrors in GTR2 as I've ever found.		This is as close to perfect mirrors in GTR2 as I've ever found.

	This will provide high resolution, enhanced level of detail compared to normal mirrors, an aspect ratio that looks decent and works on most cars (even mod cars), and fixes certain buggy behaviour with 'self-in-mirror' body parts, etc.		This will provide high resolution mirrors and enhanced level of detail, compared to normal mirrors, an aspect ratio that looks decent and works on most cars (even mod cars), and fixes certain buggy behaviour with 'self-in-mirror' body parts, etc.

	* '''Mirror BMP'''		* '''Mirror BMP'''
Line 3,095:		Line 3,092:

	* [https://trackaholics.forumotion.com/t9645-mirrors-perfect-mirrors-by-shovas#177260 Original Link]		* [https://trackaholics.forumotion.com/t9645-mirrors-perfect-mirrors-by-shovas#177260 Original Link]
	* tl;dr Search and replace '''VisGroups=(32)''' in '''TRK''' files		* '''tl;dr''' Search and replace '''VisGroups=(32)''' in '''TRK''' files
	** '''32''' is the VisGroup for instances that should '''not''' show up in the mirrors. So, by deleting these VisGroups occurrences, the instances '''will''' show up in the mirrors.		** '''32''' is the VisGroup for instances that should '''not''' show up in the mirrors. So, by deleting these VisGroups occurrences, the instances '''will''' show up in the mirrors.
	** Regex Search: <code>VisGroups=\(32\)</code>		** Regex Search: <code>VisGroups=\(32\)</code>

Main Page

Shovas — Thu, 13 Aug 2026 18:24:58 GMT

Sim Tools

← Older revision		Revision as of 18:24, 13 August 2026
Line 105:		Line 105:
	* [[Internet Archive]] - Archive.org has become an invaluable source to find and upload sim files files such as mods		* [[Internet Archive]] - Archive.org has become an invaluable source to find and upload sim files files such as mods
	* [[PortableApps]] - Simple, no fuss, established package manager, with access to popular, handy, free apps, with auto updating		* [[PortableApps]] - Simple, no fuss, established package manager, with access to popular, handy, free apps, with auto updating
	** [[qBittorrent]] - Free and open source Bittorrent ~~apps~~, available on [[PortableApps]], useful for downloading Torrents, such as on the [[Internet Archive]]		** [[qBittorrent]] - Free and open source Bittorrent app, available on [[PortableApps]], useful for downloading Torrents, such as on the [[Internet Archive]]
	* [[DOSBox]] - Emulate an Intel x86 PC, complete with sound, graphics, mouse, joystick, modem, etc., for playing DOS games or running DOS apps		* [[DOSBox]] - Emulate an Intel x86 PC, complete with sound, graphics, mouse, joystick, modem, etc., for playing DOS games or running DOS apps

GTR2

Shovas — Thu, 13 Aug 2026 00:11:24 GMT

Community

← Older revision		Revision as of 00:11, 13 August 2026
Line 84:		Line 84:
	* [https://classicmotorsporthub.org/ Classic Motorsport Hub] - Community, forums, and league focused around rFactor 1 but has some [https://classicmotorsporthub.org/repo/ GTR2] interest		* [https://classicmotorsporthub.org/ Classic Motorsport Hub] - Community, forums, and league focused around rFactor 1 but has some [https://classicmotorsporthub.org/repo/ GTR2] interest
	* [https://gtr24u.forumotion.com/forum GTR24U Scott Huhn Designs]		* [https://gtr24u.forumotion.com/forum GTR24U Scott Huhn Designs]
			* [https://rfactorgtr2modsx.forumactif.com/ Rfactorgtr2mods Forums]

	'''Extra:'''		'''Extra:'''

Monitors

Shovas — Wed, 12 Aug 2026 14:27:50 GMT

LED vs OLED Refresh Rate vs Pixel Response Time

RaceRoom Racing Experience

Shovas — Sun, 09 Aug 2026 15:31:00 GMT

RaceRoom was running a Flash-based HUD until 2026

← Older revision		Revision as of 15:31, 9 August 2026
(2 intermediate revisions by the same user not shown)
Line 171:		Line 171:
	* I have done this a number of times over a number of years with no problem		* I have done this a number of times over a number of years with no problem
	* Points are sold by KW Automotive North America who are the parent of KW Studios, formerly SimBin Studios and Sector3 Studios, who develop RaceRoom Racing Experience [https://en.wikipedia.org/wiki/KW_Studios]		* Points are sold by KW Automotive North America who are the parent of KW Studios, formerly SimBin Studios and Sector3 Studios, who develop RaceRoom Racing Experience [https://en.wikipedia.org/wiki/KW_Studios]

			== Trivia ==

			=== RaceRoom was running a Flash-based HUD until 2026 ===

			* ''"Most notably, is the complete removal of RaceRoom’s legacy Flash-based HUD (used since 2013) in favor of the new COSMO UI renderer letting users move, resize, toggle elements, or hide every individual UI module.''" [https://www.bsimracing.com/raceroom-summer-update-dtm-2026-car-pack-released/] [https://store.steampowered.com/news/app/211500/view/706652383055187287?l=english]
			* The Flash used is/was the well-known SWF, vector graphics, ActionScript, and Adobe editing/animating software
			* The implementation used the [https://en.wikipedia.org/wiki/Scaleform_GFx Scaleform GFx] common middleware for translating those Flash graphics into a GPU-accelerated, in-graphics-pipeline
			* This actually makes a lot of sense, now that I think about it. I have some experience with SWFs, ActionScript, and Adobe software, from the 2000s/2010s, and it was (still is?) legitimate graphics and animation software. So, making HUDs is a logical idea.

NVIDIA Shield

Shovas — Sat, 08 Aug 2026 02:50:52 GMT

Disable Hyperthreading in the BIOS for Stuttering, Hitching, or Freezing

← Older revision		Revision as of 02:50, 8 August 2026
(2 intermediate revisions by the same user not shown)
Line 209:		Line 209:
	* Improve video smoothness reliability by closing other apps which may be taking resources in the background		* Improve video smoothness reliability by closing other apps which may be taking resources in the background
	* Double-tap the O button on the Shield controller and close every window except Moonlight		* Double-tap the O button on the Shield controller and close every window except Moonlight

			==== Disable Hyperthreading in the BIOS ====

			* Disable hyperthreading in the BIOS as it is known to cause performance issues in some games
			* But no need to do this unless you're experiencing frametime inconsistency including symptoms such as stuttering, hitching, and freezing
			* See [[Assassin's Creed Odyssey]]

	=== Improving The Experience ===		=== Improving The Experience ===
Line 342:		Line 348:
	* Why was a duplicate WiFi SSD a problem for networking on a 100% wired Sunlight-Moonshine streaming setup?		* Why was a duplicate WiFi SSD a problem for networking on a 100% wired Sunlight-Moonshine streaming setup?
	** I suspect one or more wired devices, that also have wireless radios, was being caused stress/overload having to switch back and forth between the same SSID on two different serving devices ie. my isp modem and my home router. Being stressed or overloaded, cause momentary network glitching where traffic stopped briefly flowing (or was dropped) and that caused the stuttering.		** I suspect one or more wired devices, that also have wireless radios, was being caused stress/overload having to switch back and forth between the same SSID on two different serving devices ie. my isp modem and my home router. Being stressed or overloaded, cause momentary network glitching where traffic stopped briefly flowing (or was dropped) and that caused the stuttering.

			==== Disable Hyperthreading in the BIOS for Stuttering, Hitching, or Freezing ====

			* '''tl;dr''' Disable hyperthreading in the BIOS if you are experiencing stuttering, hitching, and freezing in a game on the host and no other fixes have worked
			* See [[Assassin's Creed Odyssey]]

	=== Known Issues ===		=== Known Issues ===

Assassin's Creed Odyssey

Shovas — Sat, 08 Aug 2026 02:45:40 GMT

Created page with "* '''Troubleshooting''' ** '''Persistent severe stuttering, freezing, or hitching''' *** '''tl;dr''' Disable hyperthreading in the BIOS for a big improvement to frametime consistency *** Yes, must be done in the BIOS, in my experience. Just setting a CPU affinity to real P-Cores (ie. not hyperthreading cores) was not enough. *** I tried many supposed fixes and tweaks from the Steam Community forums for the game and nothing worked until I tried this *** Theory: Games opti..."

New page

* '''Troubleshooting'''
** '''Persistent severe stuttering, freezing, or hitching'''
*** '''tl;dr''' Disable hyperthreading in the BIOS for a big improvement to frametime consistency
*** Yes, must be done in the BIOS, in my experience. Just setting a CPU affinity to real P-Cores (ie. not hyperthreading cores) was not enough.
*** I tried many supposed fixes and tweaks from the Steam Community forums for the game and nothing worked until I tried this
*** Theory: Games optimized for consoles may not be hyperthreading-aware and so may have compatibility issues

User:Shovas

Shovas — Sat, 08 Aug 2026 02:41:45 GMT

Games

← Older revision		Revision as of 02:41, 8 August 2026
Line 73:		Line 73:
	== Games ==		== Games ==

			* [[Assassin's Creed Odyssey]]
	* [[Castle of Illusion]]		* [[Castle of Illusion]]

GTR2

Shovas — Tue, 04 Aug 2026 19:14:40 GMT

Converting rFactor Cars to GTR2 or GTL by LkwFan

← Older revision		Revision as of 19:14, 4 August 2026
(One intermediate revision by the same user not shown)
(No difference)

SHO Weather Generator

Shovas — Mon, 03 Aug 2026 20:02:36 GMT

Description

← Older revision		Revision as of 20:02, 3 August 2026
Line 10:		Line 10:
	*** This is a single executable startup to generate a single weather scenario which means there's a lot of overhead included		*** This is a single executable startup to generate a single weather scenario which means there's a lot of overhead included
	*** When run in bulk, such as in the benchmarks below, single weather scenarios are generated in ~1ms		*** When run in bulk, such as in the benchmarks below, single weather scenarios are generated in ~1ms
	** On an i7 2600 32GB RAM with SSDs, it takes:		** On an i7 2600 32GB RAM with SATA SSDs, it takes:
	*** 3-5min to generate realtime, 4x Wet Modes, and 10/15/20/30/60/120min slots weather for ~100 tracks x 12 months x 10 weather scenarios		*** 3-5min to generate realtime, 4x Wet Modes, and 10/15/20/30/60/120min slots weather for ~100 tracks x 12 months x 10 weather scenarios
	*** 9-26min for ~ x 100 weather scenarios		*** 9-26min for ~ x 100 weather scenarios

GTR2

Shovas — Thu, 30 Jul 2026 17:13:26 GMT

TrackIR Head Tracking

← Older revision		Revision as of 17:13, 30 July 2026
(2 intermediate revisions by the same user not shown)
Line 234:		Line 234:
	=== GTR Engineers Handbook - The official GTR Setup Guide ===		=== GTR Engineers Handbook - The official GTR Setup Guide ===

	* [[GTR Engineers Handbook]] (Online) – The official GTR Setup Guide ([http://www.racedepartment.com/downloads/gtr-engineers-handbook.18045/ PDF Download]; [https://~~simwiki~~.~~net~~/~~files~~/GTR_Engineers_Handbook.pdf Backup PDF]; [https://simwiki.net/files/GTR_Engineers_Handbook.html Backup HTML])		* [[GTR Engineers Handbook]] (Online) – The official GTR Setup Guide ([http://www.racedepartment.com/downloads/gtr-engineers-handbook.18045/ PDF Download]; [https://www.mediafire.com/file_premium/1aiok4gfvwg2o1l/GTR_Engineers_Handbook.pdf/file Backup PDF]; [https://simwiki.net/files/GTR_Engineers_Handbook.html Backup HTML])
	* “The official GTR Engineer’s Handbook, which is hard to find on the internet (and not included with the game). It was made for the first GTR game title by Simbin in 2004, but it also applies to the sequel.”		* “The official GTR Engineer’s Handbook, which is hard to find on the internet (and not included with the game). It was made for the first GTR game title by Simbin in 2004, but it also applies to the sequel.”
	* “Combined with the GTR2 Car-Owner’s Manual, it’s a must have for those who use GTR2’s original cars. A great source of knowledge for GTR2 users, as it provides important information as a setup guide.” [http://www.racedepartment.com/downloads/gtr-engineers-handbook.18045/]		* “Combined with the GTR2 Car-Owner’s Manual, it’s a must have for those who use GTR2’s original cars. A great source of knowledge for GTR2 users, as it provides important information as a setup guide.” [http://www.racedepartment.com/downloads/gtr-engineers-handbook.18045/]
Line 242:		Line 242:
	=== GTR2 Car-Owner’s Manual ===		=== GTR2 Car-Owner’s Manual ===

	* GTR2 Car-Owner’s Manual – Extensive details on the car specs, tire character, power graphs, etc ([http://www.racedepartment.com/downloads/gtr2-car-owners-manual.18047/ PDF Download]; [~~http~~://~~selah~~.~~ca/wp-content/uploads~~/~~2017~~/08/GTR2CarOwnerManualNAP.pdf Backup]) <!-- [[GTR2 Car-Owner’s Manual]] (Online) -->		* GTR2 Car-Owner’s Manual – Extensive details on the car specs, tire character, power graphs, etc ([http://www.racedepartment.com/downloads/gtr2-car-owners-manual.18047/ PDF Download]; [https://www.mediafire.com/file/cbgev5rv3pxdobr/GTR2CarOwnerManualNAP.pdf/file Backup]) <!-- [[GTR2 Car-Owner’s Manual]] (Online) -->
	* ''“Along with the GTR Engineers Handbook, this manual is a must have for those who use GTR2’s original cars. It has all extensive data on every single car specs, such as tire characteristics, ideal temps and pressures, power graphs, transmission, aerodynamics, weight balance, etc, etc.”''		* ''“Along with the GTR Engineers Handbook, this manual is a must have for those who use GTR2’s original cars. It has all extensive data on every single car specs, such as tire characteristics, ideal temps and pressures, power graphs, transmission, aerodynamics, weight balance, etc, etc.”''

Line 1,411:		Line 1,411:
	* So, presently, I'm probably using the calmer versions of the profiles mentioned above		* So, presently, I'm probably using the calmer versions of the profiles mentioned above

	==== ~~TrackIR Fix for Camera Uphill/Downhill Extreme Angles~~ ====		==== More Immersive World Movement Tuning ====

	'''GTR2 In-game - World Movement: 15%''' (240823)		'''GTR2 In-game - World Movement: 15%''' (240823)
Line 1,442:		Line 1,442:
	* I just asked ChatGPT if it had to guess how much your brain is stabilizing the visual from eyes in a race car situation with a driver bouncing around inside a bouncing car and it said 70-90%. I could bet it's north of 50% anyway.		* I just asked ChatGPT if it had to guess how much your brain is stabilizing the visual from eyes in a race car situation with a driver bouncing around inside a bouncing car and it said 70-90%. I could bet it's north of 50% anyway.
	* So < 50% World Movement, tune as desired		* So < 50% World Movement, tune as desired

			==== TrackIR Fix for Camera Uphill/Downhill Extreme Angles ====

			* '''tl;dr''' Set World Movement to 1% or more to avoid lock-to-horizon mode
			* World Movement set to 0% enabled 'lock-to-horizon' mode and this causes the camera to point straight at the horizon no matter how steep an uphill or downhill
			* This can result in looking through your floor on steep uphills or looking through your roof on steep downhills
			* Just set World Movement to 1% or more to avoid this

	== Accessibility ==		== Accessibility ==

← Older revision		Revision as of 14:27, 12 August 2026
(6 intermediate revisions by the same user not shown)
Line 35:		Line 35:
	'''LED vs OLED Ghosting Example [https://www.youtube.com/watch?v=51jHC7UELaA&t=304s]:'''		'''LED vs OLED Ghosting Example [https://www.youtube.com/watch?v=51jHC7UELaA&t=304s]:'''

	[[Image:led-vs-oled-ghosting.png\|thumb\|left\|Quality OLED can produce ~~clean~~, artifact-free, ghosting-free frames, ~~every time~~]]		[[Image:led-vs-oled-ghosting.png\|thumb\|left\|Quality OLED can produce cleaner, more artifact-free, more ghosting-free frames, more reliably]]

	<div style="clear: both;"></div>		<div style="clear: both;"></div>
Line 70:		Line 70:

	* Options:		* Options:
			** [[Special K]]
	** MSI Afterburner's [[RivaTuner Statistics Server]] (RTSS)		** MSI Afterburner's [[RivaTuner Statistics Server]] (RTSS)
	*** MSI Afterburner works with any make/model of video card		*** MSI Afterburner works with any make/model of video card
Line 177:		Line 178:

	'''Why Can't I Run 2K / 1440p On My 4K Monitor?'''		'''Why Can't I Run 2K / 1440p On My 4K Monitor?'''
	* tl;dr 1080p divides evenly into 4K but 1440p does not ie. 1440p does not cleanly integer scale to 4K		* '''tl;dr''' 1080p divides evenly into 4K but 1440p does not ie. 1440p does not cleanly integer scale to 4K
	* Good video quickly explains why it's not optimal to just run 1440p on a 4K monitor		* Good video quickly explains why it's not optimal to just run 1440p on a 4K monitor

Line 195:		Line 196:
	** The big win is oled response times (0.1ms) vs led 1ms. They both have margins up to 10x in worst case scenarios but because oled is so much lower to begin with it's still a noticeable improvement.		** The big win is oled response times (0.1ms) vs led 1ms. They both have margins up to 10x in worst case scenarios but because oled is so much lower to begin with it's still a noticeable improvement.
	** So, even though I have less refresh rate, the pixel response times more than make up for it.		** So, even though I have less refresh rate, the pixel response times more than make up for it.
	** You'll hear about text fringing making text unclear but now that I see it, with 125% scaling, it doesn't ~~both~~ me		** You'll hear about text fringing making text unclear but now that I see it, with 125% scaling, it doesn't bother me
	* I don't worry about burn-in as much as I thought I would:		* I don't worry about burn-in as much as I thought I would:
	** The LG C4 really reduces the worry about burn-in with features you don't have to worry about remembering to do, like pixel shifting, automatic dimming, and a screensaver when there's no activity, and there is a manual pixel refresh procedure accessible from the menus		** The LG C4 really reduces the worry about burn-in with features you don't have to worry about remembering to do, like pixel shifting, automatic dimming, and a screensaver when there's no activity, and there is a manual pixel refresh procedure accessible from the menus
Line 202:		Line 203:
	=== You must have a quality HDMI cable that meets spec ===		=== You must have a quality HDMI cable that meets spec ===

	* tl;dr Buy a well reviewed HDMI cable capable of handling the resolution, refresh rate, and bandwidth requirements that you will need		* '''tl;dr''' Buy a well reviewed HDMI cable capable of handling the resolution, refresh rate, and bandwidth requirements that you will need
	** For example, a UGREEN 8K HDMI 2.1 48Gbps cable allowed me to max out the LG C4 to 4K 144hz HDR		** For example, a UGREEN 8K HDMI 2.1 48Gbps cable allowed me to max out the LG C4 to 4K 144hz HDR
	*** [https://www.amazon.ca/dp/B0CFFFSFFN?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 UGREEN 10K 8K HDMI 2.1 Cable 48Gbps 6FT, Certified 8K@60Hz 4K@120Hz 144Hz High Speed Gaming Cable Braided Cord, eARC HDCP 2.3 Dynamic HDR Compatible for HDTV/PS5/Xbox/SoundBar/RTX3090/Blu-ray ]		*** [https://www.amazon.ca/dp/B0CFFFSFFN?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 UGREEN 10K 8K HDMI 2.1 Cable 48Gbps 6FT, Certified 8K@60Hz 4K@120Hz 144Hz High Speed Gaming Cable Braided Cord, eARC HDCP 2.3 Dynamic HDR Compatible for HDTV/PS5/Xbox/SoundBar/RTX3090/Blu-ray ]
Line 223:		Line 224:
	=== HDMI Deep Color Prevents PC Screen Displaying on LG C4 OLED TV ===		=== HDMI Deep Color Prevents PC Screen Displaying on LG C4 OLED TV ===

	* tl;dr Turn off HDMI Deep Color from Settings > General > External Devices > HDMI Settings > HDMI Deep Color (On an LG C4 OLED)		* '''tl;dr''' Turn off HDMI Deep Color from Settings > General > External Devices > HDMI Settings > HDMI Deep Color (On an LG C4 OLED)
	** '''Update 2025-05-31''': I don't know what changed but HDMI Deep Color now seems to work. The only thing I can think of is that I have Game Optimizer disabled now. You may have to enable Game Optimizer and go through the TV menus to get the PC display back. After that, it should be fine.		** '''Update 2025-05-31''': I don't know what changed but HDMI Deep Color now seems to work. The only thing I can think of is that I have Game Optimizer disabled now. You may have to enable Game Optimizer and go through the TV menus to get the PC display back. After that, it should be fine.
	** Alternate: Reset to factory defaults		** Alternate: Reset to factory defaults
Line 233:		Line 234:
	=== Intermittent Visual Gridding Artifacting ===		=== Intermittent Visual Gridding Artifacting ===

	* ~~My Solution:~~ Disable FreeSync in the monitor settings		* '''tl;dr''' Disable FreeSync in the monitor settings
	** I wasn't gaining much anyway since I'm able to maintain a stable 90fps in the game I was playing (GTR2)		** I wasn't gaining much anyway since I'm able to maintain a stable 90fps in the game I was playing (GTR2)
	** And Windows Triple Buffers windows (I was using GTR2 in borderless window mode) which helps reduce screen tearing		** And Windows Triple Buffers windows (I was using GTR2 in borderless window mode) which helps reduce screen tearing