slug88

If you have TrackIR, why don't you just move your head to the side and look around the stick as you would do in real life?

Do you have ForcefeedbackEnabled=true in your Producer.cfg file? If so, try setting it to false. Also, do you have any force feedback devices connected to your PC?

She should, but in real life she doesn't. Therefore, she won't have it in the sim either.

You need to go to the Axis Tune page to map axes. On the top left of the control mapping screen, there's a drop down menu, and one of the options is Axis Tune written in red.

And I am sure that I could every time :). Check and let me know, if necessary I'll post a track to make sure we're talking about the same thing.

It should be pretty straightforward from the axis tune page? What are you trying to do to make it work?

This is correct. There is no bug. You have to wait for the laser cooldown to reach zero, then you can always launch another pair of Vikhr's. When you don't wait for the cooldown, it will only let you launch 1. Note that you get LA (Launch Authorized) before the cooldown fully completes; presumably this is to allow for a single emergency Vikhr shot.

Oh, my mistake. I thought you were asking about 3rd party maps, as per the title of this thread.

http://forums.eagle.ru/showthread.php?t=57948 As per the links on page 1, Afghanistan http://forums.eagle.ru/showthread.php?t=45658&highlight=afghanistan Manchuria http://forums.eagle.ru/showthread.php?t=50244&highlight=manchuria See above.

Your question was answered on page 1. Multiple new maps are being developed as we speak.

Are you referring to this article? http://www.simhq.com/_air13/air_456a.html (emphasis mine) If so, the surprise is that WH will be able to load multiple maps simultaneously, rather than having to switch between and overwrite them outside of the game with a mod manager. As mentioned several times in this thread, that SDK has been available for quite a long time now, and is currently being used to make at least 2 new maps for BS and FC2.

As Nate implies, this has been available for quite a long time. In fact, IIRC the Nellis terrain started out as a 3rd party mod back in the early days of BS, and it was only when WH development ramped up that it was decided to integrate it into the game. It's been a while, however, so I might be completely wrong about the Nellis thing :). Edit: Also see: http://forums.eagle.ru/showthread.php?t=45658&highlight=afghanistan http://forums.eagle.ru/showthread.php?t=50244&highlight=manchuria

Where in the world did you read that?? In this very thread, Viper admits that the slewing problem IS A BUG. If you're referring to the difficulty of locking the seeker onto smaller targets, then I ask, where in the world did you read that it was done to make it more challenging for A-10 pilots?? You yourself posted a link to a thread in which Wags explains quite clearly that seeker logic was adjusted to better reflect reality, not to "provide a challenge": Just about every one of Viper's posts following the above quoted is asking for evidence of a bug other than the slewing problem. Again, Viper acknowledges the slewing bug, but contests the assertion of a seeker lock bog. I repeat it because it seems that the majority of the people posting in this thread so far have failed to actually comprehended Viper's posts. Someone in the ED loop acknowledge that there is a bug in the first page of this thread! I know you didn't read it the first time, so here it is again: http://forums.eagle.ru/showpost.php?p=962004&postcount=8 Viper's contention in this entire thread has been that yes, there is a slew bug, but no, the difficulty in locking on to AA units at medium-to-long range is not necessarily a bug. He supplied two different tracks showing how he successfully locked on to said targets, and then repeatedly asked for tracks to counter his own. He asked for tracks, not videos, because tracks can be closely analyzed with one's own FC2 installation, and unlike youtube videos are actually useful for debugging purposes. Yet not a single person actually posted a track to counter. Somehow Viper's repeated attempts to make the above points were interpreted as personal attacks and denial. This post in particular is an example of one of the most acute misunderstandings in the entire thread: http://forums.eagle.ru/showpost.php?p=962704&postcount=24 Moa, I urge you to once again read over Viper's posts, and then to revisit the above post. Viper states that your experiences with IR imaging may not be relevant to assessing the effectiveness of the Maverick's seeker head, and you reply: Sorry to be so blunt, but if anyone was taking a piss at that point it was you. Furthermore, you write: Vaguely written bug reports are useless without tracks to analyze. If you had listened, you would've realized that Viper was asking for evidence in the form of tracks, and until presented with such he had no reason to believe there was a bug, based on his own experience with the game's Maverick seeker.

I think this is the most exact info we have: http://forums.eagle.ru/showthread.php?t=56699

BTW, 1.02 is the most current patch, 1.01c is outdated.

Have you installed the latest DCS:BS patch? 1.02, available from this website. BTW, CAT_101st, I think you mean 'heart ache' ;).

http://www.digitalcombatsimulator.com/index.php?end_pos=2452&scr=default&lang=en#p25 Depending on the JTAC location to enemy forces and the time of day, JTAC target designation can be by sending UTM coordinates, laser designation, mortar smoke marker, or IR pointer.

What, you've never heard of billion dollar radios before? :D

It's almost certain that DCS:A-10 will at the very least feature all of the AI units in DCS:Black Shark. This means we'll have all of the AI units from Flaming Cliffs, and more.

IMO the best solution is to combine preemptive flare launching with wingman overwatch. One helo enters the target area to get into standoff range, while another observes in a hover from a couple km back to report on enemy missile launches (and other threats). This can work brilliantly in multiplayer, and allows the forward pilot to concentrate on maneuvering and weapon deployment, while the overwatch can focuse all attention on, well, overwatching. Unfortunately this doesn't work in singleplayer nearly as well as it used to, ever since the wingman AI forgot how to hover in patch 1.01. Nevertheless it can still be done if you put a wingy in the overwatch formation (as opposed to hovering in an overwatch position). The AI is good at calling out missile launches, and you can even use the Cover Me command to tell them to engage the threat.

Good ideas :).

I think he means the Lock On Flaming Cliffs 2 GUI Manual.

If you're running FC2 in XP compatibility mode, that could explain the low framerates. Normally FC2 should run smoother than LOMAC, especially on Vista/W7 systems.

Your intuition is correct; that is indeed how it works. They'll attack just the one target, then reform. I believe they'll attack every ground target in sight, which works out to about a 5-10km radius from their current position. They'll prioritize units that are closest to them. Click my sig pic to go to the thread for the Group Vergeev campaign. This one's 20 missions long and is very professionally made, and it costs $4. There's a free 3 mission demo for it in the thread. Also, I see you've already found the thread for IgorMK's Georgian Havoc :D. That is an excellent free campaign, and is already quite playable and quite polished in the current release, imho no need to wait for v1.1.

You don't really need a v1.00 install to install 1.02. Based on my own experience and on what I've read from a few users on these forums, you can install over any version of 1.01. I've done this twice and haven't experienced any problems whatsoever. I believe the important thing is to make sure you have no mods installed prior to installing the patch. And my theory is that the only reason everyone started saying you need to install over 1.00 is because when 1.01 was released, many people experienced issues because they couldn't follow the simple step of uninstalling all their mods (and undoing all their LUA tweaks and such). Therefore, to make things simpler with this release, they simply told everyone to start from a fresh install. Of course all this is just a theory, but note how when the patch was first released, the patch instructions didn't say anything about incompatibility with 1.01, it was only in the subsequent posts that users began making this recommendation.