Ashilta

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.

Greg, did the server collate any statistics on losses, captures etc?

Hi sobek, I have considered this quite carefully... do I need to request the change somewhere more formal or will this suffice?

Sobek, If you could change it to 'Ashilta' I'd appreciate it. I suspect I have a second account somewhere already :(

You'll note the bit where I said that 75% of us know how to evade it...

Careful... This might expose Squadron tactics that people might not want sharing. There's a reason TacView export is disabled no the server, although I think 75% of us probably know how to evade the block!

BLUFORs best KA-50 pilot can't fly until Monday :(

Ah. Seems REDFOR has capitalised on a lack of organised Blues in the north and retaken Vody!

Can I also suggest that for the next iteration, we keep the RvB squadrons assigned but swap sides, i.e. currently BLUFOR pilots fly Russian and current REDFOR pilots fly Eagles? MUCH FUN!

Another one from me, sorry... I noticed a post earlier that I now can't find again (page 15 or 17?) that in the same 'patch' that night missions were added, slots for attack and transport helicopters were meant to be added when airfields were taken. From our captures of Nalchik and Vody last night, it seems that this isn't happening - a bug, or was the plan changed? Adam

Hullo team! Is it possible that I can change my forum username without re-registering? Thanks, Adam