DTWD

I am reading a book now about the BOB which has mentioned several times about the WW2 tech. I was suprised that IFF was around and before the end of the BOB it was standard kit. I always thought IFF was a product of the 80s, no real reason why I thought that, just did.

Maybe not such a stupid question then :D Thanks for the replies chaps.

Yes tune the axis, I did for my X52 pro just to make it easier to hover...like you I suppose :D

MS have already said they are releasing it for the PC, so why try and get it hacked to work? Just wait. The issue I have is that the dev units were much higher resolution, now they are lower. In there old guise they would be perfect for head tracking...maybe not so much now...unless you can zoom in on your head.

Just build your own, at Alienware prices you could get something rather special. Unless your talking about a laptop? Kilo, that's a bit of a random footer for this forum, and why isn't it the actual Video Lan website?

I am in the middle of hoovering and this just came to me: Do IR missles ever have a tendency to follow/lock onto the sun? Is there some logic programmed into them to not do it, is the sun just not hot enough, are pilots just told it's best not to shoot the sun down, or is there something else? It just randomly popped into my head, things usually do when I am cleaning. Last weeks was "what language do deaf and dumb people think in?". I think it's boredom that fires off these random thoughts. Anyway, IR missles and the sun.

You haven't accidently switched heavy winds on have you? Check the sensitivity settings haven't got altered from default on the control screen. If it has reset it. If it's flat try putting a slight curve on it.

As most have covered: Check laser is on With cannon make sure that big box on the hud is over the target Make sure your in range with all weapons Make sure your weapon station is not empty (ie you haven't jettisonned anything/used it up) If your using programming software is the software allowing the trigger to remain pressed or is it releasing it almost imediatly? Just because it's physically down doesn't mean the software hasn't released it. You can test this out by using notepad and see if the trigger continuely adds spaces or just one (or none). Make sure you don't have any conflicts on your hardware, I went through a phase where something (I can't remember what now) in the cockpit stopped responding to my input, it worked fine for a bit and then stopped. I eventually figured it out, my track IR reset key combo (which wasn't default) was mapped to my Saitek throttle and when activated didn't release (Saitek profile programming fault on my part). This basically left the keys pressed down which stopped the Track IR function working properly and the sim without several keys on the keyboard working (the Track IR software captured the inputs and didn't pass them onto the sim). Some of those keys were also bound to joystick functions which obviosly no longer worked. So in short for the last two, test it out by only using the joystick axis and the keyboard keys and see if things improve.

1) No idea sorry. 2) Basically yes, keep your eyes open, use the shval to look at the areas your intel tells you the enemy may be. I like to do a few things: a) fly high and keep my eyes open for movement (for convoys) b) race around at low altitude (but fast) listening and looking for tracers. When I see something I then make a mental note (or a map reference if I have the time) and then reposition myself for the kill. 3) There is an audible laser lock if I recall. The lights are merely there to tell you which direction that came from. Although you must remember to reset them, otherwise if you get painted from all sides, and then get locked again you don't know from where as all the lights remain illuminated.

Isn't blue detection range? I think red is best case kill range.

Steal one...we won't tell anyone :D

I don't think you could realistically use the avenger near friendly units with the lag involved doing it remotely. Missles or bombs for static/slow moving targets well away from friendlies it will be fine for. Oh and probably no more tree top flying.

Some amazing pics here, rep inbound.

Then I would un-install it, then re-install it after re-downloading it off the website. This may get moved soon as it's in completely the wrong section, so keep an eye out and let us know if it fixes it.

I would say the source is corrupted... like it says. Is it a download version or on disk?

Thanks chaps, I will take a look at the energy saving. I already have Cpu-z (an invaluable tool when overclocking), but I never thought of firing it up during DCS, will give it a go. Cheers.

I had stirling performance in Black Shark (well damn good) pre the latest patch. The patch came along and it took a bit of a nose dive, which I was shocked at due to the new sound engine supposidly taking load off the one core situation. So I made some adjustments using (I forget the guys name, checksix was it?) alpha tweak guide, made a bit of an improvement and I carried on playing. I then went about fiddling with the mission editor and after a few weeks (don't get much time to play) of running through situations with that I noticed a severe slowdown in performance, so severe that it went into a slideshow at times (this is just watching the AI). Well there I was watching the PC boot up (due to boredem and lazyness) and what do I see? Something along the lines of: "CPU 2.40 @ 2.16", what is this I thought? The Q6600 runs at 2.4 not 2.16, which is what I would expect if the mobo had removed the overclocks. It would appear at some point in the recent past part of my overclock had decided to switch back to automatic instead of 400mhz. Lo and behold, a few seconds later it's all back at 3.2GHz and the game's performance has taken a "mysterios" jump! No idea why it happened, every other part of the over clock stayed the same, so it's not like it's wiped out the overclock (it has done that in the past). I was seriosly worried for a10 for a bit, thinking of all the expense I would need to run that new water, but yay PC is now fast again!

Re-install it over the top, or backup your configs (manual copy) and then remove and re-install (and then copy your configs back). Should sort it, and won't use an activation.

Do not buy any ATI (or possibly NV) at the moment. ATI...sorry we should call them AMD now, have a new set of cards out this year, at that point either get one of them or wait for the 5 series to come down in price / flood the second hand market.

Rep inbound for letting the community know.

No I don't think the taxing caused the crash, just my alterations to the waypoints etc caused them to not be close to each other come landing time. However at some point something happened that caused the game to crash. Sadly only have one mission file now, it's the "working version" as I got rid of the rest.

Hahahaha no more crashing, however now I have a problem with the fact they are colliding on the runway again now!

Pretty much what I am doing, however congestion is actually what I am after in this mission :(

Nope, not so far. And this mission has been fine up to now. There are so many aircraft in it though, anything could be happening. I have also found another problem, some of my Su (27s I think), were landing with a broken tail, everytime I ran it. They weren't even in the combat area, they just overfly the airbase and land. Will keep playing. Thanks for the help so far.

Sorry, by tweaking I meant tweaking my mission. So moving AI paths and waypoints, moving aircraft from one airbase to another etc. I am trying to work around this problem: http://forums.eagle.ru/showthread.php?t=58226