SubmittingBugs
From GSC Wiki
|
Description
Although all versions of GSC are tested through a beta phase, sometimes bugs in the software which makes it past the beta testing team and into the release phase. GSC comes equipped with several features to help users submit information the GSC development team needs in order to combat these issues.
Reporting a bug
1. Use the clearest English possible. Please do not use word abbreviations and/or "leet" speak when reporting the bug.
2. Reread your post to ensure #1.
3. Please update to the latest version of GSC.
4. Include what version of GSC (looks like GSC Version 2.00 Build 3000) you are using. (Lastest version is not a version number. please include the exact version number)
5. Include a best description of your issue.
6. For all bug reports, please include:
a. Operating system name and version. (fully patched is not a version number please specify exact version number)
b. GSC version (looks like GSC Version 2.00 Build 3000) (Lastest version is not a version number. please include the exact version number)
7. If you are reporting a sound issue please include:
a. The codec and frequency you are using.
b. The location IP and port of your server you are using or the GSC connection string to the channel in GSC 2.00 this looks like gsc://<ip>:<port>/ .
c. Your sound settings (from Audio Panel ).
d. Your sound card information (model # and driver version and driver date).
8. If you are reporting a in game issue please include:
a. The game name and version you are using. (lastest version is not a version number please specify exact version number)
b. Please read Submitting Bugs before reporting a problem.
c. Your Video card information (model # and driver version and driver date).
NOTE: we always can assist you better when you include the information above.
Crash Report Window
If GSC encounters a crash from which it cannot recover, the user will be prompted with a dialog which asks whether or not the user would like to submit the crash information and optional system information.
Event Logger
Starting in GSC 2.0, GSC can be enabled to log out program events which also help the developers debug issues you may be experiencing. Currently, the GSC event logger can be enabled in one or two ways:
Output Level
If you are going to send the GSC team a log of GSC events, it would be most helpful to configure the event logger for the highest output level. Please follow these steps
1. Open GSC 2. On the friends list dialog, select from the help menu "Debug Console". 3. In the debug console window type: printlevel 4
Method 1
GSC can be run with the command line argument: enableLogging
1. Shutdown GSC 2. Right click on a shortcut which you use to launch GSC. 3. Select properties. 4. In the target box, the text field should appear as: "YOUR_GSC_INSTALL_DIRECTORY\GSClient.exe" 5. Make the text field in the target box appear as: "YOUR_GSC_INSTALL_DIRECTORY\GSClient.exe" enableLogging * Replace YOUR_GSC_INSTALL_DIRECTORY with the location of where GSC is installed on your computer, in most cases the directory would be: C:\Program Files\GSC 2.00
Method 2
1. Open GSC 2. On the friends list dialog, select from the help menu "Debug Console". 3. In the debug console window type: logtofile true * This enables the event logger for the current GSC session. If you quit GSC and restart the application, you will need to type this command again.
The event logger will generate the file: %AppData%\GSC 2.00\gsclient.log
You may navigate to the path "%AppData%\GSC 2.00" by pasting that link in any windows explorer window. Please submit gsclient.log to our development team so they can analyze the issue you are experiencing on GSC.
Please submit the ENTIRE LOG FILE to our developers, otherwise it will not be possible to track down potential problems.
After you have submitted your event log to the GSC team, you can reset your output level with: printlevel 3 Resetting this output level may improve the overall performance of GSC.
In-Game bugs
If you are having an issue with the in game chat then you want to ensure the following
1. you are using the latest version of the client. 2. The files GSClient.exe, GSHook.DLL and GSHookHelper.DLL are located in your GSC folder (usually C:\Program Files\GSC 2.00) 3. you are using the latest version of your video card drivers. 4. You have the 'enable in-game service' box checked. ( In-Game Panel ) 5. You have the 'enable in-game chat' box checked. ( In-Game Panel ) 6. For the particular game, you have in-game overlays enabled. ( Game Setup Panel ) 7. your hot key is set. 8. the window "Opacity" is set to full (right) in the Settings. ( In-Game Panel ) 9. If you are running Windows Vista ensure that GSC is "Run as administrator" and the game is "Run as administrator" 10. you are using a 32-bit operating system. (I.E. XP x64 and Vista x64 unsupported) 11. GSC detects you in the game. (should hear your sound notification for "Game Open" Notifications Panel );
If you continue to have an issue after that please include the following with your report:
1. Ensure GSC is the only other game software running 2. OS Version. (fully patched is not a version number please specify exact version number) 3. Video card. (ATI or NVIDIA is not a video card. please specify exact model number) 4. Video card driver version. (latest driver is not a version. please specify exact version number) 5. Full game name (please do not use short name or acronyms for the game) 6. Game version (latest version is not a version. please specify exact version number) 7. Anti-cheat system version (punkbuster version, game guard version, or other). (latest version is not a version. please specify exact version number) 8. Exact error code and/or exact error text from game, OS, or anti-cheat system encoutered 9. include a list of firewall/anti spyware/anti virus installed on your machine. 10. include a list of your running processes. SEE "Getting running processes" below
In game is disabled in All GameGuard games (check "In-Game Notes" in the Game Setup Panel ) automatically. you can always disable in-game services for these games in Launch->Game Setup.
If you are receiving a punkbuster error in any other game we would appreciate it if you could let us know.
There are rare issues where the in-game service does not shutdown/restart. In this case, a reboot should resolve the issue.
It will be easier for us to assist you with any issues when you include this information, as well as a listing of all firewall/router/antivirus software being used.
Getting your running processes
1. Start the game 2. minimize it. 3. Click "Start" 4. Click "Run" 5. type "cmd" 6. click "OK" 7. Type "tasklist /SVC > tasks.txt" and press RETURN
This will create a text file with a list of your current processes. The text file can be found at"C:/Documents and Settings/<username>/tasks.txt"
please attach or copy and paste this file into your bug report.
