Moonshine

lol, incredible. and still only ground emitters

the auxiliary threat panel with all those buttons isnt even implemented according to the manual. these buttons cant have any effect on anything currently

i doubt it. enabling "Search" just rearranges the priorities, as in shows/hides such radars if the emitter limit on the RWR is already displayed. that should have nothing to do with Aircraft radars not showing up, spikes not showing up and active missile launches not showing up. Spikes and launches should always get highest priority instantly and therefore always display

i know it isnt a trackfile, sadly MP trackfiles are way too large. however as you can see on that recording of mine, i get spiked, RWR is NOT in priority mode, the spike although audible, the RWR is not even showing nails of an aircraft at all. also you can hear the RWR tones when new emitters are detected, however on the display they never show up.

OP is right. E3 and ground units show up yet i got spiked by bandits (4YA FOW PVP server) nothing showing on RWR OBS Recording as trackfile too large: https://drive.google.com/file/d/10ro1mjqL8V5jHAEemYxgGf-b-cacaRCM/view?usp=share_link

As per page 48 in this document: https://www.gichd.org/fileadmin/GICHD-resources/rec-documents/Explosive_weapon_effects_web.pdf Mk 82 aircraft bomb produces a peak overpressure of 117 kPa at 16 m from the point of detonation. The design fragment from this weapon is less than 20 grams travelling at 2400 m/s, and at this distance the natural fragments generated by the detonation will penetrate up to 32 mm of steel armour plate. This is not what we see in DCS to date. Not to mention DCS does not simulate fragmentation. So even if the weapon blast is correct to the numbers, it does significantly less in DCS than it should. for reference, this is what happens in DCS with a bomb twice as strong as the mk82:

press List-> Enter -> you will see that GPS is set to "Off" (even though your switch in the back right panel next to your seat is switched on) then press 1 (or any number besides 0 on the ICP) and it should turn it on. then you will get DL. at least that did it for me at times

i bet he didnt. but comments like these ruin all the work and research people have done. at the very least read the original post before jumping in with stuff like that...

before starting all over again, i encourage you to actually take a look and perform the same tests as performed in the comments linked here: https://forum.dcs.world/topic/305171-f16-look-down/?do=findComment&comment=5012201 and here: https://forum.dcs.world/topic/305171-f16-look-down/?do=findComment&comment=5016740 and here is a whole lot of data collection based off of such tests with all sorts of ranges, altitudes etc: https://forum.dcs.world/topic/305171-f16-look-down/?do=findComment&comment=5048120 and please dont take it personal, yet this comment is ruining a lot of work for people who have been actively trying to get ED to fix this over the course of this year now. just saying "it works for me" is not achieving anything without bringing up valid data to not only support this claim (and i doubt you did any of these tests) but also disprove everything else that people have reported.

if the discussion is purely about the strenght of the radar it might even be correct as it is, however the limiting factor to finding and locking stuff at reasonable ranges is the excessive lookdown penalty and how this is applied to the radar in DCS. no point listing it all here, all data and evidence of how absolutely borked it is can be found here: and here: instead of saying "correct as is" dear Newy, and therefore cause even more discussions, maybe list the items that are currently under investigation. by far it isnt correct as is and the evidence is there too.

patchnotes

Different issue, please open a new report for this otherwise none of this will get looked at

As said, its the fact that in the same scenario you get so many different results from one end of the spectrum to the other. This is what makes the agm154a as modelled in dcs so unreliable and therefore not worth carrying. it might well be that there is nothing wrong with the weapon itself but rather with the lets say „basic“ damage modelling of ground units, the absence of fragmentation damage, spash/shock damage from the blast itself. nevertheless the outcome is the same, inconsistent results which makes the weapon ineffective and unreliable

thats true, the compass rose can be moved on the F10 map but i guess not the 0; 0 coordinate

i dont know how many of these very informative posts you want to open but you might want to check this post instead before just saying "its trash"...

so to summarize: in NAV mode with FCR as SOI and in TWS mode, no contact on scope at all, pressing TMS right changes bearing and range information to a steerpoint. however no inputs for steerpoint change has been made at all with either the rocker switch, on the DED or on the HSD itself. That new bearing and range points to the default start location of the neutral bullseye and therefore the position of the compass rose on the F10 map at all times (even moving the neutral bullseye wont change it). Pressing TMS right a second time does not do anything. pressing TMS right a third time returns navigation information to the selected steerpoint as indicated in the DED. If the original steerpoint is inside the radar range, the white steerpoint marker can be found on the FCR. upon pressing TMS right the first time, that disappears, only to return after pressing TMS right 2 more times

tested it again. only occurs in NAV mode by the looks of it. and yes it always points a the compass rose. and that compass rose is the default bullseye location (where they are when you start creating a new mission prior to moving them) WS_TMS_right_Range_info2.trk edit: new mission, default neutral bullseye location. I am so confused

well, surely something is absolutely borked. no TMS input on the A-A FCR should change anything in regards to the selected steerpoint and therefore ownship navigation information. i get it, on the HSD you can select steerpoints with the cursor etc but on the FCR? especially in A-A radar. totally different for AG-radar thats clear

i am not sure, the compass rose does represent neutral bullseye. maybe test what happens if you move the neutral bullseye around. i am even more confused as how would anything thats done on the FCR affect the navigation to the selected steerpoint? and here we are in NAV mode, we did not lock any target that could switch symbology to the target range etc.. and even then the HSI should still give you info to the currently selected steerpoint... also i am not sure if this issue presists in A-A mode or just in NAV as i did my test in NAV to try to replicate your YT video and provide a track for it (to avoid "missing trackfile" tag)

that is definitely an interesting one. see my track, somehow it seems to show range to the Bullseye compass circle on the F10 map, even though blue bullseye is much closer.. i have no idea how to explain that. my approach: 1. tested behaviour shown in the YT video by OP. (TWS -> TMS Right -> range to STP shows distance as explained by OP -> TMS right again -> nothing happens -> TMS right again -> back to correct STP distance and heading). noted that he is on the ground, so i figured maybe "no-rad" due to weight on wheels 2. so i took off, gear up, tested again. still same issue. 3. tried to figure out where that 500+nm range comes from, checked map to see where bullseye is. found bullseye rather close, yet the neutral bullseye/the compass rose is right that distance away as shown in the plane Track is here as it is 1.5MB too large: https://drive.google.com/file/d/1jZSJyVOFYHbxG6rzji87hXynh4hGbWdY/view?usp=sharing

How is there no direct hit? check the top left picture again. There is basically no gap between the humvees at all it would be a miracle to not hit them directly.

might have to separate the AGM154 / BLU97B subject from the CBU105 vis drop subject in this thread otherwise chances are low that anyone will look at this.. bottom line as it is now, JSOWs, more specific the AGM154A, are not worth carrying

probably got a new device ID assigned. you can find all the files under: \Saved Games\DCS.openbeta\Config\Input you should see files with the name of your controller there. if you got 2 files with the same controller name, the ID number behind it might have changed. you can simply copy paste all content from the now "old" file into the one with the new device ID in order to restore what you had before. or in DCS you can go to the keybind settings, search the respective controller, click the dropdown and load file. then choose the "old" file with the old device id. usually easy to find based on the date of creation. before doing that, might want to clear all keybinds assigned per default (clear category) Device IDs might change when using a different USB port than previously or when updating the firmware of your peripherals

and the bombs are properly aligned as you do your first pass? (upon powering them on they need some time to align). Also please drop a track of your runs so people can try to figure out what else might have gone wrong

Not sure if that’s actually a thing in the viper. It is in other planes