PYFA (Python Fitting Assistant) is a cross-platform fitting application that can be used natively on any platform where python and wxwidgets are available, including Windows, Mac and Linux.

1) Hidden fits are excluded from the frontpage and search on EVE Workbench, the fit is still available if you know the URL. Missing features? If you are missing features please let us know using the feedback button, by joining our Discord-server using this invite or by entering our in-game channel 'EVE Workbench'. Python fitting assistant, cross-platform fitting tool for EVE Online - pyfa-org/Pyfa. The ship plan can be built in Eve Fitting Tool (EFT) or acquired from Osmium. Import a ship from EFT by starting up EFT and creating a ship fitting. Next to the fitting name there is a ship icon with a drop down menu. Select copy to clipboard on that menu.

It provides many advanced features such as graphs and full calculations of any possible combination of modules, fits, etc.

To download PYFA go to this page

• 1Initial Setup
• 2Fitting
• 3Importing/Exporting Fits

Initial Setup

Linking Your Characters

To connect your EVE character to PYFA you will need to use CCP's ESI SSO.

To do this:

1. Open the SSO Character Management screen (Character -> Manage ESI Characters).
2. Create a new character by clicking Add Character.
3. A page will open in your default browser - sign in using your EVE Online account credentials.
4. Select the correct character from the list.
5. Click Authorise.

Settings

You should change your settings to match the images below. General settings are mostly personal preference, however the network settings are required for PYFA to query EVE-Central for prices.

To change settings go to Global -> Preferences or press Ctrl-P.

Damage Profiles

Copy the following into the damage pattern editor by selecting all the damage patterns, and copy them into your clipboard. Then inside of PYFA under the editors tab select the damage pattern editor. You will be prompted to name your new profile, hit OK. At the bottom right hand side there will be 2 buttons. Select the one that says import from clipboard. From now on you will be able to select the type of incoming damage and you can change your fit accordingly. (The Law damage profile is CONCORD Response.)

DamageProfile = [Asteroid] Angel Cartel,23,7,26,44

DamageProfile = [Asteroid] Blood Raiders,55,45,0,0

DamageProfile = [Asteroid] Guristas,0,17,83,0

DamageProfile = [Asteroid] Rogue Drone,10,18,28,44

DamageProfile = [Asteroid] Sansha's Nation,58,42,0,0

DamageProfile = [Asteroid] Serpentis,0,53,47,0

DamageProfile = [Deadspace] Angel Cartel,6,9,26,59

DamageProfile = [Deadspace] Blood Raiders,53,47,0,0

DamageProfile = [Deadspace] Guristas,0,19,81,0

DamageProfile = [Deadspace] Rogue Drone,8,34,32,26

DamageProfile = [Deadspace] Sansha's Nation,57,43,0,0

DamageProfile = [Deadspace] Serpentis,0,62,38,0

DamageProfile = [Hybrid] Antimatter,0,20,28,0

DamageProfile = [Hybrid] Javelin,0,32,24,0

DamageProfile = [Hybrid] Null,0,24,20,0

DamageProfile = [Hybrid] Spike,0,1,1,0

DamageProfile = [Hybrid] Void,0,1,1,0

DamageProfile = [Laser] Aurora,20,12,0,0

DamageProfile = [Laser] Conflagration,1,1,0,0

DamageProfile = [Laser] Gleam,1,1,0,0

DamageProfile = [Laser] Multifreq,28,20,0,0

DamageProfile = [Laser] Radio,1,0,0,0

DamageProfile = [Laser] Scorch,36,8,0,0

DamageProfile = [Missile] EM,1,0,0,0

DamageProfile = [Missile] Explosive,0,0,0,1

DamageProfile = [Missile] Kinetic,0,0,1,0

DamageProfile = [Missile] Thermal,0,1,0,0

DamageProfile = [Mission] Amarr Empire,56,43,1,0

DamageProfile = [Mission] CONCORD,26,12,20,42

DamageProfile = [Mission] Caldari State,0,31,69,0

DamageProfile = [Mission] Gallente Federation,0,58,42,0

DamageProfile = [Mission] Khanid,56,40,4,0

DamageProfile = [Mission] Minmatar Republic,14,5,23,58

