Jump to content

Khallimero

Members
  • Posts

    30
  • Joined

  • Last visited

About Khallimero

  • Birthday 09/19/1978

Personal Information

  • Flight Simulators
    DCS
  • Location
    On your six
  • Interests
    Engineering
  • Occupation
    Occasional glider pilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Never noticed it before. Maybe I'm not looking behind too often... Anyone knows the purpose of this ?
  2. Hum...my bad. Here is a "real" picture. Looks like the "band" is missing from the external view only, and the internal view is correct (at least now, if it wasn't before)
  3. Hello I'm flying the A-10C vanilla (not the A-10C II version, although that module is also installed), and I just noticed something in the middle-back of the canopy that looks like the beginning of the Scorpion helmet position sensor found on the A-10C II. Pretty sure that was not there before the december 2.7.9 patch. Moreover, it doesn't appear on the external views.
  4. That's why you can (and should) change the desired impact angle in the weapon's profile, and it should work accordingly. That works for the GBU-38, but the GBU-54 doesn't care about it. At least it should use a less steep angle by default, so it wouldn't miss a stationnary target with the default value. F-16 and F-18 use 60° angle by default (edit : for GBU-38), and there is no issues with them (as far as I know).
  5. Just feeling beeing ignored This looks like a serious issue to me. Here is another track where the bomb completely misses the target, due to its odd trajectory. (I strugled locking the target that time, but I wanted to be sure it was locked before droping the bomb) GBU-54-2.miz
  6. At least at flight rotation speeds. This will prevent the shadows from flickering inside the cockpit (as seen below at 0:10)
  7. Would be great if it becomes a native option in the game. At least for the cockpit view, to reduce the blade shadow flickering.
  8. They should be grounded, it could damage the optics.
  9. Any value other than the default 0° seems to work. 60° is the default value for the F-16 (and maybe the F-18 too, if I remember correctly)
  10. Maybe GBU-54s in GPS mode suffer the same issue. (sneaky topic update ) But as far as I tested, GBU-38s seemed to work fine once you changed the default 0° impact angle. Unlike GBU-54s.
  11. erf, maybe already reported, on the second page, here : sorry...
  12. Hello I may have found an issue with the laser maverick and its estimated flying time. The theroy is : after designating a target with the laser, the maverick locks on that point, and the TGP estimates the missile flying time. When the missile is fired, the countdown begins, and the laser automatically shuts off few seconds after it reaches 0, because the msiile should have reached the target. The problem is that when fired from long distance (7nm in the track I provide bellow), the missile lofts, and it takes longer to reach the target than the TGP estimated. And the laser shuts off before the missile reaches the target. This is not an issue with the laser overheating. The issue is in the estimated missile flying time. Laser maverick.trk
  13. I tried to reproduce your results with the GBU-54. Looks like it also depends on when you release the bombs. If you release the GBU-54 as soon as you are in range, the bomb will not have enough energy to reach the vertical of the target, and it will actually hit the target with an angle smaller than 90°. But if you wait and drop the GBU-54 from the middle of the Dynamic Launch Zone (as I did in the track I provided with my first post), the bomb will go above the target, and then dive vertically. Regardless of the impact angle in the weapon profile.
  14. Agreed. My first suggestion is only to make 60° the default value for the A-10, as it is for the F-18 and the F-16, instead of 0°. Agreed too. That's my second point. (strange, especially because it works fine for other GPS guided bombs)
×
×
  • Create New...