Mac bug reporting

Contents

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 Sisi"

Configuring the Singularity client to connect to the correct server

Info.plist file with edits
Info.plist file with edits
Config file with edits
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 in TextEdit
  4. Look for the following key: PrefsFolderName, and change the value to something different such as "SiSi"
  5. Save the Info.plist
  6. Run the install of EVE to be redirected and exit once you reach the login screen
  7. Edit the /Users//Library/Preferences/SiSi Preferences/config file (the folder you are looking for in the Preferences folder will be named after the name you specified above followed by preferences)
  8. Add the following lines to the end of the file
    • [AppDefaults\\EVE.exe\\transgaming]
    • "cmdlineadd" = "/server:87.237.38.50" (note space either side of '=' sign)
  9. Save and exit

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
Hint: make sure you ZIP this file before uploading it so that we can access the data

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 a Cider Trace Log File

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

  1. Run the terminal utility by starting Terminal; use Finder to navigate to /Applications/Utilities
  2. Using the command line in Terminal, navigate to your Eve installation by typing cd ../../Applications/EVE\ Online.app/Contents/MacOS (Replace EVE Online.app with the name of your installation, eg SiSi.app, and remember that if your system is formatted as Mac Journaled HFS+, all file and folder locations are case sensitive. The '\' after EVE is required to recognize the space between EVE and Online in the application name. If you have renamed to a single name, it is not required. If the above full path cd switch doesn't work for you, then do it one at a time, eg cd Applications, cd EVE\ Online.app, cd contents, etc)
  3. Run cider with '''./cider -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log'''
  4. This will launch the EVE online application. Login and perform the bug you are reporting as expiditiously as possible
  5. All output will be stored in a text file called 'EVEcrashlog.log', which can be found on your desktop, and you won't see any data on screen.
  6. Once the bug has been reproduced, ZIP the EVEcrashlog.log file and upload the zipped copy to the bug report.
Hint: make sure you ZIP this file before uploading it so that we can access the data, and is especially important for Cider traces files as they are particularly large, and will not be accepted if over 2 Mb in size.


Please note: When running the EVE client with logging enabled performance may be significantly lower then without logging enabled
  • Currently 0.00/5

Rating: 0.0/5 (0 votes cast)

Top Contributors For This Page