Z4ng3tsu

Back to normal for me

Same for me !

I fly on DCS and Falcon BMS (which is way older than DCS) and Falcon BMS is really stable in multiplayer even with a lot of pilots. The BMS team put a lot of work to improve the net code. I just hope DCS will do the same eventually. This is really the most annoying thing when playing online currently.

SRS might be a good solution indeed... Even if I would have liked sound stream capability from DCS (because some players don't like SRS, even if I can't understand why)

Would be very interested too concerning the "out of the mission" part of this question. Anyone has ever done it ?

Just what I was looking for ! Nice work on these lights, really necessary while waiting for ED to correct this.

I tested for the Mi-8. It seems to work a little more when keeping the trim button pushed when changing course. But the most effective is to reset the trim after a turn and then trimming the aircraft. I'll do some more tests to find the most effective way. For the KA-50 I was already doing this. Especially when you pilot with the trim setting your current autopilot course.

I'll try this asap thx ! If possible, I'll upload a video of my problem if it persists.

Why the deleted message ? You were suggesting to turn off the rudder trim in the options. What is the closest to reality, option on or off ?

Just saw a video about autopilot. Seems my rudder is trimmed a lot sometimes. Is it needed to reset this trim frequently in order for the autopilot to not fight it ?

Hi everyone ! I recently fly back on the Mi-8 and I was facing an issue I didn't have before. I do the starting procedure as always, no problem. Before taking off I activate the autopilot for the pitch & roll I can fly without any issue. But usually I used the autopilot heading too. In my memory it helped me to keep the chopper with the rudder, was not active when you give some rudder and is automatically set to the direction when you don't put rudder anymore (I can still see that with the autopilot light turning off and on when I apply some rudder and then release it). Now, I don't know why, when I release the rudder after a turn, most of the time the "rudder/heading autopilot" is going crazy and set the rudder full left or full right... Making the flight absolutly horrible. Is there anything I'm doing wrong ? Because some months ago, I was flying it so easily I don't understund why it's happening now... Thanks for your answers.

Is it completely modelled in DCS ? Because I always thought that if an AIM-7 (or a R-27R) was fired at me, breaking the lock will be enough to avoid the threat, even if the missile is close to me... EDIT : Ok I understand now. The missile does not track the plane, first it uses datalink from the launching plane then use the reception of the radar illumination of the target from the launching plane. So you have to lock the target until splash or miss. I thought your were saying that this missile becomes autonomous in the end of its flight

Salut lipy ! De quel type de Maverick parles-tu ? Si ce sont des AGM-65E, ils leur faut un laser à traquer, peut-être que le JTAC au sol n'a pas désigné de nouvelle cible. Si ce sont des AGM-65G, c'est déjà plus embêttant car tu indiques clairement en avoir tiré un premier et que le second n'accroche plus rien ensuite. Tu as eu ce problème plusieurs fois sur plusieurs vols ? Je testerai aussi dans mon côté mais possible que ce soit un bug

Bonjour à tous, Très fan de DCS avec pas mal d'heures de vols déjà, je cherche un groupe ou une escadrille avec laquelle voler afin de pouvoir se faire plaisir à plusieurs. Ce sera avec plaisir que je viendrai sur votre serveur et si jamais vous recruter, je suis chaud pour participer autant que possible à la vie de l'escadrille. Je vole surtout sur M2000, F18, A-10C et sur MI-8, Huey et KA-50. Je suis aussi créateur de mission (en apprentissage sur Moose en ce moment...) @+

I managed to make the OnEngineShutDown work. But I would be sad if the OnEventDead would not work (I need it !) I'll test a load of them and keep you posted ! See ya !

I'll check again (because I'm not home right now) but as far as I remember I didn't have any error in the logs (I always work on a mission with instantaneous logs, eclipse and dcs editor). And I'll do some tests on the event catching outside of a function. My code may not raise exception but maybe my events subscriptions are not living enough...

