Svend_Dellepude

I think it's an issue with the button animation that causes this. If I release the button too quickly I have the same problem.

Did they fix this? Because it used to be the same way.

My experience is that if you loose the track in TWS or your jammer goes active, the AIM-120 goes ballistic.

Yes in your example the mapkeyR would do the trick. Just use a flag for two of the modes because the last two would be given if the flag is not on. But if I understand it correct then you might end up in a situation where you have the pinky lever in the back (A-G) and need to go in DGF mode Where you have to move to the center and back, which doesn't make much sense since MRM and DGF are override modes anyway. You probably have the boatswitch mapped to something else, but that's where I would place the MRM and DGF modes. Anyway, here is my solution: Declare the two flags: char MRM; char DGF; declare the function: int MRM_mode_ON; int MRM_mode_OFF; int DGF_mode_ON; int DGF_mode_OFF; define the function: MRM_mode_ON = EXEC(" MRM=1; ActKey( KEYON+ PULSE+ DX21);"); MRM_mode_OFF = EXEC(" MRM=0; ActKey( KEYON+ PULSE+ DX25);"); map your keys: MapKey(&Throttle, PSF, EXEC(" if (Joystick[S3]) ActKey( KEYON+ PULSE+ DX22 ); else ActKey( KEYON+ MRM_mode_ON);")); MapKeyR(&Throttle, PSF, EXEC(" if (MRM) ActKey( KEYON+ MRM_mode_OFF ); else ActKey( KEYON+PULSE+ DX27 );")); MapKey(&Joystick, S3, TEMPO( DXxx, 0, 400)); This way you can still use the S3 for a momentary function with a short press and release, but if you hold it, it will work as a modifier. Just wrote the lines for the pinky forward position, you just need to copy and do the same for the pinky back position and define the DGF mode. You can write this as purescript of course, I just never got around to learn it. This is written from memory, so it might not be copy/paste, but I hope you get the idea.

You also have a 5 bar scan. Same issue as this thread.

I think that this line: if("DGF_Mode = 1;" | "MRM_Mode = 1;") should be: if("DGF_Mode == 1;" | "MRM_Mode == 1;") or simply: if("DGF_Mode;" | "MRM_Mode;") But the thing is that you are not using flags. Flags are char and just written like this char flag; you could try renaming the int to: int DGF_Mode; int MRM_Mode; int AA_Mode; int AG_Mode; But normally you use int as this: declare: int some_name; and the define it: some_name = EXEC(" if (flag) ActKey( KEYON+ PULSE+ DX25);"); And then you program some_name directly on your button. MapKey(Joystick, H3U, some_name); On a side note, if you use else if instead of else you can more precisely define the conditions of which you what the event to happen, leaving no other options to trigger the action than the ones you have defined. But you need to rewrite your script a bit. In your case there is no reason to use the AA and AG flags since they will be reset if mrm og dgf are not true, regardless.

When i postes it was a desperate thread that was merged with this one after my post.

I would just like to bring this back to attention. Cheers

?

A short track showing the SAM mode switching to the missile i just fired instead of the target that was locked. SAM tracking own missiles.trk

A small track showing the radar loose an STT target upon exit of SAM mode SAM exit loose lock.trk

A short track of the new SAM mode that switches target on it's own to a target that should be well outside of the scan area. EDIT: Added a second track of the issue showing more severe.@BIGNEWY @NineLine SAM target switch.trkRWS SAM target switch #2.trk

I too find this a bit of a hassle sometimes. Especially the TWS AUTO/MAN option sometimes doesn't change even though the cursor is returned to the dock. If done too fast it changes the azimuth of your scan zone on the way.

Just a thought. Since i didn't mess with this option for years I don't have a clear recollection on how thorough I investigated this back then.

Something comes to mind. @schmiefel Do you have any other controllers assigned to the axis in question? Like button boxes or other peripherals that doesn't have any physical axis? By default DCS assigns axis of any controller to pitch and roll, even if the controller doesn't have any.

Good question. Maybe there is something with the way the axis are programmed in DCS ( not in options but within the programme) or maybe you moved the rudders during loading. Don't actually remember if the latter is possible, I turned SYNC off many years ago after discovering this issue.

You dont both press and go right at the same time. You press and release, and then left or right.

This is the issue, and have been like this for years. The problem is that hall sensors are so precise and don't have much jitter plus a deadzone when centered build into the firmware. Therefor you need to move them before the game will recognise the position. Or turn off ''SYNC'' option.

After pressing undesignate in GACQ the radar mode is carried over to whatever missile mode you transfer to after. GACQ to RWS bug.trk

It's not a new bug, and it doesn't happen all the time.

If you haven't seen it, then here is the roadmap for the Hornet:

Unfortunately not for me.

Might be a pinched cable in the base.

If you cycle the AUTO/MAN OSB on the DDI the radar centers on the target, but if you use the HOTAS undesignate the radar will be offset.