Recluse

A long time ago, I recall seeing pictures maybe in Aviation Week and Space Technology magazine...(i don't think it is video) of early Hellfire tests against a concrete bunker. My recollection was that the missile penetrated one wall and the high velocity molten copper jet blew out the far wall as well.

(As an aside) Do yourself a favor and pick up the FREE Community A-4 Mod! Tons of fun and challenging Carrier Ops. Steam gauges and weapons delivery take some getting used to but it is really a nice mod rivaling any of the Paid DCS modules. Really makes you appreciate not only how far technology has come but how skilled those pilots were without all the computerized assistance! If you fly in VR at all, it is even more impressive!

Well, it fulfills the role of the missing TMS switch for me. I flew with a Cougar for many many years, now I have the WinWing Orion F/A-18 stick and Throttle as I mainly fly the -18 and Harrier for which it works well. When I periodically go to re-learn the A-10C I have to program a lot of stuff in odd places to make up for the differences between the Warthog HOTAS and the -18. It was similarly difficult with the Cougar, but at least the STICK portion could be mapped 1:1 with the Warthog.

Hmmm... MODE (PP/TOO) yes, but honestly, I have always boxed the J8x on the Stores Page, set the release type and Efuz and it seems to apply to all stations without further setting. Seems to be the case whenever there are multiple stations with the same type of weapon, Release type and Fuzing apply to all when set.

I think you can turn it on or off in the MISC tab: (Battle Damage Assessment).. not 100% sure it is the same BDA window that you are talking about which indeed can be set in the Mission Editor per mission. nullYou should also be able to HOTKEY it based on the settings in the UI LAYER: null

YES One JDAM per station: Program 2 stations for PP and enter the coordinates on PP1 for each station Program 2 Stations for TOO and with one of those Stations Selected, feed the coordinates to it with TPOD/WPDSG/HUD etc.. STEP and repeat for the other TOO station 2 JDAM per station: Set one station for PP and program the Coordinates for PP1 and PP2 Set one station for TOO and with the station and TOO1 or TOO2 selected, feed the coordinates to them when they are respectively selected. In both scenarios, when you drop, you need to be VERY CAREFUL about which Station (and -1 or -2 coordinate) you have selected when you drop. I don't recall the logic by which DCS willl step through the stations upon each release, except it is always different than I expect it to be

I agree with the other posters about re-designating, BUT also: Have you actually: - Set the correct laser code on the bomb(s) AND on the LTD/R of the Targeting Pod? - turned on the LTD/R (L-ARM should appear in the HUD) before dropping and verified the Laser is firing after release? You should see a countdown to LASER in the HUD followed by a Time to Impact. If you ONLY see a TIME TO IMPACT then the laser is not set up. Even if your original target waypoint is a LITTLE BIT off, but it is close enough, the bomb should still pick up and follow the laser spot and the targetting pod will fire the laser where it is pointing not at the original designated point. You might be dropping the GBU as a DUMB bomb, and the AUTO release cue of the original point is close enough to get it to the originally designated target as a dumb bomb.

Note that, in my case, I have gotten the ABORT ABORT ABORT! even when doing the SPOT-->IN calls. It may have been due to the JTAC losing sight of the target, but I have had it happen in cases where both JTAC and Targets were stationary.

I have had the same issue with a Mission Editor enabled Ground based JTAC (intermittently). I switched to CTLD for my JTAC/AFAC needs. Not as much immersion as there are no comms (I don't use SRS) but it works well (maybe too PERFECTLY, but I can live with that )

Thanks! That is a good suggestion, but I do not have the SYNC Controls checked in my options, and this only happens intermittently. I DO have an axis mapped to the Throttle for use in COLD STARTS, so I guess it is possible, that occasionally there is a "wiggle" or some spurious input that knocks the throttle out of FLY mode. When I re-watched the Track, the throttle lever was indeed bottomed out. Thanks for the insight!

Starting here vs. posting as a bug just in case. As in the title, every so often upon Spawning in initially or sometimes after landing, I will get this failure: Random system failures are OFF in the Mission. This screenshot is from a HOT START on the TARAWA on Caucasus map but it has happened to me from airbases in SYRIA as well. Anyone seen this? Happens upon spawning in. (SINGLE PLAYER). I haven't even touched anything. null Tarawafailure.trk

Bump? Anything? Just verified it still happens with latest Open Beta.

Thanks Rob! Appreciate the info! I see you provided it on that thread I referenced as well I have never noticed any Safety/Arming delay. The point of CCIP is to PUT THE THING ON THE THING and PICKLE. Even in AUTO, the delay is due to the computer waiting for the calculated release point. If you happened to hit the PICKLE at the instant the Release Cue crossed the Velocity Vector, it would release instantly as well.

Apologies for a potential FAQ, but I couldn't find much in a search or in the Manual or Chuck's Guide relating to this other than this one post - Can someone refresh my memory on the AIMPOINT logic for multiple dumb bomb drops in CCIP/AUTO deliveries. I believe I remember reading that it was different depending on whether an ODD or EVEN number of bombs was dropped. (But maybe that was in the Harrier forum section) My recollection (and the statement in the linked post) was that with an ODD Number of bombs, the AImpoint (CCIP or AUTO?) was the CENTER of the drop, so, if you dropped 5 bombs, the AImpoint was going to be the 3rd BOMB target and two bombs would fall before and after based on the interval, so if 100 foot spacing, BOMB 1 is 200 feet before the target, BOMB 2 is 100 feet before the Target, Bomb 3 is on Target, Bomb 4 is 100 feet beyond, Bomb 2 is 200 feet beyond. I thought that for EVEN number of drops, Bomb 1 was on the Target point, and the next ones were all spaced after the target. I may have gotten this hopelessly reversed. Can someone clarify the Aimpoint logic for me? (Point of AIM vs. Centroid of mulitple release) - Different with ODD or Even? - Different CCIP vs AUTO? Thanks in advance!!

Unfortunately, without one of the available MODS (which I have not yet tried) the NVG's don't work in VR. That is, they work well to see your environment as EVERYTHING is shown in the NVG Green, but that renders the cockpit displays unreadable as there is no "Peeking Under" the circular NVG FOV.

This was reported here: But I haven't seen it in this Bug Report Forum. To Reproduce: Put an Apache on any carrier. Unlock the Tail Wheel. Note the Error in the EUFD and MFD "UTIL HYD LEVEL LOW" Does not happen on a Land Base. Some Anti-Skid setting I am missing? See attached TRKs for reproducing on STENNIS, LINCOLN, FORRESTAL, TARAWA and working fine on the Batumi runway ABEFluid.trk BatumiFluid.trk TarawaFluid.trk StennFluid.trk ForrFluid.trk

I just had this exact thing happen to me!!! I was patting myself on the back for a really smooth landing on the Tarawa and as soon as I unlocked the tail wheel to park I got this warning as well. I have really abused the tail wheel lock/unlock on Land Bases and never had this happen

Thanks, but the post of mine that you quoted was made Jun 9th after the previous patch where all it said was: My question was WHAT changed in the Central Position Trimmer Mode Implementation. Probably doesn't matter as it didn't really change anything about the way I was flying and trimming

Yes. If Force Feedback is checked, none of the TRIM options actually work. When I had that happen, I didn't see the other behavior described, though. When I enter the cockpit, my cyclic and rudders are a bit off, so I have to do a quick wiggle to recenter them. My collective stays reasonable stable, though when I first touch the collective, I get a little jump and ROTOR RPM HIGH warning, but it doesn't cause any drastic change in the helo attitude. Also, I usually leave my collective (just regular throttle) fully "down" but at the MIL power detent vs. through the AB detent, so I do start off around 29% or so, which isn't quite enough to cause bad things to happen, but I probably should "zero" it out through the AB detent.

All others are answered above. This one caused me some initial confusion: The TADS is below the visible part of the nose from the crew compartment and shielded within a housing. You cannot see it move from the Pilot or CP/G seat but it DOES move with the crew member's head when TADS is selected (either as the TADS as sight slaved to the GHS as ACQ or as the Night Vision source for the Pilot/Gunner) OR when the TADS is moved manually. The PNVS, on the other hand, is mounted ABOVE the TADS and you can very clearly see that moving with your head from the Pilot's Seat when PNVS is selected as the night vision source.

The Throttle affects the SPEED of rotation of the blades. (Though rotor RPM is affected by TORQUE (the resistance on the spinning blades)) The Collective affects the Angle of Attack (pitch) of the rotor blades. In the Apache, you set the THROTTLE to FLY and leave it there. I am sure that in other, less sophisticated helos you ALSO have to manipulate the throttle to maintain Rotor RPM when countered by resistance and torque) Lift is generated by the pitch of the rotor blades. Think of the rotor blades as WINGS (hence the term ROTARY WING aircraft) that generate lift by spinning vs. being propelled through the air by a propeller or jet engine on a "FIXED WING" aircraft. Also, I have to opine that Comanche 3 was NOT a good simulation of helicopter flight, though, possibly the RAH-66 was designed to fly differently from a standard Helo via computer wizardry. All I know is when I went from Janes Longbow/EECH and any other attempt at a realistic helicopter simulation to try Comanche, I was perplexed by the flight model where the collective/throttle was more like an elevator control that went up and down. Forget everything you learned from Comanche 3.

Decided to quote WIKIPEDIA instead of my interpretation which would no doubt be flagged by people who actually KNOW something Cyclic The cyclic control, commonly called the cyclic stick or just cyclic, is similar in appearance on most helicopters to a control stick from a conventional aircraft. The cyclic stick commonly rises up from beneath the front of each pilot's seat. The Robinson R22 has a "teetering" cyclic design connected to a central column located between the two seats. Helicopters with fly-by-wire systems allow a cyclic-style controller to be mounted to the side of the pilot seat. The cyclic is used to control the main rotor in order to change the helicopter's direction of movement. In a hover, the cyclic controls the movement of the helicopter forward, back, and laterally. During forward flight, the cyclic control inputs cause flight path changes similar to fixed-wing aircraft flight; left or right inputs cause the helicopter to roll into a turn in the desired direction, and forward and back inputs change the pitch attitude of the helicopter resulting in altitude changes (climbing or descending flight). The control is called the cyclic because it changes the mechanical pitch angle or feathering angle of each main rotor blade independently, depending on its position in the cycle. The pitch is changed so that each blade will have the same angle of incidence as it passes the same point in the cycle, changing the lift generated by the blade at that point and causing each blade to change its angle of incidence, that is, to rotate slightly along its long axis, in sequence as it passes the same point. If that point is dead ahead, the blade pitch increases briefly in that direction. Thus, If the pilot pushes the cyclic forward, the rotor disk tilts forward, and the helicopter is drawn straight ahead. If the pilot pushes the cyclic to the right, the rotor disk tilts to the right. Any rotor system has a delay between the point in rotation where the controls introduce a change in pitch and the point where the desired change in the rotor blade's flight occurs. This difference is caused by phase lag, often confused with gyroscopic precession. A rotor is an oscillatory system that obeys the laws that govern vibration—which, depending on the rotor system, may resemble the behaviour of a gyroscope. Collective The collective pitch control, or collective lever, is normally located on the left side of the pilot's seat with an adjustable friction control to prevent inadvertent movement. The collective changes the pitch angle of all the main rotor blades collectively (i.e., all at the same time) and is independent of their position in the rotational cycle. Therefore, if a collective input is made, all the blades change equally, and as a result, the helicopter increases or decreases its total lift derived from the rotor. In level flight this would cause a climb or descent, while with the helicopter pitched forward an increase in total lift would produce an acceleration together with a given amount of ascent. The collective pitch control in a Boeing CH-47 Chinook is called a thrust control, but serves the same purpose, except that it controls two rotor systems, applying differential collective pitch.[3]

Wow that is really strange! Not only 2 misses, but the 2nd and 3rd MAV-E went to exactly the same spot! I don't know if Smoke and Flame causes issues with the Seeker tracking the LASER, but I have done similar attacks and never saw this happen. Wouldn't explain the perfect tracking to the same spot on the ground, though. I don't know if you were carrying a FLIR pod, but you could try putting on the LST and see if the JTAC is really illuminating a target, of if for some reason, they are lasing the spot on the ground. I have never seen this. I flew it and exactly the same thing happened to me. I did turn on the LST, and, indeed the laser spot was on that piece of ground next to the first target. Very odd. I have been having various oddities occur with the Mission Editor JTAC but this is new! For grins, I edited the mission to use the CTLD script with AutoLasing JTAC. Every missile hits! (so I guess the smoke and flames weren't affecting the laser) I have been moving to CTLD instead of the built in JTAC due to various oddities. Downside is the lack of communications. Everything happens auto-magically with only the visual messages. I think CTLD allows some Text to Speech voice comms with SRS, but I don't use SRS, so I never messed with it. When I flew it the JTAC targeted the Tunguska first, so that threat got eliminated early . Could prioritize the Tanks so the JTAC doesn't designate the Tunguska if you want to practice tactics for live SA-19's. So, the issue does appear to be with the JTAC not the AGM-65E or anything you are doing wrong procedurally. f18c_a2g_tank_convoy_agm-65e_CTLD.miz

