Moose - Range Script

[ClausHoffmann]

Currently I am producing a tutorial about basic air to ground operations and want to ship a .miz file with it to let the student fly the mission according to the tutorial. The mission is located on the Nevada map and includes a bombing range using the range script within the Moose framework together with the 476th Range Targets Package. The script (if working) is awesome and I would really like to use it to increase immersion and the training effect.

 

It is mentioned in the documentation that in case of a multiplayer mission using clients one needs to enter as spectator first before choosing a client to fly. I am producing a single player mission and unfortunately the script will not start at all in single player (no F10 menu item shown). The spectator role is not available in single player.

 

• Any way to use the script in a single player mission at all?
• Any chance the script will be improved to work without specific loading procedures in multiplayer in the future?

 

Highly appreciated if somebody could help me out on this.

 

Best regards

 

Claus

[TonyG]

What do your logs say?  Is MOOSE starting correctly and is the range script shown in the log?

[LG-Skyman]

Currently I am producing a tutorial about basic air to ground operations and want to ship a .miz file with it to let the student fly the mission according to the tutorial. The mission is located on the Nevada map and includes a bombing range using the range script within the Moose framework together with the 476th Range Targets Package. The script (if working) is awesome and I would really like to use it to increase immersion and the training effect.
 
It is mentioned in the documentation that in case of a multiplayer mission using clients one needs to enter as spectator first before choosing a client to fly. I am producing a single player mission and unfortunately the script will not start at all in single player (no F10 menu item shown). The spectator role is not available in single player.
 

• Any way to use the script in a single player mission at all?
• Any chance the script will be improved to work without specific loading procedures in multiplayer in the future?

 
Highly appreciated if somebody could help me out on this.
 
Best regards
 
Claus

There is a way to start a mission as if it was MP: set the controllable aircrafts to client instead of player. I hope, I remember it right.

Wysłane z mojego MI MAX 3 przy użyciu Tapatalka

[thornx]

2 hours ago, ClausHoffmann said:

• Any way to use the script in a single player mission at all?
• Any chance the script will be improved to work without specific loading procedures in multiplayer in the future?

Hi, the bug you mentioned (hit esc twice ...) is known in DCS since 2(3?) Years. It is reported multiple times. ¯\_(ツ)_/¯ Its ED, so expect a "soon" fix (maybe 2025)

MOOSE Discord: https://discord.gg/9K8Uxj5ftu

Edited April 24, 2021 by thornx

[ClausHoffmann]

Moose overall is working fine. I am using other functions (i.e. Atis) that are working as intended.
 

Using client instead of player makes it work. Looks weird, as there is only one client in the list, but at least it works. Thank you very much for the support, this community is awesome.

[ClausHoffmann]

I am stuck at the same problem again. I am constructing a new training mission on the Marianas Islands using a bombing range on the island of Farallon de Medinill using the Moose range script. Additionally I want to use ATIS on Andersen AFB. At mission start I load first the Moose.lua and then a script produced by myself (please find this script attached). Both files appear in the miz-file as intended. I start the mission by entering as a spectator first, as discussed earlier this year above. There are no related errors in the log file (Log-file is attached as well).

About the range:

Unfortunately after entering the cockpit of my F-16C, no F10 menu appear on the radio list. I am using the newest version of the Moose framework. Has something changed? Am I doing something stupit here?

About the ATIS:

How can I find out, whether I am using the right AIRBASE data. I can find some examples from Caucasus, Nevada and Syria, but nothing about the Marianas. Is the following command correct?

"atisAndersen=ATIS:New(AIRBASE.MarianaIslands.Andersen_AFB, 118.175)"

Every advice is highly appreciated.

iron_bombing.lua dcs.log

[buur]

I do not see the start of Moose in the log file. Are you sure that moose implemented correctly?  

[Rudel_chw]

I'm not aware of a Moose Range Script .. if you are using @Ciribob Range Script, that one uses Mist as framework, not Moose.

[fargo007]

MOOSE has a range class and I'm thinking that's what he's using.

e.g.

