Search the Community

This tool allows for automatic detection of weather conditions, visibility, time of day/night, and based on that, it provides you with automatic managment of MOOSE AIRBOSS, with this tool you can automaticaly set recowery window for any weather conditions (except dynamic weather due to DCS limitations). Coastline detection and aviodance. It also manages things like TACAN, ICLS, Link4, EPLRS, Wind Over Deck and other Airboss/Moose features see github page: https://github.com/Bartek16194/DCS-CRT-Carrier-Recovery-Tool You can just simply put carrier in mission set speed to 30, put unit name and enable carrier automation in script, load moose + script into mission and its ready to go.

The current AI recovery pattern holding procedures do not match those described in the CV-NATOPS (NAVAIR 00-80T-105). The AI when tasked with the action "Recovery Tanker" will commence a racetrack orbit with an upwind leg 10 NM in length and a downwind leg terminating when abeam at approximately 6 NM. When a player requests permission to rejoin the AI will shallow their turn and begin to hold what appears to be a circular holding orbit. This circular orbit appears to match the description of the Rendezvous Orbit described in the CV-NATOPS, Figure 6-13. Per 00-80T-105 section 6.10.1 the tanker should maintain this rendezvous circle until directed by departure to offload fuel. In the case of DCS this would be the equivalent of a player requesting rejoin to the tanker. Once the receiving aircraft is engaged the tanker should then establish a racetrack pattern with an upwind leg no greater than 10 NM, and a downwind leg 3 to 5 miles abeam, extending no more than 6 miles astern the ship (section 6.10.3).

The 101VFS is a Carrier based Milsim group. This squadron operates all available Naval and Marine fixed wing aircraft. The missions we fly on consists of CAP, SEAD, DEAD, CAS, and Anti-ship operations. On training nights we focus on anything that needs improving. On Ops night we put it all together. The goal for us is to learn the in's and out's of our aircraft of choice, down to the emergency procedures. Our end result is for members to be skilled and confident enough to go into a competition setting. [101VFS] Discord - https://discord.gg/rcraQJSZ7T

Who we are: Let’s start with our motto: Brave Men and their Proud Simulators We’re a virtual US Navy squadron, vVF-161, and we fly the F/A-18C Hornet and F-14B Tomcat. We used to say we’re MilSim-Lite, but we might be a little more hardcore than we realized. We follow NATOPS procedures as closely as possible, and we work together as a squadron to improve our skills in the jets, especially communication, coordination, and battlefield performance. We’re serious about training, professionalism, and camaraderie, but we don’t demand the sacrifices and full-time commitment of a real-life military pilot. In other words, we want the squadron to be fun and rewarding. So we don’t use ranks or give orders. We don’t say sir or ma’am, either. But we do have officers and a hierarchy. Why? Because even a virtual squadron needs leadership and organization. At the end of the day, our goal is for the Fightin’ Stingrays to be a place where we can hang out, have a good time, and foster real-world friendships. Still interested? Outstanding! Keep reading for more info and links below. We’re looking for: Pilots and RIOs of all skill levels and experience. Are you… · New to DCS and still trying to learn your first module? Then you’re in luck! We have a training cadre and missions designed to introduce you gradually to the Hornet or Tomcat. · An experienced virtual pilot who wants to try multiplayer in a more organized setting? We train and fly as a squadron at least once a week, on Thursday evenings (US Eastern). · An OG from the LOMAC days who’s tried everything? Maybe you’re tired of flying lone-wolf. Maybe you’ve flown with another group and didn’t like it for whatever reason. If that’s the case, we might be the right squadron for you. We’re serious, but we also understand the need for a healthy balance of life, work, and fun. We’re strict about: · Mutual respect, both within the squadron and for the community as a whole. · Real-world operational doctrine (NATOPS), given the limits of DCS and the ME. · Training and improving our skills. · Squadron SOP. We’re relaxed about: · Off-duty discipline; we aren’t an actual military organization, after all. (Although we’re pretty serious when we’re flying and fangs-out.) · Reports and paperwork; we’re fighter pilots, not pencil pushers. · Strict attendance; we expect you to participate in briefings and flight nights, but we understand that life and family come first. · Having fun; our squadron Discord is full of memes, talk about planes (duh), and the usual chitchat about life in general. So we’re serious where it counts—in the cockpit—and light-hearted everywhere else. More about us: We a smallish squad at the moment, about 20 members, but we’ve grown through yearly recruiting drives. This is our third one, so we have a solid track record and long-term plans for sustainable growth. We currently have pilots with years of aviation experience, both in DCS and real life, along with newer members who only have a few hundred hours of virtual flight time. We’re a mix of military veterans and private sector, and we range in age from mid-twenties to cough, cough fifty-something. So we’re a diverse group from all walks of life, but we’re united by our passion for aviation. What we do: We fly as a squadron two nights a week: Mission Planning & Free Flight on Tuesday evenings (2045EDT, 0045Z) and Operations/Training on Thursday evenings. Flight nights include briefings, flight assignments, comms, kneeboard pages, and more. We have a squadron Discord and a private, dedicated DCS server. Impromptu flight nights happen several times a week, whenever two of us are online and in the mood, which is pretty often. Our training: Whether you’re new or experienced, we’ll take you through an organized training program that’s designed to teach you advanced systems, tactics, and squadron SOP. Over the course of twelve weeks, you’ll gain the confidence and skills required to be a virtual naval aviator in the Hornet or Tomcat. If you’re new-new and don’t even know how to start the jet, we have instructor pilots and a library of resources that will help you get up to speed on the basics before training kicks off. Okay, now let’s talk about nuts and bolts. Module requirements: · Aircraft: F/A-18C Hornet or F-14 Tomcat · Maps: Syria and NTTR · Asset Packs: Supercarrier · Additional Software: OvGME and DCS Simple Radio Standalone (SRS) Personal requirements: · Are you a mature adult? You need a thick skin and the ability to laugh at yourself, especially when you screw up (which we all do). We keep things polite, but we can be utterly merciless to each other, so this is essential. · Can you take constructive criticism when it’s warranted? Can you give constructive criticism to others and be tactful about it? We’re serious about this—we debrief every flight and constantly work to improve our skills. · Are you willing to learn and improve as a pilot? Can you contribute to the squadron as a whole? The other stuff: Between us, we own pretty much every module in DCS. We fly jets, helos, and warbirds, as well as IL-2, MSFS 2020, and other sims (racing, space). We even have one guy who “flies” a steam locomotive. Yes, you read that right, the guy really loves trains. And he’s one of us, so we are… The Fightin’ Stingrays: Planes, Trains, and Automobiles! Long story short, we love sims, so you’ll always find another squad member who’s ready to fly, drive, or… uh… train with you. ( See what I did there?) What’s next: If you’ve made it this far and feel like you might be a good fit, visit the vVF-161 Fightin’ Stingrays website. You can learn a little more about us and watch videos of recent flights to see how we operate. And if you’re new to DCS, you can even get a sneak peek at our training program. Finally, you’ll find the Discord handles for the squadron CO and XO at the bottom of each page on the website. Send us a DM and we’ll reply with an invite to join the Discord server. Until then, thanks for reading, and we hope to see you soon. Fair winds and following seas, - Mongo, Otto(Wrench), and the Stingrays Admin Staff Brave Men and their Proud Simulators A quick note on our plans for the Tomcat: We’re recruiting both pilots and RIOs, and our goal is to have all-human crews when we fly. This adds an additional layer of complexity to both training and combat operations, but we’re dedicated and creative, so we usually find a way to make things work. ----- TL;DR vVF-161 Fightin’ Stingrays are recruiting Hornet and Tomcat pilots & RIOs of all skill levels for flight nights on Thursday evenings (US Eastern).