DamageProfile = [Mission] Mordu,2,32,66,0

DamageProfile = [Mission] Thukker,0,37,7,56

DamageProfile = [Other] Incursion Sansha's Nation,16,13,36,35

DamageProfile = [Other] Sleepers,29,29,21,21

DamageProfile = [Other] The Law,36,29,24,11

DamageProfile = [Projectile] Barrage,0,0,20,24

DamageProfile = [Projectile] EMP,36,0,4,8

DamageProfile = [Projectile] Fusion,0,0,8,40

DamageProfile = [Projectile] Hail,0,0,13,48

DamageProfile = [Projectile] Quake,0,0,20,36

DamageProfile = [Projectile] Tremor,0,0,12,20

DamageProfile = [Projectile] Phased Plasma,0,40,8,0

Fitting

The highlighted areas on the UI image:

1. Ship/Market browser Browser - Used for creating fits and adding modules
2. Fitting Window - Used to view fit and add charges to weapons and modules
3. Additions - Used for adding and selecting drones/implants as well as assigning fleet boosts
4. Character Selection - Drop down box for selecting imported characters, all lvl V and all lvl 0
5. Stats - Resist profile and EHP, DPS and volley, targetting and speed info, ship and module cost

To browse, edit, and add fittings use the Ship tab in the left pane (1.):

• Root list
• Back one level
• Toggle show fit ships only
• Editing current fit (Make Copy/Rename/Delete)

To create a new fit browse to a ship class and click the

Adding Modules

To add a module to your fit open the market tab in the left window (1.), browse to the module you want to add and double click it. Providing there is a free slot available, the module will be added to the fit. You can switch between T1/T2 - Faction - Deadspace - Officer modules using the buttons at the bottom of the pane.

Pokemon pllay it version 2 iso download pc.

Adding Charges

To add a charge right click a module, hover over charge and click the desired charge. (You can add charges to multiple modules by Shift-clicking modules)

Adding Drones

To add drones browse to the drones section of the market tab and double click, only drones that are ticked will be added to the DPS stats. The drone bandwidth and capacity is shown in the top left of the stats pane (5.) You can manipulate the drone stack by right clicking.

Adding Fleet Boosts

You can set a Squad/Wing/Fleet booster in PYFA, each role can have a different character and ship assigned to it. To set boosts you first need to create a boost ship, this could either be an empty ship (to apply character skills only) or a boosting ship (to apply module boosts). Once you have created a boost ship right click the fit and tick booster fit. Ships assigned as boosters are marked with . You can also drag fits in to the boost window and use the right click menu to set a Squad/Wing/Fleet booster.

When you have a boost ship set you then open up the Fleet tab under the Additions (3.) pane. you can select boost ships from the drop down box and any character can be used.

Using Graphs

Graphs can be used to view DPS - Range charts. You can add multiple ships to the same graph to compare damage projection. The targets Signature, Velocity, Angle and Distance can be added for the desired effects. To add ships to the graph open the graph window (Window -> Graphs or press Ctrl-G) and drag fits into the graph.

Importing/Exporting Fits

Importing fits

PYFA can import fittings directly from clipboard, to import a fit either go Edit -> From Clipboard or Ctrl-V. To import a fit from EVE to PYFA simply click 'Copy to Clipboard' in game. Once you have a fit copied to clipboard you can paste it into PYFA.

Exporting fits

To export a fit either go Edit -> To clipboard or press Ctrl-C, and select your preferred format. The EFT format is the most widely used and can be imported into EVE by opening the fitting window in game, clicking browse and clicking 'Import from Clipboard'. The EFT format is commonly used on forums and to import fits for a variety of 3rd party programs.

If you've found a bug in EVE Online (yes, this happens unfortunately!) and you want to help CCP fix it, you can file a bug report either directly from the client by pressing F12 and following the 'Report Bug' link (preferred), or you can send it (out of game) here: File a Bug Report

In the following guide you´ll learn in which cases it makes sense to write a bug report and how to write a good report.

Before writing a bug report

