Mac bug reporting

Creating a client to connect to the Singularity Test server

1. Rename your install to "EVE Online TQ"
2. Install another copy of EVE Online, or simply duplicate your existing install of the EVE client
3. Rename the new copy to "EVE Online Singularity"

Configuring the Singularity client to connect to the correct server

Config file with edits

The patch files for SiSi should automatically select the correct server address for you; that is unless TQ and SiSi are running the same build and there is no patch file. If this is the case you need to manually configure your client to connect to the correct server.

Configuring your client

1. Right click on the EVE install that you wish to redirect, and select 'Show Package Contents'
2. Open the 'Contents' folder
3. Open the 'info.plist' file
4. Find the key CFBundleName and edit the string value from "EVE Online" to "EVE Singularity"
5. Save and close the info.plist file
6. Start the EVE Online Singularity client, this will generate the new prefs folder
7. Close the client
8. Browse to ~/Library/Application Support/EVE Singularity/ in Finder (~ represents your current users home)
9. Open the 'config' file
10. At the end of this file add this:
    [AppDefaults\\EVE.exe\\transgaming]
    "cmdlineadd" = "/server:87.237.38.50"

Save and close the config file, start the Singularity client to verify that it connects to the correct server.

Creating a client to connect to the Duality Test server

1. Rename your install to "EVE Online TQ"
2. Install another copy of EVE Online, or simply duplicate your existing install of the EVE client
3. Rename the new copy to "EVE Online Duality"

Configuring the Duality client to connect to the correct server

The patch files for Duality should automatically select the correct server address for you; that is unless TQ and Duality are running the same build and there is no patch file. If this is the case you need to manually configure your client to connect to the correct server.

Configuring your client

1. Right click on the EVE install that you wish to redirect, and select 'Show Package Contents'
2. Open the 'Contents' folder
3. Open the 'info.plist' file
4. Edit the PrefsFolderName value to be "EVE Duality"
5. Save and close the info.plist file
6. Start the EVE Duality client, this will generate the new prefs folder
7. Close the client
8. Browse to ~/Library/Application Support/EVE Duality/ in Finder (~ represents your current users home)
9. Open the config file
10. At the end of this file add this:
    [AppDefaults\\EVE.exe\\transgaming]
    "cmdlineadd" = "/server:87.237.38.60"
11. Save and close the config file, start the Duality client to verify that it connects to the correct server.

Writing a Mac Bug Report

Writing bug reports for Mac for the most part follow the normal rules for creating a bug report. However, there are important differences that need to be considered:

Title

For a title you should use this format:

Mac: Bug report title
Example: Mac: Client never ever crashed

Category

Set the category to Mac/Linux

Description

At the top of the description you need to enter the following information:

• Build: Buildnumber - this is the client version you are currently experiencing the problem with. This can be found top left of the log-in splash screen or of the in-game settings screen found by pressing <esc>

• Server: Server name - the server you are having the issue with, TQ or SiSi

• Cider version: Version Number - this can be found by looking in the client .app package and navigating to the contents folder. The cider build version is listed in the version.plist file, which can be opened in TextEdit.

Example:

Build: 48382
Server Name: SINGULARITY
Cider version: 1086

The description of the issue follows the info in the bug report link.

Computer

Add a short version of what kind of computer and OS version. Full description should be attached as a system profiler report. This can be obtained by

1. Press the Apple sign in the top left corner and select About this Mac
2. Click on More Info
3. From the menu bar, press File and select Save As
4. select System Profiler 4.0 (XML) format and attach the file to the bug report

Attachments

Always attach a system profiler file which includes hardware, configuration, OS and version of OS.

In addition to this, attach screenshots in JPEG format if they help to demonstrate the issue.

As the Mac does not have access to the Logserver utility, we use the cider trace log utility instead. This is very important for issues relating to client crashes, but may be useful for other issues as well, so please consider using this facility.

Generating Log Files

LogServer output

In order to generate the same logging that LogServer.exe produces on Windows in the Cider Trace Log, you have to add an additional parameter specified below.

1. Browse to ~/Library/Application Support/EVE Online/ in Finder (~ represents your current users home).
2. Open the config file. (You can do this using TextEdit)
3. At the end of this file add this:
   [AppDefaults\\EVE.exe\\transgaming]
   "cmdlineadd" = "/logDebugger"
4. Save the changes and close the window
5. Launch EVE with Cider logging enabled as per the instructions below
6. To view only the EVE logs open the resulting file in Console and filter on OutputDebugString

Generating Cider Logs

You can grab valuable information by running Eve from the terminal by initiating the Cider trace utility.

1. Launch Terminal. You can find Terminal using Spotlight; it can also be located in "/Applications/Utilities"
2. Right click on the EVE install that you wish to redirect, and select 'Show Package Contents'
3. Open the 'Contents' folder, then the 'MacOS' folder
4. Drag the 'cider' file into the Terminal window, this will generate a link directly to the cider file. USER$ /Applications/EVE/EVE.app/Contents/MacOS/cider (this may look different if you renamed the EVE application, don't worry!)
5. Add the following to the end after .../cider ' -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log'. Note the space.
6. The command should now look like; 'USER$ /Applications/EVE/EVE.app/Contents/MacOS/cider -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log'
7. Hit ENTER to execute the command. This will start logging and generate the logs to the Desktop in a file called "EVEcrashlog.log"
8. Once the bug has been reproduced, ZIP the EVEcrashlog.log file and upload the zipped copy to the bug report.

In game logging

You can use the in game activity monitor to quickly and easily grab the most relevant LogServer information. This functions on both the Mac and Windows client in the same way.

1. Log into EVE
2. Hold down CTRL + SHIFT + ALT + M
3. This opens a window labeled Monitor
4. Navigate to the Logs tab (to the far right)
5. By default the THRESHOLD is set to Notice, leave this unchanged
6. Click on Start; you are now generating logs
7. You can edit the CAPACITY for the number of lines to log, this is limited to 4096
8. When you have reproduced the defect hit the Export button; this copies the current contents of the window your clipboard
9. Open a document (TextEdit or Notepad) and hit CTRL + P or CMD + P
10. Save the document and upload the zipped copy to a bug report