Carrier comms are currently limited to one frequency (albeit that the actual frequencies can be set in the ME). It would be useful and more realistic if carrier ATC had two available frequencies - one set in the VHF band and one set in the UHF band. This would both reflect the multiple frequencies available at airfields and allow more aircraft to communicate with carriers. For example, most mission makers using USN carriers leave the carrier ATC frequency at the default VHF frequency. This is fine for any F-14s or F-18s but denies A-4s the capacity to talk to the carrier ACT as the A-4 is limited to one UHF radio.

I have been trying to execute an ACLS landing in the F-14B and have followed procedures according to all instructions. The final step in the sequence is to press the NWS Button and upon the CMD CONTROL Light illuminating, the ACLS should guide the aircraft on localizer and glide slope to a landing. The bug seems to come in at this step as when the CMD CONTROL light illuminates, nothing seems to happen. I do not touch the stick and the aircraft seems to fly as if though I have not activates ACLS and just released the stick, continuing in the direction it was headed after my last control input. I asked others to try the ACLS landing and they have gotten the same result, no terminal ACLS guidance.

Johnny Carson demonstrates toy carrier In 1974, Johnny Carson and former Marine pilot Ed McMahon demonstrated the U-Fly-It on "The Tonight Show". Users launched a toy F-4 Phantom II and then tried to land on a model of USS Enterprise. U-Fly-It had a massive spike in sales due to this appearance.

As title says. If the carrier flight ops are stopped the deck crew should allow pilots to hook up but NOT do the 'wave' for run up. They should wait until the condition is set that re-enabled flight ops and then they should allow the 'wave' for run up and fire the cat.

Squadron name: Nemesis squadron - Timezone/OPS: We are a primarily UK based Squadron and as such we run ops roughly in the evening around 1930 GMT(BST if its summer). We also host additional ops at different times in the week so all nationalities are welcome! - Realism rating: 3/5. We try to be semi-realistic - Roles needed: We are currently recruiting for F18/16/14 and all helicopters. Other jets will be considered on contact. We are also looking for Mission designers, Opfor commanders and LotATC controllers to help make our missions be more in-depth and interesting. - Squadron Requirements: SRS is a hard requirement. Pilots to have HOTAS. RIO, CPG, WSO keyboards accepted. Some form of headtracking/VR. Recommended DLC: Supercarrier – F14/18. Maps PG/Syria. - Basic notes: We are a relatively new squadron that has enjoyed rapid growth since opening our ranks in December 2022. We have no required level of proficiency to fly with us. Flight Training Officers will run specific trainings for your airframe and missions weekly. We have an ‘Advanced Pilot Program’, who have progressed through the relevant qualifications to become our top pilots, who enjoy our advanced missions. If you are at all interested in us, come check us out, or shoot either me (@Armuax#2804 ) or @PRQ2021#6764 a DM, and we will try and answer any questions you may have! - Squadron discord:https://discord.gg/kEJsrhaPwp

The phrase is generally vague, but it's a wonderful concept that separates good pilots from great pilots. It can be interpreted a few different ways, but how I've thought about it is, "Think about where you're aircraft is going to be in the next 30, 40, or 50 seconds." When I was in flight school, there were moments in my lessons when we'd be on our way to a different airport or location, and I'd take the time to look out the window and enjoy the view. I'd look at the clouds, how far out the horizon was, and maybe get curious about some warehouse off in the distance near a river. "Do they make boats? Is that why they're near a river? Or is it because of some sort of regulation that requires them to stay away from residential areas? It could be because of logistics." And then, my flight instructor would break the thought process with, "Yo, are you planning on violating airspace?" I'd check the GPS, and we'd be fast approaching airspace we're not even tuned to. Then he mentioned, "You can't fly 'fat, dumb, and happy.' You always have to stay ahead of the aircraft." I figured being good at controlling the aircraft was enough, but it wasn't until IFR ground school that I realized how much work it took to stay ahead of the aircraft. So, I made this video showing how I fell behind my aircraft and how I caught up to it. To be clear, this isn't a "how to fly a CASE I pattern" video; it's a "how to stay ahead of your aircraft" video. At least, the way I interpreted it.

Took a few Bolters (not fun when you’re down an engine) but I got there eventually.