Comm menu no longer working

[shomke]

So, referring to the comment I posted this morning here

https://forums.eagle.ru/showthread.php?t=245346&page=2

 

My comm menu doesn't work anymore at all, although it was working fine few days ago.

I tried several things:

- Repaired twice DCS

- Tried in VR and non-VR

- I tried on different maps and modules

- I remapped the comm switches and key

- I tried with and without Easy Comm

- I also made sure that the ''comm menu disable'' option is unchecked in VAICOM, which anyway I haven't use for many weeks...

- I tried changing the resolution of the game

- I made a clean re-installation of DCS

- I sacrificed a snail singing war songs

No success :(

 

I could use radio in multi through SRS, so the problem is the comm menu, not the radio.

Also, other UI text, i.e. messages from AI wingmen, are working fine.

 

So, I attach my last DCS.log file.

I can't understand all of it, but the line telling "UIBASERENDERER: Cannot load font [D:\Program Files\Eagle Dynamics\DCS World OpenBeta\dxgui\skins\fonts\]!" which I find suspicious...

 

Any help would be very much appreciated.

Not having the comm menu is just a no go...

dcs.log

Edited August 19, 2020 by shomke

[Flappie]

I can't understand all of it, but the line telling "UIBASERENDERER: Cannot load font [D:\Program Files\Eagle Dynamics\DCS World OpenBeta\dxgui\skins\fonts\]!" which I find suspicious...

I have the same message in my dcs.log file, and my comm menu appears witout any problem. Must be something else...

 

But just in case, does your D:\Program Files\Eagle Dynamics\DCS World OpenBeta\dxgui\skins\fonts\ folder look like this?

 

 

(34 files)

 

[shomke]

Yes I just checked, I have the same files.

[Flappie]

I see nothing wrong in your log file. But we might have a few things left to test out.

 

Can you please rename your C:\Users\your_name\Saved Games\DCS.openbeta\ folder (don't delete it) and then launch the game and retry the comm menu? The game will create a new folder with default confguration at startup.

Edited August 19, 2020 by Flappie

[shomke]

No joy.

I want to test if the problem is that the menu is opening but invisible, or if it is not opening at all.

Could you tell me what is the path to, let say, "chief place the wheel chocks", or another comm I can test blind?

[Flappie]

Sure. Let's start M-2000C instant action "Takeoff" in Caucasus.

Here you go:

 

\ (or * on French keyboards, or whatever you've bound for "Communication menu")

F11 (Parent menu)

F8 (Ground crew...)

F4 (Wheel chocks...)

F1 (Place)

 

Wheel chocks should be set 6 seconds later.

[shomke]

Whaaaa. Where is the whip, I need to whip myself!

So, I had remapped the comm menu to Tab because I was unable to find the \ equivalent on my Norwegian keyboard. I just realized that Tab was already assigned to multiplayer chat in UI Layer. Strange that DCS was didn't warn me. So I corrected that, and now it works :).

I still don't get why my bindings on my hotas don't, but I will find out.

Merci Flappie pour ton aide!

Edited August 19, 2020 by shomke

[Flappie]

De rien! ;)

 

I've asked ED about the behavior of these "special" categories (UI Layer and NS430). Those don't raise an alarm when a key is already bound in another category. This causes people having weird control issues such as yours.

Edited August 19, 2020 by Flappie