Hi everyone ! Still in the big learning curve of Moose, I was trying to do this "autonomous" behaviour : I have a group of one Mirage2K named "BlueMirage2KSirriCAP" 1 - When spawning, the group automatically starts a CAP in a zone I prepared 2 - If the Mirage2K die, I want a message sent to the blue coalition and the CAP is stopped 3 - If the Mirage2K lands (because of damage, fuel or any other reason), the CAP is stopped, a message is sent to the blue coalition and after 2 minutes a new Mirage2K spawns (hence activating a new CAP) BlueMirage2KSirriCAPSpawner = SPAWN:New("BlueMirage2KSirriCAP"):OnSpawnGroup( function(SpawnGroup) AISirriCap:SetControllable(SpawnGroup) AISirriCap:Start() SpawnGroup:HandleEvent(EVENTS.Dead) SpawnGroup:HandleEvent(EVENTS.EngineShutdown) function SpawnGroup:OnEventDead(EventData) MessageToBlue("The Mirage has been shot down. You're the only one left alive to defend the base.", 15) AISirriCap:Stop() end function SpawnGroup:OnEngineShutDown(EventData) MessageToBlue("The Mirage2K is rearming/refuelling, ETA 2 minutes", 15) AISirriCap:Stop() BlueMirage2KSirriCAPSpawner:ScheduleOnce(120, function() BlueMirage2KSirriCAPSpawner:Spawn() end ) end end ) BlueMirage2KSirriCAPSpawner:Spawn() The initial CAP is starting perfectly but I don't know why the events "Dead" or "EngineShutDown" are not triggering my respective functions to handle them. I'm pretty sure this has to be because of the function inside function but I don't see what I am doing wrong. So if anyone knows why, I'm pretty interested :thumbup: Thank you for all given answer !

So in order to give some feedback if one day someday is just like and does not read carefully the documentation of Moose's framework : The PatrolZones method is restricted to ground units only ! This is why my chopper were landing after what it seems to be one default waypoint. To have a chopper patroling a zone, an AI_CAS_ZONE should be used (or generation of waypoints inside the patrol zone but that's less efficient I think) For the second issue, it's just DCS behavior.

Thanks for your feedback. 1-I think it is moose a bug. My helos start with full fuel tank and I observed the same behaviour with my infantry troops stopping patrol at a moment. I'll try to trace the event in the log to see what's going on and if I can find a bug in Moose (if it is in Moose). 2-Yeap definitely DCS behaviour... Sometimes it's ok, sometimes it's not...

Thanks Hardcard, Yes, as I begin with Moose I split my calls just to make sure everything work step by step. I will optimize it later :thumbup:

Hi everyone ! Quick question : I have a GROUP of two choppers I want to patrol an area around an island. I used this method to do it : BlueHeliSirriPatrolGrpSpawner = SPAWN:New("BlueHeliSirriAirbasePatrol") BlueHeliSirriPatrolGrp1 = BlueHeliSirriPatrolGrpSpawner:SpawnInZone(SirriAirbaseZone, true) BlueHeliSirriPatrolGrp1:PatrolZones({SirriAirbaseZone}, 100) It works but I met to issues : 1 - In about 5 to 10 minutes, my chopper land on the island's airbase 2 - In lot of attempts, sometimes they make a turn above the water and (maybe because of too much bugs on the windshield), one of the chopper just crash into the water... For the first issue, could it be because of fuel ? They should have full tank at start... For the second one, is it because of the natural behavior of the chopper ? Thanks for your help :thumbup:

Just resurrecting this thread because of a problem I have. I'm using a Reaper drone to do the JTAC for me (through CTLD commands) and when orbiting the ennemy at 8000ft, it is attacked by the SAM. I added the drone, with the EPLRS on, set it to orbit at 8000ft checked the invisible box in the advanced task. Still my Stinger missible is trying to shoot it down... Any idea ?

Actually, if I'm right, you just can name your prioritized units as you want as long as they have in their name "hpriority" or "priority". Quick question because I haven't tested it yet, does the JTAC change target if a higher priority target appeared ? Example : A Reaper drone is lasing some BTR on the ground ("priority" in the name) and a Strela-9 ("hpriority" in the name) is activated and appears, will the drone change its lased target or will it wait for its current target to be destroyed ? If no answer, I'll post the result as soon as I test this case

So I'm not the only one experiencing this bug ! Pretty anoying when you don't really know the area. Tried some stuff in confs but no fix.

Just asking but do you know a mission like this one but compatible with DCS 2.5 ? Because this training field was so great and I did not find anything like this for 2.5... If anyone has an equivalent mission, I'm all for it !