Falconeer

1st post edited. Just works like it should on my end.

I just tested it and for me it stows the TGP when i set it to standby in MFD

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.

Typo, corrected in original post

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

I've never been in the Eagle cockpit, but this just doesn't feel like a true (cramped) Viper cockpit

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

So what's your point with posting this picture?

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?

Sure, here is mine All 3 screens, RWR and EIFI AOC G27G2U.lua

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

And there is the huge brightness difference when you export the MFD's to a second (identical) monitor. It's equally annoying

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)

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?

Maybe a stuck key? Or double bindings?

Cool, never new about that modelviewer

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

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

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

Cool I was an armament specialist on MLU birds, retired couple of year ago (and no, we never had Sparrows )

im not on VR, just Track IR

So do I. I have spend 20+ years with F16's Look.... the wording I choose where not the greatest and may seem harsh to some. (Also not native English speaking) But really is not my intention and I apologise if I offended you.

so you're not seeing contacs at all, while they are visible on the datalink? Is that what you mean? If so, it's most likely they are outside of the scan zone of the radar. Imagine the scan zone as some sort of icecream cone, both from the top and from the sides. You need to move the scan zone, so that the contact is in that zone.

Use the radar cursor control to slew the captains bars (I I) over the target and press TMS up to lock it up. TMS down to unlock

Wrong nose fuse for airburst setting used on GBU-38. The fuse mounted on the nose currently is a M904 fuse, which is a mechanical fuse. It can never measure height above the ground, so airburst setting in the SMS will never work. The fuse needed for this is the DSU-33 which is equiped with a doppler radar