Skip to content

Aegis - v1.13.2
Compare
Choose a tag to compare
@blitzmann blitzmann released this 10 Jul 16:55
· 6056 commits to master since this release
v1.13.2
b4604f8

v1.13.2

Fixes:

  • Modules being removed from fit when their position moved (#324)
  • Mode selection with tactical destroyers (#321)
  • Price data being fetched for tactical destroyer modes (#322, #323)

v1.13.1

Fixes:

  • Fix crash for new installations (thanks @poettler-ric!) (#318)
  • Fix OS X package
  • Fix Bastion module icon (#317)

Note: Missile Guidance Computers / Enhancers have an empty market group. This seems to be an issue with the EVE data, and will most likely be fixed with the next expansion. The modules are located in the Tracking Computers / Enhancers group (see #319)

v1.13.0

Database:

  • Updated to Aegis 1.0 release

New:

  • Rigs can now be toggled to quickly see the effects on fit stats
  • Some improvements to price handling have been made (#290)
  • Quick fit shortcuts using Alt+1-9 (thanks @lunedis) (#183)
  • Average resist multiplier in resist tooltips (thanks @lunedis) (#248)
  • Like the main window size, market and browser split size are now saved and loaded at startup (#259)

Fixes:

  • Triage not properly implemented when projecting onto fit (#291)
  • Fit not recalculated correctly in some situations after adding module (#299)
  • Projected fit applying Tactical Destroyer mode effects on projectee (#302)
  • Context menu bug on fits in ship browser (#307)
  • Merging drones into stacks and dragging drones from market
  • Database conversions for Carnyx were not triggered. This release should fix that, allowing fits that have these modules to load.
  • You can no longer have multiple system effects (wormholes, incursions) on a fit
  • Much backend work has been done to combat fit loading crashes related to database rot (#312)
  • Icons were updated 1st time in a long time, we will be doing it each release now

Also:

  • Some logging has been implemented to log known errors that may creep up. By default, only warnings and errors are logged. This has only been implemented in specific object initialization to log when invalid items are being loaded, but hopefully will find it useful in other places throughout the source. The log file is saved in ~/.pyfa/log.txt
Assets 6
Loading