Rowan Posted December 27, 2017 Posted December 27, 2017 If I set a unit in the mission editor, say the E-2D, to transmit a message after a flag then the unit stops dead. The transmitted message still gets transmitted but the unit sending it goes on vacation. If the unit that is transmitting the message is in flight it immediately RTB's, if it is taxing or taking off it stops moving.
Zarma Posted December 28, 2017 Posted December 28, 2017 Strange, but not on the correct forum. i9 9900k, 64 Go RAM, RTX 4090, Warthog HOTAS Throttle & Stick, Virpil AH64 collective, TPR rudder, MFD Cougar, Trackir 5 Pro, Multipurpose UFC, Alain Dufour's TEDAC and Oculus Rift S (when I want some VR), http://www.twitch.tv/zarma4074 / https://www.youtube.com/user/Zarma4074
Zarma Posted December 29, 2017 Posted December 29, 2017 Where does it belong? https://forums.eagle.ru/forumdisplay.php?f=210 i9 9900k, 64 Go RAM, RTX 4090, Warthog HOTAS Throttle & Stick, Virpil AH64 collective, TPR rudder, MFD Cougar, Trackir 5 Pro, Multipurpose UFC, Alain Dufour's TEDAC and Oculus Rift S (when I want some VR), http://www.twitch.tv/zarma4074 / https://www.youtube.com/user/Zarma4074
Rowan Posted December 29, 2017 Author Posted December 29, 2017 Doesn't make sense, no other module I am flying at the moment does it, so now what?
Flagrum Posted December 29, 2017 Posted December 29, 2017 Doesn't make sense, no other module I am flying at the moment does it, so now what? No other module? You were talking about a E-2D and it's issue with transmitting a message - how is that specific to the Harrier? Sounds like a problem with the DCS base game to me - so I would agree that this does not belong into the "Mission Builders Corner", but instead rather in one the Bugs section under "DCS World 1.5 & 2.0 Open Alpha".
Rowan Posted December 29, 2017 Author Posted December 29, 2017 The E-2D was just an example, if I use another unit it will do the same, if I set the transmit message to my own flight of AV-8's, my wingmen will stop dead in their tracks if we are on the ramp, not sure what it will do at 30 000 feet though, haven't tested that, I have a feeling they will just RTB. It could very well be that other modules do it, but the other modules, A-10C and the M-2000 I am flying right now don't have this problem. If I come across it on another module I will say so. Let the mods move the thread if they feel it's in the wrong place, not to sure why this is such a big issue, I personally don't care either way, it is completely irrelevant in my life, I just want try and solve the problem.
Flagrum Posted December 29, 2017 Posted December 29, 2017 The E-2D was just an example, if I use another unit it will do the same, if I set the transmit message to my own flight of AV-8's, my wingmen will stop dead in their tracks if we are on the ramp, not sure what it will do at 30 000 feet though, haven't tested that, I have a feeling they will just RTB. It could very well be that other modules do it, but the other modules, A-10C and the M-2000 I am flying right now don't have this problem. If I come across it on another module I will say so. Let the mods move the thread if they feel it's in the wrong place, not to sure why this is such a big issue, I personally don't care either way, it is completely irrelevant in my life, I just want try and solve the problem. So, not the sender of that message, but the receiver - i.e. your wingman - becomes unresponsive? That is now yet another twist of the whole story. You know what? Just post a short test mission and/or a track demonstrating the issue.
Rowan Posted December 29, 2017 Author Posted December 29, 2017 Actually that's a good idea, I will set up a quick mission with AV-8 and see what it does. It gives me a chance to test and see if I screwed up something, if it does the same thing I will post a track, if it doesn't I will post a comment.
Rowan Posted January 1, 2018 Author Posted January 1, 2018 This seems to be happening when I port a mission. If I take for example an A-10C mission I created and then just change the flight from A-10 to AV-8 then this issues arises. It doesn't seem to happen with other missions I ported to other modules though, I have done this numerous times over the past few years with just about all the modules and this is the first time this has happened. Not sure what specifically is causing it though, although I have a suspicion it could be a trigger of some kind coming over from the ported mission.
Recommended Posts