Moonshine

yeah sadly OAs are currently bugged (https://forum.dcs.world/topic/315005-offset-aimpoint-logic-after-latest-update-dcs-28134437/) such a handy feature if its working correctly, makes low alt ingresses much more fun

interesting stuff @BIGNEWY: dropped 3 of my 4 GBU-12, left station was empty - got re-filled completely with new bombs, one more bomb on the right wing pylon. then the order of bomb drop would have been that the last remaining on the right station will drop. funny enough, it didnt, instead the first of the newly rearmed from left station dropped. bomb releases fine until then, 2 bombs remaining, one on each pylon, one per wing. these 2 bombs never released, no matter in which delivery mode, even tried CCIP, bombs just would not drop this only seems to happen if the pylon rearms before all bombs of the other pylon are dropped, hence why it did not happen in my first try, there i pair / ripple dropped all of them in short succession unlimited_gbu-12_2.trk

VIP and VRP are no delivery modes and should not be bound to one as such. when VIP or VRP are enabled, delivery modes will display such in the HUD some examples: VIPCRP -Visual initial point/CCRP submode VIPLAD -Visual initial point/LADD submode VIP EO -Visual initial point/EO submode VRPCRP - Visual reference point/CCRP submode VRPLAD -Visual reference point/LADD submode VRP EO - Visual reference point/EO submode HRMVIP - HARM visual initial point submode HRMVRP -HARM visual reference point submode However, i could not find any mention about VIP in CCIP and am not sure if it should still display the VIP location, even if CCIP does not make specific use of it like the other delivery modes do

did work fine for me. note in the ME there is 2 rows of options. the right row lets you select the options as desired. the left row lets you enforce these settings (when hosting a server it will overwrite client specific settings by the ones you set in the mission, given you enforce those). track attached. unlimited ammo is on, i launch 4 amraams first, and you can see them getting replaced, same thing happens later on with the GBU-12 unlimited_gbu-12.trk

yeah based on the recent test i will retract all statements and question if OPs gamefiles are as pure as they should be.

2 things; first the bug is about launch warnings in DTT (in some manuals referred as TTS (two-target-SAM, a submode of the SAM - Situational awareness mode)), which is the initial bug report as that should not be a thing. Then llOPPOTATOll said it shouldnt even trigger a launch warning in STT. newys answer regarding the need of public evidence does not clarify to which part (the DTT behaviour being wrong or the STT post from llOPPOTATOll) he needs the evidence, thats why i referred back to the original bug report, the way it is since the last patch is wrong and should not need any evidence. neither was that change listed anywhere in the changelog about the STT i understand his request. sadly his answer is not specific enough, neither is his second response

while that is cool, i hope you did take note of the initial bug report as per the OPs post as this puts any aircraft firing a missile at a severe disadvantage since everyone already knows you fired, even though DTT was used..

as reported, issue is back/still exists ghost_cbu_105.trk

Reported that yesterday, apparently now a whishlist item as they seem to be revisiting the bomb fuzes in general. while thats fine, a little info about it to clear up the confusion would have not been too much to ask.

Yup. I only tested the AD. seems logical that there is no FD on „Air“. but the fact you cant change it to GND anymore is interesting, especially since there was no info about anything in this regard.

Yes delay settings can still be changed

alright, nice! yeah its still the same tone so distinguishing between new or the same missile is not yet possible. hope thats still WIP edit: low tone does exist as long as you did not bank in a way that got you in the RWR blindspot. if you pass through the blindspot, it sounds like the initial new missile launch tone

also, is it correct that the missile launch warning tone stops beeping even though the missile is still tracking? (red missile warning light still blinking). the sound starts at missile launch and then stops shortly afterwards while the light still blinks until the missile defeated/lost track

in todays patch it was listed that the JDAM now have the correct 5m CEP. while this might be true, they all still fall short of the designated target in all cases, and on top of that they have a 5m CEP. so while that CEP is correct, why does a bomb not fall 5m long or left/right? in the attached tracks you can see the aiming point from my TGP, and the impact point afterwards. this looks like way more than 5m. the measured distance from the desired impact point to the true impact point is around 30ft which in my books is closer to 10m than to 5. tested in Point track and area track JDAM_inaccurate.trk JDAM_inaccurate_2.trk

interesting, does that mean now all jdams will explode above target (airburst)? what use is it to have a penetrator bomb if it does not penetrate?

see title. tested with GBU31 and GBU38 JDAM_Fuse_option_bug.trk

yes i know. sometimes smarter though if you have to wait for some time on the ramp instead of burning fuel and constantly rearming again

to my knowledge this issue only happens if you turn the switches in the back right panel on too quickly before your jet gets proper power. (so wait until all your displays show proper symbology/images etc..), doesnt matter if power by ground or by starting the engine first

Nice find, last time this issue existed for the UHF radio but was patched some time ago. now the bug made it to VHF..

Might also be the case. Maybe its just that proxy fuse is completely missing from multiplayer. Otherwise i dont know how to explain an aim 120 that is actively tracking, which misses by 10 or so feet due to maneuvering (or the famous barrel roll evasive tactic), without detonating in the process. And i dont think it would just be a dsync/netcode thing.

while what you say is true, the Kill distance in the same lua file is set to 15 (i guess thats meters) and is most likely the diameter. and if the kill radius is 50ft (roughly 15m) according to that document, then DCS has cut that in half. as i guess everybody understands that radius is only half the diameter...

discussed at lenght here

this. dcs really needs an actual IADS that adds some dynamic to it. (not the skynet one, which is cool but still limited by the core SAM site quirks...)

yes for real, not even ai with their perfect radar see you 100+nm out. especially not when you are wheels down in the hangar still

Long standing DCS bug that you get residual rwr spikes from stuff thats all the way across the map. Nothing you can do about it. if an enemy AI locks a guy in air combat, you still get rwr spikes even if you are nowhere near that fight