[NO BUG] [2.9.11.4686] No steering information in Pave Spike WRCS acquisition and track modes

[Stickler]

First of all, this report is based on the assumption that the developers' intention was to model Pave Spike implementation as it is described in 347 TFW DOW NIP #24. Since there are a few differences between that NIP (from June 1980) and the RL 34-1-1 of 15 April 1979, Change 20, 15 December 1986, or rather since the 34-1-1 is rather terse/unspecific about certain functions, it is entirely possible that the information contained in the NIP was subsequently superseded.

However, since

• the game manual contains quotes from the NIP (compare here and p. 69),
• the manual references details concerning memory mode which are not included in the 34-1-1 but in the NIP,
• the Pave Spike features described in the NIP are "better"/more comprehensive than the features described in the 34-1-1 and
• it is unlikely the Pave Spike implementation was "downgraded" in later F-4Es (or 1980 vs. 1986),

I suppose the above assumption is valid.

That being said, the NIP contains comprehensive information on how the Pave Spike worked, with the following table summarizing the functions relevant for this report:

In the game, the WRCS acquisition and track modes provide neither steering nor DME to a target superimposed with the radar cursors or manually tracked with the TV display, respectively.

Steering and DME will become available only once TGT INSERT is pressed, or in other words, once Memory Mode is entered.

It is noteworthy that pressing the bomb release button in-game either in the front or the rear seat actually causes the TGT INSERT light to illuminate even though the button is not depressed (MASTER ARM must be HOT, nothing happens with MASTER ARM OFF). While the bomb release button is held, the system acts as if it was in Memory Mode in that steering and range to the tracked target are displayed. That fact that pressing the bomb release button causes Memory Mode to be entered in the currently game implementation is strongly supported by the fact that moving the pod to its gimbal limits causes the same illumination of the TGT INSERT light.

I have found no indication in any RL source that pressing the bomb release button would imply a TARGET INSERT or the entering of Memory Mode. This would be rather impractical either since in Memory Mode, inter alia, the laser is shut off.

In the game, when pressing the bomb release button, the laser is NOT shut off.

The are a few issues connected to the above which I could report, but I'd first like to ask for clarification by the devs if the current implementation is a design choice (presumably for simplification), if it reflects an F-4E mod state for which I have no documentation or if we are looking at a bug/bugs.

Edited February 13 by Stickler

[Zabuzard]

First of all, this report is based on the assumption that the developers' intention was to model Pave Spike implementation as it is described in 347 TFW DOW NIP #24. Since there are a few differences between that NIP (from June 1980) and the RL 34-1-1 of 15 April 1979, Change 20, 15 December 1986, or rather since the 34-1-1 is rather terse/unspecific about certain functions, it is entirely possible that the information contained in the NIP was subsequently superseded.
However, since

• the game manual contains quotes from the NIP (compare here and p. 69),
• the manual references details concerning memory mode which are not included in the 34-1-1 but in the NIP,
• the Pave Spike features described in the NIP are "better"/more comprehensive than the features described in the 34-1-1 and
• it is unlikely the Pave Spike implementation was "downgraded" in later F-4Es (or 1980 vs. 1986),

I suppose the above assumption is valid.
That being said, the NIP contains comprehensive information on how the Pave Spike worked, with the following table summarizing the functions relevant for this report:

In the game, the WRCS acquisition and track modes provide neither steering nor DME to a target superimposed with the radar cursors or manually tracked with the TV display, respectively.
Steering and DME will become available only once TGT INSERT is pressed, or in other words, once Memory Mode is entered.
It is noteworthy that pressing the bomb release button in-game either in the front or the rear seat actually causes the TGT INSERT light to illuminate even though the button is not depressed (MASTER ARM must be HOT, nothing happens with MASTER ARM OFF). While the bomb release button is held, the system acts as if it was in Memory Mode in that steering and range to the tracked target are displayed. That fact that pressing the bomb release button causes Memory Mode to be entered in the currently game implementation is strongly supported by the fact that moving the pod to its gimbal limits causes the same illumination of the TGT INSERT light.
I have found no indication in any RL source that pressing the bomb release button would imply a TARGET INSERT or the entering of Memory Mode. This would be rather impractical either since in Memory Mode, inter alia, the laser is shut off.

In the game, when pressing the bomb release, button, the laser is NOT shut off.
The are a few issues connected to the above which I could report, but I'd first like to ask for clarification by the devs if the current implementation is a design choice (presumably for simplification), if it reflects an F-4E mod state for which I have no documentation or if we are looking at a bug/bugs.

Bomb Button causes a TGT INSERT signal to be send. What you are describing is correctly modelled to our knowledge and supported by the electric wiring diagrams of the WRCS and Pave Spike from their corresponding maintenence manuals.
SMEs also confirmed this behavior to be correct.

The logic differentiates a few cases depending on what caused the insert signal, there are certain levels. I can provide details in a few weeks after vacation.

[Stickler]

Zabuzard, the way I read your statement is that the bomb release button causing a TGT insert signal to be sent is correctly modelled according to your research.

That particular fact/issue, however, was a rather minor tangent in my report, which is mainly about the fact that no steering information is available in Pave Spike WRCS acquisition and track modes.

Am I to interpret Silhou's changing the title to "NO BUG" as the developers being of the opinion that the entire logic/behaviour I am describing in my above post is correctly modelled?

If so, how do you explain the apparent contradictions between the 347 TFW DOW NIP #24 I quoted and the game/your sources/SME's input?

If not, which is the correct interpretation of Silhou's changing the title to "NO BUG"?