Jump to content

SkyCap

Members
  • Posts

    43
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    All DCS modules/Falcon 4.0 BMS
  • Location
    England
  • Interests
    Crashing into the ground
  • Occupation
    RF Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Looking forward to another round! I'll see you all soon.
  2. I will second this! It's a very good feature that we need, it will literally save lives, how can anyone not want to support such a cause! :thumbup:
  3. This was exactly what I needed, thank you!
  4. Am I able to apply the advanced waypoint attributes found in the standard ME to units that are spawned through a mist script? I'm looking to build an accuracy test range, where the pilot can spawn a target which is essentially a ural, with M818s on 4 sides. They would then have to destroy the ural without destroying the M818 (with the M818s being at varying distances from the ural). I can do that part fine, but once the pilot has made an attack run, all the remaining vehicles drive away to defend themselves. I found that in just using the DCS editor the "Hold" command stops them from doing this completely. Any suggestions on how I can implement this into my spawn script? This is a small part of a larger training script, so ideally it would all be handled by the spawn script. Thanks
  5. This would be an awesome feature for simulated ATC! Could bring alot of those vatsim guys over, would be fun to interact on this level with live combat missions. And think if blueflag featured something like this, would be so immersive! +1 for sure!
  6. This will also be nice for mission editing, much faster than applying the skin and loading the mission or going through the liveries folder. Nice work.
  7. All the tacviews I have are here: https://drive.google.com/folderview?id=0B2RfzgKTf7AFOW1ZTmQ0LVZSWUk&usp=drive_web And tracks I have here (only from server 2 sadly), they're already modified so you can spectate: https://drive.google.com/open?id=0B2RfzgKTf7AFcWZfUmoySzZXVXc
  8. Great write-up!
  9. Highlight video here! [ame= ] [/ame]
  10. What a tournament! Thanks to all who participated, everyone was a good sport. Congratulations to Stuge and Razer for their 2vs2 victory! I look forward to seeing you all at the next one.
  11. Go ahead, you just need to stick to that airframe for the entire match.
  12. We will be keeping the same version for 2vs2 that we used for 1vs1. So that's version 1.5.3.51417
  13. Emails gone out to all who signed up for 2vs2, please make sure you check with your wingman as well that they can attend!
  14. Yes, I had complaints during some matches regarding some players immediately flying low. So we replayed the rounds where altitude would be kept the same until post merge. Later on in the quater/semi finals period the two sides would agree to allow this tactic or not, at least in matches that I refereed. I personally think this was right, it makes defining the merge much easier when you know both players are at the same altitude and thus allows for better sportsmanship. However it wasn't clearly stated in the rules either way, so I apologise for any confusion caused. Next time we will have a more definite rule on pre-merge tactics.
×
×
  • Create New...