Moonshine

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?

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