No “Weapon Endgame” messages displayed in the Message Log // Version 1.07.1567

Post bug reports and ask for game support here.

Moderator: MOD_Command

Post Reply
Uzabit
Posts: 156
Joined: Fri Jul 13, 2018 6:03 pm

No “Weapon Endgame” messages displayed in the Message Log // Version 1.07.1567

Post by Uzabit »

Bug Report
Game Version: 1.07.1567

Subject
No “Weapon Endgame” messages displayed in the Message Log

Description
In version 1.07.1567, I am no longer seeing any Weapon Endgame messages in the Message Log. I have verified that all relevant log settings are enabled.

Previously, these messages would appear with details similar to:
02.02.2019 12:52:05 - AIM-120B AMRAAM #33 HIT: Weapon: AIM-120B AMRAAM #33 is attacking Blue #1 (F-15E Strike Eagle) with a base PH of 90%. Blue #1 has nominal agility: 4,5, adjusted for altitude: 2,2. Agility adjusted for proficiency (Novice): 0,66. Aircraft has a weight fraction of 0,75 - Agility adjusted to 0,36. High-deflection impact (no effect on agility). Final agility modifier: -4%. Final PH: 86%. Result: 39 - HIT.
Now, these detailed endgame messages do not appear at all.

Frequency
Always (as of this version)

Steps to Reproduce
  1. Ensure that all Message Log settings (including Weapon Endgame logs) are enabled.
  2. Engage an enemy aircraft or target with a weapon (e.g., AMRAAM).
  3. Check the Message Log after the engagement.
  4. Notice that no endgame messages are displayed.

Attached Files
Exported log file (AALog.txt)
Screenshot showing the Message Log settings
Pre-Engagement Save
Post-Engagement Save

Additional Notes
• This behavior is new to version 1.07.1567.
• In previous versions, these messages appeared normally.

Thank you for looking into this! If you need any additional information or test scenarios, please let me know.
Attachments
Endgame Calculations.zip
(80.86 KiB) Downloaded 10 times
User avatar
blu3s
Posts: 1336
Joined: Fri Jul 08, 2022 9:45 am

Re: No “Weapon Endgame” messages displayed in the Message Log // Version 1.07.1567

Post by blu3s »

Thanks for the report,

This is fixed for the next update
Post Reply

Return to “Tech Support”