I can't tell exactly from the screenshots if this is your issue, but the closer you get to the target, it is possible to lose the radar track due to the narrow radar constraints. In the screenshot, it seems you are extremely close. Since you need to illuminate the entire flight time, SLOW down and adjust aspect to keep in constraints.. The TPOD has a better chance of keeping a lock on the target when in close, so it is usually preferable to switch to the FLIR as the sensor maintaining the System Designation as you can get further offset and maintain lock than you can with the Radar. Sometimes easier said than done. For Fire and Forget weapons like AGM-65F the radar works great. For GBU or AGM-65E where you need to maintain a radar lock as you get closer to the target, the TPOD is a better choice. For moving targets, it is kind of a pain to do this. For static targets, it is easy to just bring up the TPOD and designate with TDC. For moving targets, you need to work harder to get a PTRK. Currently there is a (bug?) behavior where if you switch TDC to the TPOD while you are tracking a GMT or SEA contact, the radar will drop the lock, but you can bring up the TPOD to get a visual as long as you don't switch TDC to it. I have a TRK file in this thread that illustrates that. (Not quite the same issue, but similar in that you will be able to track the target longer with FLIR as the Sensor providing the Designation) Here are a couple of new tracks: (Persian Gulf Map) 1) Kept radar lock only FIRE MAV-E and drove in close. Lock Lost 2)Switched to FLIR and generated PTRK. FIRE MAV-E Drove in and maneuvered to keep FLIR on target HandofftoFLIR.trk LostRadarLock.trk

For AH-64. Anyone know what was 'fixed'? Haven't flown it yet since patch, so maybe it will be evident