void68

SA-22 destroys everything that's in the air. I dropped 6x MK82 (pair, 3 RP) and one missile killed all of them at 1500ft distance due to its probably nuclear warhead . Another instant was 2 GBU-38 dropped in short succession at about 4nm with the first acquiring took about 5s for the first GBU38 to get intercepted (with direct hit and no blast damage to the 2nd, no nuclear anymore?) and then the 2nd missile launched immediately upon destruction against the 2nd GBU riding in the first's shadow. GBU38 were sometimes acquired as fast as 2s, sometimes as slow as 5s, sometimes immediately. The missile operator is a very fast guy. Settings was veteran. This thing is completely over the top. edit: it was a NOE attack at 20ft with a 4-6nm popup with 5° release angle in my beloved F-16. Seems she's turning into an old lady...

Thanks for the reply at last. Using another USB mouse with macros just for this action looks like a good idea, however in my case it leads another problem: I am on my USB limit and adding another device adds quite some instability. Having a working ejection handle between my legs feels better than a mouse button.

No, as I have no software between the input button in the cockpit and DCS. DCS recognizes just DeviceA, Button36 and all I can choose from are the states "on" and "off". I really love how the devs ignore this thread again. No statement, nothing. Perhaps I should stop throwing money at them.

Every high contrast signature should work, so hot on a cold environment for IR and bright on a dark environment for TV (and vice versa), be it a vehicle, a building, a tree. As you easily lose focus it's best to look for an isolated entity. You can cheat on this by hitting <active pause> which gives you enough time to hit the ideal range - not in MP though. Yes, BSighting might be a bit tricky as you usually operate above the cloud layer (with no sight on ground structures) and during climb you got enough other tasks to do. While you are in hot you can do BS, as it's not that important . Just do a lock / handoff with the TGP and adjust the Maverick (as it's misaligned) for another lock. When both targets are identical hit "BS" and then just fire / ripple, so the next 1-2 Maves on that rack are aligned now. Just look for an isolated, easy to identify unit you need no TGP for under usual conditions. I'd call that "boresighting on the fly". As long as it's a suspicious dot on enemy ground you need no TGP.

It's not that easy: You always should BS on a distant object due to parallax. If you want to have a match at 8nm, you should BS at 8nm. Do a BS at 1nm and you will have a large displacement at 10nm!

There is a 2 staged zoom in VR. I am using it all the time. However it's not that easy to find, because as usual the command is using some cryptic explanation. When I am home I can dig it out. There 's even an unzoom regarding cockpit position for a wider field of view. Another hint how to improve AAR: don't use rudders once under the tanker, use gentle inputs, anticipate movement and try to narrow your F16 down to correct speeds and position. If you lose connection or can't connect most of the time it's speed related. Don't stay fixed on the tanker's alitutde, like Furiz wrote, but I'd like to add you don't even need your tanker's speed! Once you are in his "sphere" nothing matters anymore, just your position in relation to his. Try flying with eyes focused far, like you are driving in a very narrow lane just between a truck and the guard railing: You notice that if you keep you eyes fixed on closer points like the truck wheels or the railing you tend to PIO. Relax and steer from the corner of your eyes.

Asked a lot of time over 3 years or so... For homepit builders using simple switches a single action for the ejection seat handle is inevitable. Other models like the A-10 or F-4 (don't remember exactly) have the option to keybind it to a single keypress, not triple. Implementation shouldn't consume so much programming time... When?

Well, I have no real additional code here, I did an "execute script file" mist.lua and "execute script" with the code under triggers action. Gruppe (ground unit group to spawn) and Zone (triggerzone) were both defined. I don't quite understand as Isn't that exactly what I wrote and what it should be: mist.respawnInZone('Gruppe','Zone')? Gruppe and Zone are valid. I even put a space at the approbiate places around the comma like in the wiki, no change. Even stranger thing is that after I copied/pasted the different codes from the wiki it suddenly worked - despite they look exactly like my input - the parameters between {} and the nil, 4000 weren't the problem as I deleted them and still the script works. SA2 is the name of both the group and the zone, not the best choice I know, but it was just for testing purpose. Well, I don't know why it does work now and did not before. Thanks for help nontheless.

I used mist.respawnInZone('Gruppe','Zone') and it comes up with with error. What am I doing wrong?

thanks guys, lots of help to prevent future issues

Thanks, I always planned to use the Command Injector but was too lazy. I didn't mention my editing first because I thought that adding a few lines in the .lua (like I did hundreds of times before - and I still wonder what might have gone wrong) could have broken the commands, but not that the devices were put to sort of offline. I will walk through Quaggles' Command Injector then. Still I wonder what will happen if DCS adds some required new code to the default.lua that the backup does not have. That's why I went from just replacing to editing / adding lines to it.

Thanks so far. What helped: After a DCS repair I got my default.lua back and it worked. Before I had copied my individual .lua entries back into the default.lua from the after-update DCS-backuped default.lua like I have to do after each update, these additions enable keybindings for ejection arm lever, pneu/elec elevation and different speed settings for CRS and HDG knobs on the HSI (again thanks to @LeCuvier for helping me with these two years ago). Perhaps something went wrong with the copy+paste, despite I went on with extreme caution and my experience is over two years... when I tried it 2nd time it worked again. DCS doing DCS things... or I had a bad moment. Ah, damn, right... there they are. Thanks for pointing me to them. They are intact I just hadn't noticed them there. I was in real stress as I lost my config 1h before a big MP game. Well, 99% is working again.

I reinstalled the default.lua and at least they respond again. Don't know why, after another edit it still works. Now my default settings like MFDs are empty. They had a default binding before (MFD button #1 on #1 etc) and I didn't save them - as they were installed after joystick / MFD installation. DCS put some default over it, like on the HOTAS switches. They are all gone. How to get the default back?

All controllers are "dark", they lost all keybindings and I can't neither load my profiles nor set new keybindings. They are just "dead". Other models work, it's just the F-16. Did a DCS repair, no change. Did restarts, reboots, the usual stuff. How to get my devices work in the F-16 again.

I can't login and have to play offline - that happened the last 2 weeks occasionally. New is "you have to enter a local password" and it says it does not match (wrong, it's the same) and don't even let me access any module. Can we have an urgent fix? What's going on since last patch? edit: did a DCS-repair, did a reboot, changed my password just to be safe: no change! No login, no access to neither modules (just the standard free ones). edit2: added this to \Windows\System32\drivers\etc\hosts now it works. 185.195.197.4 api.digitalcombatsimulator.com

Thanks to you both. My cockpit is already cramped as I put it onto a motion rig and everything has to be fixed, so no mouse, just a trackball (bolted down to an alu extrusion) on the right. Almost impossible to mount something between my legs neither on the left side (left F-16 console is packed with needed switches). Well, it might be a workaround for others, I just still wonder why no one else wants mouse movement possibility on the HOTAS with all these possibilities. I recall from my memory that mouse emulation by stick was possible even with the old 1. gen Cougar HOTAS in the 2000's. But Quaggles might be a good idea, whereas I don't like to start just another background program for a simple task DCS could solve with a minimum of corrected coding (already need a handful for DCS: rig program, 2x immersive progs for bassshakers, motion compensation, VR prog, joystick progs). Perhaps it even helps with this ridiculous 3xCTL E for ejections...

Ich empfehle Dir weg vom HF-8 hin zum Bassshaker. Den HF-8 hatte ich auch vor meinem Rig zur (bescheidenen) Simulation von Kräften / Beschleunigungen neben der reinen Vibration. Die benötigst Du aber nicht mehr im Motionrig. Ist nett, aber es fehlt wirklich der Wumms. Gerade im Heli ist das Flopflopflop des Shakers unglaublich beeindruckend und verstärkt das leichte Hüpfen des Rigs. Lautsprecher und Verstärker gibts für je 80€, Software für 30€. Buttkicker ist unnötig und überteuert. Die Rennheinis packen sich 4-5 Shaker mit 5.1 ins Gestell...

Danke schön . As I fly in VR I don't need the camera movement to look around. When I switch to any outboard view I can look around in that outer view, but I can't change its position. I can't rotate around an aircraft with any other device than the mouse, I just can look around from that initial position. So with HOTAS idea in mind it's very annoying to get the hand off the stick and grab the mouse when I got enought analoge hats/sticks on my HOTAS. I wonder why none of the devs reply with a solution. What's the idea behind limiting camera movement just to the mouse?

This is a General setting but can as well be found in all individual planes' axis setting, but I just checked for the FW-190 D-9, the F-16, the A-10 and F-4. Increased contrast dramatically for better visual difference what fields are "on" and "off"

Wake turbulunce is no factor when in pre-contact or when on the boom or way ahead below the belly. Curve parameters seem ok. Refueling experiece however varies a lot depending on weight and drag of your aircraft, asymmetric loadout, speed and altitude of the tanker, lighting conditions and pilot's endurance. Sometimes it helps, especilly when CAT I, to deploy the brakes a bit. Just a guess and from my experience as it indeed helps me: Keeping forward / aft stability is more difficult than up / down in my case as going up down can be achieved instantly. You always see an arrow up or down and know where you are or where you have to steer. Forward / aft is just helpful as long as you see a relation to a fixed mark. You really can see the "off" indicators due to the high contrast. It seems the "off" indicators are more important like in this example: you got from aft to front 1 off, 1 lit (with bad contrast), 3 off and you know exactly where you are and where you have to go. In an overall low contrast situation you just see one lit indicator and have to evaluate just by its position where you are.

Let go of all hope, they will never change that. I wait for a change in ejection button behaviour from three needed keypresses to just one keypress (for homepits) for 3 years. Sidenote: I feel very comfortable with the faint morse code while on ILS, helps me relaxing.

First try with level, straight formation flying. Your wingleader should be in autopilot and speed should already be settled. Identical loadout and Fuel Flow declaration can be helpful. Every change in speed, altitude, heading should be gentle and should be declared. That's what the winglead can do. Once you are settled stay with minimum inputs, you can even try with autopilot to keep the same altitude or pitch (yes, that's a sacrilege I know, but that's one axis less to care for). With the Paddle on your HOTAS you can easily adjust the altitude to aim for. Most of the time you have to adjust throttle inputs, a bit forth, a bit back till you find the sweet spot. Brakes help for quick change. Think ahead of your engine, it got quite some latency (other than piston engines). First get rid of your overshooting. Better take some time and learn about closure rates and how they correspond with the screen, i.e. how fast the "target" aircraft grows on your screen. Do you use VR? Headtracking? Keep your eyes somewhat fixed on your lead, but also keep him more in a peripheral view area. Like AAR and when you are dashing your car through a very narrow lane or right next a truck while in a narrow roadwork: If you fix your eyes on the side you will oscillate your inputs. Just look ahead and subconsciously you will steer correctly. Again, short, quick inputs, else it leads to PIO. Try different formations with that more or less stable lead aircraft.

yes, I tried to point that out with "All controller fields in analog axis are greyed out but mouse". Will upload a screenshot later this evening.

Looking for this for years: Camera view nick and ...yaw in General settings: All controller fields in analog axis are greyed out but mouse. Just the mouse got the 2 axis Mouse_X, Mouse_Y (plus zoom on Mouse_Z) active. I want to bind the view axis to my joysticks or throttle analog joysticks. These fields are grey and can't be programmed. Why... and how to change?

Yes, you are correct with your understanding. The SA-11 TR is very capable of performing SR tasks, once the Snow Drift is out, be aware of that. A "silent" TR does not mean it's silent, but can still be very active, just looking into another direction. On the other hand a noisy TR with a tracking or even missile launch warning does not necessarily mean that your aircraft is targeted, it can be as well one of your winmen in the same tracking cone. I might be wrong, but I did notice on/off behaviour of the radars for about half a year. Might be update related or different skill settings (the latter just influence engagement range, I guess).