Mike64

Hey. I'm part of the team developing "[Dropzone](https://dcs-dropzone-registry-viewer.pages.dev/)" a DCS mod manager I'd like permission to list this mod on there. Key things to note: We don't store your mod code we only store info to support marketing and installation (using the download link from the Github Release) We are happy to make the basic config but you will need to submit any info changes and releases going forward (we are happy to help make that process easy)

https://discord.gg/ScYSGmadkg

Is it possible to have a generic routing template for all aircraft? Don't want to be spawning a pile of aircraft just to be templates.

The lack of SP support is a bummer considering the older slot system works great on SP and I know a bunch of people who want it on SP. The work around is simple just host your own server but this really shouldn't be the case. I can't really think of a major reason why it's not available to SP unless you put all the code in the MP server code because you never thought about SP. Oh well.

Yeah its a optimisation if you know everyone spawns on an airfield so having the camera there means quicker loadings

Do you, mean the site that was built in a few days? By a Principal Software Engineer. In their spare time. According to your bio, you are an Airline Pilot (Captain) for UK regional airline. And we know you know nothing about software engineering because you think ED is good at it.

This is an issue for ED to fix. it's a bug in their deck-clearing logic (why clear other spots but miss the harriers). missing basic features of clearing catapults for takeoff. Handy feature of proper parking spot support on ships

