Mystic_J έγραψε:
Yes, we will define a Monday.
Great
![Smile :)](./images/smilies/icon_smile.gif)
.
Mystic_J έγραψε:
We dont use Rapace Launcher, although I've seen it in Global Falcon. On the other hand, we could copy & paste your falconbms.cfg file in our root Falcon directory. That will ensure that our Config Editor is the same.
Copying falconbms.cfg file is a possibility. Yet I recommand using the RL as it is not only checking this file and it is also making easier the network settings management (bandwidth, host ip, ivc server ip, etc...).
Would you be ok to test it with us at this occasion ?
I'd also like to add that we would integrate greek translation for texts of the tool with pleasure
![Wink ;)](./images/smilies/icon_wink.gif)
.
Mystic_J έγραψε:
Are these values based on the RP5 xls database? I dont have it now, so i cant compare it. Looks promising though. Good job. Did u alter the ECM values as well?
Mirage values were not in the RP5 manual. But for the whole look-down values (as we modified coeficient for all airborne radars), the look-down values we have are the RP5 one (in the result).
Actually this is a 2 factor problem that is making the LD out with the new radar code. There is also the possibility to not change LD coefficient and activate the RP5 radar code instead of the new one. We made the choice to use the last radar code, and change the LD factor to get back LD...
Till there we are satisfied with this choice.
ECM values are directly linked to the radar performance (radar looking through the ECM).
All aircrafts, absolutely all aircrafts have the same ECM, and there is no possibility to define a more powerfull ECM for an aircraft than for another
![Sad :(](./images/smilies/icon_sad.gif)
. This is hardcoded, we have to do with.
The ECM burn through value depends on the radar you're using. The RP5 manual formula is still valid.
Mystic_J έγραψε:
We dont have a preference for anything particular. We fly Mirage 2KC and -5 as well.
Roger.
![Smile :)](./images/smilies/icon_smile.gif)