Bersagliere81 Posted May 14, 2020 Posted May 14, 2020 My bombs always fall short for about one "salvo distance" with impact interval selector set to 15. QFE is properly set, no ternav errors and no wind. It appears I can get some good result if flying 150m (radar altimeter readout), M0.85 and aiming with the dot rather then between the dot and circle. But still it barely hits the target with the last bomb. Similarly, I had the same issue with low drag bombs in DYK mode, however inputing 221000 solved the issue (although I thought it should be set by default). Anyone knows what I am doing wrong? | A-10C | MiG-21bis | Hawk T1.A | L-39 Albatros | F-5E | Ka-50 | Mi-8 | NTTR | CA | SU27 | M2000C | F-86F | AV-8B | F/A-18C | Mig 15 | Mig 19| Specs Intel i7-9700k msi GTX 2060 Gaming Z msi Z390 Gaming PLUS 16gb RAM Hotas Warthog
john4pap Posted May 16, 2020 Posted May 16, 2020 I tried a high drag run the other day and indeed bombs fall short. It was ok about a year ago or more but now it seems broken. There are some other discussions from a few months ago where people reported it been fixed but it appears it isn't. I don't think there's much to do wrong as long you set the correct qfe and maintain proper altitude and airspeed. So, it appears that it is a bug. Is 221000 the code for disabling the calculation for moving targets (I can't remember how it's called). If so, yes I'm almost certain that it is stated in the manual that it should be off by default. I haven't been flying on the Viggen for almost a year now since I got tired of all these little bugs here and there (some were not bugs really but inconsistencies in the manual) and patiently waiting for its polishing :) Sent from my SM-J510FN using Tapatalk
Bersagliere81 Posted May 16, 2020 Author Posted May 16, 2020 So after few tries, I found QFE is the key to solve this issue: High Drag Bombs add +3 QFE Low Drag Bombs substract -3 QFE With these parameters I never miss a hit | A-10C | MiG-21bis | Hawk T1.A | L-39 Albatros | F-5E | Ka-50 | Mi-8 | NTTR | CA | SU27 | M2000C | F-86F | AV-8B | F/A-18C | Mig 15 | Mig 19| Specs Intel i7-9700k msi GTX 2060 Gaming Z msi Z390 Gaming PLUS 16gb RAM Hotas Warthog
john4pap Posted May 17, 2020 Posted May 17, 2020 Yes, that was suggested a while ago in the forums. I can hardly call it a solution though. Sent from my SM-J510FN using Tapatalk
LastRifleRound Posted May 19, 2020 Posted May 19, 2020 I think it's related to DYK pipper now signalling the beginning, rather than the middle, of a string. This is an undocumented change and the CCIP seemed to break around the same time. PLAN is just about perfect now. However, DYK is bang on if you use the pipper as the beginning of the string, and you're saying you're falling short, not long, so I suspect something else is at play. Do you have a track? Are you on Open Beta?
Recommended Posts