-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graph window broken since 1.6.0 #197
Comments
Can you paste example fit which has this issue? I do not have similar issues on linux and i don't think we changed anything which can affect graph functionality. It looks like fetching data for graph simply crashes, thus i guess it should be fit-specific. |
When I draw a new fitting into the window, there is a warning in the bar below saying "Invalid values in " for a short time (just a few milliseconds). Some frigate and destroyer fits actually work, but most of my fittings don't show in the graph. Screenshots in my first post were made directly before and after a Pyfa update on my Mac. Here an example build that doesn't show in the graph: [Vexor Navy Issue, PvE sniper] Drone Damage Amplifier II Experimental 10MN Afterburner I Drone Link Augmentor I Medium Anti-Explosive Pump I Garde I x5 |
Okay, drones seem to cause this issue + recent changes in resistance profile stuff. Traceback is following:
It seems to be related to fix for issue #180 - it broke graphs with drones. I will wait for blitzmann to comment on this, maybe what i was going to do could break that fix. |
Actually nvm, i will just change what graphs expect to fetch from drones. |
https://forums.eveonline.com/default.aspx?g=posts&m=5295158#post5295158 Apparently this bug is back |
The x and y axis in the graph window only show a range from 0 to 1 since version 1.6.0.
This behavior can be observed on Windows, Linux and Mac.
In 1.5.1, after loading a fit and opening the graph window:
In 1.6.0, after doing exactly the same:
Weapons were loaded and drones selected both times.
Filling in a signature radius doesn't help.
The text was updated successfully, but these errors were encountered: