Moonshine

As for this topic, some data has been collected in the bug report here:

....and the maverick still does not follow the moving SPI of the TGP

never as this does not represent the state of the f-16 block 50 as it was in 2007, which is the year after which ED are modelling the viper in DCS

okay, even weirder. i just remember that all of them were jamming at this point so there might have been a chance it would affect it. i did notice the amraam also missing other aircraft when shot from rear aspect at close range (within 5nm), barely pulling Gs, yet it seemed less frequent than against tomcats.

There might be some weird stuff going on with the Tomcat when its jamming, of course this is just a suspicion Over the last months i had multiple tailchases (within 5nm), shot an amraam and it just never tracked at all. This while shooting in STT. Missile just flew past the target, barely maneuvering at all. In all of these cases it was a tomcat with its jammer turned on.

Might also have lots to do with the lookup/lookdown penalty which is under investigation already

you are absolutely right, markpoint is way off. funny enough, i could only seem to create this with the TGP created markpoints. did it with the A-G radar and that one stayed as it should. here my track showing the issue as described by the OP Markpoint-after-INS-update_1.trk

To fix the markpoint after slewing it (refining its position as you described) you need TMS forward to actually lock the coordinates in. Only then can you press 0 (MSEL) to make it the active steerpoint. then exit MARK page, select the tgp as SOI, press TMS aft (CZ) and it should slew the pod to your Markpoint location

Yes exactly. Apparently thats how it should be based on the EWR modelled in the sim. Just sad there was no info about that change

How sure are you? I tested it by placing every EWR in the ME, making sure they are active and none would show up at all. to my knowledge, a SA2 or SA3 search radar also shows up as „S“ until it is starting to track you. you might be seing those there.

As per the last patch, EWR can no longer be found / targeted with a harm. And also not with the HTS. Sad it was not listed in the patchnotes..

NineLine, BigNewy. If you have some documents you are not sure you can share on here, better to DM them

so we just assume the nebo version we got in dcs is just vhf due to the changes made and not listed in the last patch. could have saved us all this discussion would answer the question above that the HARM training mission is in fact obsolete as it can not be completed

interesting. brings me back to the point where it would be nice to at least get some information about such changes. i could not find any notes as to which EWR version is modelled (as in what type of frequency band they are using), which leaves a lot to speculation and guesswork. would be nice to have that cleared up.

ah, thank you for the clarification. will the HARM table get reworked? as in; why would one list emitters (101 and 102 for example) that you can not see with the missile or the HTS nor target in any way with it?

now this is interesting, in the post here: the mission asks you to target a EWR. the post has been locked and under investigation by @BIGNEWY. however Flappie says no longer being able to target EWR is "correct as is". please excuse my confusion now

they must all be set to VHF then, since none can be found currently

Interesting. Might have been missing on the patch notes. Although it might now be more realistic, its sad to see such changes not to be noted anywhere as it does have an impact on how people operate and may cause not needed drama/„false“ bug reports and thus more work for ed to explain than a simple one liner in the patchnotes. also i did not go back and read the patchnotes again, if it is on there, just ignore this comment

Here my test on the issue, using CBU97 first and then MK82, all in CCIP. see how the cluster bombs all land way short of the CCIP pipper location on release, the mk82 perfectly on target. i doubt it is the planes fault (as in bombing mode bugged) CBU97 falling short.trk

I think it is back to 1500 again as the default BA (at least for the 97) not used the 87 since the patch

wondering, if it is the aircraft then something with the CCIP and CCRP symbology might be wrong, however, other dumb bombs use the same mode, same symbology and work just fine. maybe someone can test with a different aircraft

bump

not the answer to your last question but since the update, all CBU 97 fall short, using CCIP and CCRP. with other dumb bombs it seems to be fine.

yes. just ignore it and wait until the little release cue starts wandering down the bomb fall line. while thats happening, just hold wpn release, bombs will fall as soon as the release cue passes through the flight path marker

Yeah saw that too. Weird how it says it shouldnt be affected by early lasing and then it states this paragraph This bomb is not nearly as delivery parameter sensitive as is the Paveway II LGB, nor is it affected by early laser designation. Paveway III hurt itself in confusion