Darkwolf187

Easy. Put your Steam client into Offline Mode now, and your game will work forever without needing to talk to Steam servers. Done.

Got it working! You were right, even though I was using Easy Radio, I still need the FM radio tuned in anyway. All works now :)

X52Pro profile linked on my tutorial blog post; http://blog.zencoffee.org/2013/05/dcs-a-10-warthog-tutorial-reference/ That's what I use. TMS/DMS on the POV hat on the stick, ministick for slew. Works well.

We told you so :D Welcome to the fold!

I'd dearly love an AH-64. Personal preference, but I like the USA aircraft more. Still, not going to grumble. These things will make an appearance when they make an appearance. At the moment I'm happy with A-10C and Ka-50, and I'm hanging out for the F/A-18.

I'm using Easy Radio, so I wonder if it's somehow broken for that? I'll try and manually set the radio freqs and see what happens.

... except in real life you're stopping your head moving, with TrackIR you're moving your head the other direction entirely, meaning you wind up half standing in your seat to clearly see the HUD during a tight-G turn. On the up side, it's more immersive with G forces turned on, and I'm learning to fly using my needle gauges in tight turns :D

Generally, yes. Don't quote me on this, but I believe that CCIP solution requires you to be in a dive for it to work properly. CCIP is a calculated IMPACT point, whereas CCRP is a calculated RELEASE point to hit a pre-designated impact point (namely the SPI). Therefore you want to use CCIP when you can get the appropriate aspect to be able to get the impact point on the HUD, and you want to use CCRP when you either want to hit SPI regardless (LGBs) or if you can't/won't put your aircraft into an aspect to bring the impact point onto the HUD. LGBs work well with CCRP since they fly at the lase point anyway (which is usually your SPI) and can therefore correct for any inaccuracy with using CCRP. And after the drop with an LGB you don't want to be doing huge attitude corrections in case you throw the laser off anyway.

Using the same mission, I can't even get JTAC to talk to me! Which JTAC are you talking to, and how did you make it work at all?

Invalid fuzing usually means (for cluster bombs anyway) that you're currently flying below the height of function. That means if you drop it you're already below the point that it was supposed to activate. CCRP is intended to use when you're doing a drop where the drop point would be well below the HUD - eg, a level drop of a LGB, or even dropping MK82AIRs from any kind of altitude. CCIP is for diving drops and also for high speed low altitude level drops.

Note that when you assign it, you'll need to select the Throttle controller, then under Axis assign, move the slider around and it just gets detected. It works fine. Although I often find I have to press 5 on the numeric keypad before it'll start working for some reason.

$40 for a DCS-level aircraft is pretty reasonable. Consider that when you get that aircraft, you don't really get a FULL game (ie, you get limited tutorials, limited campaign, limited story to go with that), but what you do get is a pretty damn accurate and realistic modelling of a real aircraft. Doesn't matter if that aircraft is an A-10C, a Ka-50, or even a Sopwith Camel, you're paying for a realistic modelling of an aircraft. That said, I wouldn't be too cheerful about having to pay $60 or more for a single aircraft. I grizzle about paying that much for a complete standalone game, with multiple classes/roles, video sequences, and written story. $40 is on the top end of "eh, what the heck" territory - that magical price where I'm happy dropping it on a chance, or for something I know up front is going to be limited in scope.

Oh, don't get me wrong, not saying that disabling DEP and messing with userva won't help. Just saying that there may be unintended (and pretty big) consequences, so be aware of it. Matter of fact, setting userva will probably help with DCS since it's pretty RAM hungry. But be careful if you have a lot of RAM, and if you start seeing weird blue screens you're probably running out of system PTE's.

Aha! That'll do it. I can live with the needle gauges still being in metric, it's the hud that really throws me. Thanks for that!

Agreed with above. Aerodynamic braking (ie, keeping the nose high while running along the runway on two wheels) will slow you down much faster than the wheel brakes or just speed brakes alone would. You can then control your position with the normal rudder. Once the nose touches down, just use the nosewheel to keep yourself straight, not necessarily in the center. You can fix things up and get nice and centered once you're going under 25 knots or so.

Makes no difference, they're already set that way :(

Silly question. Does anyone know if it's possible to change the instrumentation (hud and gauge instruments) in the Ka-50 to Imperial (ie, aviation standard) quantities? So, stuff like; Altitude: Feet Distance: Nautical miles Speeds: Knots Weight (aircraft and fuel quantity): Pounds Air pressure: Inches of mercury (inHg) I know those units are pretty crud and in normal life I use metric everywhere, but I'm used to aviation units being as above, and it really throws me hopping into the Ka-50 and everything being metric :)

Be aware, blindly turning off DEP can expose your machine to being compromised via any number of drive-by exploits. DEP serves a useful purpose, it's not just put there to annoy you. Secondly, increasing UserVA may have unintended consequences, particularly if you have a lot of RAM but are forced to use a 32-bit O/S. Go and read about system page table entries (PTE's). Running out of system PTE's will cause blue screens. This problem gets a LOT worse when you adjust the userva setting.

I have this problem too. It tends to make me fishtail all over the runway on landing and takeoff.

Was wondering, does anyone know why they're sky blue on the real jet? I could understand white, since the idea would likely be to let the pilot be able to check the screen for dead/stuck pixels. Is that particular color picked because it's easier for the human eye to spot a dead pixel compared to white or something?

How much fuel has the mission creator loaded you with?

Well, try this. I had a problem where I couldn't zoom in/out at start of mission until I hit numpad5 to center the view and then I could zoom in/out just fine, even when moving my head around with TrackIR. Try that out.

Are you multi-monitor? What happens if you pause TrackIR, press 5 on the numpad to revert to center view, and then zoom in/out with * and / on the keypad?

One thing you will have to get used to is training yourself to keep your head still, or at least within the deadzone "box" so your view doesn't jitter. Having the trackir center hotkey bound somewhere easy to get to is vital, since during gameplay your head's "rest" position will vary.

Yeah, you'll want to adjust the default profile. I don't use TrackIR to zoom in, I just move my head closer to the screen which moves in (not a zoom). Increase the deadzones if you need them. I in particular increased the sensitivity a lot of moving my head DOWN, since that's hard to do. Just play with it so it's comfortable. Note that movement should be amplified! I have to move my head about 45 degrees to do a 180 degree turn. You don't want it much less sensitive than that, since you still need to be eyes forward with your head turned.