LastRifleRound

Here is a track file. I lock on, you can see "RDY" with a cross through it on the SMS, but all other indications are missile should be ready to go. I then switch to BRM and hit the target no problem. c701.trk

No, I had SMS open and no red symbol appeared. "WPN READY" displayed on HUD as well.

Anyone else have an issue with this? C701 powered on, completely aligned, Master arm is on, range is 8.9 nm, "Track" is flashing, red diamond over target and cross hair flashing, missile will not come off rail no matter what I do. Also carry BRM's in the same sortie. Those work just fine. What gives?

Fair enough

Could say the same for a guy who writes a post that can't see anything between no problem at all and sacrificing babies, and thinks criticism is "crapping all over someone else"s work" and doesn't put his real name in his own critical post while admonishing others' anonymity. Agree on the "hurt soul" thing, but you're just the other side of the same coin

You are wrong. I bought the JF17 and couldn't be happier. Not because it doesn't have bugs and missing features, but because they told me exactly what was missing before I bought it. Take this latest JDAMS update. I read the manual update and watched the pre release vid thoroughly. When it releases, the ASE isn't functional and the LAR doesn't refer to all selected targets, but the first one you clicked. So all this lead up, and the thing doesn't work according to their own documentation. I had no expectation that JDAMS would be feature incomplete (except for terminal parameters, which they did tell us about and I'm fine with). It should work the way their documentation says it works. Is this a big deal? I don't know. It's a study sim, and there's a pattern of this sort of thing. Half-finished features that don"t get circled back on sometimes for over a year. This isn't a pattern endemic to EA, it's an attribut of RAZBAM. I want to buy the Hornet and Falcon at some point, but I didn't because they told me exactly what was working and what wasn't, and I want to wait as a result. No problem with me there. Also, I'm not sure how these complaints are dispositive because they are working on another, even more neglected module. To me, that reinforces the point.

I get this kind of an emotional response, but run it through some Socratic iterations. Let's try buying a car. "You don't like that your car doesn't start? Go make your own damn car then. Toyota has been working really hard making the wheels round. You want better? Make better." Let's try an ear of corn at the supermarket. "You don't like that it's rotten? Go grow your own damn corn then. Del Monte has been working really hard arranging the shelf. You want better? Make better.". Let's try a different piece of software. "You don't like that Excel doesn't add correctly? Go make your own damn spreadsheet application. Microsoft has been working really hard making sure it multiplies accurately. You want better? Make better." I'm happy about the recent JDAMS release, but even that is kind of buggered, what with the ASE not working as the videos show beforehand and the manual tells you how it works. There's a history here of half-finishing things and people have a right to be frustrated. They shouldn't need to have attempted to build their own module to air those frustrations.

You don't mention that you lased the target. Did you laser range the target? The coordinates will not be accurate enough for release if you don't. Also, you are skipping a step shown in cap's video. The first marker is ignored. Cap shows it as T01 that you can discard, but it doesn't even have to be labeled. For pre-planned to work, you must have one waypoint in the mission planner that exists, and at LEAST two mark points in the F10. The first one you place is always ignored, whether you label it or not. The next one should be labeled T01, then T02 and so on

I figured this out. If your aircraft is outside your machine's draw distance, targets will not appear. I have to launch with less than 30nm to target for DIR/COO in order for things to work properly.

No one? Is this not happening to anyone else? I want to report as a bug but want to confirm it's not just me and is abnormal.

If you're doing relative mode, I found a bug. Upon laser ranging your tpod target, then holding waypoint increment, the targeting info won't appear on ehsd. Simply hold then release wp increment again to leave the mode, then hold/release wp increment again to re-enter it. You should see the symbology and be good to go.

Any tips on waypoint placement or DIR COO tips to get the missile seeker pointed in the right direction when the camera turns on? I struggle with target acquisition with these unless the targe is something massive like an airfield.

Is it me or is the dot in the middle of the hud supposed to move to show steering when dropping jdams? For me it's static in the middle of the steering circle and therefore useless. Seems like a bug.

Then maybe what I perceive as a trim issue a stick sensitivity issue. I feel the trim and stick overcompensate no matter what I do. Don't get me wrong, I can overhead break to the carrier and I have no issue manage RVL's and the like, it just seems I'm fighting the aircraft more than I probably should. The aircraft I fly the most is the Viggen which has no fly-by-wire, either, only a dampening system. Does anyone have a curve pattern they prefer for the harrier on their stick?

Is this on cold start? AKG's not working properly after cold start is a known issue.

Just a general question, but what is the use case for each of the type of external lights? In what circumstances are you supposed to use each kind (position/navigation, anti-collision, formation)? They all have redundant sounding names. Like anti-collision lights. Aren't they all anti-collision lights? I usually flip them all on no matter what then ignore them the whole flight, but I'd like to practice the actual procedures that would be used. Also, do you turn them all off when you fence in?

I saw a few topics on this, but none really conclusive. What's everyone doing out there for trim? I find the harrier's trim to be way too coarse. I find, when landing for instance, that it is impossible to trim the witch's hat level with the horizon. It's either rising or climbing quite a bit with nothing possible in between. I have the trim mapped to my 8-way hat right out of the DCS controls page. Any tricks to this, either in different control settings or in actual procedure I can use? I find the workload gets way too high on carrier landings because trim just isn't an effective means of assisting with stable flight.

The best advice I can give on landing is first concentrate on just these things: 1. Keep the witch's hat level with the horizon 2. Ignore the VVI 3. Get decent rate on the right hand altitude tape to 0 with 82 deg nozzle 4. Get airspeed below 15kts. Try to maintain that regime. Once there, do a pedal turn 360 deg to both sides to get a feel for how the rudder and bank work together to sideslip or rotate the aircraft. If you can do all that, all that's left to land is pick your spot and drop the throttle to have 250-300 fpm descent. Remember, watch the altitude tape and the witch's hat and nothing else. See if you can get them calm. Keeping the witch's hat in focus will teach you to keep wings level and how not to tip over. Keeping the altitude tape in focus will teach you to be precise with your throttle inputs to carefully select the exact FPM you desire. I find in the Harrier I move the throttle a lot more than the stick in the vertical envelope. Ignore the VVI because it is deceptive in this regime and will only play tricks on you until you get better at managing the aircraft. Just my .02

Locked up some vehicles in gmti and dropped on them. No lead was calculated. Not sure if JF17 is capable of this or it just isn't implemented yet.

Are you actually able to designate anything in this mode? I tried slight cursor movements and it's still way off. Btw to all I know it's not working as intended. Just like playing around with the concepts.

JF17 DBS and AGR, Harrier JDAMS and Viggen campaign Merry Christmas to all! Great year for DCS

Can't wait. This looks awesome!

It's a study sim. You can have the aircraft hot started for you already. Most people would find all of DCS boring. Have to draw the line somewhere. I'm all for options, but in terms of priority there are already ways to get around cold starts and it's never a promised feature. I'd say promised features should come first, then convenience features second. Also, I agree with all above. The Viggen is easier to cold start than my first car, and probably faster

I would just add, though this is not part of the formal checklist, that you should after start up press "HNS" on the UFCP and set it to INS+GPS. This is on by default on a hot start. I don't know if INS degradation is yet modeled, but if it is this should prevent it from happening outside of a GPS degraded environment

Thanks guys. NWS steering button on the HOTAS did the trick. I was using S5 and that changes both station and program, leading to a "rabbit hole" type situation.