Moonshine

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

Yeah especially fuel leaks from small arms should fix themselves due to self sealing fuel tanks but currently you lose fuel as quick as if half your plane was shot away under you. Rather frustrating in AG scenarios

It should automatically but didnt for me at times. Using the updater.exe always did it for me

I have the feeling they were not primarily made to be self lased, whats the point of letting it glide for miles when you still have to get within laser range of your own laser. Might as well drop it late then. would need to test a buddy lasing scenario (or with a JTAC) to see how it behaves edit: did some quick research online, have to correct my statement of its use case. made specifically for low level use, should not be affected by early lasing. Was an interesting read: https://www.globalsecurity.org/military/systems/munitions/gbu-24.htm

Go to the core installation folder -> bin -> and instead of launching the DCS.exe run the updater.exe, should then download the latest patch

Hm, maybe hot start does not have it already entered in DED, but if you choose Airstart, it should be already in.

Kneeboard is simulating the ground crew setting the code on the bombs. Pod needs to be fully running (right hardpoint power on), make sure thats the case. Maybe check if you have it equipped in the first place

To change the laser code on the kneeboard you need to have your jet cold (basically do it before you even start your startup-procedure) If you want a different code for a hot start jet, you might change it in the mission editor or as stated in the post below, shut down the engine. For the DED Page you need to be airborne to make changes to the Laser page. Codes in the DED page can not be changed on the ground

sounds like it might be related to the observations made in this bug report:

so, tried in SP and could not get it to wobble that much. multiple possible reasons for this: - AI doesnt defend hard enough and uses significantly less Chaff than players seem to do. maybe it would need to be tested in a LAN MP environment against something thats better than AI - Netcode might be a factor, however, if its Dsync, i cant explain the speed loss of the missile (as my tacview was taken from the server and not the locally saved one) However, as you can see in the track and the tacview of my SP test against Ace AI (i did hope they defend "best"), the amraam simply cant hit a target that just does a split-s or similar maneuvers, highest G load on the missile was 8.5G and radar lock was held throughout. (1st missile). i have no idea how a missile that can pull a lot more G than that does not pull enough to actually intercept the target. Tacview-20220610-193219-DCS.zip.acmi Aim-120.trk

indeed. the question is not the functionality as you will explain to us in the white paper, more the performance of said functionality.