Ashilta

Ladies, please. Handbags down. This is about collaboration and having fun together.

I agree, either more time for choppers work to pay off, or the location of deployed units needs to be maintained between restarts. A chopper might fly two hours to put EWR in a good place only for it to disappear an hour later...

Just had a very enjoyable time flying with others defending sochi. Never seen so many flanker in one place! Disappointed to see members of a squadron locked in their own channel...

From the contrast issues you've described, it sounds like the Sim is more limiting than the real beast! As an extension of my original question, is it more typical to pack a rack of (D's or G's) and a second rack of (H's or K's) or is it entirely mission specific? Ash

Cheers, Funk - I guess I just have to play more and find the limitations within the Sim. Forgive the direct question, but are you a driver of the beast or just particularly knowledgeable?

I agree - I wouldn't say it's become mundane but certainly more secular. Despite agreeing a plan at the start of day 1 it was disappointing to see so many individual groups chasing after things; I almost think that perhaps if we'd stuck to the plan the war might be over already, or perhaps that's wishful thinking. An appeal to everyone: this is a simulator, not a game. A massive part of combat strategy is communication and teamwork. I don't think I need to say any more...

I wonder then if I've simply been coming about this wrong... I typically load two racks of K's, force correlate my way through long range missile threats and then rely on a combination of TGP SPI and Slave Mav's to SPI to identify and Maverick any remaining AAA threats. I guess my problem is that I'm expecting to lock on further than I actually can, because of the contrast issue you've suggested. I frequently find that with the K, at ranges of seven or eight miles, I simply can't lock onto a target with Mav. I was wanting to blame the sensor but maybe it's just my expectation!

Folks, I've been picking the 10C up a lot recently and I've found that on occasions, the Maverick is particularly bad at finding targets and so I end up over-using Force Correlate. It struck me that the sensors on each Mav might be different, and so the question is raised: are the 'better' and 'worse' missiles for a given tasking, or are the sensors more-or-less the same? Ashilta

I think last time I saw the map look like this the war was over 36 hours later. Hopefully red can hold out a while...

CRC - In the profile explorer there's a DCS Black Shark interface, and in the properties of that is a 'Black Shark Setup' box with the DCS install path. It says the config is up-to-date; is that correct?

Hey folks, I'm trying to get Helios up and running on my Surface. I've got a screen extension app running, and so Helios is actually running on my desktop, however I seem not to be getting any action through the app. I've used a KA50 profile from the website and followed the read-me, part of which goes through hitting a set-up process in the profile editor which I thought configured the Export.LUA. Following that, I seem to be getting no data out of DCS into the app, and if I hit buttons in the app nothing happens. What am I missing?

BLUFOR wins! :lol:

Easy. Stop being a lonewolf! As Pikey alluded to in the de-brief after round 1, I have made so many friends and acquaintances having worked as part of a wider team following round 1 I don't think I ever need to fly alone again!

My replacement Track Clip Pro just turned up in the post... I suppose I have just over 24 hours to get ready. I'm giddy with excitement!

QG - I tried an in flight alignment and hit EGI under the stick after I'd done so - no change. Funk - There were a number of occasions where I tried to set SPI and a white 'NO SPI' flag came up in the corner of TAD, so I know it was 'unset' and I couldn't reset it. I didn't consider re-loading, but actually this sort of makes sense I think... I suppose I can try to break it again tonight and see what happens.

I was discussing this with someone on Blue last night. When BLUFOR took Vody on day 6 or 7 of the first round, we ferried F-15s up from the south east. Very quickly, chopper after chopper after chopper turned up from the nearby FARP to try to recapture Vody - Greg himself must have lost 15 in the space of about two hours, let alone a full day of fighting!

By thinking in much the same way I do! So here's a question from me; sadly I don't have a track as I'm writing from work, but I think I can remember most of what happened. I set up on the Op BlueFlag server last night, loaded armaments, started APU and ran through my start up. Whilst waiting for my engines to spool, and probably before INS alignment had finished, I went to TAD and tried to create a markpoint over Gudauta. It didn't fail, but took the CDU off of the align page. On takeoff, because I don't have TrackIR I was trying to slew around with the numpad and managed to click a switch. Alarms start going off and I realise I've turned CICU off. I restarted it, and when TAD came back I tried to set the markpoint as SPI - it simply wouldn't set. I tried an airborne re-align of INS, tried creating a new markpoint, damn near everything - I simply couldn't get a SPI set from TAD. I know the shortcut is working, as I could set SPI from TGP and slave my Mavs' to SPI, so the functionality works. I did realise later into the flight that the two switches under my throttle were in the 'off' position, but this made literally no difference. Any ideas?

Team, Do we know if it's possible to drop troops and pick them up again later? I'm scheming some schemes but don't know if this is possible as I'm not a transport pilot! Adam

Hurrah! Very much looking forward to this...

Team, Can I suggest that in the next release of the desktop app, the airport/FARP codes are added to the hover labels?

If I can be of any help with some directed testing (i.e. 'can you test feature x' as opposed to generic flying around, please let me know!

So this is what you get for trying to think of things before your morning coffee! Of course, an A-10 doing 180 knots has the same turn radius as an F-15 doing 180 knots, assuming the same bank angle of course. I'll stop talking now :)

In the visual traffic pattern, yes, but as you've identified, it's nigh on impossible to safely establish onto a localiser at a 90 degree intercept. It's damned hard in a jet that can turn on a dime, let alone in a hog. Consider that your average commercial airliner will be doing something in the region of 180 knots at intercept - you really don't have long to react!

It's worth noting as well that we're not currently in a formal round, just stress testing between rounds, so I would consider this behaviour more tolerable than if we had started round 2.

Your ILS intercept angle is too high. Anything between 15 and 40 degrees is acceptable, with about 30 degrees being normal. Ergo if your inbound course is 295, intercept the localiser between 255 and 335, with the ideal being between 265 and 325.