TWP Unknown button questions

[Guest]

From some tests with BMS and my Helios profile, I’m seeing some sync problems with the TWP Unknown button and the in-cockpit button. When I load up TE 3, the bottom light illuminates in both Helios and in-pit. When I load up TE 13 or TE 14, the top AND bottom light illuminates in Helios but it’s only the bottom light that illuminates in-pit. I’m trying to figure out what causes this sync issue. Pressing the button keeps both lights on in Helios and illuminates both top and bottom lights in-pit, and pressing the button again syncs Helios and in-pit buttons.

What callbacks are tied to this button? Is it just SimRWRSetUnknowns?

What parts of the shared memory would cause the top light to illuminate? Is it just the unknown mode indicator? What about the naval indicator? I’ve noticed that while SimRWRSetUnknown is present as a callback in the Full.key file, the manual makes reference to SimRWRSetNaval (deleted) and there is no callback of that name in the Full.key file.

Thanks in advance for any help!

[Red Dog]

TRN3 (and 1&2) is a block 15
TRN13 & 14 are KF-16 b52

Normally the bottom part of all TWP indicators (except launch) must be ON when the RWR has power.
the top part of the indicator are lighted up according to feature being active or not. Some indicators are mutually exclusive as well (think it’s the PRIO one only, need to check that as i don’t recall by heart)

when i load TRN3 and TRN13, i see no difference in the 3D pits
all bottom indicators on the TWP are lighted (except launch) and the handoff button top part is illuminated as well (that is normal)
there is no difference in the 3D pit here

the sharedmemory is perfectly in sync with what i see in the 3Dpit, on both occasion too
so i can’t reproduce what you’re seeing

by the way, when you want to check sharedmem values without the internal programming of your third party software, you can use the BMSFlightDAta.exe in the tools/sharedmem folder. that states which bits are ON straight in the sharedmem.
using that tool, i can confirm that the UNK value (top part of the unknown TWP button is never lighted up at TRN start. Not for the TRN3, not for the TRN13
so my guess is that you activated the unk function yourself either volontarily or by accident with your helios software or whatever other software

[Guest]

Thanks for that Red Dog! I appreciate the confirmation.

Can I clarify what the SetRWRSetNaval callback is for and if it is still used? I’m thinking that might be the culprit.

[Red Dog]

as far as i remember that callback was deleted
it was a mistake and it’s been replaced by SimRWRSetUnknowns

back before there was some confusion about the UNK and NAVAL behaviour

[Darkman]

See -1 (page 40) and BMS Callback Updates (page 3-11 and 3-14) for more information on the change.

[Guest]

@Red:

as far as i remember that callback was deleted
it was a mistake and it’s been replaced by SimRWRSetUnknowns

back before there was some confusion about the UNK and NAVAL behaviour

I seem to remember UNK and NAVAL were separate, but maybe this was Allied Force? That’s why I’ve put both into that UNKNOWN indicator button. Anyway, I need to look at the sharedmem stuff to double-check. Thanks!

@Darkman:

See -1 (page 40) and BMS Callback Updates (page 3-11 and 3-14) for more information on the change.

The -1 did give very little info but thanks for pointing out the Callback Updates reference!

[Guest]

Aha! It was, indeed, the NAVAL part that was causing my UNKNOWN button to light up. The BMSFlightData.exe program confirms this!

With the removal of the SimRWRSetNaval callback, why is this NAVAL bit still in the sharedmem and why is it active in TE13? Is this something that I should be hoping to integrate into my Helios profile or is this a remnant of “old Falcon” and can be safely ignored?

[Red Dog]

it was removed because there is no NAVAL option in the F-16, only a “U” for unknown
The naval bit before was wrongly implemented with the small boat being a bit by itself. but in the real TWP, the boat is engraved and can’t be lit up.

you can ignore it.
best bet as of why it’s active is because of the destroyer to boresight the mav in the TRN

[Guest]

Thanks RD!