29 April 2022 - Feedback from FN and Response

Owned by Joel Wilson
Last updated: May 04, 2022
4 min read

Feedback from FN

FN Controller Software Release - 29 April 2022

Need verification on Unity side:

MVP-020  Previous sessions are identified when the previous session window is opened, but cannot be opened for review.

Unable to reproduce this. We should verify that Jeff is following this workflow:

  1. Open the Previous Sessions UI

  1. Click the "+" button next to a session in the left pane to move it to the right pane

  1. Click the "Open Selected" button at the bottom right of the screen

MVP-041  Confirmed that files were created, could not open the files to verify the autosave was working correctly.

Unable to reproduce this. We should verify that Jeff is following this workflow:

  1. Open the Previous Sessions UI

  1. Click the "+" button next to a session in the left pane to move it to the right pane

  1. Click the "Open Selected" button at the bottom right of the screen

MVP-016  Unable to verify, Cocking Delay is not a requirement for Jabil, how is this being implemented?

  • Cocking delay is implemented on the application side only, not on the firmware. The application itself will ignore shots that come from the device within a certain time frame of a previous shot. This is configurable in the main application settings under "Cocking Delay" and can be set to 0.1 to 25 seconds

Reported bugs

 

  • Ghost devices still appear in the connection log / connected device window.  i.e. A device that was previously connected by now turned off will occasionally still appear in the connection window.

    • This is resolved in the latest codebase (build not yet provided to FN, but will be provided in the next drop 13 May)

  • Zero shots are being displayed within the training timeline and if training shots have been taken, when a software zero is initiated all previous training shots are still visible.

    • Confirmed as a bug.  Will work into next sprint.

  • Noticed on several occasions the target class was being correctly labeled but the wrong stylized target was being displayed.  i.e.  25M Zero target header displayed (correct) but NATO E-Type was rendered on screen.

    • Confirmed as a bug.  Will work into next sprint.

  • Realtime reticle does not appear to align with shots.

    • This could be due to removal of app-side code that handles software zero / shot trace band aids in anticipation of the device handling software zero. We will need to step through all removed code to see if anything needed to be left in place once we get the Software Zero firmware drop.

  • Trace is jumping to origin pixel (ignore aimpoint data plots that have a target ID class of 0 when rendering the trace)

    • Similar to above.  Will need to be confirmed with new firmware release (H).

 

Additional requested scope 

 

Settings Menu:

  • Remove Display Hit/Miss, legacy feature to Expert that does not apply to Victor.

    • Should be added to change order to be addressed in future sprints.

  • Move Limit Rounds to Device Header (More logical position).

    • Should be added to change order to be addressed in future sprints.

 

Inside Session:

  • Recommend a more visible method to indicate that a shooter is in software zero mode, i.e. A red banner across the top of the display and a sunken button appearance on the zero button.

    • Should be added to change order to be addressed in future sprints.

  • Pausing a session is not functioning, similar recommendation to zeroing that a more noticeable means of identifying a paused session is displayed.

    • Should be added to change order to be addressed in future sprints. Currently the application only supports pausing the playback of a particular shot / trace.

Sprint Review items

 

Not included in demo:

  • MVP_001: Target scale should be working as expected (please test and report feedback if it is not)

  • MVP_003: We are now writing Software Zero values to the device (however the device is not currently handling them due to not having the firmware support from Jabil yet)

  • MVP_011: Oblique processing

  • MVP_014: We are now writing mounting orientation to the device at start of a session

  • MVP_015: Shot rejection angle is now working as expected

  • MVP_016: Implemented cocking delay and added it to application settings

  • MVP_029: H+L metrics are showing up in sessions

  • MVP_040: JSON exports were verified to be in parity with data shown in UI

 

Included in demo:

 

  • MVP_004: Shooters are now prompted to software zero at the start of a session

  • MVP_006: Software zero can be triggered by a shooter

  • MVP_007: Software Zero history can be seen inside of a connected session

  • MVP_008: Software Zero can be triggered on all shooters within a connected session by a coach

  • MVP_008_PREREQUISITE/BLOCKER: Network connected sessions are now fully functional and netcode has been fixed / improved

  • MVP_017: Expose ability to raise trigger sensitivity in app settings

  • MVP_018: Expose ability to lower trigger sensitivity in app settings

  • MVP_020: Parsing/recognition of any device datalog/standalone sessions (.log extension) stored in the ~/Documents/FN/VictoR/Sessions folder in Windows. Transfer is not supported currently. Use WinSCP to transfer manually to the controller app computer

  • MVP_028: Scoring algorithm now uses estimated distance in score calculations

  • MVP_028: Scoring algorithm parameters can be adjusted by editing Assets/shotScoringConfig.json from the main application directory

  • MVP_041: Sessions are now automatically saved after every shot to ~/Documents/FN/VictoR/Sessions/Autosaves and can be loaded for review under Previous Sessions UI