Ships & Modules

1) https://github.com/pyfa-org/Pyfa/issues/422 It's something I was working on, then other things came up and I haven't really made another push since. The problem with this is simply to figure out a intuitive way of differentiating character implants from fit implants, and figure out a way to toggle between them (it will also require edits to the current database schema, which I dread doing)

2) https://github.com/pyfa-org/Pyfa/issues/445 This has also been discussed multiple times. But, due to the nature of heat damage, I am unconvinced EFT gives a reliable value for this. EFT may just be pulling numbers out of no where; someone suggested EFT used a worse-case scenero - we don't know and can't check due to it being closed-source. I am not opposed to this idea, but it needs to be efficient and correct (or at least a ballpark), and not added simply because EFT has it (the quality of which I am not sure of). There's also the undertaking of implementing it when an algorithm is developed for it, which will not be trivial

3) Yes, the pyfa graph needs a complete overhaul, but it's definitely not a priority (and generally not something I am familiar with).

To all: I would urge you to join the github discussions for these features / issues and give your input. The more input we receive on how to tackle some of these problems the better. =)

So, I'm not sure where to post this, but I figure here is a good a place as any, and who knows, maybe I'm not the only one..

First off I find Pyfa far more usable than the two alternatives EveHQ and EFT.

However, after using it for a while it will randomly stop accepting right clicks.. making the contextual menu completely inaccessible and the whole thing become just frustrating as I have to close the application and open it again.

I have no idea what is causing it, or what could be the trigger, it happens seemingly randomly.

Windows 10

which log?

The only log that actually has any text in it is "log.txt"

The other two are empty.. Or do they reset for ever launch so I should post them right after it happens?

well the only text in "log.txt" is

"2016-01-14 10:25:55,476 eos.saveddata.module ERROR Item (id: 16503) does not exist"

singularity-1015913: March 2016 Pre-Release

Is this release viable or did ccp change anything in the last minute?

Yeah, what I meant was displaying it somewhere. But its a minor thing.

Also, I'll take you up on your offer, thanks.

1) There should only be .pyfa in your user folder. This is the pyfa user directory for config / personal settings / fit database. I am not sure why you have 3, unless they are unrelated to pyfa (I know many programs used the ~/.dir convention)

2) To update: you can extract the zip somewhere (you should be able to re-write the previous location you used, unless you're upgrading from a very old version in which case best to delete old one). OR the easy way and use the .exe installer - this will install pyfa to a path you choose, and when you run the updated installer it will overwrite for you. This is the preferred method, as we can add code to the installer in the event that directory layout changes which might not be compatible with previous versions

3) Overheat timeres. It's been discussed before https://forums.eveonline.com/default.aspx?g=posts&m=6359763#post6359763 https://github.com/pyfa-org/Pyfa/issues/445 tl;dr this would be a very big project for very small benefit IMO (considering heat is based off chance and there's not way to predict it). I am not convinced EFT is doing it right so this is something where I would say just because EFT has it doesn't mean it's needed / useful. I'm open to thoughts though, feel free to provide a algorithm that might work =)

4) Ammo timers, can you be more specific?

5) DPS graphing. Yes, I know it sucks. This has been known for many years. No one wants to touch it though. >_>

6) Ah, the LP Store. I want to get it back up and running eventually, but I've had a lot on my plate recently. That and EMDR has died off (or will be) so I'd have to re-write the price caching backend of it. Not only that, but the LP Store data itself is probably very stale and I don't have the energy to keep it updated - it was very manual process of flying to each store and manually confirming if they were accurate. **** that. So yeah, I want to, but it's not as easy and simply turning it back on ;)

regarding implants. I always imagined pods just as a regular ship with mods (implants). Maybe you could just add a pod as special ship type, make it fittable with implants, then let us select the pod via a combo box (listing all pod fittings) for each ship fitting.

I know that description is oversimplified and there is more to that, but it would have the advantage that you don't need more UI for managing clones, since it reuses stuff which is already there.

Too late, we already have character implants in a development branch. However, I would like to point out that both ideas would probably take the same amount of work overall (but in our situation, the character implants already had much of the back-end functionality, so less work)



How do you mean? In general, we simply release a new Stable version which contains an updated EVE database file (eve.db) that contains all EVE-specific things (modules, ships, attributes, etc). We also have some renaming mappings so if you import an old fit with old names it converts them to the new modules.

I can get more specific if needed, or you can contact me with any of the methods listed in the pyfa README.