ajax

In the PVI-800 edit mode, press the NAV/TGT button, the target number (e.g. "1" if this is the first TGT pt.), then enter coordinates.

Once in the PVI, the flight lead .can. send to the rest of the flight via datalink: 1. Enter coords in PVI-800 as a target or nav point. 2. Select new target (or nav) point on PVI-800. (Marker should be flashing on ABRIS.) 3. Select datalink icon, press Send/Mem, reset datalink. 4. Coords are now selectable on the ABRIS and can be sent like any other target.

@Speed I have to agree with you: the "fixes" may be only coincidence. Since my post, I've had the same issue again and none of the so-called "fixes" worked.

Tried the following: 1. Launched single player then switched to multiplayer -- nope. 2. Reinstalled MS redistributable dll -- nope. 3. Deleted {my saved games}\config\network.cfg -- nope. 4. Stopped TrackIR, removed process via TaskManager, restarted TrackIR -- YES!!! It worked!!

CTD happening to me right now. This absolutely stinks!!! I've been out of town for almost week, and I need my DCS fix... NOW!!!!

I've noticed the same thing. However, there are times I can see the lights, barely -- they are very dim.

1. Yes. "E" cycles through the available weapon types and ammo. 2. ?? If it works, it is correct. 3. No, lock and unlock works for other ground vehicles. 4. You can use "+/=" key to lock zoom and "-/_" to lock unzoom. (This is for US keyboards... yours may be different.) Edit: It adds tremendously to the game enjoyment to map these to your joystick.

I thought both methods were unrealistic. That is, both methods were concessions to gameplay for those without FF joysticks.

See this thread: http://forums.eagle.ru/showthread.php?t=90584

I'm sorry, but there is a difference. I can run BS1, BS2, and BS2W one after the other and they do behave differently. In BS1 and BS2 when I pull all the way up on the collective, the warning tones beep. In BS2W they don't.

A friend and I were playing an MP mission ported from BS1 last night, and the same thing (connection interrupted) kept happening. We switched to an ED-supplied World MP mission and the problem went away. I think it has to do with possible "invalid objects" or with the AI assigned tasking (which is totally different now) in the mission.

It seems it takes more collective now and that the lift response is a little slower.

You confirmed what I was thinking: the AI pre-assigned tasking is totally different.

Make sure you have the correct x52 profile loaded before launching the game.

Permanently?

Looks like you had the autohover mode on. As soon as you relaxed your control of the cyclic, the AP tried to maneuver to the position it was last activated.

You're right -- Mozdok does not show up in the ABRIS town search. It is very easy to add, though. Edit /scripts/aircrafts/_common/cockpit/towns.lua by inserting a new line and typing in the correct information for Mozdok: name and coordinates. I do not know if it necessary, but I placed the new line where it should go alphabetically.

@Dooom IE9

@Doom Yes, I had the same problem. I tried again a few days later and everything worked. Go figure.

And: 4 for S8 OFP2 Rockets

The ABRIS ERBL function is probably the easiest way. As you move the cursor, the lat/long coordinates are displayed. Once you have the cursor in the right place, hit INFO then TO. Your route directly to that point will be displayed on the ABRIS.

That could very well be; all my testing so far has been from start at runway. Edit: Still crashes from a cold start.

It seems the key is the position of the ADF radio switch. With the switch off, you can change channels without crashing. With it on, the game crashes if you: a) change the channel or b) switch inner/outer NDB setting. Furthermore, the HSI ADF needle does not work if you manually dial in an NDB frequency and set the ADF switch to on.

Don't know about the second one, but the third is normal. BS2 introduced latitude/longitude lines on the ABRIS. You can disable them from the ABRIS menu options.

RCS = radar cross-section (a measure of radar "visibility") NOE = nap of the earth (type of flying -- close to the earth to lower probability of being detected)