wowbagger

Autostart works. Under what circumstances were you trying to use it? Got a track file?

It seems you can: They aren't preset loadouts. It works, and they launch, but I wouldn't recommend it, if for no other reason than the CCIP pipper would likely suffer accuracy. I don't know about this though - only guessing.

I tried your track and when I take control it works without issue. Check your control settings for trimmer button and also trimmer - reset. Also make sure you're not in Game Mode, please.

I'm not sure that's accurate. I use the default trimmer mode setting with a non-FFB stick and have no issues.

I find all DCS default views are tilted downwards , which drives me nuts. With every module, I tilt my view up (Numpad8) and save my default snap view in what I find a much more natural position. Here's my screen directly after re-centering TrackIR:

It's not operational yet (though the image is rendered on the reflector glass). But it will eventually be operational and usable by the pilot-operator in the front cockpit for unguided weapons.

For quick & dirty missions - many Ka-50 missions are fun in the Mi-24. I'm flying some of Deployment in the Hind . Also, once the Mi-24 gets added to Liberation, it should be great for easy mission generation.

The only way to get MG pods + ATGM on 5-8 is with a custom loadout, I think. The DCS Hind doesn't support that now, it will mess up the weapons systems, and the real Hind also has such limitations it seems.

Have you got Game Modes activated by any chance?

Glad you got it sorted.

Does it happen with instant action missions, all mission? Can you post a mission too please? There is something strange going on. If I load your trk in the mission editor and fly it from there, there is no problem...

Can you post a trk file please? After you exit a mission there is an option to save the track (trk) file.

Mine behaves the same as BIGNEWY's. Try moving your controllers after the mission loads, but before you click FLY to see if they will synchronize properly. Check controls for doubly bound axes.

Just ask his wife.

Here's mine for comparison. I have all nVidia settings set to default. Maybe there's a clue in here as to where the performance is going in the Hind. Tested with no mods in game directory or Saved Games, yes?

Yes, me too. I find myself feathering the wheel brakes on hover check.

Might be worth posting your options settings to see if the Hind is affected more by a particular setting than other modules are. I was actually quite surprised how well she runs - expecting a much bigger performance hit, given the impressive quality of the model and textures.

Those are some really obscure euphemisms.

The pipper (which isn't really CCIP in ATGM mode) is going to be where Pete is looking with the periscope sight - which should only be, at this point in development, where you told him to look for a target. Pete also isn't infallible - quite the opposite. He will miss, and he will launch beyond max range if you give him launch authority too early.

Well sure, if you 're going to be all risk averse and responsible. Only joking. You're totally right, which is why they were usually flown in groups, running in on the target, one after the other. Agree, much more fun than plinking from behind a tree 8km away.

Overflying, recklessly, through the billows of smoke you just created ... and then seeing green tracers chasing you out of it on the other side? It'll never get old.

Edit: what he of the quicker draw said. Lower range, weaker warhead. Noticeably. It's not fire and forget, the operator has to track the ATGM all the way to the target. I believe it's following a beam similar to the vikhr, but the beam is manually aimed in this case. Doing attack runs with Pete taking out AA threat and then finishing up with rockets and guns is great heaps of fun. Also, because of the simple Petro interface it's pretty easy to bind certain things to VoiceAttack if you use it.

I have it currently bound to a mini-stick, and my curves are almost flat with Y saturation way down. But it also works pretty well with the main X / Y axes of your joystick.

If you pull too hard, too quickly on the collective, the anti torque can't compensate fast enough and she will begin to tip over. You have to be very gentle with the collective on hover ... well always really.