-
Posts
192 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by SeaQuark
-
Here's the low-down on DCS versions: DCS World (stable) <---- for all intents and purposes, this is the game. play on this, have fun. DCS World OpenBeta <----- install this if you want to help ED test new features and file bug reports, or if you really really can't wait to try out a new feature and are willing to deal with bugs to do so. DCS World OpenAlpha <----- this is being "retired." we can destroy it, forget it, move on with our lives. In general, this server will always be on the "stable" (non-Beta) release. I am making an exception for this week, because the brand new map/graphics are out and everybody's quite rightly excited to try it out. Once this new map/graphics (i.e. "2.5") are pushed to the stable release, I will of course return the server to the stable, as there will be no reason to stay on Beta and subject people to more bugs or reliability issues than is necessary. What confuses people is that *sometimes* the Beta can communicate with the Stable release via Multiplayer and sometimes it can't, depending on the severity of the change. Again, this is a good reason to keep a multiplayer server on the Stable whenever possible. On this next update, whenever it comes, I'd imagine you might be able to connect to a stable server, you might not. The real question is: why would you want to regularly play on the Beta when you don't have to? Correct, 5 is Wolf flight. Switch to your flight channel when airborne, and fly your mission. You will periodically receive Bullseye calls from EWR, but it is not a perfect system, it will only alert you occasionally, depending on the amount of enemy activity. Sometimes it may not alert you at all. Fly CAP at altitude near / around Bullseye. Keep up a thorough scan, and rely on your wingmen for mutual visual support.
-
I think you misunderstand, I will return the server to the stable only after 2.5 is released on the stable. Fancy new map isn't going anywhere.
-
Heads up folks, the server has been moved to the brand-new 2.5 OpenBeta. I am pleased to report that my multiplayer mission seems to have made the transition without a hitch, running smoothly with no major bugs noticed yet. After the 2.5 Stable is released, server will likely go back to the Stable, but for now I decided to move to the Beta so y'all can enjoy the fancy new graphics.
-
Sabre-MiG Showdown schedule has been changed. Event now starts at 1900 Zulu on Sundays. Going forward, we may try out a few different days/times to see what gets the best attendance. Top of forum post or Discord news channels will always be updated with the latest schedule. Last Showdown, the two-man team of DJModeus & McGen nabbed 2nd place for the Reds. The Blues have definitely outnumbered the Reds during the last two events-- MiG drivers, get on up there!
-
Thanks Grizzly. That's completely understandable. You are still welcome to fill out an application and go on a check-ride, of course; I would say that if you can understand the SOPs posted on our website, you are fit to be a wingman in the squad, since, ideally, not much talking is done over the radios during an actual mission anyway. It's up to you if you would like to apply.
-
Glad to see new players discovering the server; welcome aboard guys. @JokerMan, TacView is disabled on server, for historical immersion's sake. Flight de-briefs are highly recommended, but instead of the all-seeing eye of TacView, try talking through the engagement with your wingmen; compare with their perspectives of the fight, and self-assess your performance. SERVER NEWS: MAPS As many of you have no doubt noticed, the F10 Map icons were disabled a while back. More recently, a detailed navigational briefing & map collection has been made available for download. Click here for the PDF (35 MB). Map includes all relevant NDB frequencies, and MGRS & lat./long. grids. "Photocopy" versions are provided for easy printing: *Note: there is indeed an NDB freq. for Bullseye, 378 KHz (no morse). Remember that mountains may interfere with NDB reception if you are at low altitude. Also included are some basic tips for Dead Reckoning & Radio Navigation. These are not intended to be exhaustive tutorials, but a quick introduction to oldschool navigational concepts, for those of you who may not be familiar with them. SABRE-MIG SHOWDOWN The 2nd weekly showdown is this Sunday at 2200 Zulu. 39th VFS currently holds the top spot. Can any challengers do better than 2 kills and 0 deaths? See contest rules for details, and don't forget to submit your scores if you & your wingman survive the sortie.
-
Thanks Tom :thumbup: Stop by anytime. A note to everyone: I do plan to update the mission with a larger variety of ground targets for both sides in the near future. However, at this point, I am waiting for the merge, as depending on how that goes down there is a large chance I may need to re-do a good part of the mission in general. Holding pattern for now.
-
Thanks to all who participated! Turnout was low on this first Showdown, but nevertheless the 39th VFS 4-ship managed to bag 2 MiGs, and all flight members returned safely. A high-scoring MiG was ultimately shot down, and thus disqualified. 2 KILLS, 0 LOSSES is the number to beat for next week. Same time, same place. Sunday, 2200 Zulu on the KOREA! server.
-
@viper, cool your jets, he was talking about scorecard system, nothing more. @DefaultFace + others, I will be taking a screenshot of the scorecard at the start of the competition, so in case anybody is erroneously starting with 1 loss, I can account for that when comparing any submitted scores. As stated above, I will also accept video evidence if you feel the scorecard has botched your results. But remember, most of all, the point of this event is to have fun and foster friendly competition & good flying. As it is a recurring weekly event, there will be many chances to fix any problems going forward. Be sure you are in the server and in your cockpit at 2200 Zulu. Good hunting!
-
It was my understanding this usually happens when switching slots, or hopping into a different slot after landing, or during a server mission-rotate? I've never seen it just spontaneously give me a loss mid-flight. Kill scores have also seemed to be suitably reliable these days. This is only one sortie, so it shouldn't be an issue. Just be sure you are starting fresh when you take-off. If you believe you have an error in your scorecard, I will accept a video recording of your flight as evidence. Make sure it shows you and your wingmen taking off and landing safely.
-
KOREA! 1952 is now hosting a new, weekly event: ^^CLICK FOR RULES / PRIZES^^ Every Sunday, team up with a wingman (or 3!) and see how many kills your flight can score in one sortie-- without losing your wingman. If either member of a 2-ship element crashes or is shot down, the element's kills will not be counted. The goal is to encourage effective leader/wingman teamwork, and promote competition between virtual squadrons. Top scoring flights will be added to leaderboards on forum post & Discord. Scramble on the server this Sunday @ 2200 Zulu. See rules above for details and how to submit your killcount.
-
Thank you! I wish the same. Maybe someday, some DCS dev will see fit to bless us with a proper B-29 AI.
-
FYI all, the server has been updated to 1.5.8 stable. There are some strange stutter bugs in the new version-- for some reason, putting a password on the server seems to fix them (???). So, temporarily, please use the password "korea" to get onto the server.
-
(sigh) I had thought it was clear that I was having a bit of fun, writing "in character" as a 50s Sabre pilot. It's worth noting that the piece of history I was attempting to reference was actually specifically about how *good* Americans thought the Russian pilots were-- when there were lulls in MiG numbers or aggressiveness, American pilots speculated that Russian pilots (who were fighting there in secret) had rotated away from the front, and the pilots who remained did not have the benefit of their training & combat experience. At any rate, I see now that there is potential for that to be taken the wrong way, so I will refrain from such "role-playing" or "historical reenactment" posts on this forum, and keep that to Discord in the future. Red & Blue players alike there like to have a bit of fun in that way. I will note that I have made an open challenge to all Red players to form their own dedicated MiG-15 squadrons, and I would love nothing more than to bring together squadrons from other countries, in the spirit of friendly international competition & historical appreciation. I have went through great effort to try and make the server multi-lingual friendly, and would never even dream of insulting players because of their nationality. So, rest assured, no apology from me will be necessary. You have misunderstood me.
-
We had just passed beacon 307, heading home to K-13, probably around the Haeju area, when we got a call on the Guard from Eagle flight of the 71st. Wanted to know if that was one of us, at their low 6. At that time lead & I were in a slight spread, and likely could not have been mistaken for a single, so immediately knew that something was up. When you get a call like that, it's not time to start guessing out loud. We took stock of the situation. I checked 3 o'clock high, and there they were, a 3-ship contrailing, heading opposite direction of us, but with a tail, below and about a mile or two back. No other flights out of K-13 were scheduled at the time. My flight leader "Invisibull" did not have sight of the bogey, so instructed me to take lead and turn into him. As we made the turn I switched to the Guard and radioed to Eagle that it was almost certainly a bandit behind them. As we arrived on their heading, we watched as all of Eagle flight rolled over and dove on the bandit, who immediately tried to escape low, and the whole lot "funneled" towards the deck into a single line. Invisibull-- flying wing for a change and enjoying the show-- finally had an opportunity to use that Brownie he always brings with him into the cockpit, and snapped the enclosed photo. There wasn't any more chatter on the radio after that-- no need. And no need to jump in and muck up a perfectly good set-up for Eagle. We left them to the hunt, and turned back for home with ample fuel. Mig activity has tapered off somewhat this past week. There are still a few out there who consistently give us trouble, but more often than not, they seem to be flying alone, uncoordinated. It's rare to see even a solid 2-ship of Migs out there flying anything close to a decent formation. Lack of leadership? Poor training? Some speculate that the "honchos" have rotated back to you-know-where, and the locals haven't quite got the hang of things. But unknown as of yet whether the situation will stay that way.
-
Just as an addendum to my old post here, I now co-run a Sabre group with Invisibull, the 39th Virtual Fighter Squadron: http://www.39thVFS.com We fly training missions on Nevada, and PvP on my Korean War server, and are devoted to putting historical Sabre procedures, tactics, and formations into practice, plus a few tricks of our own. If you're interested in serious F-86 flying, I can safely say this is the best place to look. To apply for membership, read our SOPs, then fill out the application form on the website.
-
If you see someone exhibiting objectionable behavior, see if you can note their screenname, then Private Message it to me, please. I will send notice of Court Martial Investigations to problem players-- typically I have only had to do that for instances of Team-Killing, but if buzzing / screwing around at the field gets extreme, I am happy to tell someone to knock it off. All players are expected to read the briefing, obey Tower instructions, and to listen for emergency traffic calls on SimpleRadio when approaching or departing the airfield. Note that if you have a troublemaker's plane ID number or callsign (numbers on side of plane, or what is called out by the Tower) you can easily lookup their screenname on the scorecard in-game.
-
Just a quick sanity check on this one. Is there any known issue with using the "Part of Coalition in Zone" trigger in multiplayer / with "Client" aircraft? Trying to trigger a warning when enemy planes enter a certain zone, but it seems to go off at odd times when there couldn't possibly be any enemy units around, whether they are player or AI controlled. Is there a behavior that I'm not aware of? For example, if a Red aircraft is destroyed in a certain sector, does it still read as a Red "unit" being left there? No scripts / mods being used on the server in question. I just have it set up with a "Switched Condition" and a flag + timer that limits it to going off once every few minutes maximum.
-
Rob is correct. This is a non-factor. These jets burn through fuel like crazy compared to props, especially down low. It's very common even for MiGs who take full fuel and drop-tanks to find themselves running on fumes after they get bounced unexpectedly. Personally I am always finding I want more fuel, not less of it. Taking less would only be a disadvantage.
-
Big news for all Sabre pilots who fly on the server! I am very pleased to announce the 39th Virtual Fighter Squadron: Presented by Invisibull (39th Sqdn. Leader) and SeaQuark (host of KOREA! 1952). Click here for the Official Announcement for more information & instructions on how to join. Visit our website, and check out our Standard Operating Procedures (PDF format), to see if the 39th is right for you!
-
I am very pleased to announce the 39th Virtual Fighter Squadron: Presented by Invisibull (39th Sqdn. Leader) and SeaQuark (host of KOREA! 1952). We are a virtual 1950s USAF Fighter Squadron operating out of Nellis Air Force Base (DCS 2.0) and Suwon, Korea (DCS 1.5). The 39th is for any DCS players who wish to take their skills in the F-86 Sabre to the next level in a respectful, friendly environment. We emphasize teamwork, formation integrity, mutual support, and historical accuracy. Realism & immersion are very important to us, but we will never take it too far or to the point of being obnoxious. We primarily fly the Sabre, but there is also room for F-51 Mustang pilots to serve in Air-to-Ground and Reconnaissance capacities. Our Standard Operating Procedures (PDF) are available to the public. If you wish to join, read through them carefully; they will give you a great idea of whether or not our squadron is right for you. Then simply apply for membership through the "Recruitment" page on our website: http://www.39thvfs.com And feel free to say hi on our Discord server anytime: https://discord.gg/tVFWwnX Training missions will be flown out of Nellis AFB, on Invisibull's dedicated NTTR training server. Once you demonstrate a basic level of proficiency, you will be accepted as a provisional member of the 39th. REQUIREMENTS: F-86 Sabre (or P-51 Mustang) SimpleRadio Read the SOPs Discord (chat program, great for keeping in touch / arranging flights) HIGHLY RECOMMENDED: DCS 2.0 + NTTR-- if you don't have NTTR, you can still fly with us on Korea, but you will miss out on many group training flights & activities. Note that membership in the 39th is non-exclusive. If you wish to fly other planes with other groups-- we have no objections. Our goal is simply to provide a "clubhouse," effective teaching resources, and a roster of good wingmen for anyone who loves flying the Sabre. NOTICE: To all MiG-15 pilots, consider this announcement an open challenge! If you have the necessary skills & inclination, form your own squadron, and we shall meet you in the skies over Korea, in the spirit of friendly competition!
-
Quite simply, my intention was to make the AAA strong enough to discourage people form doing it without having to make an official rule. All of the AAA units are set to "Expert." Earlier, I added tons and tons of AAA, but this negatively impacted frame-rates when they fired, and people complained-- so I dialed it back. Perhaps I have dialed it back too far, so I am in the process of adding more AAA units. Currently I am using: RED: Zu-23s Shilkas BLUE: Zu-23s Vulcans If you have suggestions to increase AAA lethality without resorting to SAM sites and such, I am all ears. For the record, I have seen quite a number of foolhardy MiGs crash into the ground near the Blue airbase after being shot up by AAA. But I have also been bounced when RTBing. Note that there are "air raid" sirens that will alert you to the presence of enemy aircraft at your base. There will be no AI fighter units, this server is designed to be a pure PvP experience. If few players are on, MiGs do have AI bombers to shoot down, and Sabres do have ground attack missions.
-
Channel 3 is the Check-In frequency for Blue team. For the Migs, Check-In is on 3.775 KHz (wave # 151) When you first spawn in, tune to this frequency to talk with your flight, plan your mission, etc. If there's any other flights at the airfield, they might be doing the same thing, which will be a good opportunity to "check in" and coordinate your flights. It's important to have a reserved channel for this, as the ATC frequency (CH .1 for Sabres, 150 for MiGs) should really only be used for traffic comms and communicating with the tower. Please keep the ATC channel free of idle chit-chat. This is all assuming you have SimpleRadio installed right and you are using your cockpit radios correctly, so you can hear your teammates. Common problems are: Speaker / Microphone not set up correctly in SRS Push-to-talk button not set up correctly in SRS Bad interactions between SRS and other mods, or remnants of mods. Uninstall all mods. If it's still not working after that, check your Export.lua file in your Saved Games----> DCS---> Scripts folder. If there's a bunch of junk in it aside from the one line that SRS puts there, try deleting it, repairing DCS, and re-installing SRS. But before you get into all that, make sure you're not making one of these "whoops, duh!" mistakes: People try to use their SRS overlay instead of actually flipping switches in the cockpit People don't apply power to their plane, or generally don't know how to use their plane's radios No one to talk to-- hopping on the server without knowing who's on what channel and expecting to find someone instantly. It's best to test it out with a buddy first, makes things much easier. If you still have problems, hit up the SRS Discord channel: https://discord.gg/5ak4jJr
-
I'd like to if somebody could link me good instructions on how to do it. I'm not super-technical, but I can follow instructions. In the meantime, I use SimpleRadio for an approximation of this. SRS will tell you how many people are connected to the server via SRS. For example, right now I just checked and there are 3 people connected, which it tells me at the bottom of the Client window: And since not everyone is on SimpleRadio, usually this is a low-end estimation of the people online. On that note: if you are using the server and not on SRS, you are missing out. Simply by checking in on CH. 3 at the airfield yesterday, I found myself part of a spontaneous 5-ship bomber escort mission. On Another Note, re: F10 "Own Aircraft" Label Unfortunately I can't seem to find an option to make "Own Aircraft" optional on the F10. I wish it were that simple, but apparently it's either "force a particular view option" or "let everybody choose their own view settings"-- which would enable people to see enemy units on the F10, etc. Obviously that is not a good solution. Failing some other solution, I will stick to my original plan of having a "dead reckoning" week, i.e. turning off F10 label on a trial basis at some point in the future.