Beamscanner

remove your DDI/AMPCD export mods. ED has added these veiwport exports to the base game. no need to change any font size, etc.. just change your monitor config to say "Center_MFCD" instead of "AMPCD". You still need an export mod if you want the RWR, UFC or IFE on a second monitor.

my test had max ageout (32) and at times a narrow scan centered on a target. still no trails.

still completely broken.. No brick trails.. bricks are acting like trackfiles and reposition themselves with each detection.. noBrickTrail.trk

downloaded the latest update. I now get a Microsoft .NET Framework error. anyone else getting this? EDIT: fixed it..

This is correct. In RWS, the scan center will not follow your cursor like it does in the Viper. But, you can manually adjust the scan center by depressing the TDC.

I think this should be a priority before moving on to new systems like the ATFLIR.

Im curious as to how this was "Fixed Internally" four months ago, but has yet to make it into OB. EDIT: the problem exists with the F-16C as well

This bug has been around for years.. It occurs when you use vertical displays (hence why BIGNEWY didnt get the bug). https://forums.eagle.ru/showthread.php?p=3631456#post3631456 https://forums.eagle.ru/showthread.php?t=226340&page=5&highlight=blurry https://forums.eagle.ru/showthread.php?t=224265&highlight=blurry

any headway on this?

The answer is right in front of you in the picture you guys posted. Notice that its showing the F-16 detection ranges for Low PRF and Medium PRF modes. These waveforms dont have nearly as much gain as High PRF waveforms(higher duty cycle), as not as many pulses are integrated. The below image is an Westinghouse advertisement of the improvements in detection range from v1 to v9. note the new "medium duty transmitter" for the "ERS" mode in the v9. keeping in mind that "all aspect" implies range gating (ie not traditional HPRF), ERS likely achieved greater detection ranges with the MPRF waveform by increasing the duty cycle.

other TGP questions: 1. Does the pod have rate slew? (ie can the pod be directed to slew at a constant inertial rate. where the TDC inputs are used to accelerate/decelerate this rate.) This would be useful in an orbit, or against moving targets 2. Is it necessary to switch to AREA track before going into the contrast tracker? It seems like an unnecessary speed bump for a billion dollar military contract.

Very disappointed with the vote.. The retro red display looks so much cleaner than the bold text LCD...

Leatherneck Simulations Ground Mapping WIP With your efforts going into the simulation of analog pulse radar, it would be nice to see an F4U-5N (equipped with the APS-19 Radar) option in the future!

Not sure that I'd want DEKA to program the F-15E module. The DEKA radar code has tracks literally disappear and reappear in order to move on screen. No extrapolation of any kind is provided. That's not how "Tracking" works. That's just RWS with vectors.

Not sure about the SA page. But I have seen it go both ways for D/L contacts on the Radar page IRL. (i have proof) I think IRL its dependent on the DCLTR setting.

Yes.. ignore the v9 and read the v5 capabilities in the image. the image shows what the detection performance for the various modes available... The v5 could do all-aspect in RWS and hot aspect in VSR.

Not all radars are capable of the same things.. This image shows that the 68(v5) can do "all-aspect" in RWS, and hot aspect in VSR mode. If you know radar theory, you'll know that certain PRFs are good for all aspect and others are good for hot aspect..

Below is an illustrative explanation on how RAID generally works in air-to-air radar. Source: Basic explanation: Normal search modes: Using RAID:

Economically speaking, the new aircraft was likely chosen to leverage recent and upcoming investments by ED. This includes: - Modern Avionics (Radar, HMD, D/L, IFF, etc) - AG Radar API - New FLIR rendering - New maps (Syria, Afghanistan) - Multi-seat (ED investing into multi-seat Huey) The obvious answer is the AH-64D Longbow Apache ED reps have stated that the choice of an aircraft is based on: community demand Yes available fleet and terrains Upcoming, yes. gameplay Considering the love for the KA-50, a complex modern gunship for team blue would do well. available docs There is indeed much material on this around the web. available knowledge/resource allocation ED has experience with Helos and modern avionics at this point. available SME A widely proliferated aircraft. I'm sure there are SMEs all over willing to assist ED. third parties developments None are developing an AH-64.. But the Kiowa may pose as competition. restrictions and risks of delivery Some AH-64D information is likely highly restricted. But consider this, Boeing has already gave ED its blessing for the Hornet. The AH-64D likely has less classified systems, has greater proliferation than the Hornet, and a Block ll AH-64 would be older than the Hornet Lot we got.

No, i didn't know DCLTR 2 was the default state. That explains it :)

just tested it again in a non-combat mission. You are correct, no issues. Must of been a coincidence. My apologies. Thanks for your do-diligence this thread is no longer needed

The Bearing/Range indicator of the TDC (lower left side of Radar attack page) disappears when a L&S and STT are selected. Track: https://forums.eagle.ru/attachment.php?attachmentid=232898&d=1587174323

I see. Yes, I dont see this in the viper either.

As stated, L&S and STT tracks should have the closing velocity on the Radar Attack page next to the ">" symbol on the right side of the display. Track: https://forums.eagle.ru/attachment.php?attachmentid=232898&d=1587174323

RWS Bricks should not be updated by the radar. They are one time hits that have a fixed location in space. Now they can move left and right if you turn your aircraft (moving only so as to stay at that specific lat/lon) Currently in DCS, RWS bricks are updated whenever the radar sweeps back over the target. In my track I set the brick history to 32 seconds, yet only one brick continues to exist for each target. Instead, I should see a trail of bricks for each target. Bricks.trk