• Customer Support: Bug reports are totally unrelated to support tickets, and filing a bug report for reimbursement or help will not work, as bug reports are never seen by the GM / support team. You can write a support ticket to get help from a GM by going to the support site
• Exploits: You found an exploit, which is abused (or may be abused) by other players? Please write both a bug report (to get it fixed) and a support ticket (for a fast detection of the exploit and dealing with the consequences). You might also want to check the list of publically announced exploits.
• Your side: It is always good to check first, if the problem could be fixed yourself, for example by updating your drivers (especially graphics drivers). It is also a very good idea in many cases to clear your client cache.
• By Design: If you just want to share your opinion about the balancing or game design, please use the forums and don´t write a bug report. Bug reports are normally not seen by game designers.
• Many problems at the same time: Please always write a separate bug report for each found issue.

How to write a good bug report

Title

A good Bug Report (or BR) title is short and descriptive. It should tell the reader what the bug is, where it happens and in which circumstances it occurs. A good idea is to put the location or a keyword as the first word, so it'd be easier for BH's and QA people to sort through bug reports. Like 'Exploration', 'Chat' or 'Mac'.
Example: 'Overview: War targets not displayed on overview'

Category

Selects one of the high-level categories for the defect:

• Gameplay: Gameplay mechanics: anything concerned the logic behind the game design and the way features are intended to work. All spelling errors in English also belong into this category. Examples: Ship & module attributes, Scanner, Science & industry
• PVE: Player versus environment: issues relating to the content of the game. Examples: Agents/NPCs, Incursions, LP Store, Missions, Factional Warfare, Sites/Complexes, Exploration
• UI: User Interface mechanics:Issues relating to the functionality of the UI (drag & drop, sort order, UI alignment, compact mode, UI scaling, window behavior). Examples: Neocom, Overview, Station services, Brackets
• Graphics: Issues relating to all visual aspects of the game except UI (textures, lighting, rffects, model geometry). Examples: Station Hangars, NPCs using incorrect ship graphics, Captains Quarters, Ship Visuals, Character Creator, Firing/Hull effects
• Technical:' Issues related to the game client not functioning. Examples: EVE Voice, Hardware-related issues, Client crashing/freezing, Exceptions, Client cache
• Localization: Incorrect or missing translations in any supported languages but not spelling mistakes in English. Examples: Translation errors in any in-game text, Missing translation for German, Japanese & Russian
• Audio: All issues relating to in-game sound. Examples: Environment music, Sound effects (gunfire, stargate jump, etc.), UI context audio feedback
• Launcher: Issues relating to updating and validating the EVE game client. Examples: EVE client fails to update, EVE Launcher fails to update, EVE client is corrupted, EVE Launcher doesn't appear
• Forum/Website: All issues relating to the forum or websites. Examples: EVE Gate, API, Account Management

Description

Here you should give as many details as possible and describe the bug scenario in detail and all the circumstances in which the bug occurred.

A good description will save the developers a lot of headaches and make it easier to fix your issue quicker. For example, submitting a bug 'War targets not displayed on overview' or 'Cannot unfit launchers on ships' sounds very serious until you specify that it *only* happens if you select a certain option in the Overview or you have a certain rig fitted on your ship when trying to remove the launchers. It's important to give a measure of how severe the bug is and how wide its area of effect is.

Mention how often that bug occurs, if it's something that happens every time or just some weird occurrence that only happened once and couldn't be reproduced. It's important to know if it's a common issue that can easily happen or some kind of oddball exception.

For graphical issues please also specify your graphic content settings.

Reproduction steps

The most useful bug reports are those that have a good description as to how to reproduce the bug in a consistent manner. Try to reproduce the bug again and determine the exact steps you need to go through in order to make it happen again. Try to find the simplest method to make your bug happen. This section should outline how you made it happen, broken down into steps, numbered chronologically.

Try to make it very clear for anyone reading the BR just what exactly they have to do in order to reproduce the bug. The bug might seem fairly obvious to you, because you've experienced it firsthand, but if the reproduction steps are complicated try to make the steps as clear and complete as possible so that we can reproduce it ourselves and fix the issue.

What else is needed for a useful bug report sent through the website?

To make it faster and easier for us to reproduce your bug report we would appreciate getting following information from you:

1. Screenshot of the bug – important for UI or graphical bugs
2. DXDiag file (Windows only) – important for technical and graphical bugs
3. LogLite log – very helpful to see if any errors were logged
4. Crash dump - if it’s a crash and a crash dump was generated

