Ships & Modules

Can already be done albeit awkwardly. Create a fit under a character with the target skillset. Then switch character to All 0, and File > Export Skills Needed. Since All 0 will always need all the skills, you have your skill plan.

I have been thinking of a better way of doing this through a new window, but haven't gotten around to it.

Or do what Darkblad suggests (I always forget EVEMon has that ability)

Unfortunately both methods wouldn't really cover the use described.
They would only create a list of skills required to sit in a fitted ship with no module offline due to missing required skills for them. But we all know that there is a huge difference between a "green" fitting sheet and actually being able to fly a ship in a remotely useful fashion or even sit in it. Core fittings skills or the diverse range of multipliers might all be relevant to a specific ships role in combat.


Anyway, I wanted to report a few "bugs" I noticed recently using pyfa 1.4.0 stable on windows.

1) The "Back" button in the "Ships" tab seems to not work as expected every time:
Whenever I copy or delete an existing fit the back button takes me to an empty page and only hitting the back button for the number of times I executed a copy or delete action plus one returns me to the parent ship family page.

2) The "Projected" function seems to be unable to cope with multiple ships of the same type providing remote effects. While I can understand the decision to prevent the projection of fits on itself to avoid recursion it would make sense to allow multiple ships of the same type to provide remote effects to another fit without having to copy the projected fit x times for every time you want to apply it.
At the moment, whenever you add a single fit more than once to the projected tab of another fit, only the effects of the first are displayed.

3) Having a fit[1] that is boosted by a fleet booster projected onto another fit[2] blocks [2] from receiving the effect from the same fleet booster unless the booster is set for [2] first and then added to [1].
I've just seen in the issue tracker that you have that pretty much figured out already... sweet! :D

Remote Reps, Cap Transfers, Remote Sensor Booster - it applies to all of them.
To reproduce:
Two fits, one of them with a beneficial remote effect (let's say a Scythe with 3 medium remote shield booster II), the other one the ship you want to test the remote effect on (can be anything).

1) Add the Scythe to the "Projected" tab of the ship -> it displays the repair amount that single Scythe can apply to the ship.
= working as expected
2) Add the Scythe to the "Projected" tab of the ship multiple times -> it only displays the repair amount one of those Scythe can apply to the ship.
= not working as expected

The workaround at the moment is to clone the Scythe fit x times and add copy 1 to copy x to the projected tab - then the total repair amount is calculated correctly.

If there is any doubt why that might be useful: You might want to know how many Logis you need to out-repair a specific amount of DPS on a target.


While we are at remote effects, i would like to sneak in two feature requests:
1) Would it be possible to add an option to set fittings as "projector fits" (similar to booster fits) that are then available via the rightclick menu in the "Projected" tab?
Whenever you want to test how a specific fit handles itself with applied remote effects you have to move out of the ships fittings tab, possibly out of the ships type tab, back to the list of all ship types and then to the specific ship with the remote effect or have to know the name and use the search function. Having the option to create a list of commonly used projectors (for example the standard logis used by your corp/alliance/coalition) that are available from within the fitting window of the ship you want to test them on would greatly simplify the process.

2) Would it be possible to add a toggle option for every fit in the "Projected" tab?
At the moment if you want to disable the projection temporary you have to remove the fit completely and re-add it afterwards. Combined with the clunky way of getting to those projector fits it can be quite a hassle.


Thanks for all the effort you put into pyfa btw. It's greatly appreciated.

Hmm... didn't know you couldn't apply the same fit multiple times... I don't see a reason why that isn't wouldn't possible to achieve. I will definitely look into it.

As for feature requests:
1) That is a much larger feature request that probably will not come to light due to a variety of :reasons:. However, I have been playing with the idea of perhaps adding a context menu for the projection view that would list all currently open fits, so you can simply right click and select the open fit to project. Kinda like how you apply wormhole effects.

2) Toggle for projected fits is already on the table. Just haven't gotten around to figuring it out. IIRC there were a few issues with it. https://github.com/DarkFenX/Pyfa/issues/83

As pyfa is the only native app for Linux and Mac, we don't view Linux as low priority. The difficulty is that I develop primarily on Windows with linux VMs which is a pain. I need to install a proper distro on a partition and get to the nitty gritty.

I would be interested in hearing about this workaround / your thoughts, as I haven't had time to make much progress since my latest comment on that issue. Feel free to join that conversation on GitHub, or continue with it here.

As for the tooltip, I assume best place to put it would be a tooltip for the align time stat

I'm having the same Problem, Windows 8 as well, re-installing 1.4.0 (Hyperion) works flawlessly.

Was having same problem as others re. pyfa not loading, renamed profile and can confirm pyfa now loads OK.

You need to reinstall 1.40 then backup all your Fittings, then delete "%USERPROFILE%\.pyfa".

Install 1.5 and import all fittings - unfortunately user profiles and API-Data are lost.

done it, tks

Seems it's not possible to import damage profiles using the old format. Mind if I post the new damage profiles here or is this simply a bug ?