Chump

An honest question. I would like others' opinions on why you would need both Stable and Beta releases installed. If you already have Beta installed, doesn't that imply that you probably won't be using Stable much, if at all? The only real reason I can find, is to engage with those that don't want to hop onto the Beta train and deal with the zero-day issues.

The author would have to manually include that. As far as I know, there is no automated way to include custom settings from your own install. I'm curious what they changed the other labels to (you mentioned square for ground vehicles). Would you please post the labels, or the mission name so I can check it out?

My guess is that there is a custom Labels.lua file in the .miz. local aircraft_symbol_near = "⬡"

You've piqued my curiosity. How would you see this working from an editor perspective? How would the routes be assigned/generated? My first thought was zoneA to zoneB, but the more dynamic/automated, the better (less work for the mission maker). Thoughts?

In my experience, I have seen very few executables for DCS which could potentially contain a virus/worm/whathaveyou. Most are simple graphics and text files. One who does their homework should know who is reputable when providing an executable for public consumption. If you are wary of downloading from a random dropbox or Google drive, then don't. I'm sure others will let everyone else know if something fishy is going on. Obviously, the safest place to download from is the User Files section hosted by ED. I'm not sure that most people in this community will agree with your fears. When in doubt, ask. The posts you refer to, in my opinion, talk about false positives from "sensitive" AV software. We all use different ones, and have different settings. If you stick to downloading LUA scripts and graphics mods (DDS/BMP/etc.), I don't think that you will encounter any issues that would cause your AV any issues, or have any dormant shenanigans to worry about. </2¢>

I think our only option right now is to reduce the volume of the sound files ourselves. This might be something for the Wish List section.

I went through and cleaned up everything in the repository. I added a readme that should help you out if you are interested. https://github.com/chump29/DCS_Mod

There is nothing I can do about how the F10 map renders. I have found that turning on Show All Routes at the top helps it draw in real-time. The info font/color can be changed on lines 114-116: {0, 0, 1, 1}, -- font color in RGBA {0, 0, 0, 0.1}, -- background color in RGBA 10, -- font size EDIT: I added this to the config section so you wouldn't have to dig through the script.

Track history updated Updates every 10 seconds Shows 30 seconds of history Color-coded to altitude of unit < 1000ft: Green < 2500ft: Yellow >= 2500ft: Red Information box updated Fixed heading Moved further up Only shows for entire group, not per unit Updates every 1/4 second Removed goofy vector line See what you think now @ https://github.com/chump29/DCS_Mod/blob/master/GCI.lua

In the Beacons.lua file for Caucasus, it has the near beacon at Mozdok as: frequency = 1065000.000000; On the F10 map, it appears to truncate the value when in MHz. It should display 1.065 MHz in this format instead (or leave it in kilohertz as 1065). I notice that it is correct in the Mission Editor map.

I have the speed line in there, just not the vector pointer. I didn't know where to cut the track history off. If you have an idea, I'd be happy to implement it.

@ron533 I did some refactoring to get it more how you imagined it. I think DCS is limited right now regarding drawing in near-real-time. The velocity vector game me some pain, so I decided to hold off until DCS drawing tools become more fine-tuned. I also added some descriptions to a few of my scripts, although they were written for my missions. I tried to keep some more generic if you find them useful. Let me know if you see anything worth using. Take a look @ https://github.com/chump29/DCS_Mod

1) The last Stable release was on May 27th (2.7.14.24228). The Open Beta release that contained the South Atlantic terrain was released on June 8th (2.7.15.25026). My guess would be that it will be available for everyone in the next Stable release.

@ron533 Here is something that I quickly made to see if this was possible: https://github.com/chump29/DCS_Mod/blob/master/GCI.lua This uses MiST You need to adjust the map zoom to see the dotted line draw It updates every 10 seconds, mainly for testing This is a proof-of-concept more than a released script It should work with all blue plane/helo groups

If you don't mess with making missions, wait a few more days. Some people that are very skilled and generous with their time will have some missions ready to go on the SA map for all to enjoy.

I'm not sure where the EMBD object is coming from. Looking at your mission, there is nothing in there that seems to load anything external, nor any additional scripts in the .miz file. I see Tacview and SRS getting loaded up, but there are a few errors: 2022-05-22 00:49:52.607 INFO LuaNET: can't open 'C:\Users\Niklas\Saved Games\DCS.openbeta_server\Mods\Services\DCS-SRS\Scripts\DCS-SRSGameGUI.lua' 2022-05-22 00:49:52.609 INFO LuaNET: can't open 'C:\Users\Niklas\Saved Games\DCS.openbeta_server\Mods\Services\DCS-SRS\Scripts\DCS-SRS-OverlayGameGUI.lua' 2022-05-22 00:49:52.765 ERROR VFS: VFS_open_write: CreateFile(C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\Scripts/MissionScripting.lua): Access is denied. Make sure you aren't loading anything else from C:\Users\Niklas\Saved Games\DCS.openbeta_server\Scripts.

Reduce the collective when diving. Watch the rotor pitch indicator on the left forward panel.

This is also caused at mission start when you remove scenery via triggers.

You can always use a program like Scratchpad to jot down target coordinates then enter them into the PVI-800 as TGTs.

Open \Scripts\MissionScripting.lua and comment out the following line: _G['require'] = nil

I do see this in MOOSE (under SCORING): if self.Players[PlayerName].Penalty > self.Fratricide and self.penaltyonfratricide then MESSAGE:NewType( self.DisplayMessagePrefix .. "Player '" .. PlayerName .. "' committed FRATRICIDE, he will be COURT MARTIALED and is DISMISSED from this mission!", MESSAGE.Type.Information ) :ToAll() UnitData:GetGroup():Destroy() end --- Decide if fratricide is leading to penalties (true) or not (false) -- @param #SCORING self -- @param #boolean OnOff Switch for Fratricide -- @return #SCORING function SCORING:SwitchFratricide( OnOff ) self.penaltyonfratricide = OnOff return self end Here is the Documentation Reference to turn it off.

I don't see anything about being kicked for fratricide in me_logbook.lua, only to display the message: if (faa > 0) or (fag > 0) then missionScore = 0 for k, v in pairs(statType) do v.totalScore = 0 end -- обнуляем счет у всех самолетов for k,v in base.pairs(stat) do if base.type(v) == "table" then if (v.totalScore) then v.totalScore = 0 end end end displayDegradeWindow() end function displayDegradeWindow() showInfo(cdata.degradeMessage) end degradeMessage = _('You have committed fratricide. You have lost all your combat scores.'),

What/where is this Kentucky windage gunsight mod you speak of?

What values do you use to achieve such thin lines? 1.0?

You should be able to do this by changing the value for ground units in the labels.lua: GroundOn = true