Jump to content

Hobel

ED Beta Testers
  • Posts

    2642
  • Joined

  • Last visited

Everything posted by Hobel

  1. No not because of flare, at exactly 18:12 you hit the notch and hold it for a short time, the missle loses the lock at below ~25kts Vc. When the missle is exactly 2798feet away from you, you leave the notch and accelerate above 25kts again. we could now argue that the missle should now see you again, but it doesn't do that and I can't answer why.
  2. can you please upload a track of your scenario, otherwise we can't help you, you have also skilfully ingorised explanations from other users so far
  3. 4 https://forum.dcs.world/topic/277761-inner-wing-pylon-payloads/?do=findComment&comment=4836887
  4. You're right, somehow altitude has no influence, the bomb hits the target.
  5. Hm ok will have a look. I'll come back to this later. Can you send me a track of it so I can see your procedure?
  6. What you describe is what I mean, the "too long" comes from the jet(in dcs) , the bomb lands around the actual coordinate in a cep that pretty much matches your experience "~13m" Also altitude actually plays an important role in dcs. For example, everything around the center. GBU38
  7. As far as I understand it, this part is still WIP. This means that the GPS bomb will land exactly on its PP coordinates in the future. No matter if the f16 drifts 10-30m inaccurately. However, I wonder how TGP designations will work in the future if the f16 always has 10-30m drift, if you then make an exact designation on the target you give the bomb the drift of the f16 with + the bombs ~5m cep. Does this depend on the sub mode?
  8. is basically still WIP. PP bombs do not currently work accurately, before each bomb drop you have to redesignate the target for a good result Here is the whole discussion : https://forum.dcs.world/topic/347411-f-16-pre-setting-jdam-accuracy-steerpoint-in-free-server-after-april-patch/page/3/#comment-5447434
  9. my first wild guess is that the 2700RPM is to blame, try holding 2600RPM and see what happens then
  10. Negative, direct hits destroy light vehicles immediately, bmp2 etc need 1-2, that's fine. But what often happens are no direct hits and since the aoe is not even or hardly able to damage a jeep, the problem lies there
  11. 45 seconds life time, with that you can cover about 10km, sometimes more, sometimes less actually, you can laser targets up to 15km with the Apache
  12. I will test it again but in the last test the airburst against infantry has 20m more aoe with mk82
  13. Similar issue with the Blu97, to achieve an effect the bomblet must hit directly. The HE effect is sometimes close to 0 with light targets. Blu97 example
  14. I am more than aware of all the points you list. So I come back to the point, what logic should the ADI altitude direction interact with if the system it is connected to only works in 2D? the indicator as described should show the vertical direction to the waypoints/mark point, but since our ka50 only has 2D what should be fixed here? Either it was a superfluous display or there was an option to enter the alt in a certain way. In real KA-50 images/videos, for example, the flag is not visible.
  15. Your other points are valid and I cannot refute them due to lack of evidence. But what do you mean by that? I have also marked point 10, but as I said, it doesn't seem to be implemented ingame. Otherwise, explain how point 10 works or how the red flag( point2) goes away.
  16. a connection between the two systems would not eliminate the redundancy, it was even initially planned that the GPS would update the INS of the KA-50 every 300 seconds, but this was then rejected, there would be no disadvantage with the connection. If the GPS were to fail, you could simply fall back on the INS, so it would make no difference whether it was connected or not Please let's not deviate from the point, it's not about the INS here. It's about whether it was possible to enter the altitude in the real KA-50 or not. if the Ka-50 is used at high altitudes and a target point is at an altitude of say 1200m, the KA-50 has difficulties because the Shkval only slew to 0m and you have big problems finding the target. and currently, if you like, Alt can be saved and retrieved through an "exploit" and that is called "ME" the targets inserted there are saved in the KA50 with a height, i am also pretty sure that there must have been a possibility in the real Ka-50 to enter the height for the targed points, as i said without this option targed points become almost pointless There are also instruments in the Ka50 that indicate a vertical deviation that make no sense in the current state of the Ka-50. >>>
  17. How do you know that so precisely? and the other point is, how do KA-50 pilots use the target points if the helicopter has no way to enter the altitude? Target points become useless.
  18. Enter target points in the PVI-800. If you create them in the ME, the target will have the correct height. but in KA50 there is no option to add the altitude... which is very annoying... shortly after the KA-50III was released, you could still set it roughly like this, now nothing works anymore
  19. The biggest secret of the ka50 is still how the altitude is entered in the real ka50, because it doesn't work in ours.
  20. Against infantry ~20m more range Maybe soft armor too.
  21. Sure this is not a mark point?
  22. Don't nail me down, but I think I heard in an interview that it is theoetically possible that the passive search head could also recognize aircraft radars
×
×
  • Create New...