169th_DedCat

I know there is another axis assignment available, but I'd rather not have to reconfigure my HOTAS every time I decide to fly a different jet. Why can't we have a universal axis for the target designators for all jets?

Looks like this is already being discussed. See this thread: http://forum.lockon.ru/showthread.php?t=7520

The problems arise when you set the microstick as a mouse/axis control, and then assign those axis to the TDS slew axis in the configuration. It bothers me too that this works for all aircraft except the A-10 and Su-25 target designators. I just started my own thread about this not knowing what this one was about. It would be a lot easier if all the target designators were controlled by the TDS axis. Asking us to just reassign this axis every time we switch between these aircraft is a ridiculous solution.

Maybe this has been mentioned before... Using the TDS axis assignment only seems to work for the Su-25T target designator and all of the A/A radar capable jets' TDCs. It does not move the target designator on the A-10 or the basic Su-25. It seems kind of odd that it does not.

I think it is pretty clear from Wags's dialogue that PayPal has made things very difficult for ED. I'm sure if ED could continue to offer us PayPal they would, but it appears they are being forced to abandon that option and accelerate their efforts to produce other payment solutions. It's no use whining... I'm sure ED did what they could to fix the PayPal payment method before abandoning it.

I haven't actually tried to produce any missions in 1.1 yet, but I don't see anything wrong with asking this question before hand. So LOMAC 1.1 pushes loadouts to the clients. Does this only prevent client LOPE hacks, or does this actually permit the host to create missions that can specifically restrict what weapons the clients can carry... say if I wanted to create a mission where the Eagle could only carry AIM-7s and AIM-9s. Can his be done, and how does one do it? Would I have to LOPE the server, or would I have to nuke all the default loadouts for that jet on the server in the mission editor? Just wondering what is the easiest and least messy way...

You're absolutely correct, it is a homing signal that is being detected and not a launch signal, but that is really just semantics in this thread. I've yet to see a sim that modeled delayed radar missile homing emissions (after the missile is already en route), but it would be nice to see that one day. Thanks for the clarification on the AMRAAM/Sparrow guidance, etc. I knew the AMRAAMs initial flight couldn't be as dumb as all that.

On that point I think NOT having a lock/launch tone for pre-burn-through HOJ shots would add to the playability of the game. Whether or not they work this way IRL is just speculation, but in the game it would force people to be smart about using their jammers instead of just flicking them on the second they detect enemy radar emissions for fear of being smacked by a silent HOJ shot.

Yes they do, but the way they were modeled in LOMAC 1.01 made them infallible if not omnipotent. They detected a missile launch at any angle, distance, and aspect. Even the TEWS/SPO has angle/aspect limits for detecting radar emissions.

Yay! :) I understand the appeal of these messages... knowing who hit who and what they hit them with, but IMHO they take away too big a chunk of the real world sense of immersion from the game for me. It would be wonderful to have an LUA option allow the host to decide whether or not to include these messages in their games.

It didn't used to do this in 1.02 before the Eagle achieved burn-through. I often tested this when locked by an Eagle at a distance to see if my jammer strobe was being tracked. I'd turn my jammer on, and the lock warning tone would disappear, turn it back off, and the tone would immediately reappear.

That depends on the missile, and a lot of the publicly available logic behind it is highly speculative. My understanding of the current Sparrow and the AMRAAM is that neither use radio controlled guidance for their initial flight phase, but the Adder and the Alamo do. The AMRAAM apparently uses purely inertial guidance for its initial phase, meaning it flies straight and blind to its designated TTA point, then turns on its radar to find the target. The Sparrow apparently employs a number if different guidance methods. Some versions of the Sparrow merely ride the radar beam towards target before reaching specified distance X and attempting an intercept... however the characteristics of the shooter's STT radar emissions apparently have unique properties that are detectable by a smart RWR... perhaps the specific frequencies bombarding the target enhance the scattering properties of the reflected radar beams allowing them to be more easily detected by a missile on an intercept flight path, but that's just my own wild imagination at work. I once had the opportunity to ask a Jane's associate and a Hornet driver why SARH missiles relay a launch warning beyond the STT warning tone to the target's RWR a number of years back. The Jane's associate gave me a response to the effect of what I outlined above, and the Hornet driver just smiled and said he was glad someone else could answer the question for him because he couldn't think of a way to answer without giving away the real reason. The TEWS and SPO are extremely smart devices, and they do a lot of highly classified things besides just detect the direction and strength of radar emissions.

However, according to the manual, if active jamming is discontinued prior to the intercept the missile will lose its track and self-destruct. It is not a bug if the missile tracks a friendly. Missiles will not detect an IFF squawk. It is up to the pilot to IFF.

That should be fixed, yes. :D

In the Russian jets ya... that was due to some crazy claim that the EOS sensor can detect the "characteristic IR signature of a missile launch", but it worked instantly at any distance, any angle, and any aspect. I'm quite glad it is gone.

I know what the manual says, I was asking about in practice. I would imagine if an ARH missile like the AMRAAM or Adder was used the target would receive a missile warning, but if it is a true SARH HOJ capable missile like the Sparrow or Alamo, then no there shouldn't be any launch warning at all for either side. As far as TWS goes, no there shouldn't be any radar missile warning until the AMRAAM reaches its TTA point and switches on its own radar. It seemed to work this way in 1.02, but I haven't had any experience with it in 1.1 yet.

Are the Eagles firing AIM-7s or AIM-120s? What about the Russians, Adders or Alamos? I think the Sparrow is supposed to be the only NATO missile modeled with a true HOJ capability. I remember in Jane's FA18/F15 the Sparrow was the only missile that could HOJ. Maybe the AMRAAM pounds the jammer strobe with its radar once it comes off the rails in an attempt to achieve burn-through before it goes terminal.

Yikes... if that's not a program taking liberties with your system I don't know what is. Why doesn't it just go one step further and disable your ability to open MP3 and ISO/CUE files too?

Whoa... it does what now? Maybe I've missed something, but my CDR and DVD drives still seem to work.

I disagree Nomad. You'd have to keep a mental tally of your kills before and after each engagement using the stats window, and it can be a major distraction to read while in combat, a pop-up message certainly is not.

It depends what circles you fly in I guess. Personally I find these messages a little to Quake-ish for me. I like having to look for the smoke trail to report a hit and the fiery hole in the ground to report a kill... just like the real thing.

Thanks, I had done that. I can't believe I missed a message titled Turn off kill messages? :D Looks like the only way to disable this new feature is to disable chat... that really stinks. :(

I know there was a thread about this in here the other day, and I've spent the last hour unsuccessfully trying to track it down to see if it had any replies. I guess it had a pretty obscure topic title. Is it possible to disable the kill messages in Flaming Cliffs? Part of the fun for me in combat is having to confirm your kills. Being able to fire a missile, then turn your back and blindly wait for the pop-up message doesn't appeal to me.

Wicked... thanks! :cool:

I had heard prior to FC's release that it might be possible to disable the F5 and Ctrl-F5 views by editing a LUA value. So... is it? I'm not an expert at LUA editing, but I had a look through the obvious ones and couldn't find anything relating to the combat a.k.a. F5 views.