Vai al contenuto
ConstantForceMultiplier = -60—–It has become a tradition to delete this line, although in reality, it doesn’t affect anything. Allegedly. But you should still delete it because I say so.
Depth = 3216/32Unless you playing this game on a very, very old laptop, 32-bit color should be your starting point, no question. If you have performance issues, 16 may give you some boost, or maybe not (I can’t say I’ve tried it).
ForceFeedback = truetrue/falseYou gotta have FFB. Or do you?
Fullscreen = truetrue/falseFullscreen mode: true / Windowed mode: false. RBR doesn’t support the use of alt+tab in fullscreen, and that’s why most people prefer the windowed mode (porridge himself being the honourable exception).
MinDepthBits = 24
MinStencilBits = 8
—–Unless I’m very mistaken, these are the original values. If you have different original values, yours must the real original values. Either way, let them be.
ParticleQuality = highhigh/low/
The quality of gravel/snow/tarmac/water particles. Obvs.
RenderCarShadow = truetrue/false(You can add this line if it isn’t already included.) Self-explanatory. In the olden days, turning this off was one of the classic optimising measures. These days it hardly matters, though.
RenderQuality = highhigh/lowThe main setting for graphics quality. Only one sensible choice and that is not Low. While low may remove the death-defying marshals (please don’t be stupid, there are mods for that, you know), it also isn’t always supported properly by some addon stages (causing things like missing ground textures).
RunIntro = false
RunStartup = false
true/falseSet both to false. Like immediately.
Sound = truetrue/falseYou gotta have sounds.
UseCubicEnvironmentMaps = falsetrue/falseAlso known as Dynamic Car Reflections (RBR Startup). It goes without saying that it somewhat affects FPS in general but on certain addon stages it murders the frame rate (like on Swiss I and II or Fernet Branca). So it’s recommended to disable this, especially if you have intentions to drive from the cockpit view. (You do have another way to maintain a decent frame rate from that view – even with this enabled – and that is to make the driver camera static with NGPCarMenu.)
UseEAX = false
UseSoftwareAudio = false
true/falsePorridge has a sound card for home studio use, so you won’t get much insight about either of these settings, but here’s a spoiler alert: Depending on your sound card, these either will have an effect or they won’t. If you’re not up for extensive testing, having both false at a start should be absolutely fine.

EAX is a feature for Creative Technology products such as Sound Blaster cards. Yay.

Even less knowledge about SoftwareAudio though, but the understanding is that if you had both enabled, RBR would ignore EAX and use only SoftwareAudio, but none of this may be true with modern hardware. SoftwareAudio may also provide a fix if you have issues with car sounds on replays.
UseTripleScreenBuffers = false(true/false)Allegedly this setting is not used by RBR, but even if it was, Triple Screen Buffer should only be used when VSync is on, otherwise it’d be pointless. And because it is said to increase the input lag, it may not make sense to have it on even with VSync. In short, to summarise. Disclaimer: Porridge knows nowt, let’s be honest.
WaitRetrace = true(true/false)Presumably “true” is the default setting, but it doesn’t matter because this setting is not in use. Thank fuck for that, because if it was, I would have been in a world of shit trying to explain this one to you.
XRes = 1680
YRes = 1050
—–RBR Startup obviously doesn’t give you that many options, so here you can set whatever resolution you want and let FixUp then correct the aspect ratio. Users with multiple screen setup should note that perhaps unsurprisingly RBR doesn’t have a built-in support for multiple screens so enabling NVIDIA Surround/AMD Eyefinity or other equivalent solution is required.
ShowFPS = falsetrue/falseRBR’s own FPS meter.
RunDiagnose = falsetrue/falseThe true usefulness of this is very much an open question but maybe this is something you’d want to try as a last resort in heaps of trouble. Although let’s be real: you will never be in trouble as long as you do exactly what we tell you. Anyway, if “true”, a file Diagnostics.txt is created when running the game. Thanks go to WorkerBee for sharing this nugget.
fullscreenWindow=10 or 1Removes the window decorations brought to you by Microsoft (titlebar with close button etc.) and positions the window automatically against the upper left corner when playing in windowed mode (Fullscreen = false).
fixAspectRatio=10 or 1Fixes the aspect ratio, regardless of your resolution. Surprised?
headGasketDurability=100 – 100 or 1 (default) and 2–10 (2 to 10 times more durability). It may or may not make a difference, but you should just set this one to 10 and move on.
centerMenu=10 or 1This fix/feature comes in handy if you don’t see the menu texts or if the HUD is excessively stretched with your resolution. Basically, whatever resolution you’ve set, centerMenu’s idea is to keep menus and HUD in 4:3-mode. You may want to try both settings and see which one you prefer. (This feature will undoubtedly have a knock-on effect on the dash position, but you can always move it back to wherever you want with Pacenote Plugin.)
processor=0——In the FixUp readme, read about “Main Thread Processor” and because you didn’t understand anything you just read, keep the default value (0).


0 or 1


0 = RBR’s original FFB, 1 = WorkerBee’s Adaptive Force Feedback. AdaptiveFFB is “stronger” than the original FFB, but it’s also more demanding performance-wise. Use AdaptiveFFB only with VSync enabled. Note! When using AdaptiveFFB with modern gaming monitors (120hz or better), you may experience unbearably long FPS drops (lasting even 10–20 secs) at stage starts/after Call for Helps. The best you can do in such cases is to revert back to RBR’s original FFB.

ffbBufferCycles is tied to AdaptiveFFB, meaning it’s irrelevant if adaptiveFFB=0. You can read about this setting in more detail from readme, but here’s the low-down:
0 (AdaptiveFFB at its best, requires the most from your computer.)
1 (Not so best adaptiveFFB, try this if 0 affects FPS negatively.)
2 (Again, slightly worse FFB than with 1, but with better performance.)
3 (At this stage, the whole feature may become pointless.)
4 (Forget it…)

Also ffbMinFPS is tied to Adaptive FFB only, meaning if adaptiveFFB=0, the setting is effectively disabled. 58 is the default setting, meant for a 60hz monitor. So always use a slightly lower value than what is your monitor’s refresh rate (like 142 for 144hz etc).
—–For the owners of direct drive wheels. I have a budget wheel, so I’ll just shut up.
0 or 1(Tied to RichardBurnsRally.ini UseCubicEnvironmentMaps setting; if that’s disabled, so is this.)

The very latest feature that improves the car mirrors especially. Safe to say that in RBR’s vast car collection working mirrors are somewhat rare, but when a car does have them (like Shenshee’s Porsche 911 SC RS does, for instance), the reflections by default are often (always?) severely lacking (blue patches). This feature makes everything properly visible.
VSync on (default)
—–These are the default settings, and make no mistake, they are truly wonderful settings.

SoundRefreshRate is primarily meant for fixing all kinds of sound issues when VSync is turned off, but in case you hear things like oddly random skidding sounds where you shouldn’t hear them (like even on a straight), by all means activate this fix by setting it to 60.
VSync off
—–Let’s make it clear that in RBR, turning off VSync makes windscreen wipers flicker rather annoyingly in the rain. You can counter this by either removing the wipers (easy with RBRCIT), or, turning VSync back on. Championships have been won with VSync, I’m sure.

SoundRefreshRate: According to The Bee, porridge’s best friend, reasonable values are from 30 to 90, with 60 being the recommended value.