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 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?

@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?

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.

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

Coming back to the original question, I still struggle with a save take off. I am coming to the conclusion, that the issue is speed. The Mossie in my impression can fly before it can steer. Aiming for a higher lift off speed helped me a lot. Is that a realistic approach/assumption?

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.

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

Hello Suntsag, thank you for your awesome work on the mission editor in DCS World. Unfortnunately I would like to use this mod but cannot make it work. I included the required lines in the lua file and executed the setup as described in the video within my mission. The mission is located on the Nevada map and I chose as frequency 99X with the designation TGT. In mission the TACAN is not emitting. My FA18C does not pick up anything in the area using 99X in AIR mode. Has the mod been broken by DCS or is there a trick or restriction I am not aware of. I would appreciate any advice on the matter. Thank you very much for providing the DCS community with such valuable assets.

Okay, thank you. I mixed up the terms obviously. Still I am wondering, why ATC in Nellis gives me the QFE, which is not of use for anything and cannot be dialed in in the jet anyway.

While constructing a training mission for navigation on the NTTR map I stumble on a problem I cannot understand. In the Mission Editor under the weather settings the QNH is set to 29.92 inHg. It is my understanding that this means, if altimeter is set to this value, it will show an altitude of zero. In the mission the tower in Nellis gives me a QFE of 28.06 inHg. This value cannot even be dialed into the altimeter of the F/A-18C Hornet. 28.10 inHg is the minimum to be dialed in and then the altitude is shown as close to zero. In fact Nellis AFB is roughly 1.850 ft high. This should be shown on the altimeter. What am I getting wrong here? Thank you very much for your support.

My desktop resolution is 3.840x2.160 (4K). The "Scale GUI" option is checked. I have my "Text Messages" on 1.25, but this should not effect the GUI, should it?

I am aware its just a minor issue, but the display of coordinates in the Mission Editor Window is distorted (see pictures attached). This happens regardless of the display in DMS or DD. Its kind of funny that the Northern coordinate is affected although this coordinates is one digit shorter than the Western Coordinates. I came across this when I was putting a navigation mission together and the precise location was checked against the in game alignment process of the F/A-18 C Hornet. Any ideas how to improve this?

I tried it and you are completely right, this was the issue. I now feel assured that I am doing it right, thank you very much. It remains the question, why there are to norms in DCS in the first place!

Thank you very much, I will try this. Its obviously the same issue as with the Mirage 2000.

No, its not giving me an issue for returning to base, as I use the TACAN 12X approach on RW 21L for this training mission. I was just wondering, if I would use INS-guided bombs in this mission, that might play a role, does it?. I have honestly no idea, whether the difference in the coordinates is significant or not. I understand, that I could just ignore the difference?

I have build myself a training mission on the Nevada map to do some navigation training. In the mission editor the position of the aircraft (Nellis AFB) is N036°14`29`` W115°02´02´´. In game on the map view (F10) this coordinates are still true. In the cockpit the current position is shown on the HSI page as N036°14´48´´ W115°02´04´´ (regardless of using Waypoint 0 or A/C as reference). If GPS is used as source for the position, this again shows the same coordinates. This coordinates are also shown on the map display while aligning INS and they are the result of the alignment. I tried to change the coordinates on the HSI page to the ones shown in the ME prior to alignment, but the alignment still followed the slightly different coordinates originally on the HSI. Ho to do the alignment correct and which are the correct coordinates in the first place? Thank you in advance for any advice or clarification.

Problem Solved! After messing around extensively with all kind of settings to improve fps, I decided to delete the .../Saved Games/DCS folder entirely. After restarting DCS World the folder was newly created. Now the Mission Editor works again as intended. I have no clue, what happened. The issue was not related to the metashader or fxo folder, as i deleted them before already with no effect.

I am working on tutorials that are accompanied by mission files. After the latest update, when I open one of my tutorial .miz files, the ME opens up as usual, but the mission is empty. No aircraft or targets are visible. If I load the mission for flight, everything works, as it should. Anybody else having the same problem?

Thank you very much Thank you very much for this really well made manual. Unfortunately most developers of complex software underestimate the need for a written manual and the customer satisfaction that is coming with it. Only with this manual the Mirage is now a complete module for DCS not only for experienced real life pilots but computer enthusiast, as I am. Hope, the Harrier will get such a useful manual as well.

After constructing a training mission for the A-10C on the Caucasus map I flew the mission several times. For a few days now DCS World crashes to desktop after successfully finishing the mission. Instead of the mission statistics screen a window appears saying DCS has crashed and windows is looking for a solution (that of course never comes). I am trying to introduce a scoring in this mission, so not seeing the mission screen at the end is very unfortunate. I am using the release version 1.5.7 under steam. Same happens on a stand alone install of DCS World on the same computer. Anyone having a problem like this? Solution found! The mission contains triggers to count certain successes with points. One "mission success" is to return to base safely. Trying to program this I included a trigger regarding end of mission, trying to add to the points counted before. This obviously caused the crash, as deleting this trigger made the mission playable again.