Svend_Dellepude

Unless you use script editor and know what you are doing. :smilewink:

I found out that pressing RESET after being in AUTO doesn't release the elevation axis. You have to cycle MAN/AUTO and be back in MAN to use elevation again.

Modes are not finished yet.

Looks like a Pink Floyd concert! :thumbup:

I did experiment with this some time ago, but gave it up because it was a hassle, took too much focus and didn't give me better results than flying the bird the way it wanted. Maybe you can do it better though. :)

You need to be gentle on the stick in this plane. The slats are not very fast so they need time to extend to create extra lift. If you pull the stick hard and fast, you will bleed a little speed before they have time to extend.

Do a couple of 90° turns at 6 G's before hard maneuvering. That will keep the pilot awake a bit longer.

I read somewhere long ago that the override modes also are used before and after a bomb run the make sure the area is clear. pretty handy for that.

It might mean that the fix didn't reach open beta yet.

Make sure you are assigning in the mode you fly. Sim/game.

Did you confirm your position within 2 minutes of starting alignment?

Just checked. the above described just creates a new center in azimuth (also a bug) but doesn't freeze elevation anymore.

Is this the same one that been around a while? It used to happen if you initiated lock by pressing tdc and then changed to a new missile before lock was achieved. Also happened if you lost lock and changed missile before radar went back to search.

https://www.ebay.co.uk/itm/223909811712 Just this one, strap it to your leg and off you go! :D

Bonusinfo: For most ppl 75Hz is said to be flicker free, but a small percentage need higher refresh rates to have a steady picture. I'm ok with 75Hz, but prefer 85Hz. :)

After each boot. I got so tired of it that i bought a 8 port powered hub with an on/off switch, that i switch on after boot. Works 98% of the time.

roger!

AFAIK a radar needs to see a return more than once before building a track file. That doesn't seem to happen here. In TWS-A tracks seems to be build immediately upon getting a return.

Let windows boot up before plugging in your controllers. That should work 99% of the time.

Here is another one. This time a MiG-21: Just happened today 04-25-2020. *added another track ACM F-16 vs MiG-21 .miz MiG-21 fly backwards.trk MiG-21 fly backwards 2.trk

Funny! I did the same for the F-14 except i used the APU switch.

It works because you now have defined the S3 button to be the modifier. But it will still output the DX command you have assigned to it. The flag thing is a bit more work and not necessarily better. Depends what you want to do. Here is an example: //define flag char shift; MapKey(&Joystick, S3, TEMPO( DX5, EXEC(" shift=1;"), 500)); MapKeyR(&Joystick, S3, EXEC(" shift=0;")); MapKey(&Joystick, TG1, EXEC(" if (shift) ActKey( KEYON+ PULSE+ 'a') else ActKey( KEYON+ PULSE+ 'b'))); Not sure the code is flawless, I need to go to the other pc to check, but i hope you can get the idea.

Like this: MapKey(&Joystick,S3,TEMPO(DX5,0)); But hen you dont get the benefit of the delayed shift function. Another option is to use flags and then control the switched controls with exec commands

Didn't know. What is the default timing then?

You forgot to define timing in the tempo code. MapKey(&Joystick,S3,TEMPO(DX5,DX100, 500)); // for 500 ms