Problem | Solution |
---|---|
I can't see the list of routes | Make sure the configuration paths are correct. (See configuring BRR section of the manual) |
I can't see the list of trains | |
BVE doesn't start when BRR has finished processing the route | |
I can't see any other signal systems than "BVE Default" | Check that you've installed the signal systems correctly. Each signal system must be installed in a subfolder of its own. (See installing signal systems) |
The train refuses to leave some stations | You're probably using the 'Randomize starter aspect' option. It doesn't work on all routes. Try starting the particular route without it. |
Some signals stick at red no matter how long I wait | |
Some starting options don't seem to work | Not all the options work on all types of routes, or have the effect you might expect. (See starting options) |
I can't seem to get any randomization on the signals | Try choosing "Train interval / Force random" option. If the signals show too much green, try lowering the value range. If you get too many red signals, make the range higher. Even this may not work on all routes, especially those which have 'random signalling' (without BRR). |
BRF-route-related error messages are not listed here.
Text | Meaning |
---|---|
Unable to open source/destination file for (pre-)processing | Some kind of error has occured with opening a file for reading or writing. You can try to do again whatever you were doing, but if the problem persists, ask help from the author. |
An error occured during the (pre-)processing of the route. The route will not be playable. | Like the message says, something bad happened while BRR was trying to process the route. You may have received some other error messages before this, which probably tell more about the actual problem. When BVE starts, it'll probably find an error and quit, or it may start with the route that you selected the last time. If the problem persists, contact the author. |
Could not create edit box! | These are a series of errors, which are related to the (creation) of the graphical user interface. These could be caused by insufficient memory. Other than that, I've no idea what to do. |
Dialog failed! | |
Window registration failed! | |
Window creation failed! | |
Could not read signal swap data. | This means that BRR couldn't read, which signal system was used the last time. You can try re-starting BRR and see if it still happens. Otherwise you'll have to delete the 'sigswap.brr' file from the BRR folder, and switch the BVE original, and the custom signal images back yourself. |
Could not restore default signals. | The custom signal system has been removed, or the folder name has been changed. If you've for some reason changed the folder name of the signal system currently in use, change it back and restart BRR. If you can't change it back, remove the 'sigswap.brr' file from the BRR folder, and switch the BVE original, and the custom signal images back yourself. If you've removed the signal system, remove the 'sigswap.brr' and install the default BVE signals from somewhere. |
Could not engage custom signal bitmaps of system: | BRR can't for some reason open the folder of the signal system and therefore it can't swap the signal images. BVE default signals will be used. |
Could not write data for restoring signal system! | BRR can't write the file, where the folder name of the signal system is stored. Therefore it can't restore the original signals. You must swap the files back manually (in the way explained in the other error messages). |
Could not load signal system | BRR was unable to read the 'sigsys.txt', or it ran out of memory. BVE default signals will be used instead. |
Author's e-mail address is on the main page. Try to give as detailed description as possible of the problem and if you have any guesses of what's causing it. If it's about a route, attach the 'brrtemp.csv' or the 'brrtemp.rw' file (depending on the route type) from your route folder, and possible 'brr.tmp' and 'brr2.tmp' files from the BRR folder.