SeaQuark

Good first night on the server! Very encouraged to see a number of folks using the SimpleRadio. Bounced two MiGs at altitude. Chased one down to deck, used up all my ammunition, and had to high-tail it when his wingman showed up. He was trailing smoke, but AFAIK he survived to fight another day. Later, had a very professional flight with Mike 3. Dropped ordnance on enemy tanks for "Roadrunner", then met another MiG, thanks to heads up from "Daisy." No hits, MiG escaped, and we RTB'd.

Thanks man! 39th Squadron is welcome at K-13 anytime.

SERVER NAME: ---- KOREA! 1952 ---- DISCORD: https://discord.gg/KqpQSSC SIMPLERADIO: 24.90.76.154 DCS VERSION: OpenBeta NEWS: *** 10-26-18: Server mission back online ---- MISSIONS AVAILABLE: * COMBAT AIR PATROL * CAS * STRIKE * ARMED RECCE * INTERCEPT / ESCORT CHOOSE YOUR SIDE: U.N. FORCES / U.S.A. BRIEFING F-86 P-51 TF-51 Spitfire (stand-in for Seafire) D.P.R.K. / SOVIET UNION BRIEFING MiG-15 Yak-52 (stand-in for Po-2) Fw-190 (stand-in for Yak-9) It is recommended to use SimpleRadio to announce all take-offs and landings. www.korea1952.com ------------------- - SQ

Hey, just a heads up for anyone still watching this thread: the new server is going to be ready this weekend. It is currently online (password-protected) for play-testing while I work out the bugs. If you want to help try it out, just stop by the Discord server for the password. I will be retiring this forum thread, as the new server is completely different, with a new name, all the info here will be outdated. Will be officially announcing the new server very soon. Stay tuned!

Yeah, for now, as placeholders for Soviet props. This is still my 'old' mission. I should note that going forward, I will probably simplify things and restrict the server to Mig-15, F-86, F-51 (i.e., strictly planes that were available during Korean War). Doesn't seem like many people are using the 'placeholder' units (German props, Hueys), and I don't blame 'em.

Thanks Javelina. Yeah, I didn't announce it officially yet, since I'm still working on it. But y'all might as well know, the Server is back up on a *hopefully-most-of-the-time* basis. I am running the same mission as before. Currently testing out new hardware for the server while I work on a new and much improved Korean War scenario. Will keep you all posted, but in the meantime, if you see SQP: KOREA! up and active, feel free to join in. Please excuse any technical difficulties during this transitional period. As always, the Discord is open, and a great place to connect with other Mig or Sabre pilots.

Feel free to stop by my Discord channel anytime; there's a bunch of folks who fly the Sabre & MiG there. I'm in the process of re-launching my Korean War multiplayer server (was on hiatus for a bit). https://discord.gg/KqpQSSC - SQ

I'm building a multiplayer mission that involves scripted calls to / from the ATC, so I will not need to use DCS' built-in system. Only problem is, I can't seem to keep the player's ATC menu from automatically opening when taxiing to the runway, even if the aircraft is not tuned to that airfield's frequency. Is there any way to stop this from happening?

SeaQuark - F-86

Unfortunately, I am closing the Korea server for now. My server PC just wouldn't run DCS reliably, and frankly, I lack the funds to upgrade / replace it at this time. Plus with the release of Normandy, I think there was waning player interest in a Korean War server on 1.5-- just bad timing. Big thanks to everyone who hopped on and gave it a shot, I hope you had fun. I learned a lot about mission-making and running a server; I hope someday to give it another shot, running either Korea, WW2, or other historically-minded multiplayer scenario. The Discord channel will remain open in the meantime as an informal flying club and meeting spot; mostly we have been flying props on Normandy, so if you are in need of a wingman, feel free to stop by. Discord = https://discord.gg/KqpQSSC

Sure thing, adding in F-51s as we speak. Been meaning to do that for a while. EDIT: Red team will get German planes as stand-ins for Yaks and La-9s.

OK, I'll look into both those issues. I just successfully did that twice yesterday. Are you sure you are in the RECON plane that takes off from Kutaisi? You will have the option to (incorrectly) take the photographs soon after you start flying towards enemy airspace.

Brilliant news!

Hey Reflected, I apologize, as many of the features in the mission are work-in-progress (especially the radar sites). Most people are just using the server for dogfights, kudos to you for checking out the objectives. I am just now finishing up the new briefing pages that should cover all these features for the Blue side, hopefully this will help clarify: As for your first point about FH9623-- that is all the information you need. The "23" aren't random numbers, that is the next level of detail in a grid reference. Once you have found FH96, imagine that square is in turn divided in 10 horizontally and vertically. Count 2/10 spaces right, then 3/10 spaces up. The secondary targets will not be the same every mission rotate, so you will need to understand a grid reference to find them. In regards to the tanks: the Primary target is designed to be beefy, you should not expect to kill everything there by yourself or in just 1 or 2 flights. 3 or 4 Sabres with a full load of rockets should make short work of the tanks. Teamwork is highly encouraged-- you can always join the Discord to find flying buddies. If you do find yourself on your own, the railcars and buildings make much easier targets. Don't sweat too much about the other frequencies, CH. 1, 2, 5 are all you really need-- if you need any other channels during the mission, Boston will direct you to them. About the Huey distances being too large-- this is the sort of thing I definitely need feedback with, since I don't fly the Huey myself. If you could suggest some possible locations for the chopper base given the radar locations above, that would be a big help. I didn't realize sling loading is bugged. In what way is it bugged? Is it impossible to use? I had someone using it in the server a while ago.

