|
Bugtracker | Downloads
Not everybody can just be a beta tester. Of course everybody can hit the download button and install the first beta. Yet a real beta tester will not just have fun (naturally you spend most time on fun), but in his 'remaining' time have a look at weapons he likes a bit less, or that mutator in the menu he hasn't really liked. After all you wont find a bug if you don't look at a mutator or weapon.
But that is not all, you should know some about UT2004, and shouldn't be scared to overwrite a u file with a new version, you should know what we want if we ask for your log file, or the error you got when UT2004 crashed. We wont ask you to open unreal ed or something (we will do that) you can just sit back and enjoy the game until you find a bug.
You are working with betas, this means sooner or later you will find 1. A bug. Now if you get a crash, make a copy of the log, and past it to notepad. Also you should make a copy of your ut2004.log. Then you can report it on the bugtracker, more about that later. Of course there are a lot sorts of bugs, from the biggest crashes, till a small type error in a message window.
You can find our bugtracker here. If you open it you will get a overview with bugs currently reported. We ask you to CHECK if you bug is already reported.You will always see 4 columns with data, the first is the bug ID. This id is used to refer to bugs quickly. Then the title, and the status. A bug can be in several states. Here is the list with status and what they mean:
STATUS |
DESCRIPTION |
| PENDING |
This means that no u4e team member has looked into your bug. Just give it some time. |
| DOUBLE |
This means that the reported bug already was on the bugtracker. you can prevent this by checking the list before posting a bug. |
| BOGUS |
This means the bug can't be real, of course this could be a bad explanation for what you did and what happened, but usually it is just someone who tried to be funny and spoil our time with 'jokes' |
| CONFIRMED |
This bug has been looked into, and has been marked to be fixed ASAP. |
| FIXED |
This bug is fixed, a solution is available in the next version |
| MORE INFO |
The bug can't be solved without more information. You can usually prevent this error by filling out the form completely. If you reported this bug you will be informed through an e-mail, asking for the information needed. |
When you add a bug please try to have all the information ready. This will make filling out a bug report a quick and easy job.
First up is the title, it should be clear. NOT something like "weapon bug" or "crash". a good example would be "Gateways time-left not updating".
Next up is the bug type. There are several bug types. a list of them:
BUGTYPE |
DESCRIPTION |
| CRASH (with error) |
This should be selected if the bug causes the game to crash, and give an error message |
| CRASH (no error) |
This should be selected if the bug causes the game to crash, but doesn't give an error message (as if the game quit correctly) |
| Lock up |
This should be selected if the bug causes your system to stop responding and has to be rebooted |
| Type error |
This should be selected if you find a type error. |
| Online bug |
This should be selected if the bug only happens online |
| Offline bug |
This should be selected if the bug happens in a offline game, but does not crash your pc (most bugs) |
| Other |
All that does not fit above, when you selected this a new box will pop-up asking you to fill out a good description |
When you selected your bug type the form will change depending on your problem. Below you will find a table containing all possible fields plus what we want you to fill in:
|
|
| U4E version |
Here we ask you to fill in what version U4E you are using. You can find this information in the description of the U4E mutator |
| What where you doing? |
When reporting a crash this is where you fill out what you where doing. An example could be
" I shot the BFG and when it hit the Dollbomb the game crashed"
If you are reporting a type error, you can type in here where the error is located.
And for a normal on- or offline bug you can fill in what the bug is. |
| Other mutators |
If you where running other mutators when the bug was found please list them here. |
| LOG file |
If your game crashed, we ask you to open your ut2004.log and copy somewhere about the last 30 lines of it (more or less depending on where the crash is in the log) If you are unsure and think the last 30 lines is not enough you can post the full log, but we prefer to have just the relevant part |
| Error message |
If your game crashed, and you still have the error we ask you to post it here |
| E-Mail |
If we need more information, or we found a solution for your problem, we can e-mail you through this address |
| USER CODE |
If you report a bug, we have given you a USER CODE (it should start with 4 numbers and then 6 letters) to prevent you having to fill out all fields again you can just enter that code.
NOTE: if you system has been updated (or a patch for ut2004 has been installed!) you will still need to fill out the form (leave this field empty) |
| Operating system |
Fill in what windows version you are using. If you don't use windows select your system and type the version in the box behind it. If your OS is not in the list, select other and type your OS name AND version in the box that will appear [LOG] |
| CPU speed |
How fast is your CPU. [LOG] |
| GPU |
What kind of GPU do you have in your pc? [LOG] |
| Memory |
How much memory do you have? |
| UT2004 version |
What version of UT2004 do you have [LOG] |
| Other relevant info |
If you got any other info about your system fill it in here. |
Items marked with[LOG] can be read from your ut2004.log if you know where to look:
EXAMPLE; Items in red will explain what the data (blue) is:
Log: Log file open, 05/11/04 16:49:58
Init: Name subsystem initialized
Init: Detected: Microsoft Windows XP 5.1 (Build: 2600) This shows what OS you are using
Init: Version: 3186 (127.29) This will show you UT2004 version
Init: Compiled: Mar 3 2004 02:43:29
Init: Command line:
Init: Character set: Unicode
Init: Base directory: C:\UT2004\System\
Init: Ini:UT2004.ini UserIni:User.ini
Init: Build label: UT2004 Build UT2004_Build_[2004-03-03_02.42]
Init: Object subsystem initialized
Log: nv4_disp.dll/NVIDIA GeForce4 Ti 4200 with AGP8X
When a new beta is released, you will usually get see a post on the forum, telling you that there is a new beta. A link will be provided there, unless stated otherwise, you will have remove the last beta (remove the u4e directory) and reinstall the new mod. Files can usually be downloaded from this location:
http://download.beyondunreal.com/browse.php?dir=u4e/BETAS/ |
