Flapjacks

Not sure if my issue is part of this 2.9 problem or not. I've been getting fps drops for a few seconds down to about 15 fps, then it'll clear up for a few seconds then drop again. Is this the same thing that others have been experiencing? It happens in both SP and MP and on multithread and regular Open Beta. I don't have any mods installed and I've run a slow repair, deleted the fxo and metashaders folders, as well as disabled hotplug. Also, not sure if it matters, but the framerate counter flashes rapidly between GPU and CPU bound sometimes. I would've added a dcs.log file but I don't see it in the log folder (in saved games/dcs.openbeta/logs), just compressed dcs.log folders. Anyways, I hope someone can tell me if this is part of the 2.9 bug or if I have some hardware issues or something. Thanks. DxDiag.txt

Mine lose speed (when they do bug) when dropped before getting to IN ZONE distances and never reach their targets. When dropped within IN ZONE (at least the -54's, I haven't tried the -38's yet with this part), they fly overhead/past the targets then try to angle back and hit them. When that happens, sometimes they hit and sometimes they don't.

@zlm63682 I tried the GBU-38's and they did good for a while but ended up having the same issue as the GBU-54's and -31's.

Yeah, GBU-54's are what I've been using, although I also seen it happen with the GBU 38's and 31 1/B before the patch and I saw it happen with the GBU-31 penetrators yesterday. I'll try out the -38's again and see how it goes.

Thought this was fixed with this patch but it's still broken. Although sometimes the bombs from L1/R1 fly correctly, so it's not as consistently bugged since the update. Anyone else still getting this problem?

Not sure if this is a bug or the function just isn't implemented yet, but changing the laser code for the GBU-54 on the sensor page doesn't seem to actually change the bomb's code. Also, it doesn't reflect the change on the kneeboard if it's suppose to. GBU-54 Laser.trk

I just tested with the -31v1 and have the same result as the -38 and -54 in that they all fall behind when dropped from the rear station but the -31v1 sometimes does make it to it's target when dropped in IN RANGE distances unlike the other two. Interesting find.

Auto Aquisition aft (while in command of the tpod) to return to designated target and Boat Switch Aft to undesignate.

yes

Make sure steer mode nav is selected while autopilot is on. Also turn off auto sequence on HSI if you're wanting to skip all the points in between.

Depending out which route you had the app input them as (1/A or 1/B), you would just type in which sequence point (i.e. 1A, 2A, 1B, 2B) you want to steer to on the scratchpad and click push button 10 on the UFC.

Maybe it's the same stations that's giving me problems thats causing your problem? Out of curiosity, could you try the run again without using stations L1 and R1? These two.

So, I just tested without loading info to the two bombs on back, stations R1 and L1(FYI another bug, can't select the bomb on L1 until some other bombs have been dropped) and it looks to be working. Going to do some further testing, but so far, I've dropped a group of 4 and a group of 6 and they all hit their respective targets. Further testing, after dropping the first 6 with no problem and 3 remaining bombs, it appears that something is up with both R1 and L1. Both bombs from those stations would lag behind. They still seem to hit their targets if dropped IN ZONE, albeit they kinda overfly their target a short bit then angle back towards the target.

I haven't seen anyone else with this issue but almost every time I pickle multiple jdams, the last one falls way short of it's target. I've experienced this with gbu 38's and 54's. It happens no matter how I designate the targets, whether it be through the tpod, HRM, or target point transfer from nav. I've tried dropping in groups of 3, 4 and 6 and it's always the last bomb of the bunch that falls short. I set direct mode, step and N/T fuze. Anyone else having this issue? UPDATE: It's not the last bomb released. It's bombs dropped from stations L1 and R1 on the CFTs. Jdam.trk

Thanks NineLine for everything you've done!

It's an 8 degree blind spot to either side of the nose, just the way it is, nothing you've done wrong. Also, no way of scrolling back through sequence points. Either scroll forward till you get to the one you want or input the number on the scratchpad and click push button 17 on the a/g MPD.

You can slew that line around when the cursor is in TGT with auto aquisition aft and TDC to slew, to get a bearing in relation to other things. I often use it if I want to ripple cluster bombs in a line between targets. The bearing it shows is in true north and not magnetic as it should be though.

You can do that in nav mode with the HSI, get lined up and then switch back to a/g mode. You'll need some type of sequence point to input into the UFC for the HSI to go off of though. You would input the target point into the UFC PB 10, switch to nav mode, go to your HSI and hit PB 6 twice to get into CRS (course) mode. Then punch in the bearing at PB 14/15. You'll get symbology like TACAN.

JDAMS coming in a couple weeks. From Razbam's discord: "Added: JDAMs. NOTE: The weapons are still a work in progress. They are not synchronized for Multi Crew in this release."

click the black and yellow striped emergency jettison button (short press, not press and hold) and it'll work again.

GBU-54

Thanks as well for checking on this and all the testing.

They do have release options set up, but in auto mode the accuracy is off for the time being (for all unguided bombs) if dropping a single bomb. If set to ripple single, and setting the BOT to 1, it does good. Or if dropping a single bomb, putting in a 10-15 degree dive when the release cue starts falling works as well.

In the track I provided, my cbu-97 dropped as accurate as it could be and only did a little over half damage to a T-72. If it were the T90 it'd have been even less damage done. Also, what about when we ripple these bombs? There's no way to get all 13 of the bombs I can carry to hit precisely on each target. They aren't guided weapons, so I don't see why we're expected to get pinpoint accuracy in order to take out a armored unit. If the change is left as is, I won't see a point in equipping these bombs if I can't count on them to do the job. Which sucks as a F-15E pilot since most of our ordinance choices aren't viable at the moment. Please ask them to reconsider this change.

Thanks for checking and the update!