Moonshine

yes you can. go to the DEST page on the DED (List -> 1) or simply change to Steerpoint 21-25 using the STPT page (4 on ICP) and then you should have Waypoints 21-25 that can be entered as MGRS (dobber right "SEQ" to switch between LAT-LONG and MGRS) or here and older video prior to the implementation of the DEST page

okay in all fairness it was 2 hits. (12.7mm x2). still veeeery far from "shredded" and even further away from how this fuselage looks

the tank lining should seal even a 20mm hit that passes straight through the tank leaving an entry and exit hole (lets say AP ammo, not APHE). currently even 7.62mm creates faster fuel loss than a boom tanker could fill up using pressure to get fuel in fast.. funny how thats still an issue needing evidence after about a year. i can not imagine the fuel loss from such a hole to be faster than a refuelling boom tankers fuel transfer speed. Not to mention that the tank is not just a simple bucket but has internal segments that would limit the complete loss of fuel due to damage to one cell. you also lose all fuel if an external tank takes a hole until you figure it out and jettison it. wonder how that works i get that the viper can not withstand the same amount of damage as a A-10 and thus is more fragile than other airframes. but still it isnt made out of cardboard or paper

so in the game files the proximity fuze is set to 7m (roughly 23feet) yet according to page 159 (11-7) in the p-825 manual, the radius should be 50 feet (15.25m)

repeatedly pressing TMS aft makes the tgp "jump" even though it shouldnt, also notice the coordinate display on the TGP page top left change everytime TMS aft is pressed. TGP_CZ_jumping.trk

as you can see, i have full internal fuel, full centerline bag, 9100lbs of fuel. with a fuel flow of around 8000lbs PER HOUR OF FLIGHT with the current throttle setting, the EDR still tells me that i have more than 2h of flight until BINGO (2000 lbs) sadly ill be empty in half the time. this does not correspond to the intended behavior described in the referenced manual on the referenced page by SteelFalcon. the function in DCS is not correctly implemented as described in the manual. Edit: added second track with no bags installed, only internal fuel, used AB to loose some gas at first, then set the throttle to a normal position and letting the fuel flow stabilize at around 7100lbs per hour. still EDR tells me that i can fly more than 1h30 with the current fuel until i reach BINGO. nonsense EDR_BUG.trk EDR_BUG_1.trk

hoping this gets patched one day... at the moment it does seem to be 5mils instead of 3/9 as Frederf described here:

let them provide at least one correctly functional Aim120 first...

+1 bump

can confirm, something with the TD box slewing (in VIS mode) is broken. could not get the box placed on one of the hangars no matter what i tried. while i did get it to slew up, it is nowhere near accurate plus automatically starts moving down again upon releasing the slew. incredible how broken everything is in the viper at the moment. basically cant really use it at all other than cruising around looking at the landscape. shame. Edit: added second track verifying that HUD is SOI. TD Slew works fine prior to hitting TMS up the first time (which then would let you finetune the position of the TD box). however this looks to be very inaccurate and buggy. JDAM_VIS_TD-BOX_slew_bug.trk JDAM_VIS_TD-BOX_slew_bug_1.trk

can confirm, seems to be off.

maybe its in one of those already: both of these have something to do with the pod being inaccurate

indeed two BUGs related to the rudder, not wishlist items. little ridiculous how such things are treated.

and here is my attempt trying to set OA1 and OA2 with the TGP. (as described here by wags: https://www.youtube.com/watch?v=SnqFHMok-hA) upon designating OA2, the position of OA1 gets lost and overwritten by OA2 or vice versa.. (in the end OA1 and OA2 end up being at the same location) also note that none of those triangles indicating the OA location ever show up in this method in the current OB build (unlike in wags video). after trying that, i end up manually entering OA1 and OA2 as you would for a pre-planned pop-up attack (or as you would load in via Data Cartridge). triangles show up, yet OA1, despite having set an altitude of 3800ft, seems to be below ground. the TGP however seems to look a what i presume the correct OA1 position in the air somewhere. however, despite the sighting option being set to OA1 (left MFD OSB 10), the SPI (which is now OA1), the target box is still on the waypoint and not on OA1 location. also something wrong there. watch towards the end of my track, you can see me trying to find the OA1 location. as i cant find it anywhere i re-enter all its data again and discover the triangle somewhere below ground all of this worked perfectly fine prior to the last minute christmas update. Offset-Aimpoint-location_bug2.trk

no need for this, already reported here:.....

even though you did power the gbu31 on, you did not wait for them to align. upon taking control of your track right as you fly above the target, SMS page still says "A4" meaning they are still aligning. sadly switching MFD page even though you are in the same master mode (AG for this one) does not finish the alignment in the background. you need to have the SMS page selected until the bombs are properly aligned otherwise it just "pauses" the alignment process (pls fix ED......). also do you really want to drop GBU31 that low? it isnt a high drag bomb, the risk of killing yourself is rather large..

indeed they are broken. tried to set up symbology for a pop-up attack using VRP, PUP and the OAs for visual references. the altitude of the OAs always seems to reset. even before i typed anything in the OA1 page, there was already some values there for no reason at all (did not slew any radar, tgp etc. nor did i cycle the sighting options at all) plus the altitude reset. watch for yourself. repeatedly typing in the desired altitude did not achieve anything, instead it reset either to 0 or to negative values for whatever reason. unuseable @BIGNEWYcan this be moved in the bug reports section? Offset-Aimpoint-location_bug.trk

and what about STT? shouldnt there be a burnthrough? at close ranges a jammer should be a disadvantage rather than an advantage as it makes you a huge target...

the question is more; does the AGM 154 also incorporate the same guidance system like the WCMD 103/105? assuming due to its larger stand off range it should be even more affected by wind along its flight path so some system to make the needed adjustments must be present. of course it hits bang on with 0 wind, but 5-6m/s wind should not be the reason why you dont hit anything anymore

strangely it is a GPS guided (glide)bomb and should it not like the 103 and 105 should adjust for wind?

When selective jettison is done (on the SJ Page on the MFD) then hit the Wpn release button (pickle button) to drop selected stores the „jettison“ button is the emergency jettison and will always get rid of all stores except a-a missiles

Just fly along the yellow threat circle if you have one on the HSD. And if there isnt one, when you get spiked you are too close to the not yet known location of the sam, so back out a bit, try again until you have found it. alternatively, let it shoot and follow the smoke back to its launcher. But for that, one doesnt need a HTS pod no need for a snap and then immediate shot but that very much depends on the mission environment and limitations

To avoid confusion: Initially Steerpoint 2 is your SPI location, so your TGP looks exactly there. By then using the HAD and locking on to the emitter, the SPI changes to where the HARM targeting System THINKS the emitter is and as the HARM targeting system is now dictating the location of the SPI, the TGP will slew automatically to that location as long as you hold the lock on that sam site on the HAD. the accuracy of this location is indicated in the HAD as PGM. PGM 5 is the lowest accuracy, PGM 1 the best. in order for the number to drop, flying an arch around the assumed emitter location helps the triangulation to narrow it down - hence dont fly in a straight line to it. normally you will get PGM roughly down to PGM 2, in which case finding the SAM site within your TGP field of view should be possible. in case i misunderstood your question, please post a trackfile

Regarding the ripple function there is another post open and the issue has been forwarded according to NineLine. Post in question:

At the very least it gets looked at. SMEs will surely be able to answer that. The current implementation is equally just a conjecture as nowhere it says that this function is limited to lau117…all it says is that you need mavs on both wings since it fires one per side and a maximum ripple of 2 missiles total. what i dont get about your statement, why would this be listed in the patchnotes if now we need to bring up evidence to even support the feature YOU listed in the patch as „fixed“, as in what exactly did you fix? It wasnt there before the patch in the first place, how could it possibly have been broken?