Beamscanner

Currently modeled in DCS The TDC and Ant. elevation axis can move at different speeds depending on how far the are moved in a direction. While this makes sense if you're using the proper axis slew, it makes it awkward when using them with buttons instead of an axis. When I map the TDC to buttons the TDC in game will start moving slowly then accelerate after being held for a second. The ant elevation works similarly. Pressing the ant elev. button once barely moves the ant. but holding it down for a second accelerates it to its max gimbals. Both of these instances make using TDC & Ant. Elev. with buttons awkward and make it difficult to get the radar to do what I want it to do. "Wish" If using either of these with a button instead of an axis, remove the acceleration and have them move at a constant speed similar to how the FC3 buttons work. ie because the buttons are binary (either on or off), have the speed be either 0 or 100%. (and slow down the ant. elevation because it maxes out way too fast holding the button)

I have this problem too. I can get as far as selecting the aircraft in the MP mission, but once i hit "FLY" the game stops responding. I have 24 GB of RAM, 8 GB VRAM, 3.4 GHz quad core with hyper-threading, WIN 10, and about $2000 more invested in cockpit/modules/accessories solely so I can fly MP missions... Game works perfectly fine in SP.. I can load complex missions (like the 104th's mission) in SP.. Its takes a few minutes, but it works. However, pre-loading missions has not fixed my problems in MP.

DCS World OpenBeta\Config\MonitorSetup it shows the default ones but not my custom lua

My ingame monitor setup (pull down in options) doesnt see the lua i placed in there. Does anyone know a fix?

Im having a problem. The game doesn't show the monitor file i dropped in the monitor configuration folder. Thus I cannot select it. (because its not showing that its there) Can anyone help?

I've read the RL Hornet manual on the CIT. Turns out that it can be programmed on the DDI however the pilot wants. If the pilot wants only the mode 4 response to auto ID the target as hostile(mode 4 yes = Friend// Mode 4 no = Hostile), they can in fact do that. There's alot of freedom with it. That being said, while what we have now is simple, it is potentially accurate. For those wondering what he means by using it in RWS: RWS is still WIP and is missing "trackfiles" which can be displayed (similar to TWS). A total of 3 trackfiles can be displayed in RWS (LTWS, L&S, DT2). When you have a trackfile displayed will show the target HAFU symbology which can be determined by the CIT.

The radar should be able to maintain track while the aircraft rolls. Only issue could be from momentary side-lobes when the plane is upside down and close to the deck, as the guard horn is on the bottom on the antenna. However, the radar has track memory, so that if it loses the track it continues to predict the targets location and will attempt to reacquire. All of this happens extremely fast, and as such a pilot may not even notice the track was lost and reacquired.

Are you guys working an in-house solution for the MIG-19s pulsed radar?

Thank you chuck

not sure. received from a friend.

no. its for SA purposes only. It will show in the HUD, SA page, Radar Attack, Az/El page and JHMCS. (with MSI selected)

No... i have no idea how you got that in your head. But the thing has far more symbols than the ALR-69. And sends the data to many more places than the ADU. ie if you start jamming an emitter you'll see the X enhancement symbol over the emitter icon. I have no idea what you're asking. it identifies emitters same as A-10. And even has special icons to denote if its AAA or a tracking SAM, or a fighter radar.

too close for missiles. Switch to gun!

Yes. RADAR is WIP. Your own Bull is on the bottom center Your Cursor Bull is on the top left Your Cursor BRA is on the bottom left inside the B-Scope And yes, its also on the RWS page

Yes. It's only the same in his picture because he's flying the A-10C which only has two displays.

wheres the designate button?

A lot still needs to be done on the radar and RWR... I'd like to see the basic systems done before moving on to completely different sensors and weapons. From what I understand, Wags said they wanted HARM and ATFLIR to be the priority after the basic systems are done.

ALR-67(v2) on the USN F/A-18C --AUDIO LOGIC-- -Status change tone- --single 455hz tone that lasts .335 seconds long ---used to indicate the following ----New Emitter (if not a fighter jet radar) ----Any emitter is moved from non-lethal ring to lethal ring (if not a fighter radar) ----Any emitter is moved from lethal ring to critical ring (if not a fighter radar) ----RWR BIT failure EXAMPLE: (starting at exactly 35:10) -AI status change tone --single burst of a 4 tone warble, in the following order. 550hz, 520hz, 490hz, 470hz. each tone lasting .083 seconds. The total time of the warble is .335 seconds. ---used in place of a status tone change when a fighter radar is added to the display or switches to a different threat ring. EXAMPLE: (starts at exactly 34:44) EXAMPLE 2: (starts at exactly 32:28 ) EXAMPLE 3: (at 11 seconds in) -STT tone- --A constant tone that switches between 455hz and 555hz. each tone lasting about .25 seconds in duration. ---Used when a threat emitter is locked on to you. EXAMPLE: -Missile Guidance/luanch tone- --A constant tone that switches between 455hz lasting .066 seconds long, and a 555hz tone lasting .1 seconds in duration. I believe this may be an EXAMPLE: (get a status tone change at 35:32 followed by what could be a simulated launch immediately afterward) This one sounds different from the STT tone example. And this example shows the F/A-18Cs defending..

I just saw a stream with RWR audio.. But it used a "status change tone" instead of an "AI status change tone" for a mig-21. So it played the wrong audio. It also had the EW page display range instead of threat rings. And they're missing the threat symbology. Also, RWR data goes to alot more places. (HUD, warning lights, Radar, plus other places that wont be available at launch) Its all WIP, but I'd still like to help them correct it while they're working on it so they dont have to come back to it later.

Anything on FC4? type of aircraft? Expected time frame (this year? next year? two years?) Anything on MiG-23? There's been rumors of its existence. Is it a thing?

RWR is WIP. That being said I've already talked to someone about the display being backwards. (they have the "non-lethal" area close to the center and the "critical" threat area on the outer ring.. IRL it goes from outside in Non-lethal->Lethal->Critical and the very center is the "status" area) ie the non-threat E3 radar should be on the outer-most edge of both the EW page and the ADU, not close to the center. Fighter radar starts in "lethal" zone, then moves into critical ring as it gets close or if it locks on/fires a missile. Anytime an emitter populates or moves from one ring to another, you get a "status tone", or if fighter radar its an AI status tone as I mentioned here: https://forums.eagle.ru/showpost.php?p=3347570&postcount=9

The pull up line?

I believe EXP 3 is otherwise known as "Medium Resolution SAR" MAP = Real Beam Mapping (Likely includes option for Doppler beam Sharpening on the sides of the RBM) EXP 1 & 2 = Doppler Beam Sharpening (different resolutions / doppler/range bin processing) EXP 3 = Medium Resolution SAR (range fixed) SEA = Surface Search GMT = Ground Moving Target (likely includes indication and tracking) PVU = Precision Velocity Update AGR = Air to Ground Ranging TA = Terrain Avoidance IRA = :dunno:

It has some tricks up its sleeve to engage notching targets. For one it has memory tracking which will let a target 'coast' through the notch (not tracking it) and predict where the target is moving. You also have the ability to select between a "normal" or "wide" doppler notch. (in the radar attack data sub-page. and yes ED has the option there but idk if it works). If the target is jamming, you can track its jammer in SIL (silent) mode. You also have MSI trackfiles which means you can continue to track the target via D/L, FLIR, etc.