Troubleshooting RBR/RBRTM/RSRBR

Last updated: 23 March 2020 (The Corona Update).


RBR in general

RBR doesn't launch at all
RBR crashes on launch
"Could not find any compatible Direct 3D devices. Richard Burns Rally will now exit."
The game complains about a missing d3dx9_##.dll (may not even launch)
A black screen starting from the menu
A white screen when launching (no crash, but loading can take a long time)
No text visible in menu
Alt+Tab doesn't work in fullscreen mode
RBR crashes when loading a stage (with or without Visual C++ message)
Stage crashes during loading screen when repeated
RBR crashes to desktop during a stage
RBR crashes during Rally Season (Updated Mar 2020)
Car issues in Hot Seat Rally (Multiplayer mode)
Controller Setup 1: The wheel is not detected / missing FFB
Controller Setup 2: The wheel is detected but can't assign steering
Wrong degrees of rotation in-game (Logitech Gaming Software)
Controller settings can't be saved / Saved controller settings disappear
How to invert controls in RBR?
Inverted controls are at 100% on the first stage of the session
The virtual steering wheel not in sync
What's the deal with Max Steering Lock? (Historical overview)
Car has only reverse and first gear
Car sound issues (all-in-one)
Changing settings when on stage don't save
A gear won't downshift if RPM too high
Bad FPS on certain addon stages
Low FPS for a while at the start of the stage / after resuming a stage (Updated Mar 2020)
Stuttering after 70 mins on 144hz monitors (NEW! Mar 2020)
Poor performance on BTB stages
Tarmac setup is forced / Wrong tyres on BTB stages
Ground textures missing in places
Black mipmap lines appear in the road
Windscreen wipers flicker annoyingly in the rain
Car glasses are all grey (NEW! Mar 2020)
Saved replay doesn't play back
Issues with co-driver (for users of Pacenote Plugin only)
Cote d'Arbroz I: Pacenotes are all fucked up
Loading Peyregrosse-Mandagout takes ages
How to open telemetry files with gnuplot
RBRCIT: Some of the "common" problems and errors
RBRCIT: How to perform a clean reinstallation


RBRTM only

Tournament Plugin missing in-game
"Connection failed, try again?"
"Data error"
"Wrong weather definition in TrackSettings.ini"
"Cant open file" in Shakedown mode
Can't choose certain cars in online events (Updated Mar 2020)
The clock doesn't stop at the finish, leads to DNF
So what's the deal with Monster Hill Climb?
"Not physics file from 1.02 version. Please use original physics file or..."


RSRBR only

Checking the downloaded RSRBR packs/updates with voirMD5
RSCenterMenu's texts and icons are somehow misplaced
The game gets stuck immediately with the camera going back and forth with the menu not showing up (Go and RSRBR buttons)
Manual gears don't work
A BTB Country Pack stage loads Cote d'Arbroz instead
Textures get all mixed up (for instance, gravel mod with tarmac textures)
Saved camera settings for a car get erased (the ini file is replaced)
In RSCenter, you can't access Public or Championship sections due to "error" or "server error"
Error "Download and Install Addon (....) for Public Sessions" in a Public Session
Depannage: changing RBR's install path in registry
"Physics file is absent"



RBR in general



RBR doesn't launch at all

By RBR not launching at all, we mean that absolutely nothing happens (not even an error message) when you try to run the game either via RichardBurnsRally_SSE.exe or Start Game in RBRCIT. In RSRBR, RSCenter would do its usual preparations before running the game but eventually it just stops loading and then nothing. Now, unless you've knowingly turned off UAC (= User Account Control), safe to say the main culprit in about 95% of cases would be Data Execution Prevention ("DEP" to friends).

(A clean, unmodded game would never have this problem, it's only after you start installing plugins or mods on top of it and Windows realises that the game has been tampered somehow and is keen to overprotect you. Worth noting that this behaviour is largely inconsistent, and can also crop up when you least expect it.)

Anyway, on with the solution:

RBR/RBRTM: Run RichardBurnsRally_SSE.exe as an administrator + add it as an exception in Data Execution Prevention settings.

RSRBR: You need to run exe-files like RichardBurnsRally_SSE.exe as an administrator + add them as exceptions in Data Execution Prevention settings. IMPORTANT! In a 64-bit Windows, do not add 7z.exe to the exceptions.

How to run as admin: Right click on .exe (File Type: Application) → Properties → Compatibility tab → Check Run this program as an administrator → Apply.

The DEP settings: Type sysdm.cpl (.cpl refers to Control Panel) in the Windows search box and run it → On the Advanced tab go to Performance settings → Data Execution Prevention tab (check Turn on DEP for all programs and services except those I select and add *_SSE.exe to the list.)

Note! You shouldn't have to restart your computer for these changes to take effect, but you may have to do just that, so do not dismiss these solutions too quickly in case nothing seems to improve at first try.



RBR crashes on launch

RBR crashing on launch but before the profile selection (usually with the RichardBurnsRally_SSE.exe has stopped working or Visual C++ Run-time Library error message) is obviously a more complex matter as it can so easily be just about anything but a DEP related issue – although it's not totally out of the question (an error message doesn't necessarily eliminate this possibility). However, you should still primarily focus on other possibilities like a plugin (the likeliest culprit) or a mod you may have installed a minute ago.

Like if you do suspect a plugin, it should be easy to test. Just disable it in one way or another (renaming the main file from *.dll → *.no is the easiest method) and run the game again to see what happens. Depending on a plugin, it could be a simple case of missing files in its own subfolder and reinstalling it may magically fix the issue (although if this was true, you really should consider changing or at least updating your archiver). If the issue persists after reinstallation or two, then it may be wise to begin eliminating a potential DEP issue next.

None of this probably helped you in any meaningful way and it wasn't meant to, let's get that right, as this is one of those issues where all we can really say is "good luck!".



