Robdcamp88 Posted February 7, 2017 Posted February 7, 2017 Hey guys, so I have confirmed that the radios are set to the correct frequency t/r Radio 1 AM, 2 UHF, 3 FM. Earlier in the mission and in previous missions Im not sure if this was the case with Overlord. UHF and the VHM AM were correct. However I do know that I did order Overlord to send in Bravo after I had fixed the radio issue, bravo moved in. Bravo has been sitting there for 5-10 minutes and I havent gotten any comms. So, I'm RTB. I also never got any response from UZI after their recce run. So, not sure if this is a bug or not, but assistance would be welcome
Robdcamp88 Posted February 7, 2017 Author Posted February 7, 2017 (edited) In Mission 5, all comms are set correctly, radio communication between myself and the checkpoints is decidedly one sided. My character is responding to them however. Is this a bug? (This was resolved, i appear to have had my radios on guard channel) Edited February 7, 2017 by Robdcamp88
baltic_dragon Posted February 8, 2017 Posted February 8, 2017 Hey! Was it resolved for both 4 and 5, or do you want me to look into 4? The way radios are handled are causing troubles at first, but I feel it is much more realistic that way :) For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
RogueSqdn Posted February 19, 2017 Posted February 19, 2017 I've had two CTDs in Mission 4, when starting the attack against Echo 2's position. DEFENSOR FORTIS Spoiler Systems: Falcon NW Talon: Ryzen 9 5950X @4.9GHz, 64GB DDR4, RTX 3090 FE; Falcon NW Mach V: Core i7 3930K @3.2GHz, 32GB DDR3, GTX 1080 FE Cockpit: MonsterTech MTX F, 42" 4K TV, HP Reverb G2, Oculus Rift S, PointCTRL Controls: RS F16SGRH CE, RS F18CGRH, VPC T-50CM2, VFX, WarBRD (Grips); VPC T-50CM2, RS FSSB R3L (Bases); Winwing F/A-18C, VPC T-50CM3, VPC T-50CM, TM Warthog, Cougar (Throttles); VPC ACE2 (Rudders)
baltic_dragon Posted February 19, 2017 Posted February 19, 2017 Hey! I am currently away from my flying rig, so can't check it, but perhaps it is a similar issue to this one: https://forums.eagle.ru/showthread.php?p=3055965#post3055965 Not much I can do as a mission builder about the CTDs, but hopefully the new patch will fix the problem with ground units reported in the linked thread. Cheers, BD For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
RogueSqdn Posted February 19, 2017 Posted February 19, 2017 Possible I suppose. Later today I will try to post a log and trk. Where would they be located? DEFENSOR FORTIS Spoiler Systems: Falcon NW Talon: Ryzen 9 5950X @4.9GHz, 64GB DDR4, RTX 3090 FE; Falcon NW Mach V: Core i7 3930K @3.2GHz, 32GB DDR3, GTX 1080 FE Cockpit: MonsterTech MTX F, 42" 4K TV, HP Reverb G2, Oculus Rift S, PointCTRL Controls: RS F16SGRH CE, RS F18CGRH, VPC T-50CM2, VFX, WarBRD (Grips); VPC T-50CM2, RS FSSB R3L (Bases); Winwing F/A-18C, VPC T-50CM3, VPC T-50CM, TM Warthog, Cougar (Throttles); VPC ACE2 (Rudders)
RogueSqdn Posted February 24, 2017 Posted February 24, 2017 (edited) I've been sick all week and am just now able to get back on the gaming computer. Here is everything from Saved Games\DCS\Logs.Logs.zip Edited February 24, 2017 by RogueSqdn DEFENSOR FORTIS Spoiler Systems: Falcon NW Talon: Ryzen 9 5950X @4.9GHz, 64GB DDR4, RTX 3090 FE; Falcon NW Mach V: Core i7 3930K @3.2GHz, 32GB DDR3, GTX 1080 FE Cockpit: MonsterTech MTX F, 42" 4K TV, HP Reverb G2, Oculus Rift S, PointCTRL Controls: RS F16SGRH CE, RS F18CGRH, VPC T-50CM2, VFX, WarBRD (Grips); VPC T-50CM2, RS FSSB R3L (Bases); Winwing F/A-18C, VPC T-50CM3, VPC T-50CM, TM Warthog, Cougar (Throttles); VPC ACE2 (Rudders)
RogueSqdn Posted February 24, 2017 Posted February 24, 2017 This may have been mission 5... I lost count. :) At any rate, I got through it by going on low detail, and looking at the log there may be a tracer issue. Not sure. DEFENSOR FORTIS Spoiler Systems: Falcon NW Talon: Ryzen 9 5950X @4.9GHz, 64GB DDR4, RTX 3090 FE; Falcon NW Mach V: Core i7 3930K @3.2GHz, 32GB DDR3, GTX 1080 FE Cockpit: MonsterTech MTX F, 42" 4K TV, HP Reverb G2, Oculus Rift S, PointCTRL Controls: RS F16SGRH CE, RS F18CGRH, VPC T-50CM2, VFX, WarBRD (Grips); VPC T-50CM2, RS FSSB R3L (Bases); Winwing F/A-18C, VPC T-50CM3, VPC T-50CM, TM Warthog, Cougar (Throttles); VPC ACE2 (Rudders)
baltic_dragon Posted February 25, 2017 Posted February 25, 2017 Glad you made it through! I will do a very detailed overview and overhaul of Enemy Within once 2.5 is out (together with releasing some of the missions in MP version), but until that update I will keep it just to bug - squashing, though many of them are not on my end. Hope you enjoy the campaign! For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Sylosis Posted August 8, 2017 Posted August 8, 2017 I have a similar problem. I can't hear Overlord. He seems to be talking, cause my guy answers (such as "Copy Overlord, bla bla..."). But I don't hear him. The radio on my top left is set to the Uzi frequency (144 AM) The UHF is left at 251 The last radio of my lower left is set to 33 FM (I set the numbers to 3 - 3 - 0 - 00, so that's 33 right?). Both VHF radios are at TR and the UHF is at Main (or Both, I don,t recall). I thought I was doing it right, isn't it? Windows 10-64bits, i7-8700k, GTX 1080Ti, 32 Gb RAM, MSI Monitor 32in 165Hz. Mirage 2000C, F5-E, Mig21bis, A10-C, FC3, F-18, AV-8B N/A, F-14, F-16, SuperCarrier
Sylosis Posted August 10, 2017 Posted August 10, 2017 Well nvm, it's just me not understanding the radios on the A10-C.... I thought that the knob selector for "FM, AM, Manual, etc" was to be used to choose which radio is for FM which is for AM. Turns out it's fixed... the lowest one is FM and the top one is AM and you must leave the selector at Manual. I don't quite understand what that knob is for then, I'll check the manual. But, that solved my problem. Windows 10-64bits, i7-8700k, GTX 1080Ti, 32 Gb RAM, MSI Monitor 32in 165Hz. Mirage 2000C, F5-E, Mig21bis, A10-C, FC3, F-18, AV-8B N/A, F-14, F-16, SuperCarrier
baltic_dragon Posted August 15, 2017 Posted August 15, 2017 Uff, glad to hear that :) still on holidays so can't do much to jelp anyone for another week! For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Recommended Posts