Jump to content

Recommended Posts

Posted

In the campaign 3 & 4 the radio to AWACS & atc isn't working, also I seem to be immortal to weapons?....haven't tested rest.

I've tried to re-save them but it isn't working.

i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.

Posted

I hope it'll be fixed someday.

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • 1 month later...
Posted

Any update on this problem?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
Any update on this problem?

 

Not from LN, but you can open each mission in the ME, go to the radio tab of the player jet, save mission* and you should find that the radio works again.

 

That has tended to fix most of the radio bugs when I've encounted them during a mission.

 

*You may need to alter a freq, save, then alter it back and save again.

  • 1 year later...
Posted

It seems that something is wrong with the training missions and the quick missions as well, I can't communicate with ATC unless I open the mission in the mission editor, in which case it works.

 

The frequencies indicated in the cockpit are wrong too, but the two I checked in the ME were matching the ATC's frequency given on the map (and they were answering), just not corresponding to the memo in the cockpit.

 

So two different problems to fix, apparently.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

  • 4 weeks later...
Posted

bump.

 

Problem is unchanged in 1.5.5.58891.190.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

  • 3 weeks later...
Posted

Wrote a bug report in LN bugtracker a while ago, but no more feedback than here. I suppose this module isn't maintained anymore.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

The frequencies indicated in the cockpit are wrong too, but the two I checked in the ME were matching the ATC's frequency given on the map (and they were answering), just not corresponding to the memo in the cockpit.

 

The 'funny" about this is, one fix the missions manually through ME, change the picture for frequencies list in cockpit files, etc.

 

Then the next patch mess all again. :cry:

How difficult is fix this in patches files to avoid this "Catch 21" again and again...?

Posted

Not sure, ED probably needs to break back-compatibility now and then, when bringing new features or necessary refactorizations, but I never had so many problems with another module.

 

Yes, the fact running missions from the ME (but not when saving them) solves some of the issues is weird. It wouldn't be enough for the first training mission, which is broken beyond any hope ;) A little sad for a first contact with the aircraft.

 

I should probably have a look at how the missions have been designed when I have some time.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

I fix this QM open their files in ME and saving, no need play from ME.

But when new patch came they are messed again...

 

For me looks like that every patch send this missions files again, and they are done old version with the error, so the "loop" continue...

 

Never had look at this "training missions" - that "White Rabbit..." but as you mention take a look (1.5.4.54596) and there the radio work OK, for ground crew and ATC. :huh:

Posted

I tried that with one mission but that didn't seem to solve the problem. Perhaps I messed up in setting the radio control at the same time (though I doubt it), will try again.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Guest deeplodokus
Posted
I tried that with one mission but that didn't seem to solve the problem. Perhaps I messed up in setting the radio control at the same time (though I doubt it), will try again.

if you manage to make the radio work in training mission on gunnery, I'm interested to know how. I'm stuck at that mission after the trainer tells me to contact Krasnodar and head there, i can't get a response on radio and nothing happens after that. I haven't tried editing anything with the mission editor yet though

Posted
if you manage to make the radio work in training mission on gunnery, I'm interested to know how. I'm stuck at that mission after the trainer tells me to contact Krasnodar and head there, i can't get a response on radio and nothing happens after that. I haven't tried editing anything with the mission editor yet though

You don't have to contact Krasnodar, just tune in the RSBN ch. 3 and use it to navigate.

 

The fact that the radio doesn't work is strange, because it works fine if you start the mission from the editor, but not if you start it from Training menu.

Guest deeplodokus
Posted
You don't have to contact Krasnodar, just tune in the RSBN ch. 3 and use it to navigate.

 

The fact that the radio doesn't work is strange, because it works fine if you start the mission from the editor, but not if you start it from Training menu.

ah, ok. well that's one thing for whoever makes the training missions: the gunnery one comes before the one on rsbn but makes reference to rsbn

Posted (edited)

Looking at QM and Training Mission files, they lack the "radio" part - green box:

 

radio21.png

In right side of picture default mission file.

 

If open in M.Editor and save, this part is created.

 

Case want add manually in mission file, use Notepad++:

 