https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Functional.Range.html##(RANGE).SetDefaultPlayerSmokeBomb

[ClausHoffmann]

I try  to start  Moose by loading the Moose.lua file at Mission Start. What else do I Need to do, to implement Moose correctly in my mission? The Moose.lua file I use is more than 6 MB in size. Is that perhaps too much?

Has the other range script the same functionality? I have no experiences with Mist so far.

 

[Rudel_chw]

46 minutes ago, ClausHoffmann said:

Has the other range script the same functionality? I have no experiences with Mist so far.

 

As I have never used the Moose range script, it's hard for me to compare them. The Mist one is designed for Multiplayer use, but can be used on single player if you enter first the mission as Spectator and after the script loads you then select the aircraft. The aircraft must be set to Client" rather than "Player".

The functionality is basically measuring the distance between the target center and the actual impact point of your bombs or rockets. It can also be used for straffing, where instead of measuring distance, it counts how many rounds hit the target. here is a video where you can see how it look within a mission:

 

I'm attaching the readme of the range script, in case you want to look how it is configured within the mission editor:

 

 

README.md

Edited December 26, 2021 by Rudel_chw

[fargo007]

1 hour ago, ClausHoffmann said:

I try  to start  Moose by loading the Moose.lua file at Mission Start. What else do I Need to do, to implement Moose correctly in my mission? The Moose.lua file I use is more than 6 MB in size. Is that perhaps too much?

Has the other range script the same functionality? I have no experiences with Mist so far.

 

 

You need to load an actually MOOSE script file after loading MOOSE itself.  For example a file containing:

TOPGUNRANGE = RANGE:New("TOP GUNNERY RANGE")

local strafepit={"strafe_1","strafe_2","strafe_3"}

strafe_fouldistance = TOPGUNRANGE:GetFoullineDistance("strafe_1", "strafe_foul_line")

TOPGUNRANGE:AddStrafePit(strafepit, 3000, 600, 270, true, 20, strafe_fouldistance)

TOPGUNRANGE:Start()

Everything "in quotes" (except for "TOP GUNNERY RANGE") is the name of a group in the ME. See the MOOSE RANGE documentation page I linked above, there are example missions already built if you would like to learn more. 

This is really all that's needed to set up strafing targets.

[ClausHoffmann]

@Rudel_chw: Thank you, I shall give it a try next week. The function I like the most with the range script by Moose is the possibility to call the range and get a report on weather conditions and altimeter settings. I assume this is not possible with the Mist range script?

 

[Rudel_chw]

1 minute ago, ClausHoffmann said:

I assume this is not possible with the Mist range script?

Probably not, On my missions I get that info from the Briefing.

[ClausHoffmann]

@fargo007 That is what I was trying to achieve with my script attached to my initial post, called Iron Bombing.lua. Is there any mistake in that script?

[fargo007]

Just like the person who posted earlier, the log doesn't show that Moose was actually loaded.

When correctly loaded, you'll have lines like these:

 

2021-12-26 20:30:33.150 INFO    SCRIPTING: *** MOOSE STATIC INCLUDE START *** 
2021-12-26 20:30:33.280 INFO    SCRIPTING:   4431( 74157)/I:                          BASE00000.?(Tracing in MOOSE is OFF)
2021-12-26 20:30:33.280 INFO    SCRIPTING: *** MOOSE INCLUDE END *** 

 

[buur]

Maybe you create a very simple mission with only the range skript in in and without any other Mods.

If than moose range skript not working we can have a look on the mission.

[ClausHoffmann]

Thanks to all for your replies. Your help and support is highly appreciated. @fargo007was right, Moose was not started in my mission in the first place. I did, what @buursuggested and have figured out that my way of starting Moose was wrong. I fiddled around now finding the proper way to start Moose at mission start. Now the log file has the lines suggested by @fargo007. This being out of the way I now have to test the modules I am using in my mission (RANGE and ATIS). Hopefully this is now a little bit easier. Thanks again and have a nice evening.

[fargo007]

Good news!  Test and debug them one at a time for the fastest route to success.