Moonshine

i did get an answer yesterday that it has been forwarded to the team. now to the usual, sit and wait patiently

it is pretty bad. i was looking forward to this patch with various long standing bugs being fixed, however so many of the base functions are so broken now that it is really not worth playing. pretty sad. RWR as a very core part of this aircraft given its SEAD/DEAD role, Cursor Zero, Mav Boresight and Ripple... while the features are technically there, most of them require a weird ass workaround for it to somewhat work (and yes i get it, its a BETA) but in this state it really isnt playable. yes it flies but thats about it.

sent 9L and Newy a PM with all the documents needed. fingers crossed...

so if we read the manual wrong, why is this point even listed? ripple mavs with lau88 has never worked in DCS so far, the feature was never implemented and now it should be fixed? would one fix a thing that can not have been broken because it was never there in the first place and then list it in the changelogs as "fixed"? seems very unlogical. newys claim that there is no evidence is completely wrong. the only time you cant shoot 2 mavs from Lau88 at the same time is when you only have one station with mavericks equipped. I dearly hope that this gets looked at and not lightly brushed off as "need evidence" or "correct as is". no manual says you cant ripple mavs from lau88 specifically. only says you have to have mavs equipped on both wings in order for ripple to work. (cant shoot 2 missiles from the same station at the same time)

Funny, then why is this in the changelog? so at the very least 2 should be able to be shot at once, yet for that we need a ripple option… I assume you will need lau88 on both, left and right wing for this to work as firing 2 mavs from the same station seems rather stupid.

Guess we have some sort of a workaround. Lets hope that wont be the case for long.. nice find tobias

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)