F-15E RWR library update

[Alex_Weyland]

Hello there!

Since we haven't received any updates, but still have this wonderful airframe, we need an updated RWR library.

For example, we currently don't have an entry for the HB F-4E, which only appears as "UK" / Unknown.

In the logs, we see the following:

2025-04-26 16:53:38.283 INFO F15E_CPT (Main): ATTENTION: Unknown RWR contact type "H-6J"

This can be easily fixed by adding a line to the ALR56C_LIB.lua file, like:

rwr_codes["S-300V 9S19 sr"] = { code = "12", coal = 2, desc = "SA-12 SR" }

—or something similar as needed. Unfortunately, modifying this file currently breaks IC.

Is there any chance we might get an option to edit this file, or will it be officially handled by ED?
It would honestly be a huge improvement!

Edited April 26 by Alex_Weyland

[jdeyrieux]

You can create the same filename in ... /saved games/DCS/Config/F-15E/ like for ALE45_PRG.lua and NCTR.lua

[Alex_Weyland]

В 28.04.2025 в 09:01, jdeyrieux сказал:

You can create the same filename in ... /saved games/DCS/Config/F-15E/ like for ALE45_PRG.lua and NCTR.lua

Unfortunately - it doesn't work like this in case of RWR library.

NTCR and ALE45 programs can be overridden by files in Saved Games directory though.

Edited April 29 by Alex_Weyland

[Alex_Weyland]

Bump.

[Czar66]

I agree with this thread. It will only get worse from here if ED doesn't intervene in things like this.

I doubt the RWR is even finished also. I can be wrong...

[Alex_Weyland]

Bump.

[rob10]

It's not worth "bumping" this thread.  ED literally can do nothing directly with the F-15 stuff until this is settled.  Even the radar issue they "fixed" was a work around outside the F-15 code.  The chances of them spending time to come up with a work around to add one entry to the RWR file are nil.

[supersylph]

5 hours ago, rob10 said:

It's not worth "bumping" this thread.  ED literally can do nothing directly with the F-15 stuff until this is settled.  Even the radar issue they "fixed" was a work around outside the F-15 code.  The chances of them spending time to come up with a work around to add one entry to the RWR file are nil.

But in fact, the work of modifying RWR symbols is very simple. We should push RAZBAM and ED to reach a consensus on modifying these documents to solve this problem.

[rob10]

It could be as simple as adding a comma on a line.  Even that would put ED in legal peril if they did it without RB's permission, and there doesn't seem to be any goodwill at all between the two companies so your chances of seeing that happen are nil.

[supersylph]

4 hours ago, rob10 said:

It could be as simple as adding a comma on a line.  Even that would put ED in legal peril if they did it without RB's permission, and there doesn't seem to be any goodwill at all between the two companies so your chances of seeing that happen are nil.

Yes, I understand what you are saying. So we should call on both parties to at least agree on this very minor change, RAZBAM should issue a statement agreeing to ED to make this change. And ED should also ensure that this most basic function can work properly, just like they fixed the radar. Imagine that you can't recognize the upcoming mig29 in the F15E AV8B M2KC, and any new aircraft that comes out later, this is simply intolerable. And the fact is that they can't recognize the F4E now.In this conflict between the two parties, they both claimed to protect their own interests in the future, but in this incident, the rights of a third party, namely the players, were also damaged but were rarely mentioned.

[AndyJWest]

1 hour ago, supersylph said:

Yes, I understand what you are saying. So we should call on both parties to at least agree on this very minor change, RAZBAM should issue a statement agreeing to ED to make this change. And ED should also ensure that this most basic function can work properly, just like they fixed the radar. Imagine that you can't recognize the upcoming mig29 in the F15E AV8B M2KC, and any new aircraft that comes out later, this is simply intolerable. And the fact is that they can't recognize the F4E now.In this conflict between the two parties, they both claimed to protect their own interests in the future, but in this incident, the rights of a third party, namely the players, were also damaged but were rarely mentioned.

'Should...should...should...' Why would either party act on what you think they 'should' do? If it was as simple as customers 'calling on' them to do things, we could have 'called on' them to settle the dispute months ago.

[Alex_Weyland]

First of all, this topic isn't about RB and ED consensus achievement or resolution. This one is about a minor issue that, probably, doesn't require any significant changes and discussions between ED and RB as well. Stay on course.

Secondly, @BIGNEWY, could you please share a comment regarding the possible solution in this case? E.g. ED team can add very particular file in exclusion to avoid IC being compromised once that file was edited. However, that will allow users to maintain RWR library on their own and add whatever signature they have, both vanilla and from mods. As I mentioned earlier, we already have F-4E as "UK" on TEWS page. 

If that's not possible - it is what it is.

Edited June 2 by Alex_Weyland

[Alex_Weyland]

15 часов назад, rob10 сказал:

It's not worth "bumping" this thread.  ED literally can do nothing directly with the F-15 stuff until this is settled.  Even the radar issue they "fixed" was a work around outside the F-15 code.  The chances of them spending time to come up with a work around to add one entry to the RWR file are nil.

Well, we aren't talking about adding a single or multiple lines for missing emitters. I want basically 1 file being excluded from IC check and being editable for any Mudhen user. So, no support from ED or RB needed. 

And looking at EULA it shouldn't interfere with anything except that Mudhen is paid module which shouldn't be altered / edited / reverse engineered etc.

[BIGNEWY]

I am sorry but RAZBAM have paused all work on the F-15E for over a year now, until there is a resolution to the dispute we just have to continue to wait unfortunately.

[Mobius_11804]

You know, the RWR Library is just a simple .lua file, called ALR56C_LIB.lua? It's located in C:\User\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-15E\Cockpit\Scripts

It is not hidden, nor is it write protected.

I just added the F-4E by Heatblur myself! You can do it too@BIGNEWY, i believe in you! 

[BIGNEWY]

Not something we can do. We have another library that we will be using for our projects, I just can not say when yet.