slug88

It's completely up to the mission designer to decide how the completion is determined. in the GOW missions, generally killing more of the enemy increases your score, while losing friendlies decreases it.

Presumably it's 'Project 10'. Project 50 was for the BS.

I don't have this problem, with either LOMAC or BS. W7 RC C2D 3.2Ghz 4gb 8800 GTS 320mb

Black and white.

Around the 20 second mark you can see that he has all 4 AP channels enabled. Furthermore the FD must be disabled, as the associated symbology is not present on the HUD. Flying with the AP, rather than against it, is all a matter of practice. It's not there for you to fight against it, it's there to assist you. Once you've spent sufficient time with it, you will learn to understand how to fly with it, and the maneuvers in this video will seem mundane.

Ok, this clears it up. Your AC generators are not engaged, so you're flying around on battery. When the batteries are dry, systems start shutting off and bad things happen.

It should be pretty easy to tell from the HUD symbology. It's been a while since I watched those videos, but I don't recall see the FD cues.

Lowering the throttle during landing is not standard operating procedure, and in fact I wouldn't be surprised if it was prohibited in real life. Also, lowering the throttle won't really do anything for you that simply lowering the collective wouldn't accomplish, except for severely limiting your ability to react in case sudden maneuvering is required.

Sounds like your AP channels may be shutting off. Check if the AP channel buttons are blinking when this happens. AP shutoff usually happens when you try to engage auto-hover at too low (below ~4m IIRC) RAlt. But there may be other causes as well. Are your electrical generators running?

Well, the "Nav" autopilot is off by default. You have to enabled Route Mode, indicated by green lamp lighting up on the overhead panel, to link the AP to the navigation system. The behavior that you describe (AP to provide Stability Augmentation damping and Attitude holding) is what you get by default, you don't have to change anything to set it that way. Sounds like you may need to dig deeper to understand your control frustrations. Have you watched the Producer's Notes?

Well, my manual doesn't even go up to chapter 11. The final chapter appears to be chapter 9, and there is definitely a chapter 7 right after chapter 6 in my PDF.

Err, no, it does have 6DoF, which is exactly why you no longer zoom with the Track IR. In Lomac, and other similar games, you had 3DoF: 1. rotational vertically (look up and down) 2. rotational horizontally (look left to right) 3. zoom (shift head in and out) In BS, you have 6DoF: 1. rotational vertically (look up and down) 2. rotational horizontally (look left and right) 3. rotational axially (tilt head side to side) 4. displacement horizontally (shift head left and right) 5. displacement vertically (shift head up and down) 6. displacement longitudinally (shift head in and out) As you can see, 'zoom' is not one of the degrees of freedom in a true 6DoF environment. Just like in real life, moving your head forward doesn't allow you to see farther.

Moving your head forward and back with TIR in Black Shark doesn't zoom like it does in LO:FC, instead it actually moves the position of the viewpoint forward and back within the cockpit. In other words, your view doesn't zoom in when you lean closer to the monitor, it just gets bigger because you're closer to it. So, to actually zoom, you need another control. As stated above, the slider on the X52 works brilliantly for this, as do the rotaries.

Yes, another exception is the M6 Linebacker, IIRC. I don't know of any such exceptions for Eastern Bloc hardware, however.

The Ka-50 cannot detect missiles. Hence, there is no such thing as automatic flare release. The 99- setting is a maintenance setting for use by the ground crew. It does not stand for auto counter. Again, there isn't a system that can detect IR missiles in the first place. You may be confused by the LWS, laser warning reciever, which can pick up a ranging/designating laser. In almost all cases, however, there is no lasing associated with IR missile targeting, therefore it would be senseless to link the flare dispenser to the LWS. If you hear the "Under Attack" warning from the LWS, it usually means a tank is ranging you and getting ready to fire its main gun.

Er, just so you know, that update is about a year old...

. I'm using one of them for the throttle, and the other for view zooming.

Odd, I can take out each T80 in that mission with a single Vikhr, even frontally. Note that the tank won't blow up immediately when it's "destroyed", it takes several second for it to brew up. Try waiting a bit after the first Vikhr strike and make sure that it's really taking you more than a single missile.

The 'Shooting Range' mission is what you're looking for.

Sorry for the offtopic, but I just wanted to express how awesome it is to see a post from a developer of my favorite game on the forum for my other favorite game :D.

Are you moving laterally at high speed when you experience this? The fact that the missile indicator is off to the side indicates that that may be the case. If so, the reason the Vikhr isn't tracking is because it loses the guidance beam from your helicopter due to the fast lateral motion.

That's a bug which will be implemented as a feature in the upcoming patch.

Load the "Shooting Range" mission. It's free of enemies, starts you on the ground with a cold cockpit, and there's a target range.

IIRC the AI gets a spotting bonus when you're kicking up dust as well. So it's a concern in single player too!

Err, the campaigns are perfectly compatible with both Vista and W7. The "incompatible" disclaimer that they wrote was intended more as a (imho very poorly worded) warning that memory issues may arise on lower end machines. However, with the affinity tools, performance under Vista and W7 is actually superior to XP. I believe it was even stated that they will change the wording of the disclaimer with the patch. Anyway, I do see this error about 50% of the time I try to launch a mission in W7. Usually, if I try a second or third time, it will load just fine. Considering that it adds about 30 seconds to the load time of each mission, I don't find it to be too big a deal. I'm going through the GOW campaign now and I've learned to live with the error.