Moonshine

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

^ this

You need to be in point track or area track to slew the pod. also if you are in CCIP bomb mode or have the gun selected, the pod is slaved to the pipper location and cant be moved. if your pod is in A-A mode it cant be slewed either and is slaved to the FCR

Yes we dont know the config however, i highly doubt that they fly anything else than clean config with a passenger on board…

This. absolutely ridiculous as it is now. Like a paper plane. I understand it isnt as robust as the a-10 but please..

any news on this? currently impossible to hold knife edge with a clean jet without the nose dipping down towards -5deg even with full rudder input. the video posted by 777coletrain suggests a different behaviour in the real jet than what we currently have in DCS. if you listen to that conversation its quite obvious. plus tracks have also been posted...

this. SPI is SPI, no matter how the SPI was set. the mav does not know the difference between VIS and PRE, these modes are only methods to set the SPI, has nothing to do with the mav itself. after setting the SPI, the mav will then slew to that SPI and thats it. so yes, if the mav slews to the SPI in PRE as the plane starts turning towards it, so should it in VIS the only mode you have seekerhead-limits is BORE as there you set the SPI with the mav itself using the HUD Boresight cross or the mav WPN page and if it would really be limited by seekerhead FOV, then it would even have to take into account which wingstation is used (left or right). makes absolutely no sense at all

Any news on this? seeing the topic still has the "correct as is" tag, yet the last comment and the info @KlarSnow brought up suggests otherwise...

there are multiple reasons for the RWR going silent 1 - you are in the notch, missile cant see you anymore - RWR silent 2 - you are in a bank so that the missile is in the blindspot of the RWR (directly below you or above you) 3 - missile lost track on you and cant find you anymore when defending a Fox 3 (Amraam for example) if it starts again shortly after your maneuver, chances are you are no longer in the notch and the missile has reacquired you and is tracking again or a new missile has been fired. usually you can see a radar guided missile on the RWR as "M". if there is only 1 M showing and the M is blinking, chances are its the same missile that has found you again. if there is a second M showing and blinking, a new missile has been fired. if the M is on the RWR (not blinking) but the RWR is silent, the missile does not see you but your RWR detects the missiles radar beams

this is just wrong. it does let you toss the bomb further than you could during a level flight release, which means you might actually survive and egress or not get in range of enemy air defense. it also allows you to lob bombs over mountains, hills or other terrain. yes it is as it is supposed to be. The DLZ indicates the range for the max pull up all the way to the minimum pull up. the end of the DLZ (bottom line) is the level release.