Ships & Modules

Not really. We were interested in wx3 mostly because of its Phoenix branch, which supports python 3, which we need for rewrite. At the moment it's mostly me writing backend, Blitzmann will join later when it's ready and when he has sufficient time for that.

Is there any particular reason you want wx3.0? As far as i remember the only potential issue is that wx2.8 is going to be dropped from newer releases of some linux distributions (like Debian Jessie), so we will be forced to update pyfa distributions to use wx3 one way or another. Biggest concern is mac skeleton (binary environment in which pyfa is launched), we have no idea how to rebuild to satisfy changed dependencies.

I use a debian jessie distro and just regularly merge the latest changes into the wx3 branch, which seems to work fine.

I clone the github repo, checkout the wx3 branch, do a 'git fetch' and then merge from a recent tag e.g. 'git merge v1.1.20'.

I've ran into the zero-resist Uniform profile on 1.10.0 after a clean install (due to a clean Windows 7 install), and after playing around with it for a bit, it looks like whichever damage profile is selected in the drop-down when attempting to create a new damage profile will be zeroed out. On a clean install, because Uniform is the only damage profile available, it's the damage profile that is up when creating the first custom profile.

I was able to get around this by creating a copy first, and then switching to that copy to create new damage profile. The copy was zeroed out, but Uniform was left untouched.

Mosaic update - 1.11.0 - is out!

Awesome, as always, however I am unable to activate either the T1 or T2 Entosis Link module on a couple of fits. Checked to see if there was stront listed to throw in the cargohold (a long shot, but who knows), to no avail. Other modules can still be activated in Pyfa fine, showing the capacitor drain/etc.

I admit I'm kind of tired at the moment, so am I missing something obvious or is this perhaps a bug with the Entosis links?

Thanks for the great work as always!

Also, sorry if this has already been covered somewhere already.. somehow...

Known issue, i forgot to add one small file before releasing. It's already fixed in development repo and fix will be included in next release.

I don't think such bug deserves separate release.

Found something strange: Yacht

Updated skills, no affecting implants. But 13.8k EHP in Eve client and 17.7k EHP in pyfa?

btw: when you check for wxPython 2.8 and there is newer version in system you output 'prepare for errors'. And yes, program does not work. Not because wxPython 'is too new' but because after wxpython.choose(2.8) you cannot do import wx: it fails. Need some way to 'reset' library after chis check.

New technical preview release:
Mosaic 1.0 build built with updated UI toolkit.

If anyone interested - please at least launch, play a bit with fits. If you run into any issues - post here or create ticket on github.

If stars align - you have Mac and is competent with python - please write me an eve-mail, i need your help to build new binary skeleton for future Mac releases.

---

There's --root command line option which forces pyfa to store its data in its own folder. It's probably not really good solution (sharing whole pyfa distributive with gdrive). I looked into better ones - checked dropbox integration API, and it seems to be not acceptable because it enforces its own database format. This is pretty big and unneeded change which hardwires pyfa to dropbox.

Personally, i'm using following approach for many applications (not just pyfa):

1) Create folder in dropbox for app sync (let's say, [dropbox]/sync/pyfa)
2) Move files necessary to sync between machines into there (for pyfa, it's [user]/.pyfa/saveddata.db)
3) On all machines where you want to do a sync, create symbolic link (with target being that file [dropbox]/sync/pyfa/saveddata.db, and its location [user]/.pyfa/saveddata.db). Symbolic links are supported not just on Linux, but on Windows too (it's feature of NTFS, you can google it up).

This way only small file is shared - but it contains all your characters and fits. It's not very trivial to do - especially if you do not grasp concept of symbolic-/hard-links, but I do not know how to integrate convenient way to do it into pyfa. If anyone has ideas (with links to API specifications) - please share, this item is one of top priorities on my to-do list.

EVE calculates worst-case-ehp (where lowest resists for each tanking layer is taken). Pyfa calculates EHP against uniform damage by default.

Please check if it's still case on wx3 branch. Blitzmann modified logic in that file to cope with various possible combinations. It works for me (on linux and windows), but it's still possible that things can break in some cases.

Exact same problem here. Same OS aswell :)