SeaQuark

My personal philosophy is, these guys didn't have TacView: So neither do we. Holding an effective flight debriefing after landing is an important part of the mission. Self-assess your performance, compare to how the engagement looked to your wingman, and come up with a plan to do better next time.

You're in luck, Invisibull and I are putting together a virtual squadron for Sabres. Will be announced when ready. In the meantime, hit up the Discord. Lots of people like doing co-op flights on the server, of varying experience levels. I personally never fly without a wingman, and I would much rather give a newbie instruction than fly alone. As long as you know the basics of your plane (start up, take-off, landing, radios, arming weapons) I am happy to fly with you anytime.

Thanks again to all who participated in last night's event! Red team won the day. Tiger flight was annihilated, and Victor flight was bounced and had to abandon its mission. The loss of Tiger flight was primarily due to my own negligence as flight lead. In future events, I will definitely be placing more of an emphasis on flight tactics + cohesion. TIGER LEAD FLIGHT REPORT, SEAQUARK: Congratulations to RFJack, whose flight scored 3 kills with 0 losses. 6-3-1 FLIGHT REPORT, RFJACK: To address other questions: There is no TacView enabled on the server, I don't think I even have it installed. It definitely should be. There are lots of Red AA units around the field. Sometimes I have noticed a bug where a damaged player will be ignored as "dead" by AA units, but generally they should work. If you encounter this problem again, let me know. Last time I checked it was working. I'm OK with placeholders for AI units, but I guess as far as playable aircraft go, I'd like to keep it as close as possible to period-correct. I actually used to have Fw-190s on the old version of the server as LA stand-ins, but nobody really used them. If any Russian prop is added to DCS, I will almost certainly put it up on the server.

That's actually a good idea, not sure why I didn't think of that before. It's easy enough to do. I definitely wouldn't turn off F10 icon unless I put together some very comprehensive navigation resources, maps, and instructions for the server. But optional may be the best way to go, I think.

Correct, no armament on the TF-51. I will have 2 regular P-51 slots available just in case someone doesn't have their TF-51 set up. But the goal of the 51s for this mission is not to engage ground units, only to spot them, radio their location, and talk the F-86 Strike flights onto target. i.e. they will be acting as Recon / Forward Air Control. Note that the TF-51 version is lighter, more nimble, and has better cockpit visibility than the P-51, so it really does make an ideal recon plane.

Noted, thanks. Porco had to bow out, so for now I will move you to the MiGs to keep things even.

KOREA! 1952 is hosting a coordinated Recon / Ground Attack multiplayer event. Sunday, November 12th, at 2100 UTC. **** Mustang pilots-- please have your controls set up for the TF-51 (unarmed version of the plane). Mustangs will serve as Recon / FAC: search for ground units, report their location over the radio, and talk Strike flights onto target Sabres will strike ground targets + fly CAP Mig-15s will attempt to ruin Blue Team's day We will meet directly in the server at 2100. Briefing + mission will both be entirely over SimpleRadio. Just hop in your plane, power up your radios, and tune to the corresponding frequency for your aircraft (listed above) by 2100. GENERAL REQUIREMENTS: Have SimpleRadio installed, tested, and working. No exceptions. Be proficient in your plane of choice. Take-off, landing, drop tanks, ordnance, external lights, etc. Understand how to operate your plane's radio, and be comfortable switching channels / frequencies in flight. Understand how to plot & interpret MGRS grid references. e.g. "FJ2662" Be prepared to fly as part of a team-- follow orders from your flight lead & squadron commander. If you are able to attend, please post below with your plane of choice. Positions are available unless noted otherwise. SIGNUP SHEET: SABRES: morpheus Grumpy 7st_AH Rob 7st_AH Mastiff 7st_AH Shamrock 7st_AH Barnacles pawel MUSTANGS: SeaQuark Bug Balzarog MIGS: SHaDoW STeP BG <51>Rage FF*RFJack*13 FF*CMF*04 Metzger (A/229) Showtime BLUE BRIEFING: Radio check-in at 2100, on COLT channel (C / 10). F-51 take-off at 2115. F-86 take-off at 2130. Steer to HOLDING POINT X-RAY (TBD). F-51s will search for targets within approx. 30 mile radius of BULLSEYE. When you find a target, switch to GUARD channel (D), call out grid reference and target description. Repeat your transmission, then return to COLT channel © to await further instructions. Next available F-86 flight at X-Ray will be tasked for the target. Swicth to COLT channel (10), and ask F-51 for talk-on to target. When target is destroyed, call it in on Guard that you are ready for additional tasking. Return to X-Ray and await next reported target. Recon F-51 plane will be released to search for additional targets. Keep unnecessary radio chatter to a minimum. Flight leads will handle all comms between flights. Continue for as long as fuel / ordnance permits. Upon RTB, flight leads will note # of targets destroyed vs any flight casualties. Deliver After Action Report to SeaQuark on forums. RED BRIEFING: Radio check-in at 2100, on wave# 151. Take-off at 2130. When airborne, flights will tune to their predetermined Flight Mission frequencies, and patrol 30-40 mile radius of Bullseye. Each flight will be tasked with a primary area + altitude-range of responsibility. Search for contacts visually and by listening for Air Warning Command alerts. Once contact is made with the enemy, pursue & destroy, then return to your patrol area. Continue for as long as fuel / ammunition permits. Upon RTB, flight leads will note # of enemy aircraft destroyed vs any flight casualties. Deliver After Action Report to SeaQuark on forums. --------------------- The KOREA! 1952 server is open 24/7. Stop by anytime to practice your skills, and familiarize yourself with the server. See the general server thread here.

For the record, at some point down the line, I would like very much to remove the F10 icon. I expect to try turning it off on a trial basis, sometime in the near future. In the meantime, I recommend everyone get in the habit of tuning your NDBs before take-off, and practice dead-reckoning when you can.

Thanks to a helpful tip from Ciribob, the creator of SimpleRadio, the F-51 flights are now fully able to communicate with the F-86s on SRS. A = Tower B = Boston C = Colt Flight (F-51s) D = Guard The Tower, Boston, Guard, and Colt channels are all shared between F-51s and F-86s. This will be very useful for general team coordination, traffic calls, Recon flights, or requesting escort / assistance from the jets. Briefing has been updated: Recommended procedure: if you need to contact the 86s from a prop plane, switch to channel D [Guard] for a brief message explaining your situation, and requesting available F-86 flight to switch to COLT's Flight Channel (CH. C for Mustangs, CH. 10 for Sabres). Remember, Guard channel broadcasts go out to the entire team, so it should only be used for emergencies, or to get another flight's attention-- the rest of the discussion should then proceed on your own Flight Channel.

Links to all of the information you could ever want about SimpleRadio is posted in the "server info" section of my Discord. Here it is for you: How to install SimpleRadio: https://forums.eagle.ru/showthread.php?t=169387 SimpleRadio Troubleshooting: https://forums.eagle.ru/showpost.php?p=2963204 Official SimpleRadio Support & Discussion Discord channel: https://discord.gg/5ak4jJr

Hey Balzarog, I'm always happy to help new users get up & running with SRS. And if there's some snag I can't handle, I can pass you off to the SimpleRadio troubleshooting channel. As for Discord, I'm a little confused-- if you are running Discord already, then isn't it already working? Just click on the Discord invite link at the very top of this forum post. It is listed in the server Briefing as well. You should then be able to select KOREA!1952 from your available Discord channels. Once there, I'd be happy to answer any other questions you have on Voice or Text chat.

Easy Communication is turned Off on the server. When in the air, you press your aircraft's Mic button to bring up the menu. For me it's RALT+ \, but I don't remember if that's the default for all aircraft.

I know it may seem silly to some, but my approach to the server is simple: if they didn't have it during the war, then it doesn't go on the server. This guy didn't have Tacview during his debriefings. Neither did this guy. We Sim pilots already have the rather enormous advantage of being able to return from the dead. A God's-eye-view of our last engagement does not strike me as necessary to becoming better pilots-- it may even be a distraction. As the real pilots did, ideally you should learn to recognize by instinct what it looks like from your cockpit when a dogfight is going wrong. The limits of that perspective is all part of the challenge. I totally understand others have different opinions about this. Thank you for flying on the server! I am open to any & all suggestions that will increase realism & historical accuracy.

Hi Shadow, there are indeed some bugs in the Russian ATC, I hopped on today and noticed what you are talking about. Will look into the mis-matched messages. Correct, 3.75 for Tower, 3.80 for Intercept orders. Yes, the other frequencies listed in briefing are for the bullseye calls. Each flight has its own pre-designated freq. to fly the mission on, to make it easier for you to coordinate via SimpleRadio. 3.85 is the frequency for Flight#1-0. The Bullseye calls require some slight effort on your part, but the advantage is that everyone on your team who hears that message will receive situational awareness. At the moment, most "bombers" do not drop ordnance, but on some days you may find a large flight of them that will "drop bombs" (trigger explosions) at Maykop + the red airfield. EDIT: * I think whether the F10 displays in nm or km can be changed in your own DCS user preferences, if you plan to fly the MiG on the server a lot, consider switching it. * Thank you for you feedback-- as I do not speak Russian myself, I rely on feedback from Russian-speaking players to correct any mistakes I've made. = )

Big thanks to all who showed up and participated in tonight's event! -photo by Sixshot, the mission in action from his F-86 Red Team won big time! The bombers were annihilated. Given that this was our first event, there were a few snags, but overall the mission ran as intended and generated an intense aerial battle. Server has resumed running normal missions, open 24/7. No need to wait for the next event-- drop in anytime!

Hey Talisman, Setting up new software can sometimes be a pain in the neck, and I certainly wouldn't want to do it with a ticking clock leading up to an event. But I definitely recommend giving it another shot later-- lots of DCS groups are moving to it. On my server, Discord is really just a springboard to get your flight onto SimpleRadio, using the aircraft radios in your virtual cockpit. That's what's great about it. Another voice service like TeamSpeak isn't so useful for this-- it's just an extra, unnecessary link in the chain. Whereas Discord is more about keeping in touch through persistent text chat / message boarding-- the Voice feature is more of a bonus. This is the kind of stuff people usually get up to in the Discord: Someone will post an alert, you'll see it on Discord if you're around (or even on your phone if you choose). Then we hop into the server, and meet up in DCS on a pre-determined radio channel in the cockpit-- like you would in a real plane, following real radio operating instructions & procedures: We fly the entire flight that way. And if you crash / die / land & leave on the server (= lose radio contact in DCS), you still have a line of communication open on Discord, for debriefing or just saying "gg, see ya later." Anyway, that's why you see tons of DCS servers switching to Discord, as SimpleRadio has become more and more popular. It's a winning combination. If you want help setting either program up during the week (when there is not a ticking clock leading up to an event) just shoot me PM and I'll try to meet you at a time & TeamSpeak channel of your choosing. We'll do a few more events now and then, probably at different days/times. But the server is really all about the 24/7 PvP experience, so don't sweat missing any.

Reminder! Bomber escort / intercept event on KOREA! 1952 is happening tomorrow, Sunday, Oct 8 at 2100 HRS UTC. This event will occur on the public server, open to all, but for those interested in participating in a teamwork-driven way, meet in the Discord voice channel at 2100 sharp. NOTE: Please have SIMPLERADIO installed and working. Each team will be sorted into flights of four. Bring your friends & wingmen! If you end up in a flight of other strangers, be prepared to speak up and volunteer as flight lead if you have the experience. There will be 30 minutes allocated for each side to plan their flight. Mission will begin at 2130 UTC, or when both sides are ready. The server may or may not be restarted just prior to mission, depending on playercount at the time. Mission start will be marked by a scramble call at airbase. Load fuel tanks, start-up, and take-off quickly but in orderly fashion, following all the typical procedures listed in the server's briefing. Then simply follow tower instructions after take-off.

Thank you all for the feedback, both here & on Discord! Has been very helpful in fine-tuning the server. I am looking into this-- the technical side of it is a little above me at the moment, but I hope to provide an interim solution soon. I believe with low contrails, EWR broadcasts, and the F-86's quite striking smoke trail, situational awareness is just about the correct level of difficulty on this server currently. Even if it is a little unreasonably hard to spot people on the deck, this will only encourage the kind of flying that this server is all about: proper CAP flights at altitude, with mutual visual coverage from wingmen, and not just lone wolves trawling the deck for stragglers. The label mod also has serious drawbacks-- like seeing dots through your cockpit. I think for a WW2 pure dogfighting server, there is a good case to be made for using the label mod, but less so in a mission-based Mig vs Sabre server like this one.

Delta has it about right, most important thing in Multiplayer is always just to be considerate and read the briefing. I would say the only things you really need to know to fly any mission on the server are: * taxi/take-off/landing * how to use your radios * what a bearing is * how to read a Pretty simple stuff. In general the 50s planes are "easy to learn, hard to master" and that's the fun of it. If you want a quick orientation flight in the Sabre on the server sometime-- and you're willing to get on a mic-- hit me up on the Discord. I'd offer the same in the MiG, except I'm still basically a noob in that plane myself.

