Speedywrx

The TGPs are loaded with DTED (digital terrain elevation data)

Close. MEZ = Missile Engagement Zone in this context

Sometimes I like hopping into a jet and starting 'er up from cold and dark. Sometimes I just like designing a mission where the jet is already started up and hot on the ramp. Perhaps there could be an option that when the jet loads already started up that you do not have to align the mavs, but if you're starting up from cold and dark you would have to.

I don't think I can copy/paste from iCUE (Corsair keyboard software) but here is a short representation of it so you get the gist: 1. Press key M 2. Pause execution for 100 ms. 3. Release key M 4. Pause execution for 100 ms. 5. Press key F 6. Pause execution for 100 ms. 7. Release key F 8. Pause execution for 100 ms. 9. Press key J 10. Pause execution for 100 ms. 11. Release key J 12. Pause execution for 100 ms. 13. Press key F 14. Pause execution for 100 ms. 15. Release key F and so on.... then I bound that whole macro to my G6 key on my K95 keyboard so with one press of the G6 key it runs through all that in about 3.5 seconds. I have bound those keys to the different OSB buttons in DCS. My advice is to do your normal set-up flow and take notes on which buttons you press, look up and assign those buttons to a unused key in the DCS settings, then use those keys to program your macro. I found for my system (others may vary) that if I tried to use 50 ms delays it ended up skipping a step every once in a while and would screw up the rest of the macro. I buffered it to 100 ms for that reason.

I made a keyboard macro that sets things up for me like: set AIM-9 to bore, populates MFD pages (SMS, HSD) in A2A mode, centers HSD, locks HSD to radar range, defaults radar to TWS, turns on RWR, arms master arm, laser, tgp... all with one button click and it takes 2 seconds for it to do it's thing. I just assigned OSB buttons to keyboard keys and used those in the macro. Not very technological, but it's what I have to work with.

I noticed an increase in FPS in VR. My specs below. I run my Index at 90 Hz. Before, it typically locks frames at 45 or 30 fps - I'd see it dip into the 20s if action got high. Well now, I can play on the same multiplayer servers with a lot of units/players and be locked at a solid 45 - maybe dip into 30, but not as often. Last night I tried a single player mission I made that only had a few elements and I was actually flying around at 90 fps looking around at the ground. I do highly prioritize smoothness over graphics, so I have a lot of stuff turned down (no shadows, no AA...)

hey man - ammo troops aren't paid enough... *faint sound of IYAAYAS being yelled as they run for cover* :D

Aside from the excellent advice already given concerning the volume knob, an alternate method is to not chaff, don't maneuver, and wait a short moment.

I have tried to map a key assignment to turn the RWR power on. So far I have tried: - RWR Indicator Control POWER Button - Depressed - RWR Indicator Control POWER Button - Depressed/Released - RWR Indicator Control POWER Button - Released None of them seem to be working. Bug? User error? RWR power under a different name? Thanks.

Just thought I'd share an update on this as I could never get the datalink to work in that mission I created. I created that mission under 2.5.6.43453 Open Beta (released 13 Feb). Well, I created from scratch the exact same thing under the new 2.5.6.43872 Open Beta (released 20 Feb) and it works now. I also tried just deleting the AWACS and recreating it from the last open beta, but that didn't work. It would appear you would have to create a new mission from scratch if you did so under the 13 Feb OB version.

Thanks for the responses. I am starting the mission from the ramp hot - aircraft is already on and INS is aligned. I see no red flags, and I verify the LAT LONG from the F10 map. I also ensured the INS was back in NAV mode. I also selected both LAT and LONG and pressed ENT within 2 min of starting. I uploaded the mission I'm using (select the F-16 that starts on the ground). What happens is, I do/verify those steps and I see the E-3 on the link as a green circle. Then I get airborne and after a few minutes, they all drop again. I'm sure it's user error.. but I'm just not sure what I am doing wrong or not doing correctly. HVAA escort.miz

Ok, it appears to be a proximity issue and not a timing issue. If the E-3 starts too far away, the only way to be on the Link and have tracks show on your HSD is to be within 0.4 NM of the E-3. As soon as I get farther away, it drops all links. Track was too large to upload to the forum, so here's a link to the track: https://drive.google.com/file/d/1RQyoDBY34mKplLYEoouYMjqRdJaOijtP/view?usp=sharing

Flying towards the E-3, it first appears on HSD at 160nm (limit of radar) as a white square. After forming up right behind the E-3, it still displayed as a white square on HSD. Then after approx 7 min, he showed up as a green friendly track. Not sure if any of this is helpful or if this is intended behavior. Update: Then I break off formation with the E-3 to engage an enemy, and as soon as I point away everything falls off the Link. I then re-form up behind the E-3 and approx 7 min again, the tracks show back on the Link. I'll upload the track later on when I'm back - have to run out.

Follow up to the follow up: In the first scenario where I take off from parking hot at 325nm away, I fly up close to the AWACS and then after some time (5 minutes?) it starts displaying friendly/enemy tracks. Continuing to test...

Follow up: I tried it with another mission I created (E-3 airborne, F-16 starting from parking hot), and it works without toggling anything. The mission in the first post I was referring to originally started the E-3 about 325 nm away. I take off and even when I'm within 50 miles, I can't get any friendly/enemy tracks.