Invisibull

Thanks Fakum! Wishing the best for you as well of course. We are always on the look-out for Huey pilots so if you make that leap please let me know.

Why are you starting a new thread when I answered you here? http://forums.eagle.ru/showthread.php?p=2303453#post2303453

If you're currently using JSGME this will take all of 1 minute to accomplish. Just unzip the attached into your JSGME mod folder. If you're not using JSGME by now, you really should be. After installation, you can change the settings via the SweetFX_settings.txt file. The settings are explained within that file. If you don't have JSGME and refuse to use it, just follow the folder structure and dump the contents into your C:\Program Files\Eagle Dynamics\DCS World\bin folder. DCS SweetFX 151.rar

Sorry for the confusion, kontiuka, it's on the third post in that same thread. I'll move it to the first one now to avoid future confusion for others. And to save you the trouble, here it is - https://www.dropbox.com/s/ita9p71tfq1oc37/39th%20FS%20Mod%20Pack.rar?dl=0

Hi Kontiuka, Glad you had fun, and hopefully the function required by the medevac script will be sorted out soon by ED. I'll certainly let you know when that occurs. I've posted a link on te 39th server page that will let you d/l our entire mod pack in one fell swoop. Is that what you did? If not, you might not have gotten all the North Korean tanks/vehicles. Hope to see you soon, Bull

Yes, and thanks for that, Grimes. The issue is that missions taking hours upon hours to put together and being enjoyed by full servers of pilots are suddenly booting all clients with no word whatsoever from ED about when we can expect them to work again.

This last update broke all my Huey SAR and troop pickup missions. Very disappointing because I spent quite a long time getting them just right and now no word on if or when the issue will be fixed. With word now coming that a World 2.0 release may come as late as June, I'm very leery to waste time building missions and doing modifications in the future if these updates are going to keep breaking them.

Glad you're enjoying it, Psbob. I am too. Feel free to join my server if you'd like to fly with some like-minded folks. Regards, Bull

Hi Chuck, I must be missing something here. You joined a server entitled "Invisibull's Korea*1953 Teamspeak REQUIRED Read Briefing" and were kicked (not banned) after you made it clear that you had no intention of complying after being politely asked three times in text to join us on Teamspeak. What did you think the outcome was going to be? In what way were you treated rudely? I'd appreciate future communications of this tone be transmitted privately. Thanks, Bull

I certainly hope so. I spent quite a bit of time implementing and testing the Medevac script on my server only to have the update break it the next day.

The Real Flying Cobras The 39th FS was attached to the 51st Fighter Wing in June of 1952, and was the first squadron to receive the new F-86F models of the Sabre. Flying out of Suwon AB, the 39th FS put up some impressive numbers during the war with 103 confirmed MiG-15 kills. This was due in no small part to their most prolific pilot and top American ace in the war, Joseph McConnell, who himself was responsible for shooting down (16) MiG-15s. The 39th, known as The Flying Cobras, differentiated itself from the other squadrons by having a black- checkered pattern painted on their vertical stabilizers.

Who Are We? We’re an online tribute Sabre squadron modeled after the storied 39th Fighter Squadron flying out of Suwon AB during the Korean War. We stress following a clearly defined Standard Operating Procedure in order to assure cooperation and maximum immersion. While realism is very important to us, we will never take it to the point of becoming overly burdensome or obnoxious. We stress formation integrity during all aspects of training and combat, and we endeavor to use clear and brief comms at all times in order to allow for a high level of situational awareness for all engaged pilots. We most definitely do not run a free for all “Airquake” style server. While the F-86F-35 Sabre is our primary aircraft, we also fly the Mustang and Huey helicopter. The Huey was added recently after I was able to integrate a SAR script into our missions as mentioned below. Understanding that the Huey did not actually see any service during the Korean War, it is one of the necessary compromises I felt comfortable with in order to bring a MASH/Search and Rescue (so important to the Korean War experience) element to our missions. This aspect of the mission was fully tested last night and I’m pleased to report that it worked perfectly. Finally, I have also taken full advantage of some excellent WW2 and Korean War mods released by both Lilkiki and Markindel. With their permission I have packaged their mods into one easy JSGME folder which you can get here. These mods add the tanks and vehicles actually used during the Korean War and will eventually become mandatory on my server. If the above sounds like something you’d be interested in being a part of, please add me on Steam (Invisibull) so I can keep you apprised of future sessions. Regards, Bull

Oh, Man, Perfect! Ty Lilkiki.

Doesn't get better than this. Well done SilentGun. Oh, there you are.

I've had such a mod up for a few weeks. You can get it here: http://www.digitalcombatsimulator.com/en/files/1169830/ This will remove cockpit shimmering when zoomed out, and also replace the current canopy with a clearer one. Enjoy, Bull

Two weeks ago I installed BMS. I had been a huge fan of Falcon 4 for years, but once i ran it, the graphics just took my head out of it instantly. I have a very hard time believing that a DCS: F-16 running on EDGE would have any problem at all in making BMS instantly obsolete.

