LastRifleRound

They're not using terrain maps, they gave the ground an RCS overlay, which some things (some placable static objects) are still missing. This is why the radar map doesn't work on the channel map. The camera views for the jf17 DBS modes are just placeholders according to deka.

This is good stuff

Correct on all, it's broken and incomplete as you say. You're not doing anything wrong.

I haven't been able to. The logic was really clumsy before so to get ptrk I'd keep slewing until the reticle jumped to the target. Now you have to be right upon entering ptrk or you have to cycle out of it. Either it no longer works at all or the precision required is so high that we just can't see it working.

Yes, this concurs with what I said. Note the IRLAR is heading dependent. IZLAR assumes 30 degrees FOV of term parameter (if any) if 30 degrees nose to target. This why IZLAR won't appear unless those conditions are met. I believe what you quoted should say "bearing" and not "heading". If that is how it's supposed to work (i.e. heading) then the current implementation of IRLAR is wrong, as it is bearing dependent, not heading. See next example for evidence. If you head to a point in the IRLAR circle perpendicular to the target, you will find launch impossible by the time you arrive. This is because the IRLAR was calculated on bearing, which changes more rapidly the closer you are to the target. Note your IZLAR description does not preclude defaults. Nothing you posted is in contra-position to what I posted (not sure if you intended it to be, either. just assumed that since you quoted me). If IRLAR responded to heading instead of bearing, it would be more predictive and more useful, but that is not it's current implementation in DCS, and the documents I have do not say what you cited.

IZLAR isn't just for terminsl parameters. When the target is within a 30 degree cone of the nose, a pie like izlar appears even withou term. This represents the actual area you can drop in by the time you get to any point in that area and changes with airspeed and altitude. This differs from the over simplified logic in the JF17 and the IRLARs we have in the Hornet now. Picture the current, circular cues on the HSI. Picture one with no term parameters. The symbology would lead you to believe you could fly to a point 90 degrees to the side and still hit. Of course, by the time you get there, the circle shrinks past your aircraft. In reality, the drop zone is always pie shaped. Tl dr, the IZLAR is the area you could actually drop when you got within range of the target and assumes any heading within a 30 degree cone of the nose and the current altitude and airspeed

The last patch notes said izlars and auto mode was done. It's not so I assumed we're dealing with bugs. Now I don't know what is supposed to be done or not. Patch notes are pointless at anything other than a high level "here's some systems we messed with".

Man, my bug reports always end up here.... To be clear, it seems auto mode will not be completed any time soon then, and what you were actually intending to release was auto hud symbology and individual izlars that react to term parameters. Please let me know exactly what we should be able to do and expect for the 06/03 release regarding jdams so I can test properly and not issue bug reports for features that are not yet finished.

I didn't think that was out of line at all. Fact is the 3 biggest items in the past two releases are full of bugs (amraam mid-course, jdam auto, tpod adds). Some of them (jdams auto) do not work at all. All bugs were easy to find by just attempting to use the feature as normal. This means either the team didn't catch them, or they did and the update was released anyway. If we can't speak obvious truths devoid of any name calling or denegration then it's unclear what kinds of crticisms, if any, are allowed on here. I tend to think the team found the errors and reported them. The SC release and performance enhancements are excellent and seem to have been well tested. Also, in the bug section, some of the team is commenting many things are fixed internally already, which indicates they're doing their job well. The release notes are wrong or incomplete in my opinion, and that is what is causing this. We're not seeing any communication and are being asked to submit track files and post bug reports for these things. Put yourself in our shoes. This hornet feature update is a month late and ranges from not working (jdams, amraam) to breaking existing functionality (tpod). There is no high level communication acknowledging any of this is going on. It's like the testers knew this stuff wasn't working and reported it but ED is acting like they're new bugs and didn't know about them. It's confusing. We're your open beta test team, myself and other active users here, and we like helping you guys figure stuff out. I dedicate a lot of time testing and reoporting. Now, I have no idea what I should bother reporting or not. You haven't even told us how some of this stuff is supposed to work (offset cursor) so I can't even tell you if it's working or not. Hope I don't strike a nerve here. Just want to help out but that's getting more difficult lately. I miss Wags!

Not entirely. One pickle will release all in zone bombs if you happen to be in zone for all bombs. However symbology will be for the active station only. Most people don't notice because the targets tend to be pretty close to one another. AUTO should give IZLAR for all bombs in QTY. One IZLAR that is the overlapped area of all the individual IZLARs. Think the center of a venn diagram

Documentation says AUTO mode should plot a solution for all targets in QTY in AUTO mode. This and the HUD symbology are key differences between MAN and AUTO. Both modes will display IZLAR, for AUTO that's for all targets, for MAN it's active station only. ED confirmed this, a while back I posted this was missing and they said wait for AUTO mode.

It was a great resource. Is it un-stickied or deleted? Was it intentional?

Selecting QTY in AUTO mode should plot solution for all selected stations with a programmed mission. Attached track shows behavior is exactly like in MAN mode, both on the HSI symbology and HUD. IRLAR's shouldn't be there at all and only IZLAR should display for all bombs, if possible. Hornet JDAM.trk

Did you report that auto is ignoring QTY and only showing IRLAR for the selected station or should I make a separate bug report?

Couple bugs: 1. QTY is ignored. Attached track shows QTY of 2 for Mk82, but the whole stick is dropped in DTOSS 2. No AUTO symbology, only release audio cue, no other cues (loft angle, auto pipper) is present. Track in this thread - forums won't allow me to re-upload: https://forums.eagle.ru/showthread.php?t=273917

