Tarres

Is the multicrew still considered in the medium or long term?

We must remenber that this module was created as a standalone product long ago (around 2012?) and had a very complicated development with some serious internal issues, but you are right regarding the silence about the long standing issues. The module only could be fixed if redone from scratch like the C-101, that has become a gem of a module.

All of this problems were/are in their mantishub bug tracker, even from the first days of the module. Maybe after the "F-8 Crusader", they could "remake from scratch" all this module, from the ASP to the ARK-10 (functional in the MiG-15), the RSBN (functional in the L-39), the MRP-56 marker beacon (funciotnal in all modules even in the FC3), missiles firing outside parameters (functional as IRL in the 39), symetrical loadouts (only need to use a call in the LUA definition of the weapons and associated pylons).... Oh, I forgot... RSBN beacons are part of the DCS core from KA-50 onwards. So no need to "invent it for the module". Well, yes, for a mod you need to "program these things from outside", back in that days. Maybe in the long run.

@m4ti140, perfect resume. The underlying problem is that all the core programming code of the mod is the old code from the 21bis lomac mod. If you dig into the files, you can see leftovers from old weapons from Lomac that are present in the warehouse of the ME for example, and how the 21 uses their own weapons (in the beginning, long ago, it was to be a "separate program"; and for example the 21(IA) has a call to the "shkval sensor" to allow the use of the grom as a "laser beam rider" sort of Vihkr. Hence the "lock on radar beam", a masked laser designator with lock-on capability (the shkval from the su-25t) In order to solve all the problems, the base code must be cleaned, but I don´t think it will be possible in the short or medium term.

Yes, RWR is the basic one that comes from LOMAC: "abstract RWR". All IA planes uses the same call to this "abstract RWR".

It´s not cosmetic. All the definitions regarding an IA plane are in this file. If you comment this line, the 19P (IA), flies without radar, with only "visual Eye MK1" sensor. It´s one of the reasons that the core database was locked in +v2.7, to prevent exploits by change this values. But it´s possible to address the bug with some minor changes (and some test) in the structure of the folder and adding an apropiate call to the correct "radar" or one designed "ex profeso" for the IA that mimics the real values of the RP-5 with less cpu charge. Anyway it´s only an IA bug. It will be solved in due time.

It´s not only Razbam.

Same.

MiG-19P IA uses the N-008 radar, stock radar from ED for the MiG-23MLD, instead of the RP-5 radar. Due to this feature, MiG-19P IA can detect a B-52 target at +40 miles (high altitude, no ECM envoirement...) You can see it in the MiG-19P.lua, under sensors. Could it be possible to change the line that recalls the N-008 radar from the database to the RP-5 that I supousse that is defined for the 19P "player"?

Same here. Yesterday works; today total electric cut off when air start.

No NWS IRL A-4E. It seems removed in a fresh A-4E 2.0 RC. No NWS action to program in my end.

How do you select the T1154 to talk? I’ve only seen a Morse key on the right side of the Navigator.

Sorry I was thinking that the question was about the Approach beacon.

For now, only works for the ils beacons. Maybe In the long term we’ve some kind of “transmitter” to set in the WW2 maps. There is a “broadcasting station” filter in the ME, so maybe in the future.

I thought that it was for custom statios but not. What is this filter for? Maybe for a future type of WW2 stations?

It works as intendeed now. Thanks!.

I’ll try again later. I don’t know what’s the problem…. I setup the beacons like in the video. Thanks

I have no problem setting beacons in the Caucasus map, but I´m unable to setup a working beacon in a WWW2 to test the R1155 of the Mossie. Is it a bug or I´m missing something?

Yes. This is the point. But I think that the off-max is the correct. Same in the 15bis.

Regarding the T1154, I think that only transmits via morse code with the morse key located on the right side of the navigator seat.

Yes, the off to max behaviour is correct. But the minimum to off in the gunsight and the move of the viewpoint to the "no gunsight view point" is the part that could be a bug.

Yes, same behaviour on all knobs.

If the "lean to gunsight" is on: activate gunsight: pilot auto leans to gunsight as intended. when knob reaches the "full bright" position, it doesn´t stop, goes to "full dim/off" and the gunsight "disconect" so the pilot position returns to the predefined standard position Track attached. gunsight dimmer bug.trk

Same here. Only rudder is synchronized.

Yes, it´s the same