rFactorLive

watch rFactor wherever

frequenty asked questions


General FAQ:

What is rfVCRmerge?

rfVCRmerge is an application that allows laps from rFactor VCR files to be overlaid and synchronised. It generates a new VCR file that can be played back inside rFactor. This allows easy visualisation of driving lines and relative speed.

Does rfVCRmerge support rFactor 2?

Currently rfVCRmerge does not read rFactor 2 VCR files. It is very unlikely that rFactor 2 will be supported until rFactor 2 leaves beta (or when the replay file format is officially finalised).

What is rFactorLive?

rFactorLive is an application that enables an overview of an rFactor session to be viewed in real-time. This can help with strategy decisions such as when to leave the pits in a qualifying session and when to come into the pits during a race.

Are they free?

rFactorLive and rfVCRmerge are free to distribute. All I ask is that I am given credit and that the contents of the distribution archive are not modified.

Although they are free to distribute, I develop them in my spare time, so any wife-placation funds will be gladly accepted. Donations will greatly increase the frequency of future updates!

Does rFactor have to be installed for rFactorLive or rfVCRmerge to work?

The viewer part of rFactorLive does not need a local rFactor installation. An rFactor installation is not required for rfVCRmerge - however the VCR files it generates can only be viewed inside rFactor.

rFactorLive FAQ:

Does rFactorLive have to connect to an rFactor Dedicated Server?

No. rFactorLive can connect to a 'regular' rFactor instance too. You can view a local rFactor session by entering 'localhost' as the server name when connecting.

Why can't I connect to a server?

Check that the Visual C++ 8.0 Runtimes have been installed on the client and the server. Check that no firewalls are blocking the connection. Check that the correct TCP port is being forwarded through any routers.

What are the CPU requirements?

The server-side CPU requirements are minimal compared to the load placed by an rFactor dedicated server.

The viewer has higher CPU requirements. Decreasing the size of the window will decrease the CPU load, as will expanding the timings window so that it completely covers the trackmap area of the window.

What are the bandwidth requirements?

The overall server upload bandwidth required above that of rFactor itself is of the order of 0.8 kbps per active viewer per vehicle in the rFactor session. For example if there are 10 vehicles in the session and 20 active viewers, the rFactorLive server upload bandwidth will be about 160 kbps (about 8 kbps download for every viewer). The maximum number of active viewers can be set in the rFactorLivePlugin.ini file. See readme.txt for more information.

I don't like the window layout. How can I make it better?

The panes within the rFactorLive viewer window are sizeable and moveable. By clicking on the edge of a pane and dragging, the pane can be made larger or smaller. By clicking and dragging the title bar of the pane, the pane can be dragged free of the main window and positioned anywhere on the desktop. Alternatively it can be docked anywhere within the main window. A pane can be hidden or redisplayed by using the 'View' menu. Columns within the Timings pane can be resized by dragging the edge of the column header.

What are the future plans for rFactorLive?

Functionality under consideration for future releases:

I have a different question

If your question has not been answered, please contact me and I will try to help.