creed

Interesting, nice to know it's not just me. [EDIT-Apples] Thanks, I did see that, and tried it, but that causes the same problem, causing him to tell me that there is no available tasking.

Ah, well, I've found the issue; he insists on me having guided munitions onboard, but the whole point of this mission was for me to be able to use unguided ones in conjunction with the NVGs and the IR pointer. In light of this, does anyone know how to make him let me use unguided munitions? Regards, Charlie

hmm... Thanks for the suggestion; I've moved him to a place where there's a clear line of site now though, and still no joy. Thanks, Charlie

Hello everyone, I've tried putting together my first JTAC mission today, as I wanted to try a simple night scenario, but whilst I can make contact with him, I'm always told that there is no tasking available. I've attached the mission, since it would probably be easiest for you to see what's going on that way, so if anyone would be prepared to take a look at it, that would be very much appreciated. Thanks in advance, Charlie Reed Ps The mission was created in World, 1.2.2 My JTAC Mission.miz

hmm, I just tried getting rid of HDR lighting, it doesn't look as pretty, but it seems to have done the trick. Thanks, Charlie

Hello everyone, I've just updated to from DCS: A-10C 1.1.1.1 to 1.2.2 (and so am now running World), but whilst I was getting a little less than 40 FPS with the settings shown in the attached screen capture at Batumi, this is now more like 20. The settings I'm using are identical in all categories which are the same, and in all new categories, on a low setting. My system specs are as follows; an i5 2500k on a P8P67 running at 3.9 gHz, 8GB of RAM at 1600mHz, a 7200RPM HDD, an Asus GTX460 (stock speed) all running Windows 7 Pro 64 bit. I'd like to ask if this is to be expected with DCS: World, or if this is due to something else, and if so, do you have any suggestions regarding how to fix it. Thanks, Charlie

hmm? I've already done that, any other suggestions? Charlie

Hi John, Thanks for the reply. I certainly didn't see the activation window upon starting up, but that could potentially be the problem. I've installed the latest version (1.2.1) on top of 1.2.0 of both DCS World and A-10C, so perhaps this is causing conflict. Regarding registration, is there a way to get the window to pop up? I should say that DCS A-10C v1.1.1.1 is still installed on my computer, and it works perfectly. Thanks, Charlie

Hello everyone, I have, until this evening, been clinging to the standalone version of DCS: A-10, however, decided to make the switch, and after several hours of downloading, and half an hour of getting my HOTAS Cougar set up just so, I decided to play one of the instant action missions. I went for the medium difficulty (it has been a long day) one, based in the Georgian Foothills, however, upon pressing pause/break to start the mission, my aircraft immediately blows up. My only idea was that perhaps my wingman and I were too close together, and collided. I tried rectifying this in the mission editor, spacing us further apart; this did not help. I would therefore like to ask, can anyone replicate this problem, and is there a known solution? Regards, Charlie