=Mac=

In a tail chase, the Tu-55 was jamming its heart out. I was zooming, waiting with 4 AIM-7s for him, and, as I closed to within 20 miles, still no burn through. No burn through at 15 miles. Just at 10 miles, with the strobe still being painted on the screen, I could see the bandit's contact. By this time, I was VISUAL on it. (Had it been 4 AIM-120's, they would have not hit, even at this close!) Previously, in a head on, I had a solid HOJ lock with an AIM-7. I checked F-10 to see I was 25 miles away. Fox one in HOJ. I watched the trail as it headed straight for the bomber. I killed lock to see what would happen. The Sparrow quit the HOJ. ?????? Really? In other news, I was 2 miles away in another tail chase. Fox two tracked straight to a hit. Smoke trailed but the bomber continued. Okay, Fox two, again. It tracked straight to a hit. Smoke trailed twice, now. The bomber continued. I was completely winchester so I decided to follow for a while. Then I gave up. No wonder BVR in an F-15 is useless. Radar that doesn't pick up bandits until closer than 40 miles? Jamming or not. Two sidewinders can't take down a defenseless Tu-55? AIM-7's can't HOJ on their own? AIM-9Ms are better weapons than AIM-120Cs? In real life, the AN/APG-63 radar has an operational range of 60 to 80 nautical miles for a fighter sized target. A Tu-55 will show up beyond 100 nautical miles. And then there's the opposite side of the fence with the ET and a thermal tracking sight. Who needs radar when the thermal sight works better and is completely undetectable. I love the DCS version of the F-15 but I will just fly it for now. Let me know when you get a realistic one. Thanks. :noexpression:

Awesome fun video, EightBall. It's a great way to run up a 12 billion dollar maintenance bill! By the way, I've tried Fraps and (a different one) but I've found that if I let DCS create a video on its own without compression, the replay gets recorded quickly but takes up thousands and millions of terabytes. However, using Handbrake to re-encode it is quite fast, (plus, you can re-encode all the way down to a four pixel semicolon, if you like.) I would imagine it is best done on a fast CPU hooked directly to an SSD. I'm going to look for that small city strip, later tonight! Looks great. Thanks for the video!

I had a .22 calibur pistol that could fire those. :tomato:

Nice write-up. To be sure I understand, to crab is to turn into the wind but keep level. Slip is to point in the direction you are going but tilt into the wind. Do I understand correctly?

I am sorry to inform you, that bombing run was no accident: you either did something or said something to get her fuming at you. What better way to get back at you than to blow you out of the sky! (You didn't fill her plane with 100LL instead of JP4, did you? Ever???) The best you can do now is make her flight lead and beg forgiveness for whatever you did! :smilewink: (By the way, according to the Flight Surgeon, THEY can pull more G's than you can.)

I flew up to the summit of some mountain northeast of Gudauta somewhere around 7,000 feet or so and tried to land on the "rooftop" angles of that mountain. Seems to me the ground effect of the rooftop (inverted V) is left on the left side and right on the right side. Cool as hell but I just can't land on it without crashing. (Not a complaint, though!)

Yup. I flew (MP) cross country from Novo to Sochi along the coast with the doors open as well as closed. I had a constant 100 knots with occasional shivers into the 120 realm, both with the doors open as well as closed. No change except sound. Don't know if that's realistic or not. Have to ask someone who flies the real eggbeaters.

In the HUEY First: Torque. The Huey will want to twist to the right. The left rudder pedal corrects for that below translation speeds. Pulling hard on the collective will increase torque. Correct for it harder. Just like riding a bicycle, once you get the hang of it, you won't even think about it. Second: Hovering. It is very easy as long as you keep a bit of left rudder in to correct for torque. Approaching the hover area at speed, you need to slow down. Tilt tail down (AND collective down!), watch your Vertical Velocity Indicator against an unwanted climb and wait. Soon, you will feel the characteristic shudder, feel a growing twist to the right (add in some left rudder) and hear the rotor go from "whup, whup, whup" to a soft "Fff Fff Fff". (God, I just love it when it does that!) Once you feel you are really slow, begin to get level and watch for drift. Keep in mind that to slow down you tilt against travel and if you un-tilt too soon, you still are traveling. Tilt again. If, on the other hand, you tilt too long, you'll be backing up (or drifting sideways). Tilt the other way to slow that down. Third (same for all helos): VRS means Vortex Ring State. That's the donut of air around your rotors that will drop you out of the sky viciously. Basically, your rotors blow air downwards, your motion is also going downwards, and thus your wind will begin downwards, move outwards and upwards, then your rotors will pull that air back down creating, in effect, a roiling donut of air that provides you with zero lift. If high enough, tilt out of the verticle and pull on the collective. Finally, keep an ear out for your rotor speed. If you pull hard and long on the collective, the Huey's engine won't keep up and your rotor speed will drop with that nasty little alarm going off. Keep an ear out for rotor over-speed, too. It's similar to an auto-rotation maneuver except the engine will be trying to keep up with the rapidly spinning rotor. Hope this helps whoever needs it. Oh, by the way, if you have a clean install of the Huey, a good joystick/throttle/rudder pedal setup and your Huey still acts like a bucking bronco when you try to lift off, it's possible you have an older version of the Huey: update. Or, your joystick and collective are not centered for some reason. I use zero curves on all input devices and the Huey is still a dream to fly. I take off or land anywhere. True, the rough weather at an oil rig tends to be a fight, but that's true with real life helos, as well.

