ChuckIV

Welcome cknight5464! SRS is a great way to communicate for full immersion. You have to press a button to speak with your squadron members. SRS even has sound effects so that the transmission sounds "radio-like". Discord is also an excellent tool for comms. DCS provides it's own "radio" as well I believe. Our Spitfire squadron uses both SRS and Discord depending on what we're doing that evening. Discord is great when you have a connection problem with a DCS server and end up losing the connection. Discord continues to work so you can still speak with your members while you reboot and get back online. SRS, I believe is only connected WHILE in a DCS server. Anyone, chime in if I'm missing something. ChuckIV

Phil, (and anyone that wants to chime in), OK, I'd like to start a poll of how long the time interval should be for the EWRS system. Currently, I believe Phil has it set for 6 minutes. With WWII aircraft flying at around 300mph, this is about 30 miles of travel before the next call. This is farther than you can even see!!! (about 26 miles right?) I vote for a perfect middle ground; 3 minutes per call. What does everyone else think?

I fully agree - that being white dots do NOT belong on infantry FOR SURE!!! I understand the white dots are a sun reflection, and that's GREAT for airplanes, but not small camouflaged ground units. KEEP THE WHITE reflection dots for planes, but feel free to remove them for everything else. I've tested the reflection white dots; they go away when in shade or when the sun is in the front of you. This is very realistic - if you have the sun to your back, you would see white dots (reflections) of planes for sure. Try it for yourself - put the sun to your back; you see white reflection dots. Put the sun in front of you, and the planes disappear. You got this correct DCS - keep this the way it is!! (for planes only). ChuckIV

I fully agree - that being white dots do NOT belong on infantry FOR SURE!!! I understand the white dots are a sun reflection, and that's GREAT for airplanes, but not small camouflaged ground units. KEEP THE WHITE reflection dots for planes, but feel free to remove them for everything else.

Gurus?? Anyone have the time to input a little lua script together so a RED coalition pilot can TransmitMessage to a BLUE coalition on the same frequency in a waypoint using run script???

I’m pretty sure I tried that. Did you try it in the mission yet to see if it works? I thought there was an issue because they’re in different coalitions.

Thanks for the reply toutenglisse, but I'm looking for a way to REDUCE the number of triggers I'm using. I need to do this at waypoints using run script instead of using zones as triggers.

