Hello, good job you guys perform, pyfa is awesome.

But, as a suggestion, would it be difficult to have volley of drones also automatically calculated?

Thanks.

It might be possible. Where do you think this info should be displayed? I think we might be able to add a colum to the drone window to show volley / dpa info of stack

Are Geckos added? :3

in the same location volley is displayed, with overall ship's volley, that would be great. http://prntscr.com/3gmsww

thanks.

Also, I just pushed a new feature to the master branch: proper support for Cargo, including adding various charges and modules to the cargo in Pyfa and having correct import/export of it throughout all formats. I started on this feature 9 months ago, then stopped. Few days ago I started work on it again and it's to a point now where it works well. I just forced a nightly build of these changes, would appreciate if some people give it a test run: http://blitzmann.it.cx/pyfa-nightly/

I'm currently working on improved drag+drop functionality, so that one can drag from cargo to a slot in the fitting window and swap them out. This would make the new cargo feature that much more handy, as it can be used a personal collection bin of modules that you may want to try on your fit without having to search for them all the time after swapping them. This is still in the works tho.

Was playing with your new cargo stuff, looks cool. But at some point, I wondered: "hey, how much space left have I got there ??"

See where I'm going ? Yes yes, indeed, that way: you should add something somewhere so we know when the cargo is full. And know anyway what's the portion of cargo used.
I think you could add a nice bar in a third column of the cargo items, bar that would show the percentage this line use in the total cargo. And add somewhere else (maybe dedicated top line in the cargo tab) with the total percentage cargo usage. Don't know if I'm clear...
I'll try to play with Inkscape and post a shot of what I mean. Or code it directly... May be faster...

Is there an easy way for an end user to edit the module/ship data? I'd like to add the new rattlesnake and gecko to do some theoryhammering.

Unfortunately, there is no easy way to edit the attributes or add new items / ships to the database. It's possible, sure, but it's also a pain in the ass. eve.db is a SQLite database and can be edited with any tool that supports SQLite (I use SQLite Manager extension for Firefox). However, that's the easy part.

The database is more or less structured in much the same way as the official EVE database dump. There might be some small differences (I believe pyfa removes some inert columns and such). If you would like to learn more about the structure, see here: http://wiki.eve-id.net/Category:CCP_DB_Tables

I can give a quick tutorial tho. For example, I recently released eve.db that included the Omni Tracking Link duration changes that came with Rubicon 1.4. I did this manually. I found all the type IDs of the affected modules, and for each one I changed the attribute value. For the sake of example, lets say I am going to modify the tech 1 meta 0 module of this group. This has a typeID of 23533. I also need to find the ID of the "duration" attribute. You can find this in `dgmattribs`, which shows us that this attribute ID is 73. Now, to change the actual attribute, you need to find the attribute value that links to this attribute and module. This is in `dgmtypeattribs` - simply search for the typeID (23533) and attributeID (73), and that gives you the value (I increased it from 10,000 (10ssec) to 30,000 (30 sec)).

This is a lot of manual work even if it's fairly straight-forward, and I wish that we had a better way of editing this. Adding an entire ship to the database is probably not worth it (especially if all of it's attributes haven't been released). Perhaps one day we'll ship a feature with Pyfa that allows us to edit this kind of stuff from the GUI.

That only pertains to attributes, not effects. If there is a new effect, you must write python code to implement it (this is very inefficient, which is why Kadesh is working on a new engine for Pyfa).

If you're techy, there is also a wiki page describing how you can update Pyfa from SISI. It's a time consuming process, and only works if SISI has been updated to reflect changes.

Is there an easy way for an end user to edit the module/ship data? I'd like to add the new rattlesnake and gecko to do some theoryhammering.

I'm stuck trying to import fits. Aimed pyfa at a file with many, it displayed "Importing" until I killed and restarted... tried a file with just one fit and it took, so tried two... no dice.

Any idea why, what can I do? Thanks!

Just added in the gecko.

Hi Guys,

I downloaded both the zip and exe files for windows, I tried both of them, but the import function is not working for me.
I used this version: 1.1.22

I can export the fittings to XML, but when I want to import, nothing happens.
The loading bar appears for a split second and that's it. I don't see my fit.

Can you help me, what I am doing wrong?

The exported XML, that I tried to import: http://pastebin.com/8BvQcLrM

Thanks,

...

Thanks, it is working!

Edit:
Although when I want to import an XML which has more then one fittings then I experience the same problem.

The file I used: http://pastebin.com/1ggjg9DB

Thanks

Something is definitely off with the Gecko. It's not getting nearly the DPS that it gets in-game. In-game with my Stratios I get 651 drone DPS, but in PYFA with the same fit and the same 2 Geckos it's showing only 541 drone DPS. (With my character imported, of course.)

http://puu.sh/8KCjf.jpg

..

Thanks, now I see my other fits too.

Can I make a suggestion:
Is it possible to show the fitted ships on the "Ships" tab in another way, for example in a separate "tree" under the ships (or just create another tab next to the "Ships" and there could be all the imported ships)?
Because for noobs like me, it is rather difficult to find the saved ships in that tree (I know that I can search for it, but it would be nice to see all my saved ships in one place).

Thanks,

PS: Keep up the good work!