Ashilta

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

One feature I'd like to see in future and could significantly sway the strategic thinking of each team: When we took Vody, we knew quite quickly that we'd have to put a lot of CAP around Vody and Nalchik to prevent re-takes. Consequently, a number of us piled into all of the F-15s from VZ, SB and elsewhere and flew them up, re-armed and re-fuelled at Beslan or Nalchik and set up TARCAP. What I'd love to see in the future is the ability to 'ferry' aircraft between slots; we know when an aircraft leaves an airfield and arrives somewhere else - is it possible that if I take off from VZ and land at Beslan, the slot moves with it until the aircraft is destroyed?

As the KA-50 pilot who was instrumental in the downfall of Vody, I would be happy to enlighten you :D

I think I speak on behalf of all of us when I say it's been a very long day...

Ahoy team, I've been doing a lot of work in the KA-50 recently, and someone suggested to me that we should try a couple of 'instrument approaches.' Now, as a RW pilot with some experience, I'm satisfied to say that I wouldn't consider flying a non-precision approach without some sort of guidance (a chart/plate for an NDB approach for those familiar with the expression), and so I'm left with the possibility of flying a precision approach. The only type of precision approach modelled in DCS is the ILS, but does the KA-50 support flying an ILS approach, and if so, how is it to be configured? Thanks, Adam

Hmmm... All was going well for me with DCS, but recently something changed and now I'm seeing some odd behaviour... The difficulty is that I started trying to install/configure TouchBuddy the same day I installed new drivers so I'm not sure which caused the problem, however... I have an i7 processor, 8GB RAM and an AMD Radeon R9. Whenever I'm playing DCS, on any graphics setting, I get moments of just... blackouts. The screen that DCS is running on will go entirely black for 2-3 seconds and then go back to as if nothing happened. There is no texture tearing, no graininess, no desynch or anything of that ilk, it simply just goes black. The problem only seems to relate to DCS, as I've just had a bash at EVE Online with everything on 'high' and there was no blacking out. This wasn't a problem for me on Windows 7. Any ideas?! EDIT: So it really, really helps if your DVI cable is plugged in securely.... I've not figured out why only DCS seemed to show the symptoms but this seems to have been the cause!