Auto always gives a loft cue, but it can be ignored. IZLAR stands for "In Zone Launch Acceptable Region". It is the region where the computer calculates a valid solution can be achieved. When in the IZLAR the HUD gives the IN ZONE indication. What we call the LAR is really the IRLAR or in range launch acceptable region. This is an indication that you are within the weapons non idealized maximum rangd. When in the IRLAR the pilot recieves the IN RANGE indication on the HUD. The IZLAR is always inside the IRLAR, and the weapon should be released when given the in zone indication

It calculates the IZLAR for all selected bombs in quantity and gives one izlar for this region, taking into account all term parameters if any. If no release point is possible for all bombs (i.e. term headings 180 from each other, targets too far away) no izlar is displayed. Man mode only calculates izlar for active station. Additionally, HUD symbology is presented in Auto to guide to the center of the izlar. You don't hold the pickle down like with dumb bombs, common practice is to wait a few seconds after solution cue to release. Loft symbology is presented as well for the selected loft angle, though this discouraged for most altitudes as it will actually decrease, rather than increase range. Izlar should show for both modes. In auto, izlar is shown when ownship has all tgts in qty within 30 degrees of the nose and, if term headings are set each term heading has ownship within a 30 degree FOV. In man, these conditions need only exist for the active station for izlar to display Source for information is official public documentation that I can't post here.

Can confirm. Couple bugs: 1. QTY is ignored. Attached track shows QTY of 2 for Mk82, but the whole stick is dropped in DTOSS 2. No AUTO symbology, only release audio cue, no other cues (loft angle, auto pipper) is present. JF17 DTOS.trk

I can confirm this feature isn't even close to functional. IZLAR's never appear, heading changes (watch the "tails" from the targets) make no sense (180 degrees and 181 are > 70 degrees from one another), and QTY greater than 1 are ignored in AUTO mode and treated just like manual mode, as in it doesn't plot a solution for all selected bombs, just the currently selected station. Pretty disappointing for an extra month in the oven. I hope they don't think this anywhere near done. EDIT: Some things I've tested: 1. Impact Angle - does nothing 2. Impact Heading - does nothing 3.AUTO/LOFT in PP mode - does not work. Bombs will never release 4. IZLAR - never appears, no matter what mode or what TERM settings exist 5. QTY - ignored. Only limits STEP function, has no bearing on centroids or bombing solutions in AUTO As far as I can tell, not a damn thing has been added. The HUD now has indications, but it's always towards the current station's target not to any centroid if a QTY > 1 is selected. EDIT AGAIN: I have a sneaking suspicion the wrong branch or merge point was pushed to production. The JF17 is missing 1/2 of it's DTOSS features. Haven't tested the other modules yet but it looks to me what we got was some point halfway to what was supposed to be released. Pure speculation on my part, but I'd like to think a patch this bad wasn't actually pushed in this state, not after all the rumblings around here lately and the almost month over deadline. I'm nervous to test the AMRAAM and I can't put my finger on it but my the speed or drag seems different, though I don't recall seeing any aero or engine changes in the notes.

IZLAR should appear when within 15 deg FOV of the terminal heading AND within 15deg FOV of the target itself. Haven't had a chance to test yet. Has anyone tried with a QTY > 1?

Before/after DBS? This year/next year?

So, the answer to #1 is "yes" after all. I knew the terrain didn't have an RCS so I was afraid they'd "cheat" but the delay notes suggest otherwise.

What is offset cursor?

I think it's related to DYK pipper now signalling the beginning, rather than the middle, of a string. This is an undocumented change and the CCIP seemed to break around the same time. PLAN is just about perfect now. However, DYK is bang on if you use the pipper as the beginning of the string, and you're saying you're falling short, not long, so I suspect something else is at play. Do you have a track? Are you on Open Beta?

This makes a lot of sense for a real world pilot, and everything you said makes me more excited to try it, not less. I want to use it for the challenge, specifically because it is not ideal. I want all the limitations 100% there so I have to deal with it. That's the point. We are virtual pilots. It costs us nothing to fly a sortie, and our skills will never be used for anything but our own enjoyment. We get to specialize in whatever we want because, at the end of the day, we are playing a computer game. A very complex one, but an entertainment product when all is said and done. I'm a tinkerer at heart. A maker. Woodworker, welder, software engineer. I like making things, and taking things apart and understanding how they work. The more complex, the better. I do it with software, with business, with everything. I know a lot of guys are like me and got into aviation because aircraft, particularly fighters, are complex things that have a lot going on, This is the opposite of what real world pilots want to deal with I'm sure. Simple is better. Definitely. But this is a sim. We are intentionally doing something we don't have to be doing. If we want "easy", then why even do a takeoff checklist or BIT or even a ramp start in DCS? None of it is "necessary". In fact, we should all go grow vegetables or something, because DCS isn't "necessary" either. (You really should grow some food though. Do both). What if I want to simulate your night time sortie? I need an AG radar in the sim to experience that. I hope this helps you real world pilots get into the head of those of us waiting for this feature. It has nothing at all to do with making things easier. For me, it has to do with taking a challenge on and seeing what I can do with it. I want to hilariously miss blobs and hone in on an actual technique that might work because I have the time and I feel like it. Some people like hours of BFM. This is what I like. I routinely use the Viggen's RR mode in ANF. Real Viggen pilots hardly ever used this. I've gotten pretty accurate with it. I enjoy using it. It's fun to try and get it to work for the same reason it's fun to try a carrier break at mach. I'm 37 and wonderfully employed (thank God). I don't need my DCS skills to translate to anything but fun for myself. Hope this makes sense to you all.