Moonshine

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:

doing it manually too normally. but as mentioned initially, all non standard values within the lua will break IC as soon as you get into the cockpit on a MP server literally just did it. ANY change breaks IC. unless you are using default values anyways, might wanna check the contents of your file. also make sure you test it on a MP server that has IC enabled

That seems weird as you can edit the CMS in Combatflite too, then export a lua and replace the default one. Yet it still breaks IC if only a single value is different from the standard one. Tested that by literally manually changing only 1 number and it broke IC

Been using custom CMDS programs so far with no issues, after the recent update now it breaks IC. This happens even when the adjustments are made within the parameters that you can tune when changing the CMDS in the cockpit itself. is there an alternative way to set up CMDS default profiles that use non standard values or do i have to manually adjust the programs every time i start the plane again?

while cycling between the threat tables does work with TMS left, TMS right doesnt seem to do anything. remapping the controls did nothing and using the default keybinds also didnt work out. what am I missing?