Moonshine

agree, i think it has something to do with what is reported in this thread (Target Selection on Pitbull) i do hope to see some imporvements to the AMRAAM in this regard.

sometimes emitters seem to show up as PGM1 right off the bat when turning the HTS on. meanwhile they are nowhere near that location plus it will never update the PGM1 tracked location at all.

the Datalink contact being stuck und the HSD is an issue in RWS, while the contact bugging issue is in TWS. two separate things yet makes using any of the radar modes in A2A way too much work and often enough force you on the back foot during engagements because of that. i really hope this gets fixed. if one radar mode would at least work as intended, we'd have a workaround until properly fixed but like this, it kinda prevents you from taking A2A tasks unless self defense

https://forums.eagle.ru/topic/293289-maverick-standby-after-boresighting/?do=findComment&comment=4895864

The jump to 160nm happens when the contact is jamming (idnicated by the yellow chevrons) other than that there are currently some bugs in terms of lost contacts being stuck on the HSD (when using RWS) and some things wrong with TWS

You can hit esc, go to controls and rescan input devices. No need to restart the game. Also fixes the issue in case trackir suddenly is not recognized by the game (or the other way around)

did some more testing: Interesting enough, when trying to manually bug a contact, it changes the scan azimuth to 2 and the bar scan to 3 (correct), just like it does when a contact is bugged on your radar, however, no launch and steering information shows up for the current weapon and the FCR symbology does not show anything being bugged. that is until you get closer to the target (in my test somewhere around 32-36nm, also close to R Max) and suddenly it either automatically bugs the contact or you can manually promote it with no issues. Track attached TWS Target Promotion issue_Test2.trk

the issue in my previous post seems to still exist in some cases. trackfile attached this goes hand in hand with a bugged target in RWS not being bugged upon switching to TWS TWS Target Promotion issue.trk

why not just wait and actually test it before judging it based off of some video?...

Go to the mission editor, set a radio preset for a specific channel (i.e. Channel 2 -> 307.55) Start the mission, go to comm 1 on the ICP and scroll through the radio preset channels -> channel 2 frequency will be listed as 307.54 dont know whats going on there, works fine with any other number (.56 will stay .56 and so on) edit: happens during cold start. havent tested hot start edit 2: added screenshot of the ME radio setup and Trackfile Radio_presets_off.trk

when bugging a target in RWS and then switching to TWS the bugged contact should remain bugged and launch and steering infromation for your selected weapon will remain, however when not bugged, radar contacts will have to go through the promotion process in TWS

is also reported as far as i know. gotta dig deep into the bug reports to find it, exists for a while now. if anything though, open a new topic instead of putting it in here to not mix topics. makes it hard to track bugs

both bug reports are commented as "reported" and i assume it will be fixed. just sad it might be open until the end of march as it makes the A-A stuff in the viper absolutely terrible for a total duration of almost 2 months.. but id rather have them fix it properly

while that is true with the antenna elevation, there are currently lots of things wrong with contacts disappearing in TWS as well as Datalink in RWS, maybe its an unfortunate mix of both. one can only hope that changes rather soon.

so after reinstalling the module and testing again i found the following: the issue seems to only occur the very first time when trying to bug a contact. if the contact has been bugged using TMS right, then degrading it to a System track again and afterwards promoting it with TMS Up will work. but trying to promote a target manually with TMS up repeatedly from the moment it appears as a brick on the radar, bugging it wont work and the contact disappears completely from the radar until TMS aft is pressed again. see trackfile attached Edit: Issue persists after clean-up and repair, see Test3 attachment TWS Target Promotion issue_Test2.trk TWS Target Promotion issue_Test3.trk

interesting. ill try to reinstall the module and check again. as you can see from the track, the target i want to bug then "disappears" completely, only to reappear as a System Track after pressing TMS aft again. Thanks anyways

When manually promoting a contact in TWS, bugging a contact manually doesn't work. TMS Up promotes the contact through its states: TMS Up (on the contact with the radar cursor) first time -> Search Target to Tracked Target TMS Up (on the contact with the radar cursor) second time -> Tracked Target to System Target then the issue: with TMS Up (on the contact with the radar cursor) again we should be able to "bug" the Target and get Launch and Steering information. yet that doesn't work. also not possible to get into an STT at all. the only thing that will bug a Target is TMS right, which promotes all Contacts to the next state. TWS Target Promotion issue.trk

Whenever a target has been locked in RWS and the lock breaks (intentionally or due to aspect change/terrain masking) the DL contact on the HSD will not update anymore and is stuck on the last position of the contact before lock was lost. only switching to TWS fixes it again. RWS_DL_Contact_Stuck.trk

Seems like you gotta close the MARK page first as you said. Upon opening the MARK page while you were on FCR but no SPI set (so TMS up hasnt been pressed, nothing designated) it returns the FCR to the AGR page. manually selecting the GM mode again and slewing the Radar will work, yet TMS input is ignored as the Mark page is still open. MARK_FCR_TMS_Test.trk

Currently when then changing MARK mode to FCR or TGP the TMS inputs for FCR or TGP don't work at all. so scenario as follows: - Start with AG Master Mode and AG radar on GM - select MARK (7 on ICP) makes HUD SOI -> correct. - now change SOI with DMS to FCR - Change MARK Mode from HUD to FCR - now here you wont be able to use TMS for the FCR still even though you changed MARK from HUD to FCR. is that intended to be like that?

while that is true, currently when then changing MARK mode to FCR or TGP the TMS inputs for FCR or TGP don't work at all. so scenario as follows: - Start with AG Master Mode and AG radar on GM - select MARK (7 on ICP) makes HUD SOI -> correct. - now change SOI with DMS to FCR - Change MARK Mode from HUD to FCR - now here you wont be able to use TMS for the FCR still enven though you changed MARK from HUD to FCR. is that intended to be like that?

cant check tacview as of now, will do when able. fair point then, "usually" it should guide towards the steerpoint if it doesnt find anything. if it didnt you might have a point that it isnt behaving as it should. Unless im missing something and someone can clarify and lecture me on how it should actually work

EOM is still using a waypoint as navigation and on your HARM page you set the desired emitter to launch at. it will guide towards the waypoint and try to find set emitter and destroy it. if it finds nothing at all it will simply impact on the waypoint as it does in the other PRE modes (PB and RUK) as well

Check these threads: