BFS uses some information from Windows about recently used programs to try and figure out where your LFS directory and executable is located. Basically. it populates the list with every recently started program that has "lfs.exe" in the path name.

Unfortunately, there is no way to delete old paths (at least, not until Windows purges the list of recently used programs). Though as long as the correct lfs.exe path is selected everything should go swimmingly.

The main reason it's there is to allow people to easily change the LFS executable path if they happen to run more than one version (perhaps they're using one of the test patches).

Quote from battle :

I really like this program and i used it allot but suddenly i kept getting this error this happend wenn i pressed refresh.

Yep, I getting the same problem now too. This particular error is being caused by BFS expecting there to be information about the track where there isn't any. That in turn causes the track to be represented as a null string, which causes the error messages...

We're working on a fix now, but can't guarantee a time frame. Also, keep in mind that Scawen may make more changes over the next few days, which may break BFS.

Thanks heaps for these translations guys, they're looking fabulous.

Those bugs are because you left those letters/words in the string Lible
No worried though, it's all fixed.

Browse For Speed 0.5 now has multiple language support. This is great, we think, but Australians are well known for only being able to speak one language (and poorly), so we need the community's help.

Translating for BFS involves copying/editing an xml file. There are about 150 (mostly small) strings to translate. You will be credited for your work (your name/details will show up in the configuration section when your language is chosen if you wish).

If you wish to translate, you can find the base English language file in /lang/EnglishAU.lang.xml within Browse For Speed directory. This file contains instructions on how to go about translating BFS into your language.

Last edited by Snookle, Wed 28 Jun 2006, 10:38.

Hi guys!

We've spotted an annoying bug in BFS 0.3. The program configuration is not correctly reflected by the U.I after making changes to the config. You can get around this bug by making your required config changes then immediately exiting and restarting the program - thereby forcing a save of the configuration.

Hopefully this doesn't cause too much heartache, besides being rather annoying. Luckily it's been fixed already, and will be included in the next release.

Hi guys!
Thanks for all the positive feedback! We've taken the suggestions on board and have fixed a number of bugs you guys have found and added some new features you've requested.

We hope to release an update soon!

@racemania: You might have a firewall blocking LFS registering your server with the master server.

Last edited by Snookle, Wed 31 May 2006, 01:00.

Quote from Vain :

You can make the pitspotter start without launching LFS. The ./spotter/config.cfg file allows to alter the spotter's behaviour. That way Browse For Speed can start pitspotter and afterwards launch LFS with the necessary commands to directly connect to the server.
Vain

Ah excellent, thanks Vain! We'll definately look into providing support for it then!

Quote from tinvek :

works nice, only thing is can it be set to run the lfs spotter executable ?

Are you talking about Pit Spotter? None of us have heard of it till now.
After doing some quick reading, it might be possible to provide support for it in a later release - providing that Pit Spotter allows us to specify a server for LFS to connect to. eg: BFS would start Pit Spotter, sending it the server to join, Pit Spotter starts LFS, passing those command line variables on.