Arclight

IR is a bit blurry at the moment, but you can see through the haze on the horizon, right out to max render distance. If you know where to look (targets are at waypoint, for example), you can pick them out with a little luck. Picking out targets at 20nm is easy, again, if you know where to look. ;) Thanks, good to hear. :D

QFT

Might not fit everyones musical taste, but here ya go. :music_whistling:

Usually it's overheating of the memory on the card that causes it to crash, rather than the GPU getting too hot. Long story short: temps are irrelevant. You just want to keep it as cool as possible. If you're suffering instability due to overheating, it's time to upgrade your cooling.

Considering it's one of the fastest, most nimble helicopters in existence, I'd say that's not really accurate. ;)

On the navigation mode select panel. :rolleyes: Just in front of the stick, center-low. ;)

Maybe it will help someone: fixed my issue by disabling the Steam in-game overlay. Noticed this in other games too: overlay and DX11 don't play nice.

Set to altitude/bank hold; switch in down/aft position.

I'm sure that won't stop people from posting yet another thread though. :D

Sound is still WIP I think.

Error appears when you make invalid input for a given function (trying to input letters for slewrate, for example). Just press "clr" on the CDU or front dash input to clear the error message.

Just a remark: after putting a Mav in force correlate, you can just slew it and it will lock. I haven't had any luck using TMS forw short to lock without redesignating SPI first. I either use force correlate with minimum slew rate to fire at range, or slew and let the seeker lock itself at 5-6 nm.

You are buying the finished product, access to beta is just ("just") a pre-order bonus.

Big difference between video and computer graphics. 30fps on PC can still look jerky. Ideally you'll want your games at 40-60fps. Depends on the engine though. Ran Crysis pretty high on a 8800GTS, getting ~25fps. Looked smooth. Same deal with FSX. Most games though, there's a big difference between 25 and 30 or higher.

DCS: Airwolf? I'll take it. :thumbup:

Seconded. Best value for money at the moment. Just make sure you get the 1GB one. Got a Gigabyte one; custom cooler and factory OC for the price of regular one. Moved up from 8800GTS 512, definetly worth it. This one runs as hot under load as the 8800 ran in idle. :D On the matter of quad-core helping; to some extent. DCS really only uses 2 cores effectively, and games in general always place the heaviest load on 1 core and less on the others, so individual core speed is important, rather than number of cores.

Yep, you really want to look at the second number for performance, at least with Nvidia.

Num/ and num* zoom. Rshift+Rctrl and those ^ to move the viewpoint forw/aft. Rshift+Rctrl and numpad numbers to move the viewpoint around (up, down, left, right, where ever).

Just hope they fix it. Had some fun when it worked. :)

You don't have to avoid them all together, just avoid the bugged method. There's 2 other ways to lock a Mav that work just fine.

That's pretty critical. It won't lock if the seeker can't track it. It's more reliable than slewing on target, but still doesn't offer maximum range. Alternatively force correlate lock for H&K let's you lock from any distance, allowing you to fire at the edge of your range. You'll definetly want to use that if you're planning to engage a SAM.

A lock. :P 2 ways to get it: slew the cursor on the target and release. Can be easier to line up with the target, slew the crosshair below it and let it drift onto the target (before it goes to break lock mode, so not too far below it) Or, get an optical Mav (H&K) and use force correlate. With Mav as SOI, use 'boat switch forw' to ake the crosshairs black, and then set boat switch center again. The crosshairs will stay black for a moment but turn white after about a second. Mav is now in force correlate mode. Slew it anywhere on the ground and it will lock there, regardless of what's beneath the cursor. Crosshairs will become solid (no gap in center) to indicate force correlate lock. Second takes some practice and low slew rate to get it on a target, but by far gives you longest range. There is the third way as described, after slaving to SPI: tms forw long, quickly followed by tms forw short, but I don't have any luck with that. Most of the time when it does work, the Mav seems to miss anyway. Given up on that method untill the 'redesignate SPI with Mav' (tms forw long) bug is fixed.

After reading this thread I tried a 'proper' aproach and got the donut right. Was a good landing, if I do say so myself. :) Was even in the middle of the night, though I did do 1 go-around.

I'll see if I can dig up that thread. :thumbup: Not that there are that many games that offer a 64b executable, but seeing any actual gains would be a first for me.

Considering I have failed to grab the performance charts for the A-10A, I was afraid to go below 145kts because I didn't know how far I could push it. Aparently you should land considerably slower. Just an example of why I would indeed appreciate some more instructions/learning material. At the moment it's more trial&error. ;)