Do I need the original RA/C&C game installed?
No. OpenRA is completely standalone. When you install the game (or the first time you run it, on osx) it will download a minimal copy of the game files that it needs to run. In the future you will also be able to install from the original game disks, which will give you extra functionality like ingame music and singleplayer missions.
Is that legal?
Maybe. EA have released both C&C and RA as freeware. The files are already available for free; we are saving EA bandwidth by hosting only the ~15MB of files that we need to run the game, instead of making everyone download the 700MB game iso.
If EA have a problem with us doing this, we will remove the files and supply an installer that extracts these files from the iso on your computer.
When will you release the next version?
Every Saturday, unless we screwed up really badly, in which case we might release a midweek version too. If you are having problems, try downloading a new version and see if this fixes your problem. For more information about the release process, see http://github.com/chrisforbes/OpenRA/wi ... d-Releases
Nobody can join my online game!
For others to join your game, you must forward a port in your router for them to connect to. By default, OpenRA uses tcp port 1234. This can be be configured in the Create Server dialog.
My game just crashed!
We're sorry to hear that
Telling us "my game crashed, you suck" is not helpful. Please follow the steps below to collect the basic information we need to help you.
Game Version: You can see this on the main menu
Crash Log: Depending on your operating system, this will be in a different location
[tab]Windows: My Documents\OpenRA\Logs\exception.log
[tab]Mac OSX: ~/Library/Application Support/OpenRA/Logs/exception.log
[tab]Linux: ~/.openra/Logs/exception.log
Before you post this information on the forum or irc, please READ THE FIRST LINE OF THE EXCEPTION LOG and CHECK THE COMMON ISSUES BELOW. If you have a problem that is not mentioned here, please let us know on the forum or in IRC.
If the exception mentions a `desync', please also post sync.log, which you will find in the same directory, and get everyone else who was playing the game to post it too. the sync log is only useful if we have multiple players submit their log.
"No Valid Techniques"
This error occurs if the game cannot start OpenGL.
This could occur for a number of reasons, depending on your operating system and graphics card
- You need the most up to date graphics drivers, EXCEPT if you have an ati card (see this thread). In particular, the intel drivers that are bundled with windows do not include *any* OpenGL support. See your graphics card vendor website to download the latest drivers.
- You have an old graphics card that doesn't support OpenRA. Although OpenRA may look like an old game, we make use of modern hardware capabilities. We require Shader Model 2.0, which means that nothing before about 2004, and some more recent cards WILL NOT WORK.
- Compiz causes issues with OpenGL applications on Linux. This is a bug in Compiz itself, which they appear to have no interest in fixing. You will need to disable Compiz before running OpenRA.
Unable to find an entry point named 'glGenBuffers' in DLL 'opengl32.dll'.
This error occurs can occur if you have outdated graphics drivers under Windows. See the point above on updating them.
My perfomance sucks
OpenRA is a work in progress, and we are doing our best to improve performance.
To help us fix this, we will need some information from you.
- Enable the perfomance graph (from the main menu -> Settings -> Debug -> Show Perfomance Information) and note your average Tick and Render times in a game.
- Your perf.log from the logs directory above
- Your computer specs (CPU and Graphics card are most important).
Where do bugs go?
I eat them. I prefer them crunchy on the outside, juicy on the inside, and with the following crucial details: --Chris
- What you were doing when something broke
- What you expected to happen
- What actually happened
- If it's a crash, the contents of exception.log.