LastRifleRound

CCIP is wrong in all modes all the time. I reported this bug here: Take a TPOD and make sure no target designated so you can see where the TPOD thinks the bombs will hit vs where the CCIP cross is located. The TPOD shows you the correct aimpoint. Conclusion: CCIP cross is mis-placed in all modes. EDIT: Looking back on this thread, it looks like we have two bugs, one on top of the other (possibly 3) 1. The CCIP cross is naturally displaced from the actual aimpoint, usually to the left. This occurs in all modes and is a confirmed bug. @IvanK this bug could explain the miss in your first test. Run it again with a TPOD like shown in the track in the bug report above and you can confirm. 2. The INS system is picking up some sort of lateral displacement it shouldn't in the absence of GPS. 3. (possible this is the same as 1 manifested differently) AUTO bomb fall line will "jump" around the TD box depending on airspeed and altitude, with certain combinations being just wrong and leading to misses. This happens in all modes. It is possible 1 and 3 are exacerbated by 2 and vice versa. I've said it once and I'll say it again the iron bombing needs to be the first thing ironed out in these jets when they roll out and they need to stay tight, as they expose many of the other issues around the programming of how the jet works in sim. Things AA modes and the like may not exhibit because of the way they must be coded. Also, there is a bug with Mk83's I reported that is over a year old that was never fixed. If you are not at 7000k and 370kts, you will miss long and short unless you adjust your altitude and airspeed accordingly. Lower = faster, higher = slower. Too low/fast you will miss long too high/slow you will miss short. So don't use Mk83's in your testing if in-line impact measuring is important to the test, they'll confound your results.

After the latest update, I have not been able to get a single kill with an AIM7, shots within 15nm at Mach .9 25k on an F-pole, second shot taken at under 10nm. Impossible to score a hit. They're not even dumping chaff half the time. They dive for the deck and the missile goes stupid almost immediately. Run the 4v4 mission. Good luck and may God have mercy. EDIT: Just got 2. One of my SOPs before was to switch the RCS setting to the smallest setting. I tried not touching it and now the pk seems back to normal. Don't know if it's placebo or not but there you go.

It's doing that thing again where it tracks objects on the way to slewing to the target

Thank you for your input. I have reported the re-scan issue already as well. Bug report is in status "investigating". I hope they address this bug as well.

ED, what are you doing? I make a post to discuss with fellow community members MSI symbols and you move it off to bugs and lock it and say it was reported earlier. I wasn't making a bug report. Now I don't know what the bug is, I can't find the earlier post that was "reported earlier", and it's locked so I have to make a new topic just to talk about it. Is the fact that the symbols are showing up the bug? Is the fact that they sometimes DON'T show up the bug? Is it the fact that it's using ground track symbols? No one knows, no explanation given and no one can discuss it further. Referenced post below:

No, I am not confused. Sometimes, MSI contacts are on the AZ/EL page. Don't know how they are on there sometimes, but they are, hence the shock. Will try to grab a screen next time.

I'm seeing many small cosmetic items on the release schedule, but there are many long-standing bugs in the Viggen weapons delivery methods. 1.) DYK pull-up cue is wrong in ANF 2.) Wind not factored in for RB04 release cue on CI 3.) Wind not factored in for RR/ANF release cue on CI 4.) Placeable objects and most native map objects invisible to radar Since dive bombing and wind-corrected release of RB04's are common things to do in a Viggen (DYK bombing probably by far the most frequently used), I would think these would need to be a priority. Being able to place a large structure as a landmark for a nav update would be a useful tool for a mission maker, particularly scenarios with a long over-water or over-desert component to their navigation. Indeed, one of the main campaign mission tasks you with shooting RB04's on a very windy day in a pretty nasty cross-wind from the launch point. I'm sure that's not a coincidence. Seeing as there is no mention of these things, I don't have an expectation that they'll ever be fixed. Is this a correct assertion?

Whoa, how long have they been in and I haven't noticed? To anyone else out there dense like me, MIDS symbols now appear on the AZ/EL format. SA in the Hornet with that, the SA page, and the HMCS is top-notch.

EXP2/3 designation inaccuracy is due to the same bug that is confirmed and causes FRZ to be inaccurate. It is not due to some ED modeling of real-world inaccuracy of radar designations. This discussion here, marked "correct as is", likely due to the title, contains evidence of the above, including tracks and references to prior bug reports with tracks showing the same behavior. The confirmed FRZ bug, reported by @Frederf, is here, as of August of 2020

I've had the M2000 and Harrier for over 3 years now. I've got to say, I'm very impressed with the dedication and level of fidelity coming out lately. I know there's always more to do, but I really appreciate what you guys have been doing over there. Your recent efforts have convinced me to day 1 the F15E and Mig23. Keep it up!