You should keep your SimpleRadio push-to-talk and mike button separate because you wouldn't want to pull up your in-game radio menu every time you talk to your wingman. Right? This may also be causing your problem of the radio menu not working for you. The regular \ button will work while you are on the ground because otherwise you couldn't contact your ground crew to turn on the ground power.

Easy Communication is OFF on the server. You have to turn the radio on (always set to TR+G), and use your radio button in the cockpit of the plane to bring up the radio menu. I believe by default the key is: RALT+ \ As for SimpleRadio in general-- the point of SimpleRadio is to limit you to the radio options available in the cockpit. You should not need to use the overlays to pick frequencies at all, unless you are using the Spectator / Forward Observer slots to provide GCI. There is no need to alt-Tab, simply use the UHF radio in your cockpit. Just work out with your squad which channels you will use. For instance, Flight 1 could take Channel 12, Flight 2 could take Channel 13. It is very unlikely all 18 channels will be in use. A breakdown of the channels available follows: CH. 1 = ATC (mandatory-- call all your take-offs and landings on this channel) CH. 2 = MISSION (general-use, public channel for all F-86 flights) CH. 3 = [free] CH. 4 = [free] CH. 5 = BOSTON CONTROL (use radio menu to call for tasking and mission information) CH. 6 = BOMBERS (B-29 chatter can be heard on this channel if they are called in) CH. 7 = GROUND FORCES (Boston may direct you to this channel for C.A.S. information) CH. 8-18 = [free] Simply pick any free channel for your flights. Switch between channels as needed. If you are trying to reach someone and you are not sure what channel they are on, you can always use the GUARD channel to transmit to all flights. Just use sparingly, so as not to clog public airways. Whenever you turn on your radio, always turn the dial to TR+G so you can hear emergency Guard channel transmissions. (general SimpleRadio info is posted in the Discord and Server subreddit and mission-specific channels will be listed in Briefings if available) Additionally, feel free to use the Server's Discord channel for general socializing / non-mission voice chatting and flight planning. SimpleRadio functionality is the same for the Red side, except instead of Channels, you manually tune to the desired frequency. See Briefing for ATC and MISSION freqs. (also, the MiG-15 does not have any Guard channel functionality)

I'm not quite sure I follow you Roblex, what goal are you trying to achieve that isn't possible with the 18 channels + Guard available to you currently in the mission?

For now, the server doesn't allow the "Simplified" easy nosewheel steering option. The realistic way to use the nosewheel steering is to press down the nosewheel steering button before applying rudder, and holding it down until you have completed your turn, otherwise it will "lose track" and you will have to cycle the rudder pedals while holding the button down to recover it. A minimum amount of throttle is also required to power the nosewheel; if your throttle is on idle for too long during a turn, your nosewheel may "go to sleep." DCS has Simplified Nosewheel Steering on by default in the Special options menu for the F-86, and many people don't realize they are learning an incorrect method of taxiing the plane. Hmm. This is very weird. I haven't encountered anything like that, although one other person has told me their Sabre once blew up randomly upon first spawning in (not in the air). It may be related to the flak script. If you encounter it again, it would help to know what A/C slot you were using when you encountered it.

Basically over the last month I have been adding all sorts of features / additions to the mission to increase fun & immersion-- for example, you can now call for detailed objective status & target information over the radio in your cockpit. Next I will be adding era-appropriate Early Warning Radar alerts in a similar fashion. Once it is all finished, I will "copy & paste" the basic template of the mission to create different variations in different spots on the map. I got a little delayed in that, because there were technical issues with the PC I was running the server on, with frequent crashing. I have since moved the server to my personal DCS machine and so far (fingers crossed) it has been running flawlessly. So server will be up and running while I work on a more permanent solution. In short: more missions will be coming eventually, but first I want to make this one is the best mission it can be, and to sort out the bugs of DCS server-hosting.

So I got the Radio Transmissions to work with the "subtitles" fine in Single Player-- but in Multiplayer, for some reason, all the text fades out the second it appears. I have the duration set to 20 seconds, works fine when testing in Mission Editor. But online, the text instantly goes away. The sound transmission itself works fine. Any thoughts on this?

I second the notion that VR gloves + this is what's really promising. Even better would be: give the pilot's body animations and link the animation to the position of the hands. This would be pretty darn close to actually sitting there in the pit.

Yikes, that just doesn't seem right. Hope this gets looked at soon.

If someone could make a label-mod where the specks weren't visible through the cockpit, I would gladly consider implementing it. Spotting a bandit through my altimeter isn't the kind of experience I want from DCS. Aside from that, I honestly haven't had much issues with spotting in these jets. Keep in mind these aren't WW2 birds-- a lot of the fights will happen at or above contrails, which obviously makes initial spotting quite easy. Plus, the Sabre's long smoke trail is striking at any altitude. I personally fly the Sabre and have had zero issues spotting bandits high or low. P.S.: Weren't Imposters disabled a long time ago? Did ED reintroduce them?

Alright, will do, thanks for the help.

That sounds awesome, although your caution about use in multiplayer is worrying. Maybe I should just stick with Messages and Radio Transmissions, so far they have been very reliable in MP. I am building a method through which players can receive dynamic ground target tasking via their radios based on mission conditions. It would have to work reliably, otherwise players would be unable to find their objectives.