Avalanche110

Really like the the new country's available in the mission editor, However their are virtually no liveries enabled for them. All aircraft have only their default liveries available. Could we get more/ all liveries enabled for Combined Joint Task Force Red & Blue. Thanks.

Further testing shows that it has something to do with my HOTAS warthog. I can reliably crash the sim by depressing the mic switch. I have it bound to the navigation modes command. EDIT! I disabled the mic switch key bind and retested. its a bug in the F-15C module. pressing the navigation modes command (default keyboard command is "1" ) will cause CTD. Only happens above a certain altitude. doesn't occur on the ground. dcs.log-20200717-085034.zip

Hello everyone, im getting a CTD since the last update. Flying in VR on Nevada in the F-15C I have updated to the latest NVIDIA drivers and performed a repair on the directory. Deleted the contents of Metashaders and FXO folders. I have reproduced the crash 3 times, resulting in the same Error. 2020-07-17 07:53:11.051 INFO EDCORE: # -------------- 20200717-075311 -------------- 2020-07-17 07:53:11.052 INFO EDCORE: DCS/2.5.6.52196 (x86_64; Windows NT 10.0.18362) 2020-07-17 07:53:11.053 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe 2020-07-17 07:53:11.055 INFO EDCORE: # C0000005 ACCESS_VIOLATION at EF9F565B 00:00000000 Im not sure what to make of this and dont have a direction to go in for debugging. dcs.log-20200717-075311.zip

Replay-ability is a huge factor for me when mission building. If I am to invest an inordinate amount of time into making a mission, I want to be able to replay it numerous times, in numerous aircraft. I use Moose to Spawn units from randomised templates, in randomised locations so that the mission is always different. To me, this is the most valuable part of moose, and 3rd party scripts. It would be a great if this feature was incorporated into the mission editor.

Hello SC_neo. Correct, I missed one of the WW2 assets in the W-O MOD version. I have updated the file in the first post. Thanks for pointing this out.

Thanks Tarres. So what I have deduced is that the ARC coordinates in the LUA file are in Decimal degrees. The mission editor provides coordinates in decimal minutes and Decimal seconds. So I have taken the standard degrees, minutes, seconds values and put them into this converter. http://www.earthpoint.us/convert.aspx then verified the coordinates using google earth before copying them into the LUA file. Thanks for your help Tarres

Thank you Scotch75 Yes that was a Bug. their was no radio transmission broadcast on ADF - 355.525Mhz AM I found a few other missing radio transmissions for BlueFor. Oddly enough, its only in the W/O Mod version. they are all present in the MOD version. I have Updated the first post in this thread with the latest versions. You will probably notice a few changes to the voice overs and I believe theirs updated Logic for the AI Aggressors. This is great feedback, I appreciate you taking the time to let me know.

