eric963

Just gave the new AOCS a quick test and I really like it. Thanks for another great update.

Deleting the export.lua file and letting the game rebuild it the next time you start it up fixed the issue for me.

When setting waypoints for flights over land using AGL(above ground level) no matter what I set it always reverts back to 3937ft. Can not increase it past that height. MSL works fine. Having the issue on PG, Caucasus and Nevada maps. Could someone try this and let me know so I can rule out my setup. Thanks Eric

This is what I use to set the number of aircraft available to 3 for the Lar squadron. A2ADispatcher:SetSquadron( "Lar", "Bandar Abbas Intl", { "Red Squadron" }, 3 )

I’m pretty sure that’s the number in seconds the a2a dispatcher uses to determine where the detected target will be based on its speed and direction. It then decides which airfield to launch the gci intercept from based on that projected location. Sent from my iPhone using Tapatalk

MOOSE - Mission Object Oriented Scripting Framework A2ADispatcher:SetSquadron(“HDR”,”Havadarya”, and the rest Sent from my iPhone using Tapatalk

Just use “airbasename” where airbasename is the exact name of the airbase on the f10 map screen. Sent from my iPhone using Tapatalk

Great news!! I'll get it installed and test it out later tonight.

Fuel threshold is currently not working. Issue has been reported just waiting on a fix. Sent from my iPhone using Tapatalk

For the Persian Gulf map just use the airfield name. Sent from my iPhone using Tapatalk

Take a look at you dcs.log file and see if there are any errors related to your mission.lua file. Sent from my iPhone using Tapatalk

The only way I know is to use this.. [color=black][size=2]A2ADispatcher:SetSquadronOverhead( [/size][size=2][size=2]"Sochi"[/size][/size][size=2], [/size][size=2][size=2]2[/size][/size][size=2] )[/size][/color][/Code]The number 2 is a modifier used with the number of detected planes. So, in the test mission with the one F5 being detected you get this 1(Number detected planes) x 2 = 2 GCI planes launched. And don't worry about asking the questions, trust me I have asked many..

Spuds Spuds, Sorry about the delay. You had a couple of minor things preventing the planes from launching. Funky Franky got the first one, need to change Detection = DETECTION_AREAS:New( Detection, 30000 )[/Code]to [Code]Detection = DETECTION_AREAS:New( DetectionSetGroup, 30000 )[/Code]Then change [Code] [size=2]A2ADispatcher = AI_A2A_DISPATCHER:New( DetectionSetgroup )[/size][/Code]to [Code][size=2]A2ADispatcher = AI_A2A_DISPATCHER:New( Detection )[/size][/Code][size=2] [/size] [color=black]Then add this line back in[/color] [Code][size=2]A2ADispatcher:SetBorderZone( { CCCPBorderZone } )[/size][/Code]And the last one is change [Code][size=2][color=#3f7f5f][size=2][color=#3f7f5f][color=black]A2ADispatcher:SetSquadron( "Sochi", AIRBASE.Caucasus.Sochi_Adler, { "SQ CCCP MiG29" }, { "DF CCCP MiG-21 01" }, 20 )[/color][/color][/size][/color][/size][/Code]to [Code][color=black][size=2]A2ADispatcher:SetSquadron( [/size][size=2][size=2]"Sochi"[/size][/size][size=2], AIRBASE.Caucasus.Sochi_Adler, { [/size][size=2][size=2]"SQ CCCP MiG29"[/size][/size][size=2], [/size][size=2][size=2]"DF CCCP MiG-21 01"[/size][/size][size=2] }, [/size][size=2][size=2]20[/size][/size][size=2] )[/size][/color][/Code] I moved the F5 closer to the shore line so when you run the mission it should get detected around the 35 second mark and launch the fighters. I'm attaching the miz and lua files for you [size=2][color=#3f7f5f][size=2][color=#3f7f5f] [/color][/size] [/color][/size] [color=#3f7f5f] [/color] [color=#3f7f5f] [/color] revised_moose_mission.lua moose test.miz

I'm looking at it now.

Spuds, Attach the dcs mission file and I'll take a look.

Try with deferred shading on. Sent from my iPhone using Tapatalk

Just connected by IP.

Just tried says server offline. I will be on for another hour or so and will keep checking for you.

Might need to check ports to make sure they are open/forwarded correctly.

Running 1.5.8 and don't see it either.

Ok just text if you can Sent from my iPhone using Tapatalk

chromium, Attached is a zip file containing the test mission and the dcs log. Tested in 1.58. Mission runs fine with just DAWS, runs fine with just MOOSE, but no units spawn from a template with both DAWS and MOOSE. Line 658 in the dcs.log is where the error is first reported. dcs.zip

Neon, I am attaching a basic mission with a vehicle being spawned in by Moose at 10 seconds into the mission. It works on my dedicated server and in SP. Run it on your system at let me know what happens. dawsmoosetest.zip

No problem I'll watch the thread for any more updates.

Ran a couple simple test missions and all seems to be working. Enabled the map object persistence and it was working as it should.