Jump to content

Devastator

Members
  • Posts

    89
  • Joined

  • Last visited

About Devastator

  • Birthday July 12

Personal Information

  • Flight Simulators
    DCS
  • Location
    Germany
  • Interests
    Gaming

Recent Profile Visitors

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

  1. just wanted to mention that this issue makes MIL/MAX takeoffs not possible
  2. One more point, is it normal not to have a sign here?
  3. yes looks like issue is there since the MT release..
  4. it is not for F18s only. Happens by all aircraft and turning off the SSAA fixes the issue
  5. I have the very same problem. ST version used, single monitor and my NVG has an offset to left side with a weird zoom (pictures attached)
  6. it shows the fonts are embedded. I created the PDF from an Excel file initially null
  7. anybody else having any font issues when converting PDFs to the PNGs via kneeboardbuilder? Somehow the English text which I have became Japanese when PNG is created..
  8. very interesting. Is jsow-a works in different way than the rockeye or that one is also always 1500ft no matter what you set?
  9. bypass not doing only single flare or chaff? In your picture shows double. Do we have a bug in DCS or the picture is wrong?
  10. idea is to fail the mission if you dont listen the LSO. LSO must be followed and you failed that, so failing the mission in such case is the expected result
  11. that weapon will work with any kind of settings which you have in VT section. If the settings would not work, why would they have that possibility in first place right? VT adjusts the height where the bomblets will spead out. Higher means more area will be covered but less intense explosions as the amount of bomblets per area will be lower than a low opening setting. Try default VT setting by a BUK site and then compare the results with a low opening one like 900 or low. One of them will destroy the launchers the otherone will only do little damage
  12. I had the same issue when I launched from CAT3 after a usual startup with the usual start up checks (firetest, probes etc.) Blade took off and decide do defect to Syria (proofs are attached for the courtmartial) ! When I took of from CAT2 (wihtout any start up checks to speed up the whole process) all worked fine. So either the cat is playing a role, or some trigger have some short time limits to achieve and a longer startup causes the issue
  13. I used 1200 before and didnt work. So I assume 1500 is the one which the trigger cares
  14. m04 is not a case3 launch but the brevity is still used there
×
×
  • Create New...