lunaticfringe

Run a DCS Updater repair function and perhaps you will find the protoculture you seek.

They should be treated with regards to the information available concerning their function, signal power, calculated propogation and falloff, honoring LOS in accordance with transmitter capability. Problem is, some modules are far better modeled in these (and other EW) respects than others.

Something to keep in mind regarding GG's remark- there's a caper known in EW circles from ODS where Navy had to run a hundred miles worth of cable across the desert to maintain repeaters for Link signals off of Air Force E-3s to the fleet, because the USAF refused to adjust the southeastern AEW track slightly to keep them in signal strength range. The magic behind these things is far closer to your kid's $10 magician's kit than David Copperfield.

The shift registers installed from the factory PCBs on the Suncom are not compatible with the Warthog, hence the replacement boards Debo was making. Ergo, there's no way to directly go from Suncom to Warthog without a change in PCB.

Your contention is predicated on the idea that the opponent, knowing you're in the area, won't shoot, or even maneuver in accordance with denying you a positional advantage, because he doesn't have an active signal. That's horrible logic. They know you're there. They're either maneuvering to deny, operating in a fashion dependent on a mission requirement, or just plain stupid. Shooting in TWS doesn't keep them stupid, it simply affirms they were if the first round hits.

See attached. Also see PM for other confirmation.

Got the invoice, thanks. One question, though- any reason the weapon selector's top position is "SP/PM" rather than the correct "SP/PH" in the renders?

Cy.ph3r- does Virpil need any further confirmation of TransferWise payment once complete, or will the status on the account be changed once applied to the order?

All due respect, Nine- they've been doing that for at least six months. The F-14Bs track replay has not functioned correctly in test for at least that time, and HB has been engaged with ED to solve that. Given recent events of the third party under-bus 2.5.5 toss, can I suggest a bit less of the instant recrimination, and a bit more unified front between partners? Heatblur has notified ED. ED should make it clear that they're going to work through the issue with their partners, rather than saying said partners need to come to them after a review that many of us know has already taken place.

Look at the date on Cobra's post.

First and foremost- you, your husband, and your family will be in the prayers of mine at this time. I understand the desire to recover some of the cost in the hardware, especially now with costs involved in treatment, and those to come. That said, as a way to disperse with the lot as a whole, I would actually suggest contacting one of the many air museums in the region. Simulator setups are becoming a bit of a thing in such venues, and it would be a way for many people to enjoy the hardware, and a way for his memory to be used to educate others on why he enjoyed it so. Having such a turnkey donation would be a boon for many such institutions. Further, the taxable writedown implications of such a donation are far greater than immediate cash in hand, which may be of use for estate planning. A bit different of an idea than I'm sure you were expecting, but one that may be more fitting.

You don't fly formation looking at an airspeed gauge in anything but 90s flight simulators. You have a fuel flow gauge that does a better consumption calculation because that's its job. As to turn optimization in BFM, if you can't determine your relative state against an opponent based on his rate along the canopy and aircraft buffet, you've got bigger problems.

It's not my opinion; it's the words the OP used- your argument is with him. *shrug*

Do you believe the dev was acting in bad faith, or do you not see the changes going on in the back seat for player functionality and Jester interaction with the controls? Because I've personally seen the TCS work properly, and not work properly. But in the lead up to this update, the people who work both for pay, and for free, may not have focused on changes taking place and how they would interact with this particular individual concern of yours. Relax. Things will work. Things will break. When it's all done, it will all work.

Can anyone explain the usefulness and use of the Computer address panel ? "usefulness *and* use"- OP explicitly said he wanted to know what it does, and how it's used. A single paragraph detailing what it does is the first item in the Computer Address Panel section of HBs manual, and how it is used is the balance of it. Your read was incorrect; hence the fact RTFM is absolutely the correct response. The forum is to help with questions related to using the hardware based on information in the manual- not to supplant it wholesale.

He was absolutely helping you. The functionality of the CAP demands study, not Cliffs Notes. It's not a system that prides itself in shortcuts or cribbed answers. Thus, spending the time to RTFM is absolutely the right suggestion for your question.

Turn off the ECS.

There's a difference between "showing" and "indicating". The gauge can indicate a value less than 80. It does not, however, have gradation to show less than that.

"Please fix these nitpicks of minimal importance before getting the big CTD/Jester/TWS Auto stuff out of the way!" Simmer down, Hoss. They proceed in an orderly fashion. Because the indicator quite literally, and physically, doesn't show less than 80 knots.

Because a Tomcat pilot had 100% throttle resolution spread over (if memory serves) eight inches of travel, while you barely have three. Similarly, you have an inch and a half of stick movement in each direction, whereas the pilot had four. Arguing that you shouldn't need to apply curvature for your controls, when an actual pilot used less than your total physical throw on both the stick and throttle for tanking applications, while it accounted for less than a quarter of the applied output from said controls, is rather amusing. In essence, you're arguing that because his inputs were within half an inch of center, you should be able to do so within less than one eighth. Good luck with that.

As a work around, would replacing in the same track work with a triggered action to turn off the first tanker TACAN, while turning on the beacon at the same time using the same channel on the other?

Elevation adjustment won't help for this with datalink on, because he's still going to see that stuff behind you until it's deactivated. Until Jester knows not to offer up aircraft beyond the AWG-9's potential field of regard, the best thing to do once you know where you're commiting is to make sure he has elevation set for the relative altitude (note intended track altitude [in tens of thousands] number, make sure the volume numbers on the left of the TID repeater are valid for that target. Tell him to turn the datalink off, and then select the target you want to lock. It's a bit unwieldy, but generally speaking you may simply be better off getting comfortable with the azimuth position, and then speeding through the instruction menu based on that, rather than multiple instructions to work around it.

Set throttles up as Slider axes with User Curves. Negative and positive curvature collapse or expand both ends, when what you need is to expand the center- thereby increasing resolution, and therefore control, and minimize the loss of throw on the bottom end. Linear axis settings easily lose 25% of usable range just past idle given the "flat" power curve of turbines in that region. Get rid of the symmetry and increase the usable range. Stuck hand syndrome and power over/undershoots go away. As for TIR, add a dead zone, a precise mode command on your controller, as well as a pause. Put your sight line where you want it, freeze it by keeping your head reasonably still, or using pause to keep it locked.

A negative relative azimuth value is to the left of your nose, positive is right. Anything in excess of +/-60 won't lock because of gimbal limits. This occurs when datalink is on because hes fixated on relative range rather than angle he can attain a lock in.

Sounds like shaders need deleted or a water detail lowered (flicker).