-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Assets mapping to wrong Stations #27
Comments
Thanks for your bug report. To investigate I would need the asset data from your instance (raw xml from Fuelblock consumption doesn't take into account TCU bonus. It is however
|
Because your tool is so amazing im surely willing to provide you the information you need to fix the bug. Just tell me on what platform you want me to send it to you because i dont want it to share that openly. Btw. can i somehow contact you on a easier way ? GitHub sure is great for bug reports but since your tool isnt that well documented it is quite hard to get into it for new users (besides the installation, it is well documented if you know how2linux). cheers Claas Störtenbecker |
Please send it to my e-mail at pozniak(dot)lukasz(at)gmail(dot)com Thanks! 2016-05-17 16:09 GMT+02:00 ClaasStoertenbecker notifications@github.com:
|
Done |
Have you got my E-Mail? Im just curious because there wasnt any reply. |
I did yes, but been very busy and didnt look into it yet. I'll get back to you as soon as I find the cause Best regards,
|
I checked how lmeve.apiassets is mapped to eve_cit_dbo.staStations and found no problem there. So i think either the API somehow messes up in pulling the right locationID or the eve dump is wrong. The both stations are btw. only 1 digit apart. (60014943 and 60014944). |
Bug confirmed. Fix included in the upcoming patch. |
Fixed in d132dd5 |
Hello,
For me LMEVE is mapping the Assets to a wrong Station. The Assets are fine but located under the wrong Station. Also is SOV calculated in Fuelblockconsumption ?
The text was updated successfully, but these errors were encountered: