Mike5560

I only use the throttle on the Hotas X as I have a warthog stick; but here is what I have mapped. Backside: Triangle: Coolie Hat Left Circle: Coolie Hat right X: Coolie Hat Down Square: Coolie Hat Up Front Side Big top button (9): China hat Aft Smaller lower button (10): China hat forward Paddle for rudder The lower buttons I don't use, but could be useful for speedbrakes and such. When I did use both stick and throttle, my stick layout was: Trigger: Gun Button 2: PAC-1 Button 3: Weapon release (pickle) Button 4: Master mode Hat switch: Slew Control, added a keyboard modifier to switch it to trim control and another modifier for TMS control. Obviously it's difficult to have all the controls you want on a HOTAS with this stick. But you have to make some compromises.

Or a bit unaware/ careless. If I lived on land being contested by Daesh, I would want to keep a low profile.

Perhaps, but at what speed though? The Viper becomes hampered below 300 KIAS, IIRC if it can be lured into a slow turning fight. Realistically, if the F-35 were to merge with a 4+ Gen fighter, it's likely to be a Chengdu, Mig or Sukhoi..........at least the latter of the two historically boast impressive low speed maneuverability.

The TISL controls the no longer used Pave Penny pod. It could only detect laser energy and did not have a laser itself..... So I dont see how having a mismatched code would affect your ability to lase through the TGP.

