v2.3.0

Note that importing a fit with an Abyssal module will actually remove that module. This is due to the fact that we often don't have data on the module that we need in order to do a proper import (we don't have the base item, mutaplasmid, nor mutations). There are some ideas being thrown around, such as prompting the user to enter these values, but nothing is set in stone.

In certain situations, there may be errors when starting up the local pyfa server to handle the SSO login request. These errors usually have to do with the client machine's environment, and are difficult to pin down. There is now a message that directs the user to a workaround if we can't start the server for some reason so that they can add their character (#1627)(thanks @WatchMeCalculate!)

You can now default to character implants for new fits, instead of fit-specific (#1667)(thanks @MaruMaruOO!)

There's been a bit of work on icons; how they're generated, stored, and accessed from within the client. This should be a transparent change for most folks. Please let us know if there's any errors relating to icon fetching :) (#1621)

There was probably a few other contributions / fixes that I forgot to add >.<

As always, thanks so much to the community for reporting on bugs, and to the various contributors for helping out with bug fixes and feature implementations!

Note that importing a fit with an Abyssal module will actually remove that module. This is due to the fact that we often don't have data on the module that we need in order to do a proper import (we don't have the base item, mutaplasmid, nor mutations). There are some ideas being thrown around, such as prompting the user to enter these values, but nothing is set in stone.

In certain situations, there may be errors when starting up the local pyfa server to handle the SSO login request. These errors usually have to do with the client machine's environment, and are difficult to pin down. There is now a message that directs the user to a workaround if we can't start the server for some reason so that they can add their character (#1627)(thanks @WatchMeCalculate!)

You can now default to character implants for new fits, instead of fit-specific (#1667)(thanks @MaruMaruOO!)

There's been a bit of work on icons; how they're generated, stored, and accessed from within the client. This should be a transparent change for most folks. Please let us know if there's any errors relating to icon fetching :) (#1621)

There was probably a few other contributions / fixes that I forgot to add >.<

As always, thanks so much to the community for reporting on bugs, and to the various contributors for helping out with bug fixes and feature implementations!

Mutaplasmids

Of course, the biggest feature missing with our Into the Abyss release was feature parity with relation to Mutaplasmids. This required a bit of research into how to basically mutate existing attributes, but I think we finally have it at a point where it's both functional and user-friendly.

To convert a module to a mutaplasmid:

To change the values of the mutable attributes, simply open the item stats. The first tab will give you the panel designated for editing the attributes (still debating on where this tab should go):

When changing the values, the fit will recalculate after 1 second with the new values (this prevents calculating multiple times if people are quickly changing the values)

I focused on getting the basic functionality down. As such, at this time, you can't change the base module or the Mutaplasmid used - those will hopefully come later. If you need to change it, simply remove the Mutaplasmid through the Module context menu, and re-apply. :)

This is a large change, and I expect some brokenness / suggestions to come out of this beta release. Please try to break it with various shenanigans. If you run into anything, or want to generally discuss the feature, please head over to the issue page linked above. :)

Icons

pyfa is testing out a new way of fetching icons in an effort to update some of it's scripts. This required a bit of refactoring to how they are stored and accessed. I believe all the places that needed to be fixed are fixed, however there may very well be places in some parts of the code that I haven't tested that may still spawn an error. If you happen across anything like this, please report the issue in the thread linked above.

Other things

This also includes some other tweaks and fixes, such as font sizes closer to the 1.x releases for the tabs, some bug fixes, and maybe another feature or two that I'm missing.

Note: this release does not include any support for mutaplasmids or Abyssal modules. This is a feature that is currently being R&D'd, but it will take some time. Please keep this in mind, and be on the lookout for pre-release builds that feature this... well, feature, in the next couple of weeks.

If you wish to follow the in-development notes on that feature, please subscribe to #1597

v2.1.1

Fixes:

[Windows-only] Critical issue in which the updated pyfa was using an old EVE database file (and thus, none of the awesome new stuff) (#1622)

v2.1.0

Database:

Updated for the Into the Abyss 1.1 expansion

New:

Support for new weapon system (DPS calculated is assume to be full DPS. A way to show DPS range is currently being researched)

Abyssal weather effects can be selected the same way wormhole effects can: right click the "Projected" panel and select.

Note: this release does not include any support for mutaplasmids or Abyssal modules. This is a feature that is currently being R&D'd, but it will take some time. Please keep this in mind, and be on the lookout for pre-release builds that feature this... well, feature, in the next couple of weeks. If you wish to follow the in-development notes, please subscribe to #1597!

WARNING: To those that use the installer, there may be an issue. For some reason, it's using an old EVE database file hen you don't run pyfa as an admin. This causes the new content to not be included, and errors hen using things like the Projected Panel context menu. This issue is being tracked here: #1622 and is of utmost importance.

As a workaround, simply run pyfa as Admin, and you should be good to go.

Database:

Updated for the Into the Abyss 1.1 expansion

New:

Support for new weapon system (DPS calculated is assume to be full DPS. A way to show DPS range is currently being researched)

Abyssal weather effects can be selected the same way wormhole effects can: right click the "Projected" panel and select.

This first point release for pyfa 2.0 contains improvements over the new ESI system that was implemented to replace the XML API.

A few notes beforehand, though: please be aware that pyfa used a different database file during the beta builds. This was to prevent gambling with users fittings database using what was, at the time, very new beta code. If you are wondering what happened to your fits during beta... well, they are still there, just in a different database. Easiest way to get those fits would be to run a beta build, File > Backfup Fits. Then, open this release, and import those fits.

If you are one to download the zip file and extract to and overwrite a previous version, you cannot do that with the 1.x > 2.x upgrade. It will break your pyfa install. if you like to use the zip files, please completely remove the old pyfa directory (or, better yet, use the windows installer, which we now have again!).

Also note that ESI support is still quite new, and I am expecting more bug reports. Please, if there's anything funky, let me know through the GitHub issues page! (please glance through the issues first though, if you see something similar, leave a like and comment on it)

Added:

The ability to provide your own custom developer account details for SSO (bypassing our authentication proxy entirely). Please see this wiki page for more information.

Removed "esipy" from requirements. pyswagger was just causing too much issue. It's a bit too robust a feature-full for pyfa, which is using a very tiny subset of available ESI route. EsiPy is a great package though, and pyfa still uses a lot of it's code as a boilerplate for ESI integration. Many, many thanks to @Kyria for their support for this package :D

Today marks a special day, the release of v2.0 to the masses! This version drops support for Python 2.x, wxPython 3.x, and simplifies our build process to better handle new packages / features that we may want to include in the future. Please see here for more details.

v2.0 has been in beta for the last couple of months, and has done surprisingly well. With over the 18k downloads collectively between beta releases, there haven't really been any major reports of bugs with the 2.x codebase. Coupled with the XML API / CREST being shut off today, and I believe it is time for it's Stable debut!

Below I'll be covering the major changes coming with this release for those that may not have been keeping up with it. In case you want more detail, feel free to peruse the previous release notes: beta1, beta2, beta3, beta4, beta5, beta6

Please note that, as of right now, there isn't an EXE installer for Windows. It's simply a zip that you'll have to extract and run. I'm looking into getting an installer up and running, but there's a few caveats. Please stay tuned!

Added:

ESI support

All of the old XML API information is no longer accessible. In order to link you pyfa character to your EVE character, please go to the character editor and, under the "EVE SSO" tab, click the "Log In with EVE SSO". This will open your browser and direct you to the EVE Single Sign-On process. Once you log in, you should be able to link the pyfa character with the currently logged in EVE characters.

Special thanks to @Kyria, developer of EsiPy, for answering a boat-load of my questions and even developing a few features at my request!

What happens to 1.x codebase?

Originally I was going to segment it off into it's own branch and keep it up to date with the latest EVE changes for at least a few releases. However, due to 2.x being well-received so far by beta testers, the fact that the upcoming expansion has integral mechanical changes, and the fact that I haven't heard of many issues from Linux users, I am not sure if I will be continuing to keep the old codebase up to date. If there is demand for it, I will do my best, but for now, the old codebase will be put into the 1.x branch and left alone.

Thanks so much to all of the folks who have tested these beta releases and provided feedback. And thanks to all other users for your continuing support! As always, if you're having any trouble with anything, don't hesitate to submit a ticket to out GitHub issue tracker.

This is most likely the last release of the 1.x version cycle, unless some major issues crop up in 2.0. Please use the 2.0+ releases from now on. The only major difference between this release and the previous release is the removal of XML / CREST API functionality, as that functionality has now been converted to ESI in 2.x.

This is the sixth, and hopefully final, beta release for v2.0. Please see this release for more information on the v2.x cycle!

This beta release is a big one because it strips support for the EVE XML API and implements support for seamless ESI integration! There are bound to be errors with this (there's already a couple that are tracking), so please let me know if you notice anything funky! Please see here for a list of current ESI issues.

Added:

ESI support

All of the old XML API information is no longer accessible. In order to link you pyfa character to your EVE character, please go to the character editor and, under the "EVE SSO" tab, click the "Log In with EVE SSO". This will open your browser and direct you to the EVE Single Sign-On process. Once you log in, you should be able to link the pyfa character with the currently logged in EVE characters.

Better documentation on how this works is forthcoming!

Special thanks to @Kyria, developer of EsiPy, for answering a boat-load of my questions and even developing a few features at my request!