thegipp Posted Tuesday at 11:56 PM Posted Tuesday at 11:56 PM I think the JDAM ripple has changed in the last update (last week, not today's hotfix) for the F18. This is the setup: - 8 500lb JDAM loadout - 4 pre-planned targets - PP1 selected on each station - QTY activate all four stations Previously, I'd hold the pickle button (you have to hold it otherwise it would only release one) and the 4 stations release with a slight delay between them. And then, release the pickle button without any need to be careful about holding it too long.... you get where I'm going.... NOW, I hold the pickle button and if held any longer than the time it takes to pickle 4, the sequence continues with the next 4 bombs on the SAME PP1 targets. I was used to not having to count the bomb releases and quickly release the pickle button. I don't have a trackfile for this (have never made one before). I'd appreciate a second opinion on this if someone has the time to experiment.
rob10 Posted yesterday at 04:49 AM Posted yesterday at 04:49 AM (edited) 4 hours ago, thegipp said: I don't have a trackfile for this (have never made one before). I'd appreciate a second opinion on this if someone has the time to experiment. You don't have to "make" a trackfile, just SAVE it from the debrief window when you end the mission (it's an option along the bottom). Best to keep it as short as possible and ideally for the devs if it's on the Caucuses map. A track would be very helpful as this feels like user error more than a bug. You should need to press once for each release in PP mode (not hold) assuming you are dropping them on different targets. Edited yesterday at 04:53 AM by rob10 1
ED Team BIGNEWY Posted 22 hours ago ED Team Posted 22 hours ago please include a track replay thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Enrico-Pallazzo Posted 14 hours ago Posted 14 hours ago (edited) In the hopes of determining if this change was intentional or an inadvertent bug, I've put together a very quick trackfile demonstrating the behavior OP described. I used TOO mode as it was quicker and easier to set-up for this example, but the difference in pickle behavior is identical regardless of mode selected. With eight GBU-38 JDAMs loaded and eight different waypoint targets designated (4 for TOO #1 & 4 for TOO #2) and all four pylons selected under the QTY OSB after mission designation. In the past, in this configuration, if you were to press and hold the pickle button, four bombs would drop (one from each pylon) and strike the four separate designated targets. The remaining four bombs would not drop. There would be a pause allowing for a change in targeting (perhaps to TOO #2 on each pylon to strike the remaining four targets)... or you could press and hold again to drop the remaining four bombs on the same four TOO #1 targets. With the last major update (2.9.21.16362) this behavior changed to what you see in the attached trackfile... if you press and hold weapon release it will cycle through each station a second time without any pause and drop all eight bombs... but those eight bombs are directed at the same four TOO #1 targets. If you roll back to DCS version 2.9.20.15384 you can experience the old behavior with the pause after the selected pylons have each dropped a single bomb. Obviously this can be mitigated by just pressing and releasing one time for each bomb drop, but since a change was made, it's worth getting a clarification. F-18C_Ripple_Test_01.trk Edited 9 hours ago by Enrico-Pallazzo
thegipp Posted 9 hours ago Author Posted 9 hours ago (edited) 7 hours ago, Enrico-Pallazzo said: In the hopes of determining if this change was intentional or an inadvertent bug, I've put together a very quick trackfile demonstrating the behavior OP described. Thanks for posting the track file. I've replayed it and it shows the same behavior I explain in the OP. Now the question for the developers is: Is this new behavior how it should have always been? or Is this unintended - perhaps somehow caused by the fix made to JDAM QTY in last week's update? Edited 7 hours ago by thegipp
Recommended Posts