Jump to content

Falconeer

Members
  • Posts

    613
  • Joined

  • Last visited

Everything posted by Falconeer

  1. And thats: Gaps between pylons and wing - Fixed In RL, the pylons and wing don't touch each other. The weapon pylons have bushings on top which create a smal gap between the wing and pylon
  2. Hello, i started to go through the training missions, but this mission is constantly freezing. It hangs when it says "World Preload 1/60" at bottom of the screen. I then need to kill the application and restart DCS dcs.log
  3. Falconeer

    GBU39 SDB

    Thats not what i was saying... Those were specific demands which came later and is something different than the fact the F16 was designed to be a light weight fighter jet in the very begining The USAF and (later) EPAF countries later decided it needed to be multirole. You said you didn't feel like it to be true multirole in a thread where SDB's won't get added But we are getting a littlebit off topic
  4. 1st post edited. Just works like it should on my end.
  5. I just tested it and for me it stows the TGP when i set it to standby in MFD
  6. Falconeer

    GBU39 SDB

    The black radome was 1 of the first things that changed from block 1 to block 5. Pilots complained it was to easy to spot the VIper in A-A engagements.
  7. Falconeer

    GBU39 SDB

    Typo, corrected in original post
  8. Falconeer

    GBU39 SDB

    See Northstar's post. He explains it very well. The original design was a light weight fighter jet. It envolved to a multirole plane, by all the upgrades it received. The Danish F16's were not the first F16's build, they are Block 15's? First production model was the Block 1 with a black radome. Which meant they already received updates to a new standard. The F16 became "multirole" with the Block 15 upgrade in which they received a new radar and increased capacity for intake hardpoints So the Danish bought aircraft that had already have some AG capability. This was further enhanced with the Operational Capability Upgrade (OCU) and later the Mid Life Update (MLU), which brought them to the same standard as USAF Block 50/52's. The EPAF (European Participating Air Forces) F16's were in the first place intended to replace the F-104 Starfighter and the Danish F16's were also build by SABCA Belgium
  9. I've never been in the Eagle cockpit, but this just doesn't feel like a true (cramped) Viper cockpit
  10. Falconeer

    GBU39 SDB

    First, the F16 was never intended to be a multirole fighter Second, being multirole has nothing to do with the ability to drop smart weapons
  11. So what's your point with posting this picture?
  12. Hello, I run a dual screen setup to export various viewports on the second monitor, which works great Except for the RWR from various modules..... When those get exported, you'll only see the threat id number/type, but without the threat rings, which makes judging priority's targets quite difficult at times. It would be very usefull to export the RWR as a complete instrument for better SA. It this something to be added in the future for us multiple screen users/ cockpit builders?
      • 1
      • Like
  13. Sure, here is mine All 3 screens, RWR and EIFI AOC G27G2U.lua
  14. Same here. Sat in dozens of Viper cockpits and the MFD's are far better to read (and seem bigger) than in DCS. Based on my own experience, i think you're sitting to far back in the seat in DCS, due to the incline seat modeling. In RL, the UFC is almost in you face and i really dont have that feeling in DCS. It's just to far away
  15. And there is the huge brightness difference when you export the MFD's to a second (identical) monitor. It's equally annoying
  16. In the first couple of seconds, the bandit you are trying to lock is under the search zone of your radar. He is flying between 500 and 1000 ft above ground and you radar is scanning in the ranges between 17000 and 50000 ft. (the 2 numbers next to your radar cursor) Your radar simply doesn't see it and the reason you can see it, is because its a datalink target. Later on, the same thing happened with the second target. He was outside of the scan zone of your radar To fix this "problem", you need to lower your radar antenna to match the targets altitude Imagine the radar search cone is like a flashlight in the dark, you need to point the cone over a target to see it After you matched the targets altitude, the radar needs a couple of seconds to build up a track in TWS, then you can lock it (solid square)
  17. I never noticed in the situations i had a bad alignment that it show the "original" location like in your screenshot. To me it looks like a SPI slew of some sort did you fiddle around with the TGP by any chance?
  18. Cool, never new about that modelviewer
  19. Then we need multiple models of gbu 38 ingame, depending on how you want to use the bomb and on what target * M904 Nose Fuse * Conical Nose for more penetrating capability * DSU 33 for airburst function
  20. Why is this on wishlist now? The current model of the gbu38 uses the wrong fuse for airburst. It's not a request, but a bug. A 100% mechanical fuse (m904) has no way of knowing its height above ground used for airburst. That's what the doppler radar is used for
  21. We never had the AIM-7 pylons, only the block 15 launchers and later the Lau-129. The block 15 launchers could be quite problemetic at times. Mostly electronics, but nothing a good bang with a wheel chock couldn't fix
  22. Cool I was an armament specialist on MLU birds, retired couple of year ago (and no, we never had Sparrows )
  23. im not on VR, just Track IR
×
×
  • Create New...