Jump to content

Wingthor

Members
  • Content Count

    50
  • Joined

  • Last visited

About Wingthor

  • Rank
    Junior Member
  • Birthday 03/31/1968

Personal Information

  • Flight Simulators
    DCS World
  • Location
    Oslo
  1. Happens when its an AI kill due to if PlayerGroup:GetName() == playerGroup:GetName() then ... KillDataTable.target_name = EventData.TgtTypeName is never reached, and MESSAGE:New(KillDataTable.target_name.." destroyed",5):ToGroup(PlayerGroup) holds a nil value... But putting --show kill message if ES_Settings.PilotKillNotification == true then MESSAGE:New(KillDataTable.target_name.." destroyed",5):ToGroup(PlayerGroup) end inside the if PlayerGroup:GetName() == playerGroup:GetName() then clause seems to take away the error: S
  2. Just tested and version 1.2 works fine. However it seems not work when setting Skill "Client" and playing in a "Single Player" mission. Not sure if that is addressed before. I would like to propose a few enhancement: Report Carrier Landings. Night (or low visibility landings, instrument landings) Regards...
  3. Scripts functions: Spawning, AI tasks, Client Tasking, Cargo generating and more Script Tool: MOOSE. (Mission Object Oriented Scripting Environment) Reason: The object oriented approach Moose provides to mission scripting. Overide functions, inheritance and reuse of code. I can make rather sophisticated missions/sceneries with just few lines of code. Moose provides a huge API, which makes me able to do much with less code. Documentation written and Youtube vids Moose community provides help with code and sharing of code and such.
  4. You need to specify? Does the Moose spawn change unit names? or do you mean Groups name. When regular spawning and also with the ai-a2a-dispatcher Groups name have the original names from the mission editor plus a #number as a suffix If spawning with warehouse class name might change. You can have a look at this docs from Spawn class. Regards :) Wingthor
  5. Hi Mano, many things to fix here, First when grabbing object from Moose Wrapper (eg UNIT, GROUP, AIRBASE +++) classes you will use the FindByName(). For Unit that will be units name in Mission Editor (ME) So to grab carrier your call: carrier = UNIT:FindByName("Stennis")So now you have the carrier as a Wrapper.Unit#UNIT object which you can use. Next you have built a function which will be called from a menu object, fine. However you are using the GetPosition (with lower G which prob will return nothing) which will return a table with x,y,z values which is probably not what yo
  6. Hi Viper39, thanks for a great tool. I have had for a while but have started to look deeper into your application. Hope I can provide some useful feedback's. Bug: Kneeboard: After choosing "metrics" as readout, and choose BE as readout in "note" column. The distance seems to be in "nautical miles". Kneeboard blanks manually added fields, when updated. Feature request: Export of flights only, so you can share your flight plan into an overall plan. Export knee-boards by packages. So each package is in one separate directory, you easy can send to rest of the fl
  7. There is plenty of YT vids with examples how to use, Here :) Regards Wingthor
  8. Hi Ciribob, I am currently working with function which is called from CTLD (Latest from github) callback function. I have tested in both single player and multiplayer and I seems not to receive any inforantion about user in args table? I can see only information about AI group involved. Regards Wingthor
  9. Here is a log file where only the latest connected player gets a file. dcs.zip
  10. I am using feature "export a separate file for each player" in TacView 1.7.1. It appears like it only exports TacView file for the latest connected player. Anyone else have this problem? Regards :)
  11. Can someone confirm the fix? From tacview it seems like ARMs Kh-58 and Kh-25mpu does either to far without hit, or when hit do no dammage. That is Open Beta latest ver. as pr this date.
  12. Have you solved this? Look into Moose demo mission. I do believe you will find demonstration of what you try to achieve here: Moose Demo Missions for Groups (Patrol) If not plz ask and I will try to help. Moose also has a community on Discord, for more instant help :) Regards
  13. [string 'C:\Users\xxx\AppData\Local\Temp\/DCS~mis000000920']:4: attempt to index 'EVENT' (a nil value) slack traceback: [C]: ? [string 'C:\users\xxx\AppData\Local\Temp\DCS\/~mis000000920']:4: in main chunk AM I screwing something simple here? I mean, this is not a huge complicated script. Its hard to say based on this info. I wonder if you can share your troubled code with us, especially line 4 in your script is of interests. :)
  14. SpawInZone will execute the spawn. Same with SpawnScheduled. Look for all the commands prefixed with Init. These will defined the Spawn Settings. If you look at Moose docs, you will find InitRandomizeZones which takes a table of Zones as argument. By give a table with only one Zone I guess will achieve what your want by use SpawnScedueld. So if you have BluelaunchZone (A Zone defined in Mission Editor (ME)) you use BluelaunchZone = ZONE:New("Bluelaunch") -- What ever its called in ME SpawnArray = {BluelaunchZone} BlueSpawn3 = SPAWN :New( "Blue Strike 1" ) :InitLimit( 4, 10 ) :InitRand
×
×
  • Create New...