Unsolved Logbook Question
-
NOTE: I originally posted this in the wrong section of the forum. My apologies.
This past summer I created a Excel worksheet that I used to track my campaign missions.
Part of what I tracked/charted was my Logbook stats. After several months now, I’ve noticed what appears to be a data display anomaly.
Specifically, the numbers in the ‘Total Score’ and the ‘Last Mis Pts.’ seem to be reversed from what the should be.
I assume that ‘Total Score’ is your cumulative career score, and ‘Last Mis Pts.’ (I assume this means ‘Last Mission Points’) is the points you earned on your most recent mission.
Yet in the Logbook, my ‘Total Score’ always varies a little bit up & down according to how much I accomplished during a mission. In other words, it is NOT cumulative, as ‘Total Score’ would suggest.
But my ‘Last Mis Pts’ ALWAYS increase slowly and steadily, as you would expect if they indicate cumulative points awarded.
Months of tabular logs (and chart lines to back them up) indicate to me that these two numbers are reversed on the display. Any input would be appreciated.
-
Really? Over 2 weeks later and not a single response, hopefully from a dev who is familiar with the logbook code?
-
Same boat. I’ve never understood the mission score aspect. I too have a csv file since 2002 that has been track my logbook. As best I can figure is that score is based on you and the Total Score is based on package/flight performance. Have no clue. Total Score is what rank is based on per the manual.
-
I don’t put too much stock in logbook accuracy other than fun counter of your flight hours etc. It has had some bugs for many years. Thats why I have logbook editor. The “game” aspects like medals and promotions are not very serious thing anyway so no big deal if they are not perfect. I mean seriously, the only time I got AFC I had 6 AA kills and 100+ AG kills (bombers and HARTs). Pretty much arcade stuff. Total Mission Score divided by number of missions flown is used to get Ace Factor . Total score is used for promotions. Medals are given for kills and other things like you must land and I believe entire flight must survive also. I have had spurious deaths logged in my logbook I think when my wingman or some other in my package were killed and I was not killed or even damaged. That can make a big problem getting the Longevity medal.
-
@Icarus I tend to concur. I’ve only kept it so long as for a tally of campaign missions and hours.
-
@SoBad sounds like maybe a UI bug?
we’re in the middle of U4 development and testing, and have an abundance of serious bugs to investigate… it might be a few falcon-weeks before this one makes it to top of the queue.
-
@airtex2019 said in Logbook Question:
@SoBad sounds like maybe a UI bug?
we’re in the middle of U4 development and testing, and have an abundance of serious bugs to investigate… it might be a few falcon-weeks before this one makes it to top of the queue.
With all respect, AirTex, and because you have always been very helpful and responsive, let me just make a point regarding your reply–
Back in the day when I had to work for a living, I did a lot of Project Management. An important fundamental is that if you use the rationale of ‘Larger Issues’ to establish priorities, then the ‘Smaller Issues’ will NEVER get addressed.
I’m as eager for U4 (and 4.38, or course) as anyone, but frankly the logbook has always been in serious need of an overhaul for decades, not just a few falcon-weeks. I just hope that we don’t continue to always push it to the back of the line indefinitely with ‘larger issues’ being the rationale.
Thank you for your dedication to Falcon BMS.
-
@SoBad fair point – and if it’s just a little UI bug it’s probably an easy fix and low risk
was just answering your question why no devs have responded after two weeks
-
@SoBad said in Logbook Question:
Back in the day when I had to work for a living, I did a lot of Project Management. An important fundamental is that if you use the rationale of ‘Larger Issues’ to establish priorities, then the ‘Smaller Issues’ will NEVER get addressed.
I know this problem well (starvation) and I agree with your POV: we need to find BW to fix that. Small problems matter.
Please also understand our POV: as Airtex mentioned, we have lots of bugs to deal with U4. We will see if we can find a coder to deal with this, thanks for the detailed report.
One of the problems with BMS is that most coders want to join the team to create new things, but very few want to fix problems. That is why sometimes we are slow to respond.
-
@Seifer said in Logbook Question:
One of the problems with BMS is that most coders want to join the team to create new things, but very few want to fix problems. That is why sometimes we are slow to respond.
Thanks for your reply. I’m a 35+ years software programmer (Google RAD Software), and I specialized in User Interfaces. Now in retirement, I develop Excel-based personal productivity workbooks as a sideline, but back in the day I created and sold Windows-based software all over the English-speaking world (Google 911CAD for an example). I mention this for two reasons–
-
I would be willing to look at the Logbook code for options and solutions. If nothing else, I could provide pseudo-code that one of your coders could use for reference to address the issue.
-
A much larger Falcon 4.0 issue is the problematic User Interface methodology. Much is non-intuitive, with differing UI approaches in different areas of the 2D screens. I think it would be helpful in the long run to acknowledge that and designate someone as UI coordinator for all UI work done in the future, and that is one of my areas of expertise.
-
-
@SoBad I took a quick look at the code … I can say, TotalScore is clearly designed to go up and down – you lose net points for things like getting shot down, crashing, wingmen getting shot down, collateral damage, friendly-fire (and court martial), etc.
Conversely it does appear the field labeled “Last Mis Pts” only ever has positive score numbers added to it, as you observed. The field name in the data model is “TotalMissionScore” but the true intended semantics aren’t super clear – and it’s definitely not the same number or scale as TotalScore. Tbh it looks more like an internal metric used for awarding medals, during course of a campaign… Will discuss with the team.
-
@airtex2019 said in Logbook Question:
@SoBad I took a quick look at the code … I can say, TotalScore is clearly designed to go up and down – you lose net points for things like getting shot down, crashing, wingmen getting shot down, collateral damage, friendly-fire (and court martial), etc.
Conversely it does appear the field labeled “Last Mis Pts” only ever has positive score numbers added to it, as you observed. The field name in the data model is “TotalMissionScore” but the true intended semantics aren’t super clear – and it’s definitely not the same number or scale as TotalScore. Tbh it looks more like an internal metric used for awarding medals, during course of a campaign… Will discuss with the team.
I know you’re super busy with everything going on, and I appreciate the time you took to look into it.