Folks, can I just say, I am completely thrilled with the turnout & response so far. I put a ton of work into increasing the reliability of the server & new features, and you guys are really making me feel like it was all worth it. Thank you so much. I would also like to reiterate that the server is still in its initial testing phase-- once all bugs are worked out and I know the basic template works 100%, I will continue to add possible objectives. Mission variety will only increase over time. Delta's post above is correct, use of GAR-8s would not be historically appropriate to the Korean War. This was a guns-only, "last of the duelists" era of air warfare. Of note: the MiG has higher-caliber guns, yes, but flown properly, the F-86-F can almost completely control the engagement. A MiG pilot might claim it's the Sabre who has the overall advantage, and I would find it hard to disagree with him. Which factor becomes the deciding one in the merge depends entirely on pilot knowhow and teamwork. No. In general, server will stay on Caucasus, as I believe it remains the best stand-in for the Korean peninsula. Additionally, I would like to keep the server A) in one place, and B) on the basic map included with DCS World, so as not to limit the potential audience of the server. Along with everyone else I am eagerly looking forward to the eventual facelift of the Caucasus.

Hey thanks Delta, glad to hear it. I think I can manage that, was working on a system like that before and just didn't get around to finishing it. Will try to include in the next big mission update.

Nevermind! Turned out the guy who was having this problem thought he was running the latest version of DCS, but wasn't. He forced an update, and shazam, problem solved. I am starting to learn that being a server host means I will get a lot of troubleshooting questions that may or may not be related to my server!

I think we had ~26 players on at one point today! Runway got a little busy, but overall good order was kept, and the Tower only had to scold a couple people. Keep it coming, guys. There were a few mission bugs noticeable today, which I have fixed. Apologies to Red team about the repeating transmission on their ATC channel-- the Tower should work properly now. Thanks for playing, Al! Not keen on adding my screenname to it-- I did that last time around, but I suspect the server will appeal more to random joiners if the name is clear & concise and explains what the server is all about. I would definitely consider removing the "----"'s from the title; someone advised me to add special characters to make the server easier to see; personally, I don't really get it, I'd kind of rather just have it start with KOREA and then people can find it by sorting alphabetically and looking for "K". But hey, it seems to be working, we got a bunch of people online today. If anybody has some sage words of wisdom about this matter, I am all ears. That's the way a lot of servers do it, but do me a favor and try it the way I have set it up for you first, and tell me what you think: If there are no / few players online, call Ground Control for a mission. During your mission, tune to your Flight Mission frequency-- if bandits are in the air and approaching the general combat zone, you will receive their Bearing & Range from Bullseye, plus their altitude, over the radio. (I think that's way more useful than just hoping the enemy will go after ground targets at Bulls) If you're a finicky fighter pilot and don't want to fly the mission from Ground Control, you may also search for hidden ground targets anywhere in enemy territory, on your own initiative. Just stay tuned to your Flight Mission channel / frequency to be kept up-to-date on bandits near the Bullseye. There's also nothing wrong with doing a straight up CAP flight and cruising at high altitude (in contrails) over the combat area. Trust me, you will find bandits quickly-- plus you might even start from a position of advantage.

I know what you're talking about, that's a different issue with the Radio Transmission triggers. Makes sense, but not what I'm running into here. All of my Transmit Message triggers are on ground units, and triggered by various circumstances or Client actions (enter a zone, press a F10 radio menu button, etc). Then the (brief) sound file is played whenever called for via Switched Condition. So there is no looping necessary, no one time that the sound needs to be loaded. When in the mission, the one player with the problem can trigger all the necessary actions at any time, and other players can hear the sounds-- but he can't. That's why I feel like he's had some kind of issue downloading the necessary files from the server. But the issue has remained after system restarts, repairs, and a new mission file, weirdly.

I have a Multiplayer mission that involves Transmit Message triggers with sound files for AI units. For most people, the messages work fine online, but I have one person who is unable to hear any of the sounds, despite being on the correct frequency, in radio range, and radio on. He is not hearing the sound files, or seeing the accompanying subtitles. I double and triple checked it to make sure he wasn't doing anything wrong. What troubleshooting advice can I give him? He told me the game did crash for him once, and he had trouble getting back into the server for a bit. Now he gets in, but receives no radio messages. I am unsure if the sounds were working for him before his crash. EDIT: PROBLEM SOLVED. Turned out he just hadn't updated DCS World. Update went through, problem solved. Case Closed.