For those who are never quite sure whether their airbrakes are open or not, please find my new Airbrake Beep Mod attached. You'll get a faint beeping whenever your brakes are extended. I've only tested this on the Sabre, but I believe it should work for any a/c with airbrakes. This mod is JSGME ready, and I strongly recommend it being installed in that manner only. Enjoy, Bull Airbrake Beep.rar

Thanks for going to all that trouble, Charly. The community will greatly benefit from this.

39th VFS, 51st VFW Server name: 39th VFS KOREAN WAR Website: http://39thvfs.enjin.com/ Teamspeak = 68.174.240.125 password: dcs ***Important - I frequently check the TS server to see if anyone is waiting for a flight before putting the server up. So, if you're interesting in flying, please join the "Waiting For Flight" channel to convey your interest. Adding me on Steam is the quickest way to find out what the 39th is up to, and to express your interest in joining us. Get Steam here: http://store.steampowered.com/about/ My Steam ID is Invisibull If you'd like to fly with us please be sure to have the 39th VFS Server Pack installed. If you don't install the required mods, you will not be able to see the various tanks, jeeps and supply trucks being used on our server. The latest version was updated on 2/19/15. Join Us If you've flown with us and would like to join the 39th, please feel free to make your wishes known to me by registering and sending me a message on the 39th VFS website. Membership will never preclude your participation with other squadrons, it simply means you like what we're trying to do here and would like to have an active voice in the squadron going forward. All I ask of 39th VFS members is to always observe the few rules I've set out, and to help me in assuring the same of our many visiting guests. Standard Operating Procedures for the 39th VFS v1.1 (Please read and heed) This document is a provisional statement of the 39th VFS's SOP's. Please expect edits going forward as we continually strive to achieve operational excellence. 1. Find a flight. Please do not join a TS channel and start speaking until you know for sure that the flight is not in progress. If no flights are available, wait in the cleverly named "Waiting For Flight" channel for other pilots in order to form a new flight. After you've gotten at least a 2-ship of Sabres together, check in with all active flights. This does not currently apply to Mustang or Huey flights, which need only a single member in order to be tasked. If you're joining as a guest, please read the briefing and, if at all possible, join a guest channel on Teamspeak. 2. Check-In with other flights. Once you've got a flight together you'll need to check-in with the other flights to find out if anything's being tasked and to announce your presence. A check-in is accomplished by setting all other flights as whisper targets in Teamspeak and making the following call or similar: "Cobra flight, Viper flight checking in with X number of pilots." Cobra flight, if able, will respond with tasking information. At this point you will confirm you understand and would then begin briefing your flight. 3. Brief flight Flight lead will brief the flight. No one should be starting engines or fumbling inside the cockpit at this point. Having a pad to write down important information is recommended. Briefing should include load out for all flight members, joinup headings and speeds, cruise enroute speed/altitude, nature of sortie and bingo fuel amount. At this time a rendevous point should be established in case the flight gets split up during an engagement. 4. Start-up, Checklist, and Taxi Once briefing has concluded, all pilots will start their engines, go through the checklist below, and then call out that they are ready to taxi. Ready to taxi calls should go in order, i.e., no one says anything until lead makes his ready call, and then all will wait for #2 to make his call and so on. This will help lead know that once he hears #4's call, that it's OK to go ahead and taxi. Checklist: A. Airbrakes in B. Flaps down C. Voltage/RPM/Hydraulic pressure in range D. Control surfaces operation E. Fuel tank selector switch F. Canopy closed G. Take off trim set H. Pitot heater on (To be done right before take-off in order to prevent an overheat situation) 5. Take-Off Only one flight will lineup on the active runway (always 050 at Krasnodar) at a time. Flight lead should be in the right lane, his wingman slightly behind in the left lane, #3 on the left behind #2, and #4 on the right behind the lead. Elements will always stagger by at least 10 seconds. This is to say that #3 and #4 will never take off simultaneously with the first element. 6. Join-Up Join-up's will be accomplished as briefed. Recommended as a tried and true method would be for leader to turn to enroute heading as he arrives at the opposite threshold of the runway after wheels up. Altitude should be roughly 2,000 feet with speed being held at exactly 300 knots until all have made the "saddled" call. It's important here that flight lead does what he says and maintains the heading/altitude/speed that he has announced. If a member of the flight is having trouble, lead will need to deal with it before increasing power settings or altitude. Lastly, do not enter an active sector until you've achieved formation integrity. 7. Fence-In Once formation integrity has been achieved the flight should fence in. Nav lights off, gun check and final check of external fuel tank selector switch if applicable. 8. Fuel Check Flight lead must monitor his flight's fuel status closely during sorties. It's an historical fact that more than a few Sabres were lost due to "fuel exhaustion" over Korea. If any member of flight reaches a bingo fuel state, he and his element partner must RTB. A fuel check should go as follows: Flight Lead: "Cobra flight, give fuel state" The flight should answer in order by giving only the first two numbers of their remaining fuel weight like this: "Two is One-four" (This means that #2 has 1400 lbs of fuel remaining.) 9. Rally Points If the flight should for some reason become separated, flight lead should call for a rally point as soon as practicable. To do this, lead will call out a grid (a safe distance from any enemy contact or a previously briefed grid) and will proceed to fly to that grid and begin a right hand orbit at 5,000 feet (or a more suitable altitude as the situation dictates). As each member of the flight arrives in the grid they will announce their arrival and enter into a right handed orbit as well. Once the entire flight has made the grid call ("#x is in the grid") lead will then call out a heading and announce when he's left the grid at the announced heading. As in the case with join-ups immediately following take-off, lead will hold a steady speed of 300 knts, at the announced altitude,and heading in the direction he called until the entire flight has reformed. 10. Landing The 39th will use either an overhead or straight-in approach. This will be decided at flight lead's discretion. If operating out of Krasnodar, 050 should be used for all landings. Landings should be done with full flaps brakes fully extended (this allows the engine to run at a higher rpm, which is handy if you need to abort you landing at the last moment). Pilots should be holding 150kts as they cross the threshold. A Few Words on Comms: Good comms can make or break a mission. By good comms it's not meant that you talked a lot during the mission, it's instead meant that you were able to exchange VITAL information quickly and in as few words as possible. Flight lead doesn't have to announce in detail every single turn/descent/ascent he makes. Just say the minimum required to get the intended result. Also, it's unnecessary for members of a flight to announce the status of their landing gear or flaps during take-offs. The less talk during a flight, the more each member of the flight can concentrate on performing their jobs at a high level. Inter-flight comms should be even more limited and briefer due to the nature of them being broadcast to the entire squadron. Roles of flight members: Flight Lead: The flight lead is responsible for briefing his flight, navigation, maintaining formation integrity at all times, and is the primary shooter during air to air engagements. Most importantly, he is also responsible for the safety of his entire flight. During A2A engagements flight/element leads must do everything possible to help their wingmen stay with them. This includes letting your wingman know if you're going to extend/retract your airbrakes and any drastic changes in attitude or power settings. #2/#4: The wingman's primary responsibility is defending his leader. He is also responsible for constantly scanning for enemies and for doing his level best to stay in position. During an A2A engagement, #2 and #4 will go into trail formation and stay with their respective leads through all manuevers, letting lead know that he's clear every 30 seconds or so. A wingman should never engage targets unless cleared by his lead to do so. Remember, the wingman is a defensive member of the flight. If you're not behind your lead, you should be doing all you can to get there. Element Lead #3: The element leader will assist the flight lead in performing his duties. During an A2A engagement, the element lead will often be directed to act autonomously along with his wingman in order to enhance the flight's effectiveness. This server is a work in progress. We are slowly learning how to run a fun and realistic Korean War era server. Your input is welcome. Thanks for your attention and have fun. Please feel free to d/l the following document written by Sabre Ace and instructor extraordinaire, Frederick "Boots" Blesse: https://www.dropbox.com/s/7n1gm5kbf7246ec/Blesse.pdf?dl=0 It's my intention to begin incorporating the tactics found in this document over the next short while. We will be practicing all the above in the coming days. From No Guts, No Glory: Things to work on by yourself or while training with the 39th: - Being able to fly a given heading/speed/altitude and sustain it for more than just a few minutes. Also work on being able to quickly and accurately change any of those variables. - All Sabre and Mustang pilots should be able to engage and destroy armored targets with rockets. - Flying in formation, formation landings and takeoffs. - Knowing the role of all flight members during an air to air engagement, and if in the 2/4 spots, being able to stay with your element lead during high G maneuvers. These topics will all be covered extensively during our many training sessions. Server missions will usually include flak thanks to the Flak script by Sithspawn and Stonehouse. You will find the flak quite handy in helping spot enemy aircraft. Our default formation on the server will be the finger four formation. Yours truly in the 4 hole. Regards, Bull

Silent's gear pretending that it's down. He found out otherwise when he tried to land.

ICQ To all those interested in keeping tabs on the server status, please d/l Steam and add me. My ID is Invisibull. Regards, Bull

Hey Zeke, Glad you enjoyed yourself. It's only going to get better my friend. That terrain (by Barthek) can be found here: http://forums.eagle.ru/showpost.php?p=2283313&postcount=209 I can't recommend it enough. Regards, Bull

Sorties 1/11/15 The 39th Squadron had 3 sorties in support of Operation Broken Axle this evening. In the first two we had a full 3 flights up (12 ships) and all was stable. All sorties were CAPs. SilentGun bagged a MiG 15 in the first sortie and I got one in the second. We made no contact with the enemy during the 3rd sortie. If you're interested in joining in on the fun, see the first post in this thread. Mustang pilots for tank hunting missions are needed. SilentGun, my number 2, right after he bagged a MiG and we were RTB. Spring terrain compliments of Barthek. Of note is the fact that during the 3rd sortie, Green Flight was able to reach 49,040 feet as it patrolled 30 miles north of Sochi. Apparently, this has been modeled very well by Belsimtek. From Wiki:

Great shots, Silent. Thanks!

Thanks very much, they're fixed now.