I have tried in both DCS 1.5 and 2.0 to set up a ground laser hosting from a JTAC, but was always unsuccessful to "stage" it. In previous versions, when the JTAC says "laser" in line 7, you will get several comms prompts for the laser calls: Starting from "IP inbound" to "10 seconds", "Laser on", "Spot", and "IN" Now the term "SPOT" is a call from the aircrew to the pilot indicating that he has successfully acquired the laser energy from onboard sensors or weapons. This is not a required call as per the Joint Pub 3-09.3, but the comms sequence may cue simmers to press the LSS button to search for the laser. When a LSS is done (don't know for sure in DCS 2.0 or 1.5) the TGP will find the spot, but will make your current steerpoint as the SPI generator....this will trick you into thinking the countdown timer for a CCRP drop is anchored off of your TGP; it is anchored off of your current steerpoint, which very possibly be near your target, but not on it. Obviously if your bomb's ballistic flight path is too far from your target, the LGB will either not acquire the laser at all or not in time to make an accurate correction.

Ground vehicle scaling is pretty apparent to me; only thing is inside of a few miles distance there's little to no noticeable effect. Place a cluster of vehicles somewhere, fly over them, switch to F2 view and watch them as you fly away.

I had to do the same thing with the update: I was reading the A-10 Red flag mission cards while launching/ updating and the updater did not finish as it was attempting to delete the 3 mission cards I was reading.

Just by eyeballing a comparison, it appears to have more fin control area than a GBU-12, which guide using the front fins. Compared to a GBU-54, it uses the same control fins. GBU-54 was made for and is preferred for moving targets vice a -12. This is one area where Falcon BMS did it better; the INS/JDAMs.....the ability to release at a more realistic weapon footprint, off axis releases, ability to select weapon heading at impact, etc.

I use this as well with a Warthog stick. I dont like twist rudders, but this works half decent once you get used to it. One day I will get actual pedals, but I can fly the Ka-50 pretty well even with the rocker rudders.

I have not found a good reason to select a HOF any higher than 700' for the 97/105s. Any higher, the wind drifts the skeets more off target; it doesnt seem to increase the dispersion.

Or your wingman could've employed off the wrong SPI, i.e. a steerpoint vs TGP.

Or you can Nav to the airfield like the mig-21 uses RSBN.... you can select CDU mode to nav, then divert, pick your destination airfield, and set your HSI heading to correspond with the airfield.

I'm not sure what you mean by your question. The way I understand it, (and this may be completely untrue) is that the AGM-65 is powered by the aircraft when on the rail; the one second delay you mentioned after launch has to do with the internal transition from offboard power to the thermal battery. The battery just doesn't last very long in-flight, and the only reason the aircraft prevents you from launching at too great of a range is to prevent the pilot from wasting a missile. Once the battery runs out, it's running on a memory of the target through inertial guidance. Similar to a HARM missile in flight when the target radar turns off.

I'm a little surprised at the dog fighting capability of this little guy. I've been replaying the dogfight instant action and haven't hit by a bullet yet, so far I can manage 2-3 kills vs Su-27s and Mig-29s before I run out of guns.

Apparently you have to use the mk-82 snakeyes to do CCIP bombing.

Also note that if you perform a laser spot search (LSS), your SPI will be moved to the steerpoint. If for example, you have your TGP as SPI generator and a JTAC lazes a target and you search, your TGP may find the spot..... but you will not be performing a ballistic release on that laser spot unless you make the TGP as SPI, or your current steerpoint is right on the target.

DCS crashes if I perform a cold start. Usually it's 10-15 sec after I fire up the engine. If I start from parking hot, flying or from the runway everything is fine.

After an LGB release, you can turn left 30 degrees (If TGP is mounted on the right wing) engage alt/hdg autopilot and not have to worry about the TGP becoming masked. I've been able to go up to a 50 degree left turn at higher altitudes <13,000ft. That's for self lasing, JTAC terminal guidance or a buddy lase on multiplayer it's different. If you drop, then turn where you please.

http://foxtrotalpha.jalopnik.com/how-to-win-in-a-dogfight-stories-from-a-pilot-who-flew-1682723379 "Accelerating straight up? That's a myth. First off, the old coal-burning Pratt F100-100 proved troublesome. When the throttles were pushed into afterburner you weren't 100% sure if the flame would come out of the back end or the front end. Sometimes, it came out of both ends. I've flown a twin-engine glider, meaning that both engines, while still operating but producing no thrust, as they had stalled. I had maybe 30 hours in the jet at that point. While the Pratt F100-220 in the F-15C is more trouble free, it only produces about 23,500 pounds of thrust. Installed thrust-to-weight is slightly less than 1:1 with eight missiles and no external fuel. If you point the jet straight up and start climbing thrust starts to fall off as the air's density starts to decrease. Weight is not decreasing, as fuel is burned off faster than thrust is decreasing. So stop it everyone – there's no accelerating going straight up in the F-15."

If you forget to change the target waypoint altitude on the mission planner, you can adjust the waypoint's altitude on the CDU. The way I see it, you have several options for acquiring a target and/ or having the TGP on a target that you identify otherwise. Visual spot / TDC: You see a potential target or ground object through the canopy and turn to point your nose at it. Make the HUD SOI, slew the TDC over the target, TMS up long, turn away and China hat fwd long to slave TGP to SPI and boom.... you now have TGP in the area....make any fine adjustments with TGP SOI and TMS up long to make TGP as SPI generator. -Alternatively, you can do this directly with a TGP diamond, as long as it's boresighted and SOI. (ground slewing will be slower than the TDC) Visual spot/ ground reference/ markpoint on TAD: You see a potential ground object through the canopy, then determine if it might correlate with an object or terrain feature on the TAD. Select the TAD as SOI, slew to the target's location and TMS right to create a ground markpoint. From here you can either hook the markpoint and make spi and slew the TGP; or make sure the CDU selector dial is set to "mark", call up the corresponding markpoint and china hat aft long to slew TGP to markpoint. Shoot first, ask questions later: You identify a hostile object and want to shoot at it, but also want the TGP in the area. Roll in and shoot with weapons of choice, egress, make sure CDU selector dial is set to "mark", then select Z-mark (location of last weapons effects) and China hat aft long to the Z mark point. Wingman help: Have your wingman find something, i.e. engage targets of opportunity on single player. Now you have to make the TAD SOI and watch the TAD for blue lines originating from your wingman. At the end of the blue line should lie a small wedding cake (SPI marker). From here, you can slew your TAD cursor and hook (TMS up, then TMS up long) the SPI and China hat fwd long to slew you TGP to your wingman's SPI. Hope that helps, having a HMCS would really help this process :smilewink:

This may be a bug, or maybe I am missing something. In the video options I select "Off" for civilian traffic, as the mission(s) I am building are located within the NTTR ranges......where very few, if any ambient vehicles should be driving. However they are still present.

Well, in this case maybe not 15,000, but right above 14,5k feet. Strela was at 10ft MSL. I had previously did tests on DCS 1.2 or earlier and had similar results. Speed I think plays a factor. edit: the track is from 1.5 open beta Str 10 test.trk

Simple and straightforward OCA mission over Northern NTTR. For F-15C module, if you dont have F-15, just edit and change the F-15 flight at Nellis to whatever you have. OCA trng.miz

I cannot speak for the tor, but I have done tests on DCS 1 with the strela 10 (sa-13) and have repeatedly been hit at 15,000ft AGL (in an A-10C).

The CAOC is a headquarters element, sitting at some base, in a large room with a bunch of computers and TV screens. They manage the taskings of all the air players, and will contact you seemingly at random with information, often target information. The JTAC is a guy on the ground, usually embedded with a front line force, such as armor, mech, infantry of SOF. Usually they won't talk to you unless you check in with them first. Some mission designs may include triggers that prompt them to talk to you and pass you targets without you formally checking in with them. As a general rule I avoid checking in with more than one JTAC at a time. The information gets confusing, and it may not be possible to monitor both frequencies at once. Only bits of advise I can give is to work with only one JTAC at once. If someone else passes you information, have a pen ready to write it down. Since sometimes JTAC or AWACS calls are delayed due to the traffic, one technique is to turn off "Allied flight reports" in the settings. You will miss out on AWACS calls (unless you ask?) and you wont hear things like "Colt 11, passing waypoint 4 at 15000".