VTJS17_Fire Posted March 8, 2015 Posted March 8, 2015 (edited) Hi guys, at first, the facts: + I have a vanilla DCS installation, no mods installed. + I tried the repair function. + Other modules and radio comms with ramp start hot setting works fine. But: If I build a new mission with ramp start (cold start), I can't open the comms menue. I tried it with Ralt + \, I also changed the settings in the options to only \. The comms menue doesn't showed up. My canopy is always open, the airbase is red (same team, as my aircraft). Easy comms is off. I tried it at Batumi, at Maykop and Krymsk. In the Chuck's MiG-15bis Guide I read, that some of you have the same issue. But for me, it seems to doesn't work anyway. Any hints/ ideas? Kind regards, Fire EDIT: And no, there are no other settings with this key binding (RAlt + \ or only \). EDIT 2: Track attached. Edited March 8, 2015 by VTJG17_Fire Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit [sIGPIC][/sIGPIC]
ED Team BIGNEWY Posted March 8, 2015 ED Team Posted March 8, 2015 Hi VJS161_Fire when you have no power and canopy open use the communication menu, check key bindings. Seems to be working for me. but also bare in mind the track you provided the airfield is neutral so even if you get the communication menu up they will not rearm you, solve that by placing a friendly unit at the airfield. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
VTJS17_Fire Posted March 8, 2015 Author Posted March 8, 2015 :doh: I only checked the K-6 radio keybindings and throttle radio knob. I forgot, to check the common communication keybindings. It seems to be, that the radio menue wasn't setup correctly by default. As I saved the new binding \ to my radio transmit knob (at the throttle), DCS didn't show me a conflict with another keybinding. Thanks BIGNEWY, it's solved. :thumbup: Kind regards, Fire Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit [sIGPIC][/sIGPIC]
ED Team BIGNEWY Posted March 8, 2015 ED Team Posted March 8, 2015 No problem, happy to help. Enjoy :) Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Cunning_Fox Posted February 24, 2016 Posted February 24, 2016 Yeah, I can't get the communications menu to work in the air after I take off. If I don't exit it I can give one command to my Wingman. This is for latest (2/25/2016) stand-alone. Any solutions, or is it a known bug?:pilotfly:
slicker55 Posted September 4, 2016 Posted September 4, 2016 Cunning_Fox, I'm watching this thread with interest - also noticed the same issue - comms works until I'm airborne? i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]
Art-J Posted September 4, 2016 Posted September 4, 2016 Make sure "comms menu" and "microphone button" are set up correctly - only one of them will work both on the ground and in the air. Also, do You use easy comms, or game avionics modes? These are known to cause some weird issues with modules functionality. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
slicker55 Posted September 4, 2016 Posted September 4, 2016 Art-J, Thanks - I will check my settings and report back. i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]
slicker55 Posted September 4, 2016 Posted September 4, 2016 Art-J, Seems to have sorted it now after checking the keyboard commands. Thanks i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]
Recommended Posts