Hello everyone. I am trying to setup ARC stations on the NTTR map. I have edited the R_NAV_data_Nevada.LUA file as per this excellent video. To my absolute amazement, it worked and I can Use the ARC to navigate. However..... The coordinates are close (within 5-10Nm) , but not totally accurate. The coordinate system used in the NTTR LUA file, differs from the coordinates given in the mission editor. Example. Co-ordinates in mission editor are LAT N 36-34-20.08 LONG W 116-07-21.77 Co-ordinates in the LUA file are { -- 3: COORDINATE_ZONE_04 country = 'USA - Nevada', freq = 275.0, lat = 36.34200, long = 116.072177 * long_modifier, location = 'unknown', code = '.- --.. -.-. ' --/N/ AZC I believe i'm having issue with the "long modifier" in the longitudinal coordinate. The "long modifier" is not required for the Caucasus Map. When entering the coordinates for multiple ARC stations, I found I would need to be creative and add a zero here and there to make the coordinates from the ME correspond to the Examples in the LUA file. I have gone through the LUA for the Caucasus map and found the coordinate system is straight forward. The coordinates can be taken directly from the mission editor and entered into the LUA file. example. country = 'RUS', --3 freq = 662, lat = 44.78778, long = 38.79639, location = 'DK85', code = '-.. -.- ---.. ..... ' --/N/ DK85_ Does anyone know how I can (accurately) convert the coordinates from the ME into the LUA for the NTTR map? What is the "long modifier" and how does it affect the coordinate format? Any feed back would be greatly appreciated.

Hello Scotch75 The Engagements are triggered when a players aircraft enters a trigger zone with a Radius of 5Nm. Can I ask what aircraft you were flying and how did you navigate to the Engagement area? It is important to be fairly precise when navigating to the engagement area. (Maybe a little too precise)

Just wanted to say thank you for this Awesome campaign. I realise that its no longer supported and no longer available, and i totally understand. I played the campaign through twice and it has given me some of the most memorable experiences I have had in DCS. I am saddened that I wont be able to fly it again in the future. Also, your ME tutorials were invaluable while I was learning to make my own missions. All the best for the future Ranger 79.

Hello Apollon01. Firstly, thank you for taking the time to test the mission out and provide feed back. It really is invaluable to see how others fly the mission and how everything works for them. OK, to answer some of your Questions..... 1. I'm glad you had fun, that's all that really matters 2. The aircraft available are preset in the mission, all Flyable (fighter) aircraft are available with exclusion of war birds, as they will get their own campaign. 3. All the aircraft are cold and dark at either Nellis (for BlueFor) or Tonopah (for RedFor ) 4 & 5. The altitude advisory is to encourage good airman ship. Your instructor will advise you if you overshoot your altitude or if you are loosing altitude. This feature is very much WIP , its "calibrated" for the F-5 which is what I do most testing in. this is something that will require more attention to make it relevant for all aircraft. I.e Some voice overs at the start of the mission to set a standardised QFE. OR additional triggers to give the values in meters or feet to suit the Players chosen aircraft. 6. After you complete Both engagements, the Instructor will rejoin on you and provide feed back on your performance. this is also tied into the scoring for the campaign. 7. I too have crashed into my opponent. It is very important however, that only 1 aircraft is selected at mission start. if you were to select an aircraft, then change your mind and want to fly something else. Re-start the mission. 8. I have never had the Mission crash while testing. This might be a DCS bug. 9. Navigation for the mission is customised to each aircraft. A full fidelity Module (like F/A-18C) will be given a Lat/Long co-ordinate to enter. The F-5 uses ADF and a Beacon will be activated for you to home in on. FC-3 use way points, I have only flown the F-15C and based the navigation for FC-3 around that. SU-27 Does have INS navigation so you should be able to navigate to each way-point without to much trouble. Bellow is a GrimReapers Tutorial on how to use the INS in the Russian FC-3 aircraft. 10. I'm glad you like the voice overs, Text to speech has come along way. They are only temporary, I will most likely re-write several of them. I would LOVE to use actual Voice actors, hopefully I can find some volunteers. 11. I have already made 2v1 and 2v2 missions. They make for a very different experience and THEY ARE SO MUCH FUN....! 12. I am aiming to keep the mission time to around 60min, so I will likely keep the distances around 80nm 13. Time of day is not something that can be randomised for an individual mission, However as the campaign progresses the time of day and the weather will vary. Once again, thanks for the feed back and I hope you continue to enjoy it. Please feel free to post TRACK or TACVIEW files. That would be a huge help in seeing how the mission behaves for different users.

This looks awesome. Cant wait to try it.

Hello Milan. The mission uses the WW2 asset pack. (Which I don’t think you have) The WW2 asset pack is used for the “follow me” vehicles. This is because path tracing is a problem in DCS at the moment and the only vehicle capable of accurate path tracing is in the WW2 asset pack. I have updated both of the Miz files attached to the first post in the thread. The W/O Mod version no longer uses any WW2 assets. I appreciate you testing the mission out and really hope you enjoy it.

Your welcome! please feel free to post tacview or track files, leave a comment or suggestion. I really want to see how other people fly the mission and what potential problems arise. I spent the weekend updating it, making changes and adding some voice overs. Many more good things to come!

Should I update? Hello everyone. I have missed the last 2 updates and im still on 2.5.6.5031 I am pretty happy with this version as its stable and most things seem to be working. What bugs have been introduced and is it worth updating to 2.5.6.50793?

Bellow is a list of the mods required for this campaign. A-4E-C ( https://heclak.github.io/community-a4e-c/ ) Grinelli F-22A (https://drive.google.com/uc?id=1uAOlRlYVEBUmIghIuY4slKUoZBscj5iU&export=download) Cubanace SU-57 (https://www.digitalcombatsimulator.com/en/files/2539621/) VSN_Eurofighter VSN_F-35 VSN_F/A-18F VSN mods available here. (https://filehorst.de/folder.php?key=b6O86Ll4) Rafale mod 2.0 (https://www.digitalcombatsimulator.com/en/files/3309258/) MIG-21BIS navigation rely's on use of the ARC radio compass. to use this, download the R_NAV_data_Nevada LUA file in the first post. Go to your DCS install directory C: ProgramFiles\EagleDynamics\DCSWorld\Mods\aircraft\MIG-21bis\Cockpit\Systems\ Replace the R_NAV_data_Nevada.lua file with the modified file. You will now be able to use the ARC navigation system in the mission.

Hello everyone. One of the projects I am working on is a Dynamic (SP) BFM campaign. The campaign is set on the NTTR Map and features all (Fighter) modules with the exception of WW2 aircraft. War-birds will have their own campaign on "The Channel" map. The campaign is targeted at players learning a new module or brushing up on an old one. CAMPAIGN FEATURES: Dynamic airbase: Airbases are populated with dynamically spawned static aircraft to make the airbase feel alive. Random events will occur at each airbase to make the experience different every time you fly it. Dynamic Adversaries: The player can select his opponent’s skill level using the f-10 menu. Opponents will be intelligently generated based on your chosen aircraft's capabilities. Intelligent coordinate system: The campaign encourages players to learn the navigation systems of their chosen aircraft. Co-ordinates will be provided in a format to suit each aircraft. Their is a modified LUA file available for the ARC radio system in the MIG-21 (See next post in thread for instructions). Follow me vehicle: Ever gotten lost on a taxi way? A follow me vehicle will escort you to the runway. Intelligent wingmen: Allied flights will operate independently of the player and execute their mission independently. Intelligent tankers: A Tanker will always be in a convenient location should you need one. So far the campaign engine has over 150 triggers and an unimaginable amount of variability. I have come to a point where I require player feedback in order to continue developing the campaign “engine” The campaign is far from complete, but I really want to nail down the basics before continuing. I would like a couple of experienced DCS users to test it and provide feedback. The campaign will be available in 2 versions. one with MODS and one without. I have set up a discord channel, if your interested please follow the link bellow. https://discord.gg/yYtvjy I would really appreciate any tacview, Track files, comments, questions and feedback NTTR_BFM_CAMPAIGN_v7.0.miz R_NAV_data_Nevada.lua NTTR_BFM_CAMPAIGN_w-o_MODS_v7.1.miz

Navigation info Thanks Quigon. I'm in the process of going through and entering in the nav data for each aircraft. I have found the mig-21 to be the most difficult. However. Users can modify a lua in the MIG21 directory to generate their own ARC stations. Here's a GREAT video on how to do it.

Hello everyone. I am making a dynamic campaign on the NTTR. It features nearly all flyable aircraft in DCS. The campaign encourages the player to use the navigation systems in their chosen aircraft. However, despite owning nearly all the modules I haven't flown the majority of them. (Not for a lack of wanting to, or enthusiasm.... JUST TIME) Now I have the problem of trying to design a campaign for 20 different navigation systems, that I haven't used and don't understand. Here's an example. During start up, the player is assigned a mission and a set of coordinates. The Hornet uses Degree's, minutes, seconds. N 37-47-07 W 118-27-23 But the Viper uses decimal minutes (I think), so the navigation instructions need to be in the correct format. Ok, that's not a problem. Now what about the F-14,or the mirage? I set up ADF for for the F-5 and that works great. I really came unstuck when i tried to set up navigation for the Mig21 (which I have never flown) So Im turning to the community for Help on this one. If you have any insights into the navigation systems and what format they should be in, please share them. It would be greatly appreciated and save me a few hundred hours.

FunkyFranky. This is a huge help, This has puzzled me for a long time now. Thanks for the feedback and all your work with MOOSE.

I have tried this a number of times over the years without success. I am wondering if anyone else has had more success. I am trying to spawn AI aircraft in a specific parking spot at Nellis. I have a simple MOOSE script that will successfully spawn them at the correct airbase, even the correct Terminal type. but I do not understand how to spawn them in a specific parking spot. Any Help would be greatly appreciated.

Since update 2.5.6.49314 AI aircraft taxi into objects blocking their path. an AI aircraft that is on the ramp at mission start will taxi into any object blocking its path. destroying both it and the object (either static or another unit) Prior to 2.5.6.49314 the AI would remain stationary until the object was cleared. (This issue remains unchanged in today's update .5.6.49718) AI_TAXI_BUG_1.trk AI_TAXI_BUG_2.trk

FIXED IT I found the issue. The objects I was spawning had the incorrect country ID. (blue units on a red base) Now there's a trap for young players.

This is a weird one. if a static object is spawned near an f-5 on a cold and dark start. it prevents the player from interacting with ground crew. if the static object is not spawned near the f-5, the player can interact with ground crew normally. the distance to the static object doesn't seem to make a difference. if I spawn the static 500m away, the issue remains. I found that if I removed the script that spawns the static object. Comm's work normally. Conducting the identical test with the f-14 shows that the coms work normally. not entirely sure if this is an F-5 issue, or an issue with the tonopah airfield. below are some track files that highlight the issue and its resolution once the script was removed. (note: the script is identical between the f-5 and f-14, I do not believe its the script causing the issue) GROUND CREW BUG.trk GROUND CREW BUG_F-14.trk GROUND CREW BUG_FIX.trk

PATH TRACING I can confirm this. Path tracing is still an issue on OB. The path tracing ability is different depending on unit type. Below are two tracks that show how one unit is incapable of negotiating a simple route, while another can complete it just fine. the First track shows a follow me vehicle (HMMWV) unable to negotiate the route. The second shows a (WILLYSMB) successfully complete the same route. Note: the HMMWV could complete this route without issue on the previous OB version. Since the update, it cannot. (WillysMB has always been the most reliable path tracer in all my testing..... and I have done alot. PATH_TRACING_BUG_HMMWV.trk PATH_TRACING_BUG_WILLYSMB.trk