Reproduction (Mission provided): Spawn Carrier with Parked player aircraft + AI helicopters and Harriers on deck Attempt to take off from carrier (Finding there isn't an ATC call to make and ground crew Request launch doesn't clear decks. Take off (usually using a just about clear catapult) Do Radio calls to Carrier to Land (Observe Helos de-spawn but Harriers stay in place on the arrestor gear) Crash into harriers Expected behaviour: Either Radio call or automatic deck clearing when connecting to catapults Harriers de-spawning when landing setup is needed via radio (Bonus) Re-organise aircraft on deck to clear needed areas but still show on deck if possible. Caucasus - Operation First Support.miz

Hey Current Hill, One of my January Tasks is to add all your 1.0.0 mods to my database did you get around to sorting operational information? (No worries if not I'll do it manually if needed)

Main Release Version 0.5.312.22 * Added: * Added: SA-10 Radar Variant Templates * Added: Kneeboard Editor (Only compatible with BR mission post this release) * Added: Kneeboard Rendering and standardized briefing component * Added: Livery Selector will choose a Livery from coalition nations if country set to CJTF(B/R) * Added: Payloads default now auto assigns loadout. Clean/Empty option * Added: Escort Attacking units now try to intercept hostiles * Added: On Road variants of escort * Added: Escort Refactor Units now attack escorted units * Added: Support for timed aircraft spawns * Added: Transport to player airbase or any airbase * Added: Transport objective troops Support vanilla transport methods * Added: Missing C-17A and Mig-29S (Mig-29G also flyable) * Added: Support for Folder based liveries * Added: Unlimited fuel for target aircraft * Added: CAP variants of Idle (Aircraft ROE free fire original Return fire) * Updated: * Updated: Aircraft attackers delay spawn relative to intercept point * Updated: Automatic troop loading limited to Aircraft not supporting native loading (currently: UH-60L) * Updated: Corrected JTAC unit as Static (it doesn't move) * Updated: Custom and Vanilla Templates * Updated: Data to DCS Open Beta 2.9.2.(purging non default liveries) * Updated: DB data to DCS 2.9 * Updated: Dotnet from 7.x.x to 8.x.x * Updated: Increase Kneeboard image size to ED default size * Updated: made "CombinedArmsPilotControl" default on * Updated: Missing Tasks for aircraft * Updated: Moose script to Moose 2.9.2 * Updated: Process Images at save stage (Faster generation, Slower saving) * Updated: Reduce Kneeboard resolution for performance * Updated: S-3B Tasks and upgraded tanker out of lowpolly * Updated: Unit selection no longer chooses immovable units that will be asked to move * Fixed: * Fix: Aircraft on base targets now have waypoint on aircraft not airbase * Fix: Attack logic for Escort mission attackers * Fix: Auto check for and fix undeclared modules in templates * Fix: Bad testing package version * Fix: Broken Target coordinates scripting * Fix: CLI failing due to uninitialized DB * Fix: Error after trying to spawn Non existing aircraft * Fix: Escort direction wrong way round * Fix: Escorted units go direct to end * Fix: Failing to clear Objective Hints * Fix: Infinite loop crash * Fix: JSON parsing missed module for Cargo and Static Objects * Fix: Medium and Long Range SAM site should always spawn full template. * Fix: More bad filter count occurrences * Fix: Null error * Fix: Objective CAP feature & Taskable CAP ROE incorrect * Fix: objective complete count logic * Fix: Objective features spawned at pickup for move to front line rather than at drop off * Fix: Objective hints no longer allow objectives to ignore borders. * Fix: Override Radio Frequencies type conflict * Fix: Packages Airbases not showing in Briefings * Fix: patrol aircraft ROE incorrect * Fix: Remove bad and incomplete data. * Fix: Standardize DCS Task usage for players * Fix: Stop multi detection for FlyNearAndReportComplete * Fix: Template groups shouldn't be shuffled order * Fix: Throw error when template file missing * Fix: Values set to null rather than empty string causing null pointer error * Fix: Yak-52 now player flyable * UI * UI: Ban and allow everything buttons on ban list page * UI: Clearer on Objective separation setting relocation data * UI: Improve Kneeboard Editor Functionality * UI: Incorrect filter on Subtask Behavior * UI: Payload to QuickBuilder * UI: Task & Behavior have descriptions * UI: Use Task for player Payload instead of default * Upgraded: * Upgrade: Bump FluentRandomPicker from 3.4.0 to 3.5.0 in /Source * Upgrade: Bump Markdig from 0.33.0 to 0.34.0 in /Source * Upgrade: Bump Microsoft.AspNetCore.Components.Web in /Source * Upgrade: Bump Microsoft.AspNetCore.Components.WebView.WindowsForms * Upgrade: Bump Microsoft.Maui.Graphics from 7.0.100 to 7.0.101 in /Source * Upgrade: Bump Microsoft.NET.Test.Sdk from 17.3.2 to 17.8.0 in /Source * Upgrade: Bump Polly from 8.0.0 to 8.1.0 in /Source * Upgrade: Bump xunit.runner.visualstudio from 2.4.5 to 2.5.3 in /Source * Upgrade: Bump YamlDotNet from 13.4.0 to 13.5.2 in /Source * Misc: * Misc: Add warnings for BR data missing DCS data * Misc: Correct bad link * Misc: Update docker readme command * Misc: Update editors notes for timed spawns * Misc: Update links * Misc: WebApp shutdown much quicker

Problem: Scripting doesn't stop you from adding more than 10 items in the F-10 Radio option. With multiple scripts, it's not possible for scripters to deal with it with SubMenus as mission makers can simply put in too many scripts. Expected Solution: The radio menu gracefully handles it by replacing the last option with a "More" option. This would allow users to "scroll" through the options.

Hey quick permission check! I am developing BriefingRoom for DCS and we would like to add your units to the tool. We load the mods in DCS and then take configuration info in order to allow our tool to support the mods. This data is also made available (although not public) to others building similar tools eg DCS Web editor Example mod configuration: https://github.com/akaAgar/briefing-room-for-dcs/blob/main/DatabaseJSON/Mods/A-4E-C/UnitPlanes.json Unfortunately, ED sucks at configuring half-decent operator tables so we have our own https://github.com/john681611/dcs-data-miner/blob/main/customDataSets/UnitOperatorsMods.json if you can provide this info it will save a bunch of googleing. I'd love you to add your units to our tool if you would allow us.

Not really viable and ChatGPT doesn't like talking War or anything that could be used as Misinformation Yup Watch our discord main released are every few months but betas come out as regularly as I can make them We also have a proper domain now! https://www.dcs-briefingroom.com/ Should be sometime this month, I'm trying to do main releases more often but life keeps saying no. Sure! The only advantage of running on your gaming rig is you get access to any custom Liveries and Payloads you have installed. We do not actively monitor the forums. In fact I forget about it regularly. Beta updates and discussion are hosted on https://discord.com/invite/MvdFTYxkpx

Its caused by me messing with the mission Lua and it causing an unhandled error lockup. The issue is it doesn't gracefully handle an error when loading a mission.

Just gave it a go nice work. Great to hear its not a replacement mod anymore. Personally the Super Hornet is a much better looking airframe. Shame that the pylons are a bit janky wonder if some pylons should just be marked as travel or at least limited to weapons that can be launched. From Nightstorm's message I understand that fully functional extra pylons is not easy/possible fix without someone at ED conveniently adding support for it to the base aircraft. Never the less I've added it into the next Briefing Room Release as a compatible mod.

Briefing Room V0.5.211.15 released - Real World Map! Headline Items Added: Real-world map the UI Added: Full Builder Objective Location hint option Added: Situation Editor Added: Moose Core and Moose ATIS for home base Added: Enhanced Gamemaster Script (Zeus) Added: Linkage between campaign missions (starting airbase, objective area & situation) Discord Full Changelog and Download

I've just implemented the fix for this. Hopefully should show up in the next beta

Nope, its off My second post shows exactly where this example fails and the code to fix it (as the lua code is public)

BriefingRoom Try now: https://www.dcs-briefingroom.com/ BriefingRoom for DCS World is the much more advanced successor to my own Headquarters for DCS World (HQ4DCS) application, and a massively improved version of DCS World's own fast mission generator. BriefingRoom allows you to create complete scenarios in just a few clicks. Missions generated with BriefingRoom tend to be rather "player-centric". Their purpose is not to simulate a real war theater, like Falcon 4's dynamic campaign, but to provide the player(s) with interesting objectives and challenges. This approach is a perfect fit for DCS World's limited number of units and very capable scripting engine. While BriefingRoom is designed to be easy to use and to allow the creation of missions in mere seconds, it is also heavily moddable and will give many options to power users ready to tackle with its most advanced features. BriefingRoom is free and open source and will always remain so, but if you want to support its development, you can make a one-time donation when downloading from Itch.io, or a monthly donation using the PayPal link you'll find here. Initial version by Ambroise Garel, now developed and maintained by John Harvey Source code, changelogs and additional information are available on the repository. Found a bug? Have a suggestion? Post it in the issue tracker. Join the Discord! Features summary Can generate any kind of single-player or multiplayer mission, from deep strikes behind a hostile superpower's cutting-edge integrated air defense network to photo reconnaissance flights over a terrorist training camp. Choose from a large variety of mission types, from combat air patrols to bomber interception, target designation for artillery strikes, photo reconnaissance, bomb damage assessment and many others, or create your own by picking target types, players tasking, and various objective and mission features. Extremely easy to use: generate missions in seconds without any technical knowledge, then export them to a DCS World .MIZ file in just a few clicks. Automatically generates proper friendly/enemy units according to countries and time period, but also able to create "what if" scenarios (2010s USAF vs 1940s Luftwaffe) and freely choose player aircraft in any country/time period. Generated mission can include custom scripts for various effects (advanced SAM AI, JTAC smoke and laser designation, artillery strikes...) Save mission templates to small .ini files and share them with your friends. Easily moddable to add more countries, units and scenarios Available as both a graphical user interface for ease of use and as a command-line tool for batch mission generation Customize enemy SAM and air-to-air opposition for any mission difficulty. No units spawned through runtime scripting. All units are added to the mission itself, so they can be edited with DCS World's mission editor for further customization. Please read the user's manual and the modder's manual for more information The development roadmap and a list of features planned for future versions can be found here: trello.com/b/iGsqgbTu/briefingroom-project-tracker Try the Web version no download needed. Download Latest - Version 0.5.312.22 We don't monitor this thread actively and recommend you go to our discord for quicker communications Images

For example given I've figured out a fix for missions failing to load: me_toolbar.lua: 580 (loadMission) local ok, result, err, theatre = base.pcall(module_mission.load, filename) --print("----result=",result, err, theatre) if not ok then MsgWindow.warning("Corruped mission:"..result, cdata.warning, cdata.ok):show() if base.isInitTerrain() == true then module_mission.removeMission() module_mission.create_new_mission() -- progressBar.kill() end end I find it odd the lack of `base.pcall` usage as its more or less designed for this and retuning bool as a result it rather fragile

Version: Latest beta. Issues have existed for: Over a year (version doesn't matter) Problem: The mission editor code is able to crash in situations where either: * Mission won't save * Load mission window refuses to open up (until complete Game restart, sometimes even removal of offending mission) * Game locks up on either Mission load into editor or Load into game screens. (Requiring Murder via Task manager) Cause: Exception not being gracefully handled leading to some form of game lockup (can be seen easily in logs) Cause of Exception: Mission with logical issue in it. Expected result: Graceful handling of errors with reverting back to editor main page with error message (just like what happens with an invalid Lua syntax in the mission file. Are these logical issues caused by me: Yes (I develop which briefing-room-for-dcs generates missions from scratch) and I do work to fix every corrupted mission I hear of. I'm ok if you close it as I am cause and that is the end of it but I do believe that the game should gracefully handle issues as much as possible. One dev to another a few top level exception handlers would do fine Example given locks up on mission load. FAIL_TEST_5_PersianGulf_-_Operation_Resolute_Waters.miz dcs.log If this is not closed instantly I'll post missions and logs as I get them

If you click without moving the mouse you can avoid ending the polygon early but tbh its hard. The drawing is very good but we need some interaction improvement for free polygons. - Separate button to end free polygon (right click probably) - Ability to Add/Remove points from selected polygon point.

I think I'm just going to have to live with it. We always assume our user isn't not going to be perfectly happy with the generation and will fiddle and its a quick manual fix.

Spot1.Coordinates=-258767.265625,-75132.0078125 Spot1.DCSID=40 Spot1.Type=UNKNOWN Spot2.Coordinates=-258765.28125,-75105.5 Spot2.DCSID=41 Spot2.Type=UNKNOWN Spot3.Coordinates=-258770.765625,-75185.6875 Spot3.DCSID=38 Spot3.Type=UNKNOWN Spot4.Coordinates=-258767.265625,-75132.0078125 Spot4.DCSID=40 Spot4.Type=UNKNOWN Spot5.Coordinates=-258765.28125,-75105.5 Spot5.DCSID=41 Spot5.Type=UNKNOWN Spot6.Coordinates=-258763.28125,-75079.2890625 Spot6.DCSID=42 Spot6.Type=UNKNOWN Spot7.Coordinates=-258684.96875,-74703.0078125 Spot7.DCSID=11 Spot7.Type=UNKNOWN Spot8.Coordinates=-258826.5625,-74570.46875 Spot8.DCSID=12 Spot8.Type=UNKNOWN Spot9.Coordinates=-258841.953125,-74549.3671875 Spot9.DCSID=13 Spot9.Type=UNKNOWN Spot10.Coordinates=-258770.765625,-75185.6875 Spot10.DCSID=38 Spot10.Type=UNKNOWN Spot11.Coordinates=-259899.4375,-74221.8125 Spot11.DCSID=47 Spot11.Type=AirplaneOnly Spot12.Coordinates=-259878.71875,-74210.53125 Spot12.DCSID=46 Spot12.Type=AirplaneOnly Spot13.Coordinates=-259919.453125,-74234.0234375 Spot13.DCSID=45 Spot13.Type=AirplaneOnly Spot14.Coordinates=-259939.59375,-74245.90625 Spot14.DCSID=44 Spot14.Type=AirplaneOnly Spot15.Coordinates=-259959.875,-74257.828125 Spot15.DCSID=43 Spot15.Type=AirplaneOnly Spot16.Coordinates=-258763.28125,-75079.2890625 Spot16.DCSID=42 Spot16.Type=OpenAirSpawn Spot17.Coordinates=-258765.28125,-75105.5 Spot17.DCSID=41 Spot17.Type=OpenAirSpawn Spot18.Coordinates=-258767.265625,-75132.0078125 Spot18.DCSID=40 Spot18.Type=OpenAirSpawn Spot19.Coordinates=-258769.078125,-75158.296875 Spot19.DCSID=39 Spot19.Type=OpenAirSpawn Spot20.Coordinates=-258770.765625,-75185.6875 Spot20.DCSID=38 Spot20.Type=OpenAirSpawn Spot21.Coordinates=-259269.84375,-75576.8203125 Spot21.DCSID=37 Spot21.Type=AirplaneOnly Spot22.Coordinates=-259277.3125,-75543.53125 Spot22.DCSID=36 Spot22.Type=AirplaneOnly Spot23.Coordinates=-259802.6875,-75081.9296875 Spot23.DCSID=35 Spot23.Type=AirplaneOnly Spot24.Coordinates=-259785.734375,-75052.375 Spot24.DCSID=34 Spot24.Type=AirplaneOnly Spot25.Coordinates=-259567.296875,-75468.484375 Spot25.DCSID=33 Spot25.Type=AirplaneOnly Spot26.Coordinates=-259545.140625,-75441.203125 Spot26.DCSID=32 Spot26.Type=AirplaneOnly Spot27.Coordinates=-259999.78125,-74810.203125 Spot27.DCSID=31 Spot27.Type=AirplaneOnly Spot28.Coordinates=-259974.390625,-74785.578125 Spot28.DCSID=30 Spot28.Type=AirplaneOnly Spot29.Coordinates=-258394.875,-75913.296875 Spot29.DCSID=29 Spot29.Type=AirplaneOnly Spot30.Coordinates=-258415.015625,-76203.28125 Spot30.DCSID=28 Spot30.Type=AirplaneOnly Spot31.Coordinates=-258390.296875,-76228.515625 Spot31.DCSID=27 Spot31.Type=AirplaneOnly Spot32.Coordinates=-258909.03125,-74462.171875 Spot32.DCSID=26 Spot32.Type=OpenAirSpawn Spot33.Coordinates=-258892.796875,-74483.296875 Spot33.DCSID=25 Spot33.Type=OpenAirSpawn Spot34.Coordinates=-259322.9375,-74411.125 Spot34.DCSID=24 Spot34.Type=AirplaneOnly Spot35.Coordinates=-259535.546875,-74323.1484375 Spot35.DCSID=23 Spot35.Type=AirplaneOnly Spot36.Coordinates=-259876.1875,-74352.453125 Spot36.DCSID=22 Spot36.Type=AirplaneOnly Spot37.Coordinates=-259300.5,-74383.8203125 Spot37.DCSID=21 Spot37.Type=AirplaneOnly Spot38.Coordinates=-259533.484375,-74288.09375 Spot38.DCSID=20 Spot38.Type=AirplaneOnly Spot39.Coordinates=-259885.6875,-74320.171875 Spot39.DCSID=19 Spot39.Type=AirplaneOnly Spot40.Coordinates=-258360.25,-75909.640625 Spot40.DCSID=18 Spot40.Type=AirplaneOnly Spot41.Coordinates=-258840.78125,-76822.9375 Spot41.DCSID=17 Spot41.Type=AirplaneOnly Spot42.Coordinates=-258823.6875,-76847.84375 Spot42.DCSID=16 Spot42.Type=AirplaneOnly Spot43.Coordinates=-258874.171875,-74506.359375 Spot43.DCSID=15 Spot43.Type=OpenAirSpawn Spot44.Coordinates=-258858.09375,-74527.859375 Spot44.DCSID=14 Spot44.Type=OpenAirSpawn Spot45.Coordinates=-258841.953125,-74549.3671875 Spot45.DCSID=13 Spot45.Type=OpenAirSpawn Spot46.Coordinates=-258826.5625,-74570.46875 Spot46.DCSID=12 Spot46.Type=OpenAirSpawn Spot47.Coordinates=-258684.96875,-74703.0078125 Spot47.DCSID=11 Spot47.Type=OpenAirSpawn Spot48.Coordinates=-258928.6875,-75672.6171875 Spot48.DCSID=10 Spot48.Type=AirplaneOnly Spot49.Coordinates=-258929.875,-75696.2421875 Spot49.DCSID=9 Spot49.Type=AirplaneOnly Spot50.Coordinates=-258930.84375,-75719.875 Spot50.DCSID=8 Spot50.Type=AirplaneOnly Spot51.Coordinates=-258932.171875,-75743.546875 Spot51.DCSID=7 Spot51.Type=AirplaneOnly Spot52.Coordinates=-258930.734375,-75766.90625 Spot52.DCSID=6 Spot52.Type=AirplaneOnly This dump is generated by this code: function briefingRoom.f10MenuCommands.debug.dumpAirbaseDataType(o) if o == 16 then return "Runway" end if o == 40 then return "HelicopterOnly" end if o == 68 then return "HardenedAirShelter" end if o == 72 then return "AirplaneOnly" end if o == 104 then return "OpenAirSpawn" end return "UNKNOWN" end function briefingRoom.f10MenuCommands.debug.dumpAirbaseParkingData() briefingRoom.debugPrint("STARTING AIRBASE PARKING DUMP"); local base = world.getAirbases() for i = 1, #base do briefingRoom.debugPrint(base[i]:getID()..":\n") local parkingData = base[i]:getParking() local parkingString = "" for j = 1, #parkingData do if parkingData[j].Term_Type ~= 16 then parkingString = parkingString.."\nSpot"..j..".Coordinates="..parkingData[j].vTerminalPos.x..","..parkingData[j].vTerminalPos.z parkingString = parkingString.."\nSpot"..j..".DCSID="..parkingData[j].Term_Index parkingString = parkingString.."\nSpot"..j..".Type="..briefingRoom.f10MenuCommands.debug.dumpAirbaseDataType(parkingData[j].Term_Type) end if j % 10 == 5 then briefingRoom.debugPrint(parkingString) parkingString = "" end end briefingRoom.debugPrint(parkingString..";") end briefingRoom.debugPrint("DONE AIRBASE PARKING DUMP"); end There are 3 occurrences of position 38 and what are the unknown spots I assume the docs are out of date. Even when I update my data and remove the unknowns and duplicates it still occurs. I'm hoping I've made a dumb mistake somewhere because I'd love to have this issue solved. In grabbing the data for this I've managed to fix a bunch of bugs but in the end the issue is still there. BTW this isn't just this airfield I've seen it on Caucuses too.

This mission is generated by my tool but based on the data from the function (note parking spots mentioned do not match the ones on the map that is `parking_id` which is not exposed by the function E-3A parking position 38 ["type"] = "E-3A", ["unitId"] = 28, ["x"] = -258770.765625, ["y"] = -75185.6875, ["name"] = "Overlord 1 1", ["heading"] = 1.633627839884963, ["alt_type"] = "BARO", ["livery_id"] = "default", ["skill"] = "Excellent", ["speed"] = 138.88888888889, ["AddPropAircraft"] = { }, ["psi"] = 0, ["payload"] = { ["chaff"] = 120, ["flare"] = 60, ["fuel"] = 65000, ["pylons"] = { }, }, ["callsign"] = { [1] = 1, [2] = 1, ["name"] = "Overlord10", [3] = 1, }, ["onboard_num"] = "961", ["Radio"] = { }, ["parking"] = 38, }, Its spot is also occupied by a AH-1W Parking Spot 41 [1] = { ["type"] = "AH-1W", ["unitId"] = 58, ["x"] = -258765.28125, ["y"] = -75105.5, ["name"] = "Enfield 2 1", ["heading"] = 2.9739903300826516, ["alt_type"] = "BARO", ["livery_id"] = "default", ["skill"] = "Average", ["speed"] = 138.88888888889, ["AddPropAircraft"] = { }, ["psi"] = 0, ["payload"] = { ["chaff"] = 30, ["flare"] = 30, ["fuel"] = 1250, ["gun"] = 100, ["pylons"] = { [1] = { ["CLSID"] = "{3EA17AB0-A805-4D9E-8732-4CE00CB00F17}", }, [2] = { ["CLSID"] = "\[M260_HYDRA}", }, [3] = { ["CLSID"] = "\[M260_HYDRA}", }, [4] = { ["CLSID"] = "{3EA17AB0-A805-4D9E-8732-4CE00CB00F17}", }, }, }, ["callsign"] = { [1] = 1, [2] = 2, ["name"] = "Enfield20", [3] = 3, }, ["onboard_num"] = "016", ["Radio"] = { }, ["parking"] = 41, } Syria - Operation Frequent Brother.miz Assuming I've screwed up and made a mistake then this is using "parking_id" same issues occur. Syria - Operation Steady Support.miz