Hello Gaijin Developers and Community,
I am writing to request the restoration of the rangefinder dogfight mode functionality that allowed infrared missiles to slave to radar designation. This feature stopped working after the “Seek and Destroy” update in February 2024, significantly impacting multiple aircraft across several nations.
1. The Problem: What Changed?
Before February 2024:
- Rangefinder radars (like EL/M-2001B) could detect and track targets in dogfight mode
- After radar lock, IR missile seekers (AIM-9, Python 3, R-60, etc.) would automatically slave to the radar designation
- This allowed pilots to engage targets beyond visual range or in poor visibility conditions
After February 2024 (“Seek and Destroy” update):
- Rangefinder radars can still detect and display targets
- However, IR missiles no longer slave to radar designation
- The radar essentially functions as a range-only display, losing its fire control capability
- No official announcement or patch notes explained this change
2. Technical Background: What These Radars Can Do
The affected radars are NOT simple rangefinders - they are multi-mode fire control radars with dedicated dogfight modes:
EL/M-2001B (Kfir C.2/C.7/Canard, Nesher):
- Multi-mode pulse-Doppler radar
- Dogfight mode: ±60° azimuth scan with automatic target tracking
- Can provide range, closure rate, and aspect data
- Should be able to slave IR missile seekers - this is standard functionality for this radar class
- Source: IAI/ELTA technical documentation, Israeli Air Force manuals
RLPK-22M (Su-22M3/M4):
- Fire control radar with air-to-air modes
- Can track targets and provide data for missile guidance
- Historically used with R-60 and R-13M infrared missiles
Type 226 (J-7E):
- Marconi-built radar with dogfight capability
- Should support IR missile slaving per original design specifications
3. Affected Aircraft (Complete List)
Based on community testing and reports:
🇮🇱 Israel:
- Kfir Canard
- Kfir C.2
- Kfir C.7
- Nesher
🇷🇺 USSR:
- Su-17M2
- Su-17M4
- Su-22M3
- Su-22M4
- Su-22UM3K
🇬 United Kingdom:
- Swift F.7
🇨🇳 China:
- J-7E
🇮🇹 Italy:
- AMX
- A-1A
4. Why This Matters: Gameplay Impact
At 11.0-12.0 RB (where most affected aircraft operate):
- These aircraft already face significant disadvantages: • No radar-guided missiles (only IR missiles) • Limited radar capabilities compared to F-15, F-16, MiG-29, etc. • Often uptiered to 12.7-13.0, facing advanced BVR platforms
The rangefinder dogfight mode was their PRIMARY advantage:
- Allowed engagement beyond visual range
- Provided situational awareness in poor visibility
- Enabled “first look, first shot” tactics against similarly-equipped opponents
Without this feature:
- These aircraft are reduced to “visual range only” fighters
- Cannot effectively compete at their current BRs
- Historical authenticity is compromised (these radars DID have this capability)
5. Community Evidence & Reports
Official Issue Reports:
- “Radar rangefinders no longer slave missiles” - Report #n2AxwWTuOD6f (April 2024)
- Status: Open (unresolved for 2 years)
- Complete affected aircraft list provided
- Multiple community confirmations
- “Radar Range-Finder potential bug” - Report #IV3lfWfy5UGk (March 2024)
- Specific to EL/M-2001B on Kfir aircraft
- Detailed technical analysis provided
Forum Discussions:
- “Kfir C.7 Radar Improvements” (February 2025)
- Provided real-world HUD photos proving radar tracking capability
- Cited official IAI/ELTA documentation
- Community consensus: this is a bug/regression, not intentional nerf
6. Historical Accuracy: This Is NOT a “Buff” Request
Important clarification:
- We are NOT asking for new functionality that never existed
- We are requesting the restoration of functionality that worked before February 2024
- This is a bug fix , not a balance change
Historical evidence:
- EL/M-2001B dogfight mode with missile slaving is documented in official IAI manuals
- Su-22 series used radar-directed IR missile attacks in historical conflicts
- J-7E’s Marconi radar was designed with this capability
If Gaijin believes these radars should NOT have this capability:
- Please provide historical documentation proving otherwise
- Community is open to discussion based on facts
7. Our Request
Primary Request:
- Restore IR missile slaving functionality for rangefinder radars in dogfight mode
- This should apply to all affected aircraft listed above
- Implementation should match historical technical specifications
Alternative Solutions (if full restoration is not feasible):
- Provide clear documentation explaining why this feature was removed
- Adjust affected aircraft BRs downward to compensate for the capability loss
- Implement a “partial slaving” mode (e.g., radar provides target cueing, but missile must acquire visually)
Timeline:
- This issue has been open for 2 years (since February 2024)
- Community has provided extensive evidence and technical documentation
- We respectfully request an official response or fix in the next major update
8. Impact on Game Balance
If restored, will this be overpowered?
No, for several reasons:
- Limited range: These radars have detection ranges of 15-20km (vs. 70-100km+ for modern radars)
- No BVR missiles: Aircraft still limited to IR missiles (Python 3, AIM-9L/M, R-60, etc.)
- No multi-target capability: Can only track one target at a time
- No all-weather capability: Still limited by IR missile constraints (clear weather, rear-aspect preferred)
- Current BR environment: At 11.0-12.0, these aircraft face:
- F-15A with AIM-7M (50km SARH)
- F-16A ADF with AIM-120A (50km active)
- MiG-29 9-12 with R-27R (50km SARH)
- Multiple radar-guided threats
The rangefinder dogfight mode simply allows these aircraft to compete at their intended BR, not dominate it.
9. Conclusion
The rangefinder dogfight mode with IR missile slaving is:
- ✅ Historically accurate (documented in technical manuals)
- ✅ Previously functional (worked before February 2024)
- ✅ Essential for gameplay (allows affected aircraft to compete at their BR)
- ✅ Not overpowered (limited by radar range and IR missile constraints)
We respectfully request that Gaijin:
- Acknowledge this issue officially
- Provide a timeline for restoration or explain why it cannot be fixed
- Consider interim BR adjustments if restoration is delayed
Thank you for your time and for developing this amazing game. We look forward to your response.