Ships & Modules

find the ship you want to see that effect on and open that specific fit.
then search for the FAX or any ship projecting the effect you want, right click on the fit "project onto active fit"

just tested and is working fine for me
pyfa v1.27.2

obviously those 2k projected are base hp without taking in consideration resistances!
when projected the 6k hp of my fax became 12k hp of rep on the tengu

something like that :)

1.28.0 out boiz!
thanks as always for your work!

bug:
- dragonfly(light fighter) - variations menu: t1, t2.... and gecko :thinking:
same with gecko that gives dragonfly as variations.

- shadows not having the microwarpdrive ability?

also right click on implants tab to call a set you preassembled isn't working

wtf?

so 1.27 worked for you, but 1.27.2+ has not... That's odd... I'll make an isue on our tracker about it. We did move around some code for matplotlib from 1.27.0 to .2, but nothing significant.

HellGate can you register on Git and post in this issue:

https://github.com/pyfa-org/Pyfa/issues/1046

This is how I will contact you for testing new builds or for any additional information. Doing troubleshooting through the EVE Forums is a *****

Suggested Feature:

on the boost command tab (in the additions section, between "notes" and "projec" to be clear)
would be appreciate a right click command or whatever to rapid call one of the boosting fits already presettled.

without going back to the ships menu every time to right click the right fit and "add command booster"


ty

Could you describe exactly what is not functioning correctly, instead of providing a screenshot comparison (don't get me wrong, screenshots are awesome). You say Electronic Superiority does not work, yet the fit you applied to it does not have any ewar modules on it.

I am assuming you are expecting the WD range to increase. WD/Scram is not considered EWAR. That would be handled with the Skirmish Burst - Interdiction charge. If you're noticing another discrepancy, please let me know the specifics and I can look into it.



The no graphs thing was my bad - worked fine for me but the build failed, and that was the one build that I didn't test before uploading. Also, Ebag has been actively working recently on backend things and other areas that haven't been touched in years. Unfortunately, when you touch a lot of these things, it's easy to not notice some other things going wrong. We don't have an active QA department to test all changes and make sure they don't interfere with other things, nor do we have a large community of devs that keep up with the latest commits in git.

I am interested in the "lag" which you note. You've noticed an increase? Can you describe it / when does it happen? What platform are you using? pyfa never has been the fastest application (partly due to being written in python, but also because of design decisions made early on in the projects life), but we are very interested in hearing about performance issues when they seem to get worse. Please be specific when describing these issues.

And of course, as I always state, pyfa is FOSS; you're very welcome to contribute to the project if you notice and want to fix bugs and performance problems. :D

I'm with Blitzmann on this one. I don't see any obvious issues here.




As Blitzmann said, this is partially due to simple human nature, any time we touch things there's going to be bugs that crop up.

There has been a MASSIVE amount of work done on Pyfa in the last year. Not only have many new features been added (Fighters, command bursts, new stats panes, new preferences, lots of QoL improvements, and many many many MANY other things), but we've gone and done an entire rework on the back end that fixed a ton of low level bugs that have been around forever, and greatly simplified things which will make it much easier for us to work on and support Pyfa in the future.

To be honest, the current Pyfa codebase looks dramatically different from the code base two or three years ago. The front end might look similar, but nearly every single line of code behind it has been touched.

That sort of work never happens without introducing a new set of bugs and issues, but it will absolutely make a big difference in how easy Pyfa is to build new features for. We actually have coding standards now! And unit tests!

Besides, our work on Pyfa is worth exactly what you pay us, and/or the quality of your submitted pull requests.

The only way to guarantee that the reliability won't go down is to freeze the code. And there are a few examples of that floating around, if you want to use those.

Here you go bud:

https://github.com/pyfa-org/Pyfa/pull/1063

As long as tests turn out fine, should be out with the next EVE release. :)

1.28.1 is launching, no more problems for me !

Nicely done and sorry for late answer.