Mike5560

What works for me with triggered artillery: Go to the tab for scripted actions for the artillery group. Add a new action, set fire at point, select your location and radius. Then set a trigger zone at your artillery's final waypoint and name the trigger zone accordingly. (add trigger zone, on left side of mission editor) Go to triggered actions on the left side, near the top of the mission editor, and select once, then all of group in zone (pick your arty group in dropdown menu) , then flag true....then pick any flag number not already used. Create another triggered action that says once, flag true (pick the same flag number) and select "unit action" or "scripted action" IIRC, then a drop down should appear and one of the options should be "(group name) fire at point". I know its pretty roundabout, but I've tried it via the method you described, and also setting a trigger directly (not through a flag) and they haven't worked. But that was several updates ago. It might be fixed to trigger the arty directly.

Il-2 BoS is 59.99 right now on steam. Maybe if the price would drop down Id think about it. Completely off topic but wouldnt it be kinda cool if DCS had an "old war" filter? Like where you could assign a key command to make the screen black and white and with all the film spots and scratches. Would be cool for replays and making movies.

+1...... I'd buy it for the siren sound in F3 view alone.

Not really a simpler way to do it unless you're firing at multiple targets within 50 or so of eachother. In which case it's probably best to fly path hold autopilot nose down a few degrees and slew the MAV seeker to the TGP SPI and fire, then adjust to different targets manually through the maverick seeker. Assuming you have the TGP on the left MFCD and MAV on the right. If you're slewing the maverick seeker onto different markpoints, you have two options: 1. Set HUD as SOI and DMS fwd /aft, china hat fwd long to slew, coolie hat right long to set mav as SOI and work it from there. 2. Leave Maverick sensor as SOI and manually switch steer/mark points with the UFC switch. I think you can hot key the UFC rocker if you have the keys to spare. It's not a simple procedure, but with practice it's not unrealistic to have two mavericks rifled at different markpoints within 6 seconds of eachother. Of course, if you have moving targets things get interesting.

I'm interested to see what EDGE will bring. If the terrain modeling would be suitable for first person shooter fidelity at ground level, like if the detail is high when low to the ground and it scales appropriately based on altitude. This could open up the doors for a FPS module (whether or not that's even on the foreseeable horizon). Having a campaign that incorporates all modern aircraft modules and CA/FPS could be epic. One mission you're doing a special ops HALO infil to sever IADS comm lines, destroy repeater stations, etc while the next mission you're in an F-15 providing escort for both air interdiction and personnel airdrop missions. A true DCS/ARMA hybrid could make for one hell of a MP experience.

1. Leaving master arm switch on all the time. 2. Cycling thru F2 view when friendly AI CAP doesnt do their job. 3. Not making markpoints of targets I find in TGP, even if Im about to attack the group anyway. 4. Not hand jamming jtac coordinates when I know he's EPLRs capable. 5. Too impatient to shoot helis from the rear with aim-9 if we're head on. 6. Never turning on ILS since Ive gotten the hang of it. Wild Bill, why do you turn on your APU in your #6?

This is mainly centered around A-10C but could be incorporated with any CAS aircraft. I know ED is probably super tasked out but just throwing some ideas out there. 1. WP marking with friendly units. The ability to task wingmen with engaging targets at your WP mark. Just like you can already do so with a SPI, only using the script to use targets within a small radius around your last fired WP rocket, and the supporting menu to do so. Also can be used with a JTAC with a submenu under F4 "contact".....e.g. "confirm the tanks at my mark are the targets" 2. Artillery suppression (SEAD). Although this can be used to some degree with CA activated and selecting a target for artillery, AFAIK degrading air defences with artillery is not modeled. Since JTACs IRL have the ability to coordinate artillery fire missions, or are at least within close comms with a joint fires observer, being able to request arty suppression on a threat through a JTAC would be a great addition. Now that in itself would be awesome... To really amp up the realism, when the artillery starts firing, the JTAC briefs the gun to target line (GTL)....(this is an azimuth in which the arty is firing to) and the "max ord" (this is the max altitude the artillery rounds will reach) This could even add a unique dynamic where the artillery suppression is not always effective (defined by the proximity of the impacts to the threat, tracking radar or skill of the AD crew can all effect it's effectiveness) and potentially present a false sense of security. These two ideas are IMO two facets that could add realism to the FAC-A experience (known as AFAC in DCS) which is a capability A-10Cs are uniquely suited for. Managing airspace/ safety for other fighters, marking targets coordinating attacks, etc.

I think this is much less of an issue with more modern AESA radars. Though no current playable aircraft in DCS has one.

Based on my limited (SP only) experience the dora seems to indeed climb/accelerate better but the P-51 has a turning rate advantage. I set up a 3 P-51 vs 4 Fw-190 head on dogfight mission with me as one of the P-51s. In a one circle dogfight, Im able to get on his six after the initial 180 turn and lag persuit in the opposite direction. Two circle fight the Dora resorts to the zoom climb, dive down/ repeat once you start getting behind them. I tend to stall before they do in a climb, so the seconds prior to that are critical for lining up a good shot. I have to manage the throttle since oil temps get high after repeating this a few times. It doesn't take a lot of hits to kill, IME as long as you can get close enough. It's just me but I prefer the fixed sight over the gyro. The gyro is supposed to work better but it messes with my head.

As I understand it, from reliable sources a main battle tank needs a 500lb bomb to hit within a meter or two to cause a k-kill. This seems to be accurately modelled. People are tough to kill. From talking to many pilots and seeing pod footage, many a times guys will run away from a bomb impact between 5-10 meters away from a gbu-38/12.

AFAIK the bombs weren't rippled. There was several rapid bomb release "sounds" during and after the 4th bomb release. Looking at the F7 view and debriefing it displayed only 4 bombs. Might have been a glitch in the replay. All I can say is reiterate what txmtb said. Lase while creating markpoints. JDAMs aren't pinpoint accurate in DCS. They usually kill MBTs, but not always.

Aginor, you read my mind a few weeks ago. I came onto this forum to post exactly what you said. Suggest S-60 and KS-19 medium/ heavy AAA with optional Firecan or Flap Wheel radars. SA-2/ HQII would be my next radar SAM request. Its like an SA-11 buk that you have much better hopes of defeating.

When you added advanced options for the JTAC did you select "FAC assign group" or "FAC engage group"? I know you just said "assign", but it would make sense if you selected "engage" as this requires the JTAC to physically see the target to nominate it, whereas FAC assign group does not.

I can't tell either way if he's using the bore cross or the pipper. They both seemed to track nicely along that lazy "S" road though. I don't understand the symbology on the lower left HUD. Doesn't seem to indicate ammo type/count. Might be a result of one of the many suite upgrades from 3.1 to present.

Set the sa-15 as SPI through your TGP, slew AGM-65Ds to SPI, launch two mavs and turn around with chaff. Works every time. Getting in close through terrain masking is a little more dangerous IME since the tor acquires, tracks and fires so quickly. As far as vikhrs go, I think it'd be rather difficult. Unless a hovering KA-50 somehow is in the doppler notch.

Never had any luck being able to "FAC assign group" to a stationary object, or for anything other than ground vehicles (i.e. Boats) You should be able to determine the order in which the JTAC assigns targets (based on priority) and what weapons to request per group. If one group is triggered to activate after a recently destroyed group assigned by the JTAC, you may have to re-do the fighter-FAC check in.

Open windows, lights behind you or people can do this. You can go to diplay, then camera view to see what the camera is viewing. Anything that is red is an outside IR source. On the left side of the control panel you can click on the camera tab and adjust the light filter threshold to your liking.

I stand corrected on the drift part. Indeed lasing does help (demonstrated in excessive headspace's video). In the instances where I noticed it drifting off was where I was standing off 20+nm from a snow drift radar and didn't bother to lase as I doubted the laser's effectiveness at that range anyway.

Since I have seen very many recent posts about there being no solutions to running the oculus with AMD cards, link below is to a fix posted by Jeesus back in September if you have trackIR. http://forums.eagle.ru/showthread.php?t=129728

Thanks, it works! Though the offset cursor is annoying, its still fun. I used 0.030 for my left and right eye offset, works much better for me. I still may be a thousandth or two off, so Ill experiment.

Though I like the convenience of being able to see through clouds during missions, I know it's unrealistic. It seems that since the FLIR of the litening pod is modeled via filter, it would be easy for ED to incorporate cloud masking; i.e. Wouldn't it require more programming to not have the clouds visble than to have them? Which leads me to a thought, or possible TTP if cloud masking was modeled. Say there's a low weather deck and you have some JDAMs. You could spot a target under the weather with the TGP, set a markpoint, climb up and bomb the target. Of course the gun and other weapons may be used but the options still there. Ive gotten to using markpoints often and it seems they are staked inertially; the more time goes by and the more turns I do the more the markpoint drifts off my original stake. I suppose I should bother checking the coordinates on the CDU and see if they change over time. Is there a more accurate way to save a point I may wish to reliably drop a JDAM on?

Some find the TAAF (TGP Attitude Advisary Function) useful, though I dont particularly use it. It's a tool to warn you of your A/C attitude so you dont pod mask, but it's a general guidline and is not a magic bullet to prevent pod masking. It's accessed by OSB 1 on the TGP main page, then OSB 20. You enter in your orbiting altitude into the scratchpad, and will get a red "Check Attitude" warning box when certain parameters are exceeded. More info on it on pg 339 in the flight manual.

Noreit, sent you a PM, off topic.

I say that MGRS is the metric system of coordinates, every unit is 1/10th of its next higher unit. Lets use 12T ET 12345 45678 for example. MGRS grids read from left to right with increasing precision, with easting and northing 5 digit strings. 12T This is the grid zone designator. Basically a huge swath of area. ET This is a 100,000 meter square identifier and represents a smaller swath of area (albeit still very large) within the grid zone designator. The E represents easting, while the T represents northing. It's not like lat long coordinates where you measure from one point on the earth (so lat long has South and West measurements also), the letters increase in value as you move east or noth, respectively. If youre in the ET 100,000 meter area, and you move east enough you will eventually end up at FT. 12345 is the easting "string" for lack of a better term. Each number represents its own level of precision. So 1 is 10s of thosands, 2 is thousands (km), 3 is hundreds, 4 is tens and 5 is just meters. So this means that this example is 12,345 meters from the border of DT and ET 100,000 meter grid zones. The northing string works the same way. You will see the JTAC in game pass a "6 digit coordinate" e.g 12T ET 123 456. This means he is indicating the coordinates are within 100 meters of precision. Its not realistic that a JTAC would be able to pass a true 10 digit grid with true 1 meter precision. Since Earth is a sphere, and MGRS is made of a bunch of giant squares the dont evenly match up when laid out on a sphere, you find some overlapping grid zones. I think theyre even present on the DCS Black Sea map. UTM works the same way as MGRS, only the 100,000 meter square identifier is represented by four numbers (not 2 letters like MGRS). The military came up with letters to simplify the system, as reading and copying down 14 numbers said over a radio can get confusing quick.

Thats some insane piloting on the vid linked on page 2! Made me want to go kill some stuff in the frogfoot. I dont know how he fired those vikhrs like that though. I know about ripple fire, you hold down the trigger and multiple missiles release. However, theyre to close in succession I dont have time to slew the shkval to a different target after the first impact. And a quick press of the trigger fires one and it's another 10 sec or so until I can fire another. IMO, the SU-25T excels at battlefield air interdiction and SEAD (forward looking sensor for linear fights, fast speed, fantasmagoria, etc. The A-10 is the king of CAS, and CSAR with its slower speed for visual spotting and nasty GAU-8 which is great for danger close, rounds-down-quick attacks. Im a fan of its fast turn and roll rate as well.