Moonshine

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?