Saving a screenshot

Windows:

1. When you encounter the bug, press the Print Screen (Prt Scr) button on your keyboard.
2. The screenshot should be located in 'My Documents' -> 'EVE' -> 'Capture'.
3. Find the screenshot you took (the one with the most recent timestamp).
4. Edit the screenshot in paint to highlight the point(s) of interest.

Mac:

• Full screen: Press Command button + SHIFT + 3
• Windowed mode: Press Command button + SHIFT + 4 and select the EVE Online window

The screenshots will be saved on your desktop

Saving a DXDiag

1. Select 'Start' -> 'Run..'
2. Type 'dxdiag' and press Enter
3. Select the 'Save all information..' button and save the file in a place you'll find it again.

Getting a LogLite log

See the helpdesk article about LogLite

Finding the crash dump

Check the article about reporting crashes.

Eve Fitting Tool 2019

Restrictions (file size / type) for attached files

There is a limit on the file size of those files submitted with bug reports of 15 MB. In the need for larger files please use a 3rd party upload service and give the link in the bug report.

Please make sure that you always zip files of any significant size (over ~200 KB)

Please note that only following file-types are accepted in Bug Reports, for everything else use zip/rar: jpg, gif, png, avi, flv, mp4, mov, mpg, mpeg, wmv, txt, rtf, lbw, lsw, zip, rar, 7z, dmp and mdmp.

Eve Ship Fitting Tool Online

You can also attach multiple files to a report and add further attachments later. The report will be listed under 'Bug Reporting -> My Bug Reports'.

Eve Fitting Tool App

Please note: Be aware that it is currently not possible to attach files to a bugreport, if you are using the in-game browser. Please use any external web-browser for adding attachments.

In-game bug reporting tool

For in-game bugs it is normally best, if you send a bug report directly through the in-game bug reporting tool. You can find it in the help menu (F12) at the bottom: “Report Bug”

Hint: If you want to continue your report later you can Save it (stored under your settings folder) and Load it again later via the tool.

Be aware that the client might be unresponsive for a bit when sending the bug report, while the client gathers all the information and sends it to the server.

Screenshots

You can create up to three screenshots directly through the bug reporting tool. The screenshot editor lets you add frames, arrows and text to a screenshot. You can take screenshots of modal dialogs by pressing CTRL+ALT+SHIFT+P.

You can change the color of the added arrows, frames etc. by right-clicking them in the editor.

Attachments

The Report Bug feature attaches several files for you automatically.

These are the following :

• DXDiag file
• prefs.ini
• screenshots
• logs.txt containing last 1000 lines of in-memory logs.
• methodcalls.txt containing all calls made to the server since the client started
• processHealth.txt containing cpu, memory and network info
• settings.yaml containing all your user, public and character settings

In addition to file attachments the tool automatically writes information into the 'computer' field of the bug report as follows:

• OS: type and version
• Video Card: Manufacturer, type and driver version
• CPU: Type, manufacturer and speed
• Memory: Total and used
• User: name, char name, solar system

In the case that you need to attach additional files you can do so through the regular website after you sent the bug report through the in-game tool.

What happens to the bug report

After a bug report (BR) has been submitted it arrives on the list of currently open bug reports. The usual process is then that a bug hunter (BH) verifies it by reproducing the problem

Eve Online Fittings

When a problem can be reproduced, the bug hunter will create a defect that is forwarded to CCP's QA department. The defect will be assigned to one of the CCP development teams, who will then be responsible for fixing the issue. After a defect has been fixed, it will be tested again on one of the test servers and once the fix is verified it will be applied to TQ in a patch or expansion.

If there is already an existing defect about a bug when you submit your bug report, then your report will be attached to that defect. This gives the programmers all available information and may help them fix the problem.

Other resources and tips/project-jojo-how-to-not-take-dmg-from-sun.html.

• Often it might be useful to clear the cache and settings of your EVE client, when encountering a problem with the EVE client.
• Latest Patch Notes
• Forums about Issues, Workarounds & Localization, Test Server Feedback, Macintosh and Linux

CCP introduced a new bug reporting system in August, 2013. Information about the new system is available in the following Dev Blogs, including how to file a bug report in-game: