FlightControl

Dude... This is cool

Since the release of 1.5.0, this event stopped working, which now about .... 2 years? Sven

Wait, spare the work. Tanks DO have an event birth, but you cannot use the event birth to detect if a person entered a tank...

sunki34, thanks for the suggestion by the way.

No avail for the the other approach. For ground units, the Unit:getPlayerName() returns a blank string ...

Is there an update on this issue from the dev team, anybody knows?

Is there a known issue related to the detection of static structures? When using the method: DetectedTargets = Controller:getDetectedTargets()this API code returns an array of detected targets... When in the visibility of the detecting group a static structure is located and is detected, it will be included in the list ... So, when i have the following code: for DetectionObjectID, Detection in pairs( DetectedTargets ) do local DetectedObject = Detection.object -- The detected object local Detected = false Detected = Detected or ( DetectedObject and DetectedObject:isExist() and DetectedObject.id_ < 50000000 and DetectedObject:getCategory() == Object.Category.UNIT ) Detected = Detected or ( DetectedObject and DetectedObject:isExist() and DetectedObject.id_ < 50000000 and DetectedObject:getCategory() == Object.Category.STATIC ) self:E( { DetectedObjectType = DetectedObject:getTypeName() } ) end then this logic seems to be failing because in that list, an entry is included with a wrong DetectedObject.id_ entry. The value is above 500000..., but should be in my case 24... As a result, the static cannot be found and an error is thrown. It does know however that it is a static, because it writes "Static doesn't exist" in the error message log. Is there anybody who has used the getDetectedTargets() API and has experienced this behaviour too? This is the relevant extract from the dcs.log: 04333.369 INFO SCRIPTING: 560( -1)/E: DETECTION_UNITS00060.function({["DetectedObject"]={["id_"]=16777472,},}) 04333.369 INFO SCRIPTING: 565( -1)/E: DETECTION_UNITS00060.function({["DetectedObjectType"]="ammo_cargo",}) 04333.369 INFO SCRIPTING: 701( -1)/T: DETECTION_UNITS00060.{} 04333.369 INFO SCRIPTING: 560( -1)/E: DETECTION_UNITS00060.function({["DetectedObject"]={["id_"]=16777728,},}) 04333.369 INFO SCRIPTING: 565( -1)/E: DETECTION_UNITS00060.function({["DetectedObjectType"]="MiG-25PD",}) 04333.369 INFO SCRIPTING: 580( -1)/T: DETECTION_UNITS00060.{["TargetIsDetected"]=true,["TargetIsVisible"]=true,["TargetKnowType"]=true,["TargetLastTime"]=true,} 04333.369 INFO SCRIPTING: 598( -1)/T: DETECTION_UNITS00060.{[1]="Detected Target:",[2]="Recce",[3]="Pilot #001",[4]=0.17596424140721,[5]=0,} 04333.369 INFO SCRIPTING: 701( -1)/T: DETECTION_UNITS00060.{} 04333.369 INFO SCRIPTING: 560( -1)/E: DETECTION_UNITS00060.function({["DetectedObject"]={["id_"]=16777984,},}) 04333.370 INFO SCRIPTING: 565( -1)/E: DETECTION_UNITS00060.function({["DetectedObjectType"]="Ka-50",}) 04333.370 INFO SCRIPTING: 580( -1)/T: DETECTION_UNITS00060.{["TargetIsDetected"]=true,["TargetIsVisible"]=true,["TargetKnowType"]=true,["TargetLastTime"]=true,} 04333.370 INFO SCRIPTING: 598( -1)/T: DETECTION_UNITS00060.{[1]="Detected Target:",[2]="Recce",[3]="Pilot #002",[4]=0.13939431565013,[5]=1,} 04333.370 INFO SCRIPTING: 701( -1)/T: DETECTION_UNITS00060.{} 04333.370 INFO SCRIPTING: 560( -1)/E: DETECTION_UNITS00060.function({["DetectedObject"]={["id_"]=16778240,},}) 04333.370 INFO SCRIPTING: 565( -1)/E: DETECTION_UNITS00060.function({["DetectedObjectType"]="ATMZ-5",}) 04333.370 INFO SCRIPTING: 580( -1)/T: DETECTION_UNITS00060.{["TargetIsDetected"]=true,["TargetIsVisible"]=true,["TargetKnowType"]=true,["TargetLastTime"]=true,} 04333.370 INFO SCRIPTING: 598( -1)/T: DETECTION_UNITS00060.{[1]="Detected Target:",[2]="Recce",[3]="Unit #1",[4]=0.11842186601992,[5]=2,} 04333.370 INFO SCRIPTING: 701( -1)/T: DETECTION_UNITS00060.{} 04333.370 INFO SCRIPTING: 560( -1)/E: DETECTION_UNITS00060.function({["DetectedObject"]={["id_"]=50331904,},}) 04333.370 INFO SCRIPTING: Error in SCHEDULER function:[string "Scripts/Moose/Functional/Detection.lua"]:565: Static doesn't exist 04333.370 INFO SCRIPTING: stack traceback: [string "Scripts/Moose/Core/Fsm.lua"]:586: in function <[string "Scripts/Moose/Core/Fsm.lua"]:582> [C]: in function 'getTypeName' [string "Scripts/Moose/Functional/Detection.lua"]:565: in function <[string "Scripts/Moose/Functional/Detection.lua"]:528> (tail call): ? [C]: in function 'xpcall' [string "Scripts/Moose/Core/Fsm.lua"]:594: in function '_call_handler' [string "Scripts/Moose/Core/Fsm.lua"]:661: in function <[string "Scripts/Moose/Core/Fsm.lua"]:599> (tail call): ? [C]: in function 'xpcall' [string "Scripts/Moose/Core/ScheduleDispatcher.lua"]:129: in function <[string "Scripts/Moose/Core/ScheduleDispatcher.lua"]:90> If needed I can post a demo mission to reproduce this. This error notice has a less urgency than the S_EVENT_PLAYER_ENTER bug report, which is much more urgent to be fixed. Thanks in advance! Sven

okay! lets do that! ping me when you want to test or do a root cause analysis together.

Hi chromium, i wasn't aware that moose was creating problems for your mod. Is there something that I can do also? Sven

You can use it immediately! What do you mean with "post?" A video?

Guys, I've made quite some effort this weekend to make the following video, continuing the Gori Valley mission video series. It demonstrates the upcoming class TASK_CARGO_TRANSPORT which will be included in release 2.1 of the upcoming MOOSE release. The use cases are explained in the mission, demo flying, menu system of the tasking framework are shown. The last part goes into a more extensive explanation of the different MOOSE classes utilized to: - create cargo objects - the command center - create the transport task - create deployment zones - handle the event when a cargo is deployed. - make the task a success. - make the mission a success. The video is a bit long, just remind that the audience is very diverse. Noobies to experienced programmers. I really hope this somehow starts ringing a bell to where this framework in heading... Cheers guys! Enjoy.

All this is directly on the server, no clients involved. I know. Try now to connect a client to the machine. No event is fired.

Find the following VIDEO showing what the error is about and how to simulate it. The demonstration missions to re-simulate this error can be found here: https://github.com/FlightControl-Master/BUG_REPORT_MISSIONS/tree/master/BUG-001%20-%20S_EVENT_PLAYER_ENTER_UNIT We hope that feedback can be given what is the root cause of this, and if this can be fixed soon. Sven

This problem appeared again ... After this last release...

Now gePlayerName() is not working anymore neither in an MP setup on the server. A client logging into a server, and a getPlayerName() is enquired, does neither work anymore. It did work however somewhere in 1.5.5 or something.

A scripting engine issue... In a multi player setup (MPS), when a player enters any unit from a client connected PC, the event S_EVENT_PLAYER_ENTER_UNIT is not fired on the server! When a player enters a slot (a plane) from a client connected PC, the S_EVENT_BIRTH is fired on the server, which is okay. But again, no S_EVENT_PLAYER_ENTER_UNIT is fired on the server. When a player enters an already alive unit using the CA module (so on the map, select a unit and press ALT-J) on a client connected PC, the S_EVENT_PLAYER_ENTER_UNIT is not fired on the server. This is a problem, because there is no CPU efficient way to know when a player enters a unit in a MPS. The event S_EVENT_PLAYER_ENTER_UNIT is correctly working in a SP setup though. As a workaround, the only way now for me to know if a player is in a unit or not, is to iterate through the set of units and check the player name, and do this continuously. This is not ideal ... I will leave it up to DCS developer team to evaluate the urgency of this issue. I can imagine that testing and fixing this may require some effort. FC

Okay, maybe I am mistaken, but the underlying correspondence confused me a bit, which is some time ago now . This was still in the back of my mind when writing that first statement... My concerns were posted herein the past. The chapter 2. CLEANUP https://forums.eagle.ru/showpost.php?p=3013014&postcount=34 concerns the same subject as outlined in this thread. The response was: https://forums.eagle.ru/showpost.php?p=3013132&postcount=36 It appears that every time I bring up this subject, I seem to upset people. The post that I made however was neutral and I tried to explain the facts, and outlines some of the issues we have with clear examples that can be demonstrated. The response was quite discouraging. While reading the response, I got the impression that these issues are not important enough, thus not being actively monitored and managed. Sven

Unfortunately some people who are key community representatives have a different opinion about the urgency of this issue. I hope this issue will be considered at a point in time, as it damages the simulation experience of many, unfortunately.

In progres... Fc

Target Designation... In progress... Fc

Don't bother looking at this further. Problem solved. Ciribob helped us out. He showed the correct API to use and the laser code logic... Thanks Ciribob!

Does anybody know if targets lased by AI using Spot in the scripting engine, are working correctly? It seems that su-25T cannot fire an kh-25L to a Spot with code 1113. The A-10Cs seem not to detect any valid laser spot neither when targets are being lased and the code is known. Anybody can help and prove the contrary? Thanks in advance! Sven

Singer player or multi player?

Setup Videos Redoing the setup and configuration videos on YouTube. Check this playlist: It contains how the release process works, how to configure the lua editor, where and how to download and install the moose demonstration missions in ldt, and how to build your first mission using the moose framework. Especially video #4 will be of great helo for many! All is explained in much detail while showing what to do. Good luck and ENJOY! Sven

Hi Maxi! Welcome. I know you have a lot of questions but was not able to respond. Instead of responding directly to you, I've done the effort to create new videos explaining the setup in detail for mission designers. Please have a look to the following videos in this playlist. And let me know if this helped...