["Radio"] = 
                                       {
                                           [1] = 
                                           {
                                               ["channels"] = 
                                           {
                                                   [1] = 124,
                                                   [2] = 150,
                                                   [3] = 121,
                                                   [4] = 131,
                                                   [5] = 141,
                                                   [6] = 126,
                                                   [7] = 130,
                                                   [8] = 133,
                                                   [9] = 122,
                                                   [10] = 124,
                                                   [11] = 134,
                                                   [12] = 125,
                                                   [13] = 135,
                                                   [14] = 137,
                                                   [15] = 136,
                                                   [16] = 123,
                                                   [17] = 132,
                                                   [18] = 127,
                                                   [19] = 129,
                                                   [20] = 138,
                                               }, -- end of ["channels"]
                                              
                                           }, -- end of [1]
                                       }, -- end of ["Radio"]

 

Open the mission files - is inside a .RAR file - with Notepad++, search for = "Player"

 

is from ["Skill"] = "Player" line- that is your plane and add the lines bellow this line:

 

"type"] = "MiG-21Bis",

 

Above are the "["radiochannel19"] = 138," etc. frequencies list - this is common in all planes in mission, the lines that need add is exclusive for player aircraft.

 

Some Training missions are not able to don't fix in ME and since they include several scripts this can end broken too.

But there work OK after add the lines with Notepad++.

 

The last time I use Mig-21 was at more than a year and this problem already exist at time.

 

And when a new patch came will broken this missions again, because download old and bugged mission files, and the "loop" start again... :music_whistling:

Edited by Sokol1_br
Posted

Well spotted!

 

I've put a bug report on their bug tracker a while ago, but I don't think they use it anymore. They don't much read the forums either, so...

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted
Well spotted!

 

I've put a bug report on their bug tracker a while ago, but I don't think they use it anymore. They don't much read the forums either, so...

 

Thanks for reporting that. Does this problem only affect the training missions or is it the same with the campaign missions?

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

Haven't tried, so I'm not sure but I saw posts mentioning similar problems in the campaign. Something to test, one of these days :)

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted (edited)

It seems to be more complicated than that, I copied the files in my user directory and ran the taxi and take-off missions from the mission editor several times, it's really random.

 

Sometimes the ATC would respond on channel 0 (124 MHz, Krymsk) if I'm fast enough to ask permission to taxi.

 

Whenever I tried channel 10 (normally 124 MHz too), I never got any response.

 

I've seen there was a comm option for the player aircraft, with the frequency also on 124 MHz, but I don't see what this is (haven't found an explanation in DCS doc). If I disable it, it seems I get more chance to use channel 0 to communicate with ATC, but not always, and channel 10 still does not work. Perhaps there's an interference of this feature.

 

I don't know what they've done, it simply doesn't work well, and it's not reproducible all the time. But then again, the ATC does not always respond in other aircraft either.

 

 

EDIT: OK, channel 9 answers, so there is a shift in the channels at some point (and does not correspond to the sheet in the cockpit). It's getting even weirder.

Edited by Redglyph

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted
In the campaign 3 & 4 the radio to AWACS & atc isn't working,

 

I look at campaign (the default that came with Mig-21) files and contrary to Quick Missions campaign mission has the correct radio list.

 

I move the 3rd mission for single mission folder and play then, ATC and AWACS radios work OK.

 

I use only "not-Easy" communication and always select the the proper channel for given ATC using the list in kneeboard before use PTT.

 

Only notice is that if you send to radio calls in rapid sequence (e.g. Cancel Inbound and then Request Inbound) the recipient tends do take more time to respond.

 

EDIT: OK, channel 9 answers, so there is a shift in the channels at some point (and does not correspond to the sheet in the cockpit).

 

The list in right side of cockpit (in Cyrillic) start in 1 and not in 0 - so don't match with radio in missions and kneeboard list.

 

This list was wrong (?) since early 2015, when I use MiG-21 for last time (start use again a week or two ago).

At time someone post the list image edited and correct, I install but latter patches revert for wrong list (like happen with Q.Missions files fixed in ME), so start ignore this list.

Posted

Yep, saw the list started with 1 which was suspicious. And sure enough, this was reported at least one year ago on their bug tracker (probably earlier here from what you say), but they haven't addressed this bug, it's assigned to a "Cobra847". Perhaps the guy isn't working there anymore. I'll put another ticket but I doubt they'll ever see it.

 

Since they forgot to translate quite a few items, I had a nice English cockpit mod installed (by Quartermaster), at least the time to get familiar with the Mig. But I haven't found a way to install it properly like other aircraft, this module seems to make it mandatory to overwrite the original files, and because of that it's replaced on every update.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...