Jump to content

Viking355th

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Everything posted by Viking355th

  1. Viking355th
    Not me. I fly both, bought 'em around the same time, and find the Hind much easier to fly.
  2. Viking355th
    until
    TBD -- might put up Operation Foothold if people feel confident, or might just do training with TTI if people want to learn something new.
  3. Viking355th
    until
    TBD, but there may be warbirds involved
  4. Viking355th
    until
    Details TBD, but all are welcome (and encouraged) to attend.
  5. Viking355th
    until
    As we're trying to be that's friendly to less experienced pilots, but also want to run missions together, I think it makes sense to split the mission into 1/3 training/practice and 2/3 mission. HOUR 1: Training / Q&A / Drillwork For the first hour, we'll run Through the Inferno and just practice things. This can just be in pursuit of personal interests, but if you don't consider yourself combat-effective, try to use this time to focus on ensuring you can meaningfully contribute to the upcoming mission. HOURS 2 & 3: A Reasonably Challenging Mission We've been having fun with Operation Foothold lately, so that's likely to be the mission we use. It's a persistent mission involving capturing and reinforcing different zones as we progress from Anapa to Krasnodar. If no one's interested in drill/training, we'll just spend all 3 hours in Foothold.
  6. Viking355th
    until
    This week, we may change things up again. The TTI practice sessions are fun and a good way to hone skills, but don't provide many surprises or a sense of progress. Option 1: Carry on with Through the Inferno Option 2: Try Operation Foothold Foothold involves proceeding from Anapa to Krasnodar, capturing Krymsk along the way. We'll need to knock out enemy air defenses and clear areas for capture, then protect friendly AI helos and cargo planes as they move in to capture the bases. The distances involved are short, so slow aircraft (A-10s and attack helos) are viable.
  7. Viking355th
    until
    We're just starting out as a squadron, so we'll be be trying things and making adjustments until we have a format that suits us. What we do is likely to change as we grow into ourselves, but the scheduled time almost certainly won't. The event is scheduled to work for people that are in a time zone within a few hours of the Atlantic. After dinner for EU folks, after lunch for the NA folks. As we're trying to be a squadron that's friendly to new pilots, but also want to run missions together, I think it makes sense to do a little of both for now. HOUR 1: Training / Q&A / Drillwork For the first hour, we'll run Through the Inferno and just practice things. This can just be in pursuit of personal interests, but if you don't consider yourself combat-effective, try to use this time to focus on ensuring you can meaningfully contribute to the upcoming mission. HOURS 2 & 3: A Reasonably Challenging Mission Because I'm not yet sure what to expect in terms of pilot attendance and airframe preference, I'll probably just let Briefing Room auto-generate a mission for us towards the end of Hour 1. I'll have a rough template set up, ask everyone present what they'd like to fly, and in what role, and then punch that into BR. If that should turn out to be inconvenient or impractical, we may just run TTI the whole time, or possibly load Operation Variable. In the early days of this squadron, we'll be calling a lot of audibles. COMMS: Briefing in 71st Discord, flight in SRS. For the SRS server IP and password, use the !srs command in the 71st Discord. The DCS server has the same IP and password as the SRS server.
  8. Viking355th
    until
    We're just starting out as a squadron, so we'll be be trying things and making adjustments until we have a format that suits us. What we do is likely to change as we grow into ourselves, but the scheduled time almost certainly won't. The event is scheduled to work for people that are in a time zone within a few hours of the Atlantic. After dinner for EU folks, after lunch for the NA folks. As we're trying to be a squadron that's friendly to new pilots, but also want to run missions together, I think it makes sense to do a little of both for now. HOUR 1: Training / Q&A / Drillwork For the first hour, we'll run Through the Inferno and just practice things. This can just be in pursuit of personal interests, but if you don't consider yourself combat-effective, try to use this time to focus on ensuring you can meaningfully contribute to the upcoming mission. HOURS 2 & 3: A Reasonably Challenging Mission Because I'm not yet sure what to expect in terms of pilot attendance and airframe preference, I'll probably just let Briefing Room auto-generate a mission for us towards the end of Hour 1. I'll have a rough template set up, ask everyone present what they'd like to fly, and in what role, and then punch that into BR. If that should turn out to be inconvenient or impractical, we may just run TTI the whole time, or possibly load Operation Variable. In the early days of this squadron, we'll be calling a lot of audibles. COMMS: Briefing in 71st Discord, flight in SRS. For the SRS server IP and password, use the !srs command in the 71st Discord. The DCS server has the same IP and password as the SRS server.
  9. Viking355th
    I've actually solved this one on my own, but it took hours, and I can't find any info on this problem when I search, so I'm hoping this post saves someone some time and effort. So, when launching DCS, prior to reaching the main screen (the one that lets you into Settings, Mission, Multiplayer, Instant Action, etc.) there's a brief loading screen with a progress bar. After today's OB patch, mine hung at 10% and wouldn't advance. Had to task kill DCS (so, technically this is a freeze, not a crash, but I think it still belongs in this section -- feel free to move it if I'm wrong about that.) I did the usual things (disable mods, delete fxo & metashaders2, run a repair, reboot) to no avail. I looked at the log, and found this: ALERT Dispatcher: Error starting Game GUI: error loading module 'gui_map' from file '.\lua-gui_map.dll': The specified procedure could not be found. Deleting the lua-gui_map.dll file in the root DCS folder solved the problem for me. I ran a repair afterwards, because I was actually expecting the file to be needed but corrupt, and wanted the repair process to get me a fresh one, but it didn't replace the file, so I now believe that step was unnecessary. The last modified attribute on that file was May of 2016, so it's clearly quite old, and probably not going to cause any issues with people who have downloaded the game recently, but my DCS install is very old (the install folder is still called DCS_15OB, if you can believe that.) In case someone else runs into this issue but doesn't find their way to this post, I suggest that the next OB patch/hotfix check for the presence of this file, and remove it if found.
  10. Viking355th
    Most aircraft can have their gear down at 250 kts or slower. 550 km/h is 297 kts, so it's a bit faster, but nowhere near double.
×
×
  • Create New...