ME Gurus, I need your help. I've attached a VERY simple .miz file to show what I'm trying to do in the Channel Map. I have an enemy plane (Bf109) flying a route, and at its waypoint 1, I want the run script command to put out a written message and a sound message on a frequency of 125MHz AM. I added the sound file (.ogg) to the Allied Spitfire (client that needs to hear the message), to the Axis Bf109 that has the WP1 used, and even an Allied Willlys Jeep at Manston AB for comms for you to use as the sound source. I have the written message working for the client (it's just sent to the entire Blue coalition); it's the sound message I need your help with. I have searched the forums and Internet for the proper lua code, but to no avail. Could one of you lua code Gurus open my .miz file and add your magic code to the Bf109's waypoint 1 (run script) command? Please repost with the working .miz file. Any help would be EXTREMELY helpful! Thanks in advance, ChuckIV TransmitMessage Test.miz

COMMS My comms do not work with the ATC in both SP and MP. Also, I'm suspecting that SRS is also a bit bugged with the Channel Map.

Here are several BUGS that need addressing at your SOONEST CONVENIENCE... PLEASE. Create your own .miz file and see these behaviors/lack of... 1. In sorties before 05:45, AAA will not work; fighters will not engage either ** In WWII, there were MANY, MANY sorties started out before 04:00 ** 2. Ju88 bombers are not engaged by Bofors guns. Fighters ARE engaged. 3. ATC comms still do not work in the Channel map 4. We have yellow/orange flashes on the screen after latest update. 5. Temperature is still locked at 0 deg. C. Pilots, please add your input to this thread to confirm!!! ChuckIV

Hi Everyone, I was hoping you could suggest some solutions for my stuttering mission that I'm creating... I suspect two things that are causing the stuttering... First, I have numerous SWITCHED CONDITIONS in my mission that may be causing stuttering in-game. The switched conditions are used to turn off Group AI in zones assigned to those units. I start the mission with turning OFF all Groups' AI. Then, as enemy units enter their zones, their AI turns ON. These are mainly AAA units, but there are a few other vehicles/ground units. So, my guess is that with sooooo many switched conditions, this may cause some stuttering. Secondly, I wrote a simple MOOSE.lua file to spawn all the aircraft in the mission. They are all set to REspawn on landing, engine shutdown, and I use the CLEAR function set to 60 seconds for all aircraft. I suspect the ongoing spawning is causing stuttering as well. ANY suggestions you have to help with my stuttering would be most welcomed!! BTW, I have a new system, i9 CPU, 2080Ti card, 32 GB of RAM and very fast internet speed. Thanks for your help Everyone, ChuckIV

I think I figured it out. If I use InitRepeatOnLanding, InitRepeatOnEngineShutDown, and the CLEAN function all at the same time I think it works pretty well. I had to also include a scheduler function that includes the spawning itself

A flag is a placeholder that is filled with either a 1 or a 0 (zero). So, if flag 6 is true it is equal to 1. So you could say Flag 6 = 1. If flag 6 is false, it is equal to zero. So, flag 6 = 0. Now that you know what flags are, you can use them to do some pretty cool stuff. For example, you could set a trigger in mission like "If enemy is in this particular zone, set flag 12 to true, or 1. Then you could set up a message to tell someone something. Like this... If flag 12 = 1, then output this message "Hey, look out someone's entering your zone!!". Hope this gives you an idea now of what flags are.

I am new to SRS but isn’t there a toggle option for this pop-up?

For me, the problem ended up being the Xfinity routers built-in security. There is an app that lets me turn The security off. Then players could see my server on the list. make sure your router doesn’t have a built-in security firewall

Can someone show me the scripting for this scenario... Spawn a Bf109 group of 4 infinitely that will respawn if they all die OR if any of them land. Thank you in advance ChuckIV

SSAA? or MSAA? Try switching to SSAA ONLY - Turn off all other antialiasing. Might help

Please confirm... Are your ATC comms working?? I get no response whatsoever, and I’ve triple-checked the frequencies. ChuckIV

It might be REM at the beginning of the line

I'm ALSO putting this thread here because it is the mission designers like us that create multiplayer .miz files, and I need your help... I need help with creating the correct folder structure inside the .miz/.zip file so that players are automatically given the skins, labels for spotting, etc. that are to be used in the mission when they join. If you have experience with creating these folers within the .miz/.zip file, PLEASE enlighten me as to the exact structure I must use for DCS to "find" the necessary files upon loading the mission. If you have a SAMPLE .miz file that has all the folder structures, please attach as an example. MODERATORS: You are MORE than welcome to respond here as well if you have the folder structures I need here. Thank you Everyone, ChuckIV

Other guages Don't forget, if you have trouble with using the RPM guage, there's other guages like oil pressure that will indicate when an engine is started or stopped. ChuckIV

Sunstag's Marston Mat Mod Try using Sunstag's MARSON MAT mod. Maybe you can line up his mats and cover the outside lights with buildings, etc. Just a thought... ChuckIV

Drop the "thickness" Try dropping the density to 0.01 - might help a little.

I'm putting this thread here because it is the mission designers like us that create multiplayer .miz files, and I need your help... I need help with creating the correct folder structure inside the .miz/.zip file so that players are automatically given the skins, labels for spotting, etc. that are to be used in the mission when they join. If you have experience with creating these folers within the .miz/.zip file, PLEASE enlighten me as to the exact structure I must use for DCS to "find" the necessary files upon loading the mission. If you have a SAMPLE .miz file that has all the folder structures, please attach as an example. MODERATORS: You are MORE than welcome to respond here as well if you have the folder structures I need here. Thank you Everyone, ChuckIV

Multiple Inputs Check to see in your control settings that you don't have more than 1 input for each control surface. (i.e. you don't have rudder controlled by several different inputs at the same time) ChuckIV Also, once you have all your control settings perfect, I highly recommend that you back them up in a new folder somewhere on your hard drive.