Yes I've reported this numerous times, though I didn't know the cue was operating correctly in "quick" mode.

M2000C requires ground power

For the TWS one, are you guys setting your aging to 8 or 16? If you don't TWS drop contacts like crazy. You shouldn't have to do this in the real jet but this will get you by in DCS for now.

I wouldn't mark it off as a solution, it's not solved. Thread should stay open and be addressed. @Frederfis right about what is likely happening here. It is likely not intended. I will test this weekend, but if he's right, they've been working on it. @Santi871 it would be great if you could take a second pass at this. We provided some solid evidence here that this isn't working correctly.

I think disingenuinous is a bit hyperbolic. They are clearly the same thing. Seeing as "FLIR difference bug" was never fixed, even if that were the issue this can't possibly be correct as is. I interpreted that as him acknowledging the issue especially in the context of myy previous bug report and the FRZ mode bug report are both confirmed also. I can dig them up if need be, I've already done it once. 1. The TPOD is on the designation spot, ie bombs go there 2. FRZ mode exacerbates the issue 3. FTT co-locates radar designation and FLIR designation 4. Minimizing angle off and speed improves designation 5. If you take the FLIR off and use the HUD, it also confirms this is the real designation spot. Therefore, there is no difference between what the radar designates and where the FLIR goes. The FLIR is simply looking at the designation. This is a bug, plain and simple. It's not simulating "general inaccuracy", as the radar is inaccurate in a very specific way. Documented methods of using the radar to bomb lead to the opposite result, IE making your last designation at 7nm, 450kts at 45 degrees angle-off is FAR worse than 20 degrees at 20nm. The performance is too good far away and too poor close in. The user should be able to follow the TACMAN to achieve the best possible result. Right now, TACMAN ought to be ignored as it leads to the least optimal result. Just how accurate it should be, I don't know. Again the -65 says 100ft. The problem isn't how inaccurate it is, it's that it should be at it's most accurate when it's at its least.

This is not "correct as is". I have a confirmed bug report on this very issue. INS ag radar designations are subject to a phenomenon called "map shift". This is because in an EXP mode, you aren't seeing what the radar "sees", rather a mathematical extrapolation of it. The equations used to render this have errors in azimuth that get smaller the larger pool of doppler data there is to work with. What this means is that the faster, more off angle, and closer to the target you are, the more accurate your designation should become. It is within 100ft for the APG65. I do not know the value for the 73. In DCS, the opposite is true. This is because map shift isn't modeled. What you are seeing is ED not adjusting properly for the aircraft's own movement between scans. You can test this with a FLIR and see the exact things that should make designations more accurate actually make them worse, and always in the same direction counter to the aircrafts angle off and direction of travel. For a more extreme example (and also a separate, but related confirmed bug) use the FRZ mode to make a designation. The longer you wait to make a designation, the farther counter to the direction of aircraft travel the designation will be. ED, I can find the links if need be, but I've reported this and had it confirmed twice months ago and months apart. I didn't want to be a pain and list it again because I can see you're still working on the AG radar. Let me know if you want the links to the previous bug reports and please update the status of this report to some other than "correct as is". EDIT: Here's a link to one of the older reports that was confirmed. I forgot to mention you can further confirm the issue by going to active pause. Wait a few scans, then your designations will be 100% accurate because the aircraft isn't technically moving.

True!

Are you actually talking about the A10? Reason I ask is "TGP" and long actions are a thing in that jet, but not the hornet. Not being pedantic, I've posted in the wrong forum before, too!

I will add that once FLIR is slewed, not only TDC depress, the radar should lose designation and enter AGR mode and FLIR should drive designation. Any time FLIR is driving designation radar should be in AGR. Source is TACMAN

OP is 100% correct. The third one tracked because it was pitbull off the rail. DL in STT is not working

It did before the HOTAS update. Weird. Only ones that work for me are SCS right to get ATK/RADAR and down to get/cycle HSI/SA page. I'll have to play around and see what's going on. Work around would be to use the AA weapon select switch, as that brings stores page on the LDDI. However, SCS left doesn't do anything for me with that up. You can try it out it should work.

Castle left stopped working for me after the HOTAS update. I go AA mode or AA weapon select, stores page comes up on left DDI, SCS left and nothing happens. I have to press the DDI buttons to get it to come up. Same thing with EW page in NAV. Did this happen to you?

Lol same here. It is super annoying now when combined with it locking mystery contacts at 99nm

I'm guessing their map angle bug where the designation isn't velocity corrected is a huge pain for your team

It's not slewing per se. When you release the TDC the scan area will be centered around the cursor's position, but the scan won't move until you release the TDC.