Skip to content

v2.1.1 - Into the Abyss 1.1

Compare
Choose a tag to compare
@blitzmann blitzmann released this 31 May 05:14
· 3589 commits to master since this release

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.
  • Can now copy text from Traits / Description section of item stats (#1529)(thanks @minlexx)
  • ESI requests can now use the same proxy information defined in Preferences > Network (#1578)(thanks @minlexx)

Fixed:

  • Attribute export to CSV (#1613)
  • Bug with the RAH not applying proper resists in certain situations (#1602)
  • Issue with the asterisk on character name signaling unsaved skills not going away after refreshing skills ( #1599, #1616)(thanks @WatchMeCalculate)
  • Database migration breaking when being run against an extremely old user database (#1595)
  • Export to EVE. Yep, the entire feature. 😛 (#1593, #1502)
  • Removed obsolete market group (#1562)
  • Some issues with out update notification formatting should now be resolved (#1532)
  • Incorrect modifications from Structure Missile Rigs (#1526)
  • DPS graph when enabling certain fighter abilities (@1521)(thanks @WatchMeCalculate)
  • Inconsistent charge sorting (#1520)

Remember, if you run into any issues, please report them on our issue tracker here: https://github.com/pyfa-org/Pyfa/issues!