"Could not find any compatible Direct 3D devices. Richard Burns Rally will now exit."

You've set the game's resolution too high for your system (compared to your monitor's max resolution). Edit the XRes and YRes lines in RichardBurnsRally.ini (again) to fix it.



The game complains about a missing d3dx9_##.dll (may not even launch)

Download and install DirectX End-User Runtimes (June2010). (Note that directx_Jun2010_redist.exe as such doesn't install the DirectX files, it only extracts the installer files to the location of your choice. The actual installation then begins by running DXSETUP.exe.)



A black screen starting from the menu

To clarify: RBR doesn't crash, it continues to run normally otherwise, so unless you've muted the menu sounds/music you should still hear them.

The solution is to right-click on RichardBurnsRally_SSE.exe → Properties → Compatibility tab → check Disable desktop composition. That should do it.



A white screen when launching (no crash but loading can take a long time)

This is RARE, let's make that very clear. We hadn't even read about this until recently and the only thing we do know is that on certain setups RBR doesn't like it if the headphones (or speakers) are not plugged in before running the game. Now, if merely having your cans plugged in doesn't fix the issue as such and you had previously changed the DEP settings only because of this, try reverting back to the default DEP setting to see if it helps. Don't ask us why.

(If your RBR crashes back to desktop via white screen and has nothing to do with any connections, you should probably look more into this one instead.)



No text visible in menu

To cut a long story short, open \Plugins\FixUp.ini: centerMenu=0 → centerMenu=1

This may have side effects in terms of dash positioning, but you can always use Pacenote Plugin to move the dash wherever you want, like demonstrated in this article.



Alt+Tab doesn't work in fullscreen mode

So you can get out of the game, but you can't return to the game. This is perfectly normal as alt+tabbing works only in windowed mode (RichardBurnsRally.ini: fullscreen=false).



The game crashes when loading a stage (with or without the dreaded Visual C++ Run-time error)

Before anything else, let's make it very clear what these issues are NEVER about: Visual C++. And also, you can easily make the game crash by impatient alt+tabbing during the loading screen, so above all, respect the game! #RespectRBR

Porridge has heard there are roughly three ways of how RBR would crash during a splash screen: 1) Loading freezes to about 25% and pressing any key exits the game instantly; 2) the Visual C++ Run-time error complaining about... well, whatever it complains about; and 3) loading stops at 50% because you amateurishly forgot to import the model to \Cars. There may be some subtle variations to these but porridge wouldn't know because RBR has never crashed on him.

Generally writing, the problem is with either the car you selected or the stage you're going to. Or both. Or something else entirely. Simple as that.

Stages (offline + online): There is also the more sinister variation to this topic that deserved its own chapter, but generally, issues with stages more often than not come down to a faulty texture pack that may not properly support certain surface types/weather packs and in cases like that, reinstalling a stage using an official CZ installer is useless. What you need is unofficial stage patches. Most of the fixes known to man are already included in the RBR Czech TrackPack, but luckily they can also be downloaded separately from here or here + then there is the one for Puy du Lac. But please note that in online rallies any fixes won't mean a thing if a promoter has used wrong, unsupported options for a rally (in RBRTM, you can draw your own conclusions just by looking at Show retired cars).

Cars: Most likely an issue with a modified skin if other cars work fine on the same stage. Either retrace your steps or just re-download the model again with RBRCIT to be sure. Obviously, it can also be a typo in relevant files like \Cars\cars.ini, \Audio\Cars\Cars.ini etc. (highly unlikely with RBRCIT, of course). For potential skin related issues, you should also study this chapter.

RBRvr + Pacenote Plugin: This combo is also known to cause crashes to desktop because they aren't all that compatible. However, WorkerBee added a working solution to Pacenote Plugin's version 1.11.0.11: Whenever VR is in use, turn off the plugin GUI (Pacenote.ini: enableGUI=1 → enableGUI=0). This will cut out the CTDs, and your pacenotes still get called just like you want them. (To easily switch between driving and recce modes, using a generic mod enabler is recommended, and here's how to...) Note! For other VR-related issues, there is now also a separate article.

Broken engine sounds (.eng): Let's face it, RBR is an unfinished game and one of the most peculiar and unnecessary bugs pointing this out is that half of the original engine sound files simply don't work at all and the game crashes during the loading screen. The broken .eng files in question are bubbla, fiat, Saxo and vaux (feel free to delete them in \Audio\Cars). The rest – subaru, subaru2, mitsu and test – are OK (although test is basically the same sound as subaru). But since the original sounds aren't all that good, you can download some addon ones from sources such as Nanamiso (some of the mods are for other games) and MEGA (mostly the same mods by Nanamiso, but a decent collection nonetheless).



Stage crashes during loading screen when repeated

For a small minority of gamers certain stages – most notably Semetin – are known to crash during loading screen when they are driven more than once in a session/rally. Other less talked about stages are Carvalho de Rei and Verkiai. (Although at time of writing, porridge has already forgotten most of this topic).

The first recommendation would be to delete RBRTestPlugin (dll + subfolder in \Plugins), and if you're VERY lucky, it may help things considerably, but the reports do show that for the vast majority the crashing will continue, even if without the infamous Debug Error! message. But still, it's worth trying regardless. (Removing RBRTestPlugin may stop you from running the game, but the first chapter should help you through that.)

To further solve these crashes, WorkerBee chipped in by adding a feature called Enhanced Trackloader in FixUp 3.0. However, it isn't an automatic (global) change when it comes loading stages as it does require the user to split the "problematic" lbs files to new .lbs and .lb2 files with splitlbs.exe that can be found inside FixUp's \bin folder.

But does it work?

No-one knows, the fix remains largely speculative, at least we are not aware of anyone with the problem having even tested it. After all, online plugins like RBRTM do not currently support splitting the lbs file for online rallies (lbs files are CRC checked too), so if it did work, it'd only be useful in offline driving. More info: here.

So, to lower the threshold for gamers with techno fear, let's split Semetin 2009's lbs files as an example:

  1. First we're going to find out the ID of the stage from \Maps\Tracks.ini → Semetin 2009's ID is 582.

  2. Copy files track-582_M.lbs and track-582_O.lbs to \Plugins\fixup\bin.

  3. Drag them one at a time onto splitlbs.exe (splitting multiple files doesn't seem to work).

    → splitlbs makes a backup of the original by adding an extension ".orig" + splits the file into lbs and lb2 files

  4. Cut the newly-created lbs and lb2 files and paste them back to \Maps.



RBR crashes to desktop during a stage

Let's leave possible antivirus and Windows 10 features aside (that can often be countered by using the windowed mode, or – and this is quite revolutionary – by adjusting their settings) and focus purely on RBR, then the most likely culprit must be the sounds, whether it's erroneous sound effects (cars or otherwise) or a flawed co-driver mod. That's all we can't think of, really, especially if the crashes tend to happen at the same places, more or less.

However, explaining how to find and fix these RBR sound issues may be too boring even for this blog but here's a spoiler alert: more often than not it's just a case of a wrong entry in .ini file.



RBR crashes during Rally Season

Ignoring the obvious mishaps of editing the driver stats like mentioned here, what is already known from years ago is that modding dds files in Generic folder mid-season makes the Rally Season very unstable and there's no way to fix it other than starting a new season. But by the same token, it is possible that any kind of modding mid-season – be it changing a car or merely installing a different skin – may prove to be unwise (but this is just speculation and NOT proven by any means).

Update Mar 2020: For some years (presumably), there were far more grave stability issues with the Rally Season mode, but hopefully with FixUp's version 3.1 that tries to address at least some of the concerns, these issues should now be in the past. (We here at Vauhtimurot HQ haven't tested any of this yet and perhaps never will.)



Car issues in Hot Seat Rally (Multiplayer mode)

While Hot Seat Stage should be fine with any addon car, certain car models – regardless of the physics version – are known to hit big problems like missing tyres at some point during a Hot Seat Rally. Unfortunately, even WorkerBee deemed these fundamental RBR issues unfixable years ago.



Controller Setup 1: The wheel is not detected / missing FFB

In case RBR doesn't detect your wheel at all or the FFB is missing, try installing DirectX End-User Runtimes (June 2010). Depending on the wheel you're using, the more ancient DirectX files provided by the game itself may not be enough. If problems persist and even changing to another USB port doesn't make a difference, try running Microsoft DirectX Diagnostic Tool (type dxdiag in the Windows search box) to see if it knows any better.



Controller Setup 2: The wheel is detected but can't assign steering

For some reason, assigning steering with some wheels is way more difficult than normally (Fanatec tends to get mentioned a lot), and that's because you'd have to turn the wheel very fast lock-to-lock to get it done. So, change the rotation degrees temporarily to something silly like 180 or even less to make it easier. Works every time.



Wrong degrees of rotation in-game (Logitech Gaming Software)

A known explanation for those who are using Logitech Gaming Software (aka LGS) with different, custom game profiles is that the buggy, ageist and now unsupported(?) software can't always change to the correct profile when running RBR, but instead it somehow manages to force settings meant for another game entirely. So with modern games everything will surely work but not with the best game of all-time, it's an utter farce, it really is. In order to solve this, you can go two ways:

1) You stick to Logitech Gaming Software and learn to work around its bug. This may prove to be a right pain in the arse because at worst, every time before running RBR, you may have to reboot the utility and make sure that the so-called default profile is in use + also that RBR's own profile truly has the desired degrees set. Something along these lines should definitely work but it's not exactly practical, is it? Another approach would be to ditch different game profiles, but obviously the more games you're playing regularly, the less ideal solution it is.

2) You switch to the current Logitech bloatware called G HUB (that officially replaced the old LGS in 2019). This should eradicate the problem with profiles but may of course introduce other issues (apparently G HUB doesn't have the greatest of reputations). But everything may also go just fine. No harm in testing it, at least.

Your call, good luck, but before we leave you, there's just enough time for a reminder: Regardless of the software, always link the game profile to RichardBurnsRally_SSE.exe.



Controller settings can't be saved / Saved controller settings disappear

(First it's absolutely crucial to differentiate RBR's basic feature from the nasty and more surprising issues covered in this chapter!)

There are known cases – albeit rare – where the controls are not saved at all if a desktop shortcut is linked to RichardBurnsRally.exe instead of RichardBurnsRally_SSE.exe. So always link the shortcut straight to _SSE.exe. (Obviously running the game via RBRCIT is more than recommended and none of this should be of any concern with RBRCIT.)

If you play in windowed mode and your controls tend to disappear always when resuming RBR – forcing you to re-assign them everytime – something's gone horribly wrong, let's get that absolutely right. What you should do is to go to your SavedGames folder and delete pfYOURPROFILE.acm and then re-assign the controls in-game. It should work a treat for a while, at least. Until the next time. (Since .acm file contains only your controller settings, deleting it instead of the entire profile is the more preferable option. However, if the problem doesn't go away, then you may be forced into deleting and re-creating your profile from scratch but it shouldn't come to this, really.)



How to invert controls in RBR?

Open input.ini and change the problematic controls from false → true. However, if you need to invert FFB (not that I've ever heard of anyone needing to do that), the option can be found in-game. But please, do read the next chapter as well.



Inverted controls are at 100% on the first stage of the session

It's an annoying bug, no doubt, but at least it's the same for everyone! To normalise them, you have to remember to use them on the start line and it'll be fine. We can assure you that you'll forget to do that every now and then, but that's all part of the annoyance! Note that the same issue recurs when resuming RBR in windowed mode, so it's not exactly advisable to go and surf the net mid-stage.



The virtual steering wheel not in sync

The game's default degrees centre-to-lock is a modest 60 for the wheel animation, but you can change it to anything you like by first extracting LM_Driver.ini from Misc.rbz to \Misc (create it if needed) and then edit its line Max Steeringwheel degrees. Care! Turn off the file's read-only attribute before editing. You can read more about files located in Misc.rbz here.

An alternative and perhaps more preferable solution to the hardcore is to remove the steering wheel (either with RBRCIT or even manually) and get rid of this snag altogether.



What's the deal with Max Steering Lock? (Historical overview)

Way too late for this, in fairness, but because it is the 2nd most frequently asked question in the history of RBR, here's a short overview factoring in different versions of physics.

Vanilla physics & NGP v1–5: The vanilla presentation of this particular setting has understandably caused a lot of confusion amongst newcomers, and all because of the devs forgetting to add a decimal point to the setting. Basically it's about how much the tyres are turned at full lock, that's it, plain and simple. If the game has a setting of 540, it's really 54.0 degrees in all, meaning about 27 degrees "on average". But you shouldn't quote porridge on it, because he didn't really bother to "cut open" any of the cars again to be absolutely sure. (But I'm sure you got the general idea anyway.)

NGP6: The NGP creator extraordinaire WorkerBee removed the possibility to edit Max Steering Lock and also changed its original meaning in the process. Now it's only meant as a hint how you would set the degrees of rotation IF you wanted to match the real thing. The value is center-to-lock, so for instance, the modern WRC/R5 cars would all have 270 (as they are supposed to have 1.5 turns lock-to-lock). As an added bonus, the steering ratios should now be closer to real life counterparts too, but I purposely use words "should" and "closer" because with the exception of M-Sport, I don't think that in the last 20 years other rally car manufacturers have shared this relatively unimportant piece of info.



Car has only reverse and first gear

Excerpt from the current ReadMe.PhysicsNG.txt: "Only genuine NGP cars will work with [NGP6] plugin. All other cars are limited to using only reverse and first gear." This essentially means that with the NGP6 plugin, you can only use the official NGP6 releases put out by WorkerBee. To make this abundantly clear:

- You can't add to the car selection in RBRCIT by mixing NGP and vanilla physics anymore like you may have done in the past, which is only a good thing because it didn't really make much sense to begin with.

- The Original RBR Cars will not work either, simply because they do not have NGP physics.

- And lastly, WorkerBee doesn't regard even NGP5 cars as genuine NGP cars which should tell you everything you need to know in order to solve your NGP related issues.



Car sound issues (all-in-one)

The engine sound changes when resuming from the menu or turning Pacenote Plugin on and off: Go to \Plugins and delete/remove eq_mix.dll. The plugin in question only comes with things like RSRBR, so the chances are that you have never even known to have it, let alone used it, hence getting rid of it shouldn't cause any heartache.

Strange "warping/echoing" blow-off valve sound: There hasn't been enough cases (that we know of) to make properly weighed conclusions about the subject, but usually it's been a case of edited NumberChannels setting (like 64 or above) that has caused this particular bug and reverting back to default 0 (zero) has been the cure without exception, just like suggested here.

Broken engine sounds (.eng): Let's face it, RBR is an unfinished game and one of the most peculiar and unnecessary bugs pointing this out is that half of the original engine sound files simply don't work at all and the game crashes during the loading screen. The broken .eng files in question are bubbla, fiat, Saxo and vaux (feel free to delete them in \Audio\Cars). The rest – subaru, subaru2, mitsu and test – are OK (although test is basically the same sound as subaru). But since the original sounds aren't all that good, you can download some addon ones from sources such as Nanamiso (some of the mods are for other games) and MEGA (mostly the same mods by Nanamiso, but a decent collection nonetheless).

NGP6: The engine NOLOAD sound lower than before: This is normal: it is an NGP6 feature explained here.

The clattering of NGP cars: It was a common belief that the clattering sounds would be a sign of cars tending to bottom out on bumpier roads with default setups, but according to WorkerBee himself, this is not true and the sounds actually originate from the bump stops instead. Now, if you're not a setup engineer yourself and you only wish to partly silence this annoyance, you can download Kaderabek's mod and replace the files in \Audio\Impact\Ranged. Care! For setup engineers it is worth knowing that RBR unfortunately uses the same sound files when cars do bottom out.



Changing settings when on stage don't save

That's normal because any changes would need to be saved into the profile (like MULLIGATAWNY) too, so changing settings during a stage is only meant for temporary changes. The only way to actually save your profile is via Options in the main menu.

RSRBR: In RSCenter all of this means that you'll have to go to SSE mode to change and save settings permanently, Go and RSRBR modes are no good.



A gear won't downshift if RPM too high

Go to game's Options >> Gears >> Gear protection → off.



Bad FPS on certain addon stages

By "certain", porridge would mainly refer to classic format stages such as Swiss I + II (III and IV are fine), Fernet Branca and Verkiai, but the following nuggets will apply to other similarly heavy stages.

In RBR, two of the biggest frame rate stealers – ignoring FixUp's AdaptiveFFB now – that some stages are not particularly fond of must be Dynamic Car Reflections (better known as UseCubicEnvironmentMaps in RichardBurnsRally.ini) and the shakiness of the driver cam (cam_internal). Both have a pretty similar impact on FPS by comparison, but naturally the easiest and wisest move would be to disable the former (because it's pointless) and consider the latter only if you really want to have a static cockpit cam or if you wished to retain those allegedly dynamic reflections for whatever reason.

You could do both, of course, but let it be known that there would be no real upside in terms of frame rate (on the mentioned stages, at least) and even if there was, it'd be next to nothing.

Another classic optimising measure has been to disable car shadows (RichardBurnsRally.ini: RenderCarShadow=false, add the line if needed), because at the end of the day, what do you need shadows for if you rather watched a screensaver than an RBR replay? Turning it off can indeed give you a small boost, but intriguingly – and porridge may be wrong about this – Fernet Branca is an absurd exception with its performance actually dropping a bit without car shadows. How can this even be, porridge wonders without a clue but then again, maybe you should test it yourself, and that is if you're truly interested which you probably aren't. To be fair.

(Do remember that sky options like Heavycloud Heavyrain are more ideal for testing the limits of your hardware than the usual default Crisp Clear would be, because they tend to be "heavier".)



Low FPS for a while at the start of the stage / after resuming a stage

The problem where frame rate takes a long time to normalise itself (even 10–20 secs), can only be about AdaptiveFFB. As FixUp's own readme clearly states, you should use AdaptiveFFB only with VSync. But that's probably only half of the story, because if you already have VSync enabled, and it's still doing it, which – according to some reports, at least – is indeed possible, it is likely because AdaptiveFFB isn't really meant to be used alongside the so-called gaming monitors (120hz or above). So while you can always try to fiddle with the ffbBufferCycles setting (0→1→2) first, you may also want to give in immediately and change back to the original, award-winning FFB of RBR.



Stuttering after 70 mins on 144hz monitors

Disclaimer: Porridge hasn't given this topic the respect it deserves and the following summary has been written purely from memory and may therefore have shocking inaccuracies. For the full story with its twists and turns you can go to GVRC.

This is a known issue that cropped up at earlier stages of NGP6. In an attempt to fix this for NGP plugin 6.3 release, WorkerBee included a configurable physics update rate (RichardBurnsRally.ini: physicsUpdateRate), check out ReadMe.PhysicsNG.txt for details.

However, for a lot of users there seems to be a trade-off with this fix: if you increase physicsUpdateRate to, say, 150 (essentially anything above your monitor's refresh rate), it would more than likely fix the 70 minute bug, yes, but it may then introduce a new type of annoying micro stutter that would start immediately once the game is running. So, is it possible to find a value between 137 and 153 that would get rid of both types of stuttering? Perhaps. But it's wise to prepare yourself for a bitter disappointment and simply learn to live with the 70 minute bug, which may not be easy considering that with certain online plugins you have to often endure long legs in one sitting. All this is something that promoters may have to take into account in the future.

Apparently, not all 144hz monitor owners have recognised this issue on their setups though, so in case you want to experiment this on your own hardware, remember that you don't have to actively play RBR for the first hour, leaving the game running in the background is enough.



Poor performance on BTB stages

It's worth reminding that some BTB stages are much heavier on resources than your average native format stage. Try lowering the resolution and/or graphics settings.



Tarmac setup is forced / Wrong tyres on BTB stages

If TrainingDay plugin is installed at the same time, RBR_RX cannot load gravel and snow setups automatically, meaning tarmac setup is the default setup everywhere. Therefore you should uninstall TrainingDay plugin to properly enjoy BTB stages (renaming TrainingDay.dll to TrainingDay.no should suffice).

It's very likely that merely removing TrainingDay wipes out any issues of wrong tyres, but in case you still occasionally feel like you're driving with the wrong tyres on gravel/snow, that's probably because you are, but fortunately, you can use a nifty little tool called RBRWRONG+TYRE (by Racer_S). With it, you can choose the tyres you want and leave it running in the background before launching RBR. Practical? Of course not.



Ground textures missing in places

Change Render Quality from low to high in RichardBurnsRally.ini. Some addon stages (such as Northumbria, Bruchsal-Unteröwisheim and Undva) are known to not support the low setting.



Black mipmap lines appear in the road

From the official 1.02 patch notes: "The black lines appearing on the road is caused by the users forcing the driver to use AF (Anisotrophic Filtering) and/or FSAA (Full Scene Anti-Aliasing). By default it is set to be application controlled, which the game works fine with. This can have other graphical side effects, such as poor looking fonts and 2D graphics, because if you force to use these techniques they are applied to everything that is rendered instead of the application selecting where to use it. Also it does degrade the performance." There you go. Couldn't have put it any better.



Windscreen wipers flicker annoyingly in the rain

This will indeed happen if you disable vSync in FixUp, it is what it is. With some cars you may be able to just edit the camera in such a way that hides the flawed animation, but you can also let RBRCIT remove the wipers entirely from all cars, or, you can do the same yourself manually by opening a car's own IniFile: Find [i_wiper_r] and [i_wiper_l] and edit the line Switch = false → Switch = true.



Car glasses are all grey

Not an everyday occurrence, it has to be said, because not only it requires massive skin files, likely it'd crop up only on certain stages such as Shurdin and Ouninpohja (they are the known examples). At day's end, here are the two reasons that would usually cause this issue:

1) The car's textures have been exported with a "wrong" preset and the files have ended up unnecessarily gigantic because of it. You can try exporting the DDS files again; using the preset BC3/DXT5 should be enough for all textures, but if you'd like optimise even more, you can use BC1/DXT1 for anything non-transparent.

2) The car's texture quality is way too high (like 8192x8192), which would render a simple re-exporting insufficient. You'd also have to rescale the texture files first to something less excessive (like 2048x2048 or even 1024x1024). Fixing only the transparent files may be enough, or maybe not. If you're using a skin made by someone else and you're not that interested in doing the dirty work yourself, remember that you can always reinstall the default skin as they tend to be reasonable enough.

Important! Both of these flaws would be well capable of making the game crash during the loading screen too (especially for VR users).



Saved replay doesn't play back

Not only do you have to have the same car installed but also it has to be installed to the exact same car slot when watching replays, otherwise the replay will load but not play back. (Although let it be known that in RBRTM, there have been some rare and isolated cases where even a matching car and slot have not worked but they're just that: rare and isolated cases.)



Issues with co-driver (for users of Pacenote Plugin only)

Mods by porridge: The symptoms vary depending on a stage but usually they occur because the order of installation has been wrong. Only two things to remember of porridge mods: 1) you have to set RBR's pacenote language to French*, and 2) the mods have to be (re-)installed on top of a clean unmodified copy of Pacenote Plugin, not the other way around. So a simple reinstallation of the co-driver mod usually suffice.

*There are one or two localised versions of RBR without the French co-driver option, which obviously can complicate things somewhat.

Almost all the other mods by modders not named porridge: Let's be absolutely clear: The mods that aren't made to be used with Pacenote Plugin are not fully compatible with Pacenote Plugin. Simple as that. Least of all those .dat packages that are put together for Rallyesim's Pacenotes Manager**. The amount of issues is largely dependent of a special stage. If you've grown accustomed to a certain co-driver that currently isn't working properly, the good news is that you can apply the necessary fixes yourself by following this guide.

**Do not use Pacenotes Manager outside of RSRBR. Not that it's of any danger itself, but you mustn't blindly trust a single dat package you download for it. Just learn how to extract the dat packs with dattool and install only the relevant files manually.



Cote d'Arbroz I: Pacenotes are all fucked up

In a moment of utter carelessness, you must have accidentally saved pacenotes in dls format for a BTB stage and thus ruined Cote's pacenotes (because BTB stages use its track slot 41 to load).

You can try to recover Cote's original pacenotes from \Plugins\Pacenote\Backup (track-41_M.dls), but here's the original, unmodified dls file (2004) anyway, install it to \Maps. Obviously.



Loading Peyregrosse-Mandagout takes ages

Yes, when it comes to native format stages of all-time, it really is in a league of its own – almost on its own – but with Peyregrosse stages (570 and 571) you can at least try extracting the contents of texture rbz packs to \Maps. This well-known trick will definitely speed up the process, but by how much and is it really worth the extra space it requires, that's for you to find out. Normally their textures take up about 800MB in all, whereas extracted textures (with empty rbz replacements) take up about 1.7GB.

By the way, it's worth noting that while loading of Pikes Peak 2008 is notoriously slow too (and it does come with a warning), the same trick seems to have an adverse effect, making the loading even slower!



How to open telemetry files with gnuplot

NGP6 famously introduced the telemetry recorder but quite frankly, the PhysicsNG readme's very brief explanation on how to use the recommended gnuplot left most non-engineer gamers stumped. "These scripts rely on a gnuplot variable 'file' to be present and pointing to the telemetry data file to be plotted." Now, luckily for us, the RBR champ and future hall-of-famer tbcktu can explain that sentence in less than 75 seconds.



RBRCIT: Some of the "common" problems and errors

Before jumping to conclusions that you're forced to reinstall RBRCIT to get it working, you should see if the issues have some other reasonable explanations.

Because of the recent Dropbox debacle, you mustn't start with Zissakos' github to download your copy of RBRCIT as the original version isn't really valid anymore and only spells trouble; go and get The WorkerBee Edit from GVRC instead (replacing a flawed RBRCIT.ini is the minimum requirement).

NGP plugin doesn't update: From NGP 6.1 onwards WorkerBee began to alter the download link for each plugin version, meaning that now you have to Update carList.ini first in order to update the plugin.

Here's a selection of known RBRCIT error messages and how to deal with them:

Object reference not set to an instance of an object: A pompous way of saying that the current host of all NGP releases (GVRC) is down. Comes up when trying to update models/physics/plugins. (However, if GVRC is up and you've only just installed RBRCIT, let it be known that this error can point to RBRCIT being incorrectly installed somehow.) A harmless error in the end, as long as you don't go and try updating the carList next! And why's that? See below.

Unable to connect to remote server: The same reason as in the previous one (GVRC must be down), the difference being that this variant crops up only when trying to Update carList.ini. But this is not as harmless, this is much worse. See below again.

Unable to locate RBRCIT\carlist\carList.ini: The unavoidable bad sequel to the one above which stops you from running RBRCIT altogether. Unfortunately, the previous error causes RBRCIT to wrongly delete your carList.ini when trying to update it at the wrong time. Since the downtime can last even days at worst, it's recommended to ask someone to upload the latest carList.ini for you so you can at least get back to using RBRCIT.

An exception occurred during a WebClient request: This shouldn't really occur to any of you unless you're careless during installation, but you may want to check that the folder \RBRCIT was extracted properly or even exists. Either way, you'll be looking into a reinstallation next.

Then there are some other errors that have never been investigated properly to say anything educated about them, like the ones that point to allegedly missing files such as File Cars\\.ini not found. In these instances – while there are always ways to fix everything by yourself – most users will be much better off reinstalling RBRCIT with real care (see the next chapter). (Note that having 7-zip installed and therefore working alongside RBRCIT improves its stability to no end.)



RBRCIT: How to perform a clean reinstallation

If you succeed in making RBRCIT crash all for wrong reasons (that are not mentioned in the previous chapter), the chances are that you'll only end up in a vicious circle of not being able to do shit without it crashing again. Therefore reinstalling RBRCIT is often the most efficient and sensible option. As long as you're extra meticulous, you can solve any underlying issue and avoid having to reinstall it again in a minute.

Here's how you do it for RBRCIT with NGP6 physics (you can also use this to upgrade NGP5 → NGP6 successfully):

  1. If you can Restore Original RBR Cars before exiting RBRCIT, by all means do so, but if you can't, no worries, because we will replace all the files that are affected by RBRCIT anyway.

  2. Delete RBRCIT files + the folders \RBRCIT and \Physics.

  3. Download NGP plugin + the original Cars.ini files. Extract both packs to the installation folder → replace all files when asked.

    (Note! The NGP plugin link obviously leads you to the latest NGP revision, but if RBRTM's online rallies are be-all and end-all to you, you can alternatively download the plugin from CZ site instead, no harm in that.)

  4. Now you can finally install RBRCIT again.

  5. Run RBRCIT, download carList.ini + missing physics.

If this doesn't work, then nothing will.




RBRTM only



Tournament Plugin missing in-game

This chapter was originally added only because of Windows Defender but thanks to Reddit user attheicearcade's report to Microsoft, Defender hasn't caused problems since, which is lovely indeed.

But of course, it is worth reminding that the exact same risks do apply to any other antivirus software, so if you do have one and RBRTM.dll suddenly goes missing from \Plugins, first you should set your RBRTM installation (or at least the Plugins folder) as an exception in its settings, and only then see if you can restore the file from its quarantine. If you can't restore it, then you may have to re-install RBRTM or simply ask someone to upload RBRTM.dll for you.



"Connection failed, try again?"

A common issue from time to time and you won't be able to access rbr.onlineracing.cz either because of expired security certificates. It'll get fixed in due course. However, if you can't wait until tomorrow, you can always go to Tournament Plugin's options and turn Secure login off temporarily and try again.



"Data error"

If you can't access rbr.onlineracing.cz either, then you may be able to enter rallies just by turning Secure login off temporarily, just like with the Connection failed -error.

But in case that's not enough, and especially if you haven't been able to enter rallies in a while or ever, perhaps you should make sure that cookies are not blocked in Internet Explorer's settings. Launch Internet Explorer, go to Tools → Internet Options → Privacy tab. With the factory setting Medium everything will surely work but by all means test with High and Medium High too. Caution! Do not confuse cookie settings with security settings that have very similar terminology.

If neither of previous suggestions bring results, then open RichardBurnsRally.ini and remove your details from AutoLoginName and AutoLoginPassword lines in order to login manually in-game. This has been known to help, but don't ask us why.



"Wrong weather definition in TrackSettings.ini"

As you can probably imagine, this is related to specific weather pack check in a rally. When creating rallies, promoters have a choice of either leaving on/turning off the check for each stage separately. In most cases, turning it off is highly recommended, but if left on for some/all stages, RBRTM would then scan the competitor's own TrackSettings.ini (located in \Maps) to check if its lines for chosen weather pack match the official ones. If not, this error message will emerge.

So, all in all, we can come up with THREE reasonable/not-so-reasonable explanations:

1) If you have installed one of the more recent CZ TrackPacks (Sep 2019 or newer), you shouldn't have this problem because the correct TrackSettings.ini lines have seemingly been restored, but if you have begun with any of the TrackPacks dated BEFORE Sep 2019, first you must check if any of these stages are included in the rally you're trying to enter (with the exact same weather conditions). If so, you can then use the provided info to restore the lines back to their original state.

2) Your TrackSettings.ini have either incorrect lines or the required lines are missing entirely. This must be the case, if other drivers have been able to enter the rally without issues. You can always try to fix this temporarily by using the TrackSettings.ini that comes with the most recent version of CZ TrackPack. Triple caution! Do remember to backup your current TrackSettings.ini first if you have installed stages that are not part of the CZ TrackPack, or if the file is already outdated in terms of new stages.

3) It's the other way round, so the lines in your own TrackSettings.ini are faultless, but the corresponding lines on the Czech server are not. This is the likeliest scenario when no-one (practically or literally) have been able to enter a rally. Although in reality, this is a very rare scenario. One notable example is Versme's Morning - Light Rain - Heavy Clouds combination, where the weather pack check will fail if a promoter has left it on for the stage, and there's no way of fixing it yourself.



"Cant open file" in Shakedown mode

Basically this is about physics.rbz. We can safely say that using well-known software like 7-zip/WinRAR to edit physics.rbz is foolproof but there may be software that tamper with the file in a way that RBRTM doesn't accept. (Obviously this particular error will never hit an RBRCIT user.)



Can't choose certain cars in online events

When you're convinced that you've got the right physics installed, which obviously is always the first priority, the one further thing you need to know is that RBRTM is not only checking the physics as it performs a similar check also on the car's .sgc file. This means that you can't switch to any alternative sgc modification that some cars – such as C3 WRC 2017, DS3 WRC and i20 Coupe WRC 2017, to name a few – are known to have.

Since the older NGP5 physics are still usable online at time of writing, it's perhaps worth reiterating that Hyundai Accent LC WRC2000 can't be chosen because its physics' or model's CRC check simply fails, and this never got fixed (presumably because everyone forgot to tell the admins).



The clock doesn't stop at the finish, leads to DNF

This is a pacenote issue. Because of RBRTM's buggy anti-cheat system in place, you MAY run into problems if you edit/add pacenotes after the finish line. Also adding notes too close to splits is risky. Of course, the original idea of this anti-cheat has been to check only that the locations of start, splits or finish haven't been altered, but quite clearly it's not always working as intended.

Now, we don't want to discourage you from adding or editing pacenotes because after some deliberate tests, you should mostly get away with it and ending up with this issue would be just unlucky. It'd be nice to go through some rules of thumb but unfortunately every stage seems different: in Noiker II you can't remove an Easy Right located behind the finish line; in Lyon-Gerland you can't add a note 0.4 metres or less after the finish line; and you can't add a note right after one of the two splits of Kuadonvaara.

If an added note causes this problem, usually it's enough to just move it by a metre or so.



So what's the deal with Monster Hill Climb?

There is a possibility that if Monster Hill Climb v2 was indeed released with ID 999, then it most definitely meant that installing SSS York II (with the same ID) overwrote the Monster HC files from anyone who may have had them. Hopefully you have a backup because casgra11 doesn't seem all that keen to re-release his first ever native format stage.



"Not physics file from 1.02 version. Please use original physics file or physics file for this tournament"

If you have installed RBRCIT correctly, the most likely explanation for this classic error is that you simply have a newer version of NGP plugin installed than is currently in use in RBRTM's online rallies. Sometimes it takes only a day or two from the admin to deploy the latest version, but in the worst-case scenario this can be put off on purpose by a week or two (depending on scheduling of certain rallies).

If you wish to drive online right now, you can go back to an older plugin version like this:

  1. In RBRCIT, Tools > Restore Original RBR Cars. Exit RBRCIT.

  2. Delete folder \Physics. (Care! The one in the game folder, NOT the one in \RBRCIT!)

  3. Download the "NGP 6 physics" from here (you can see the used revision right there) and extract it to your RBRTM installation → overwrite files when asked.

Thaaat easy. Basically, when it comes to these kinds of manual installations, deleting the old Physics folder (at the right time) is the difference between success and failure. Because if you didn't delete it, physics.lsp in physics.rbz would only be overwritten by the corresponding file in \Physics once you start installing cars again.




RSRBR only



Checking the downloaded RSRBR packs/updates with voirMD5

To be honest, you should check all the RSRBR installers you download before using them and wondering why your RSRBR doesn't seem to work like it did before. Although lately the remaining devs haven't cared enough to publish md5 checksums too diligently, it has to be said.

1. Download VoirMD5.

2. Launch VoirMD5 → drag and drop the installer into VoirMD5 → wait → compare the checksum to the one given on the download page → if it's a match, happy days! Otherwise, re-download the pack.



RSCenterMenu's texts and icons are somehow misplaced

This is just a minor bug with the RSCenterMenu. For the Menu's layout to be correct, the Windows' text size setting would have to be 100% but in some OS versions it has been set to 125% by default. We advise to not give a shit, as it only concerns the Menu and how often do you need the Menu anyway? Once a year? Just create shortcuts of the exes (Alone/Public/Championship) you need to the desktop; and opening and closing RSCenter quickens considerably.



The game gets stuck immediately with the camera going back and forth with the menu not showing up (Go and RSRBR buttons)

It's clear that you're trying to launch the game with a profile that has the required car or stage slots still locked. So, you need to create a profile MULLIGATAWNY in SSE to unlock everything at all times. If you already have done that, then you need to ensure that MULLIGATAWNY is really the one that gets loaded (go to RSCenter's settings → see Profile).



Manual gears don't work

Changing the gears to manual in RBR's own settings (Options >> Gears) is the obvious one, but really the choice between the automatic and manual transmission in RSCenter's settings is the one that matters in RSRBR.



A BTB Country Pack stage loads Cote d'Arbroz instead

The BTB Country Pack in question surely is corrupt, so download and install it again.



Textures get all mixed up (for instance, gravel mod with tarmac textures)

You can make this much more difficult for yourself but we give you the easiest solution. The guys at Rallyesim often suggest using their own troubleshooting tool (Depannage) to fix this, but quite frankly we are not aware of any case where it would have helped, so:

1. Delete ALL subfolders in \Maps.

2. Re-install Track Pack >> Updates >> Cars. (Another reason to retain the installers.)

→ Works again until it doesn't. (One way of avoiding this issue in the future would be to never shut down or restart your computer without closing RSCenter first.)



Saved camera settings for a car get erased (the ini file is replaced)

This issue presents itself with a couple of car packs and there are no good reasons for it except that no-one's asked Rallyesim to fix it.

Open the car class pack located in \RSRBR with 7-zip (for the sake of example, A8W-07.7z) and delete all of the car subfolders in \Cars so that the only remaining file is cars.ini. That cars.ini is the only relevant file that RSCenter needs for the cars to work as intended. Close 7-zip and the pack saves automatically.

Note that the faulty 7z packs may crop up again after an Update, which is why you should always make a backup of the edited files.



In RSCenter, you can't access Public or Championship sections due to "error" or "server error"

Go to RSCenterMenu.exe and re-type your password.

Go and check http://xx.rallyesim.com/public_accueil.asp to see whether other drivers are online. If there are no drivers in prime time, it may be safe to assume that there must be a real "server error" that should get fixed sooner or later.

If neither of the previous two seem right to you, could it be that the last update you installed was corrupt? Try downloading and installing it again.



Error "Download and Install Addon (....) for Public Sessions" in a Public Session

This long-standing issue stems from errors in RSCenterPublic.exe (my own assessment, not necessarily the truth), which is why certain BTB Country Packs do not work in Public Sessions. If a public session rally has special stages from BTB Italy, BTB Portugal or BTB Argentina, no driver will make it to the start line. You can read this this thread for more info and some hilarious entertainment.



Depannage: changing RBR's install path in registry

Depannage is an easy-to-use troubleshooting utility for RSRBR. However, if you have installed RSRBR to an install copy, Depannage is pretty much useless because it can only scan the original installation. But no worries, you can always temporarily change the install path of RBR to the one with RSRBR simply by editing the registry.

32-bit Windows: Run Regedit → go to HKEY_LOCAL_MACHINE\SOFTWARE\SCi Games\Richard Burns Rally\InstallPath → double-click (Default), edit the path and click OK.

64-bit Windows: Run Regedit → go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SCi Games\Richard Burns Rally\InstallPath → double-click (Default), edit the path and click OK.



"Physics file is absent"

This is brutal. For one reason or another the integrated 7-zip is not able to extract the physics pack (xyz.7z). Different suggestions to tackle this can be found here but while many of those ideas are very reasonable, the only known way ever to fix this error has been a complete re-install of Windows. Although we would probably just ditch RSRBR and test another online plugin instead.