I'm like Justificus: I want to create missions specifically for me. As it stands right now, I have some racing pylons leading a trail around Krasnodar city and fly the streets (!) without rising above 100 feet or leaving the asphalt. (Nor hitting busses or trucks!) Doing Las Vegas in Edge will be a career killer for me: I'll never go back to work!

GPU driver up to date? WINDOWS power scheme set to never turn off the cpu? Just some suggestions.

Migs, be careful, there are Eagles in the sky!

I finally found a few minutes this morning to fly my favorite aircraft: the Huey. It had been a month or so since I flew so when I got in at Lochini and took off, I felt I was flying with an angel. She's such a wonderful thing to fly, now. The sounds, the visuals, the flight dynamics, all of it is my dream machine! Thank you so much BST and ED!

Two GTX 680's in SLI running one 40" at 1920x1080 except the A-10C which I run two 27" for the MFDs plus the 40" for out the window.

Aggression. A mad, kill everything, attitude. THAT'S the mark of a combat ace. Tenacity, desperation, luck, skill, and good equipment. Awesome flight even in spite of the damned warp.

CVN-70 @ 30 knots into 13 m/s (about 25 knots) headwinds. A/C speed, 150 knots. Tire marks on the starboard bow deck edge shows 1/2 inch clearance! (I planned it that close....)

Yeah, I could not get UZI's audio in any I flew. I was tuned to 251 UHF (and could hear fine) and (IIRC) 128 VHF AM.

My apologies. What I intended was to show a bad weather approach by looking out the window. The F-86 has no ILS equipment so, true, this cannot be an ILS approach and landing. My use of Cat III was erroneously used to describe the conditions. Sorry.

It's actually Krasnodar with CYYZ audio. Note the crosswind! Note that I almost couldn't find the runway! [VV]120973095[/VV]

I was flying a Cat III manual approach (no ILS!) on Krasnodar Center. Mild crosswind, light snow, 2200 hrs, temps below freezing. At the threshold, Krasnodar lit the numbers for me. I already had the landing light full extended but there never was a landing light illumination of the runway. Even as I cleared the runway, still no ground illumination. F2 showed that the lights were on and reflecting off the ground, but from the cockpit, everything was dark. Because I was practicing crosswind landings, I ran the mission a few times. Once or twice, I did get the illumination. I don't know why or what was different. I suspect a bug somewhere.

Years ago, I flew in international level inter-squadron A2A competitions. We flew training missions for months. Ninety percent of the time I would lose SA because I could not follow what the heck my flight lead was doing if he was padlocked engaged. I could not see anything. I chalked it up to my monitor being too small, a 22" at the time. Today, I have 27" monitors on either side of a 40" that I sit about 2 feet from. Even with these tremendous aids in visualization, I still can't see other aircraft until they reach out and tap me on my forehead. What I discovered recently was, if F5 is allowed, I can check on relative position of the nearest a/c but, to my great delight, I could actually SEE it. I could see the hard bank continuing a scissors or vapes of a quick high yo-yo. In the cockpit, even though I know where the bandit is relative to me, I still can't see him. The adage, "Lose sight, lose the fight", is blatantly obvious. Like you, I felt labels or F5 were a kind of cheating. But this does bring up the problem you are discussing here. Visualization in DCS, although the best sim for "spot the dot", still isn't even close to reality. That's why I don't like labels (even as dots) because it, too, is not close to reality. I wish there was a study that would show how capable human eyesight at 20/20 is in clear atmosphere. Then the scaling in DCS would more accurately allow for such realism. How that would be done is beyond me. But much desired.

Got it. Yes, very helpful. THank you. Now... can you show me how to fly it? :D Just kidding.

It's going to depend on what feel your joystick is giving you. It seems to me you would want a linear curve but if that curve in your photo is working for you then fine. The idea is to find delicate control near your hover point. The problem with that is your weight changing. I, too, have the HOTAS but my curve is completely linear (curve = 0) and I fly (collectively) very well: smooth control at all times. (Cyclic is another matter but that's due to poor pilot input. :)

This is not a bug, I don't think, but a design issue. Something overlooked? I was flying early in the morning with DCS World shadows extra impressive. I was in the weeds near Sochi and pulled into the shadow of one mountain and noticed that the sun was still shining in the cockpit. When I looked up to see if I could see the sun.... Line of Sight problem overlooked? Should be a simple flag fix, eh? Will this be a problem in EDGE?

Devrim, I have gotten the exact same thing twice on my rig. I think it's a memory leak OR the card(s) are resetting. Both times I had been flying for a couple hours. Edit: I don't overclock my cards. I have two in SLI that are idle even at the highest setting DCS has. Both times, it was a slow slide into green. First a texture went missing, then more textures, then text was blocked out, then most of the cockpit left, then total green.

Wonderful video. Excellent videography. It makes me want to get up off my office chair and go FLY!!!