Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/16/2020 in all areas

  1. Better late than never but yes, got some of 402 squadron start up, take off and formation to target. When it all works - it's thrilling!
    2 points
  2. Apologies to all that last night was a bust; obviously there were a number of technical issues, many of which that were no one persons fault, but considering it took 40 minutes to get from server up (2120) to ultimate scrubbing (2200) there is obviously some work that is required. I have my suspicions that my internet connection is partially to blame; it may also have to do with the server being hosted by a player - DCS seems to run happier with a segregated host/client architecture and I suspect GBS may be the same. I will look into options hosting the campaign on the DDz dedicated server with FT. I cannot guarantee this will fix all the issues (lord knows I've experienced the occasional kick/crash even flying our usual coops) and may require a full campaign restart but I will know more in the coming days. As for personal technical issues; gremlins strike, we've all had them and on occasion even a full test prior to joining an event does not completely eradicate the chance of them occurring. However it will help mitigate the chance of spawning in and finding your TiR has gone for a burton or that for some reason a controller detection has decided to go south. Personally I'd recommend a quick mission free flight or a test on the DDz dogfight server. Speculatively, it may help to fly the test on the Rheine map before joining the campaign mission as this could load textures into your RAM, minimising the information that your PC is having to process and the load it is having to cope with when attempting to join, making a successful connection more likely. Maybe. The upshot of this is: from hereonin, if we have all players successfully spawned in but your hardware screws up, then sorry we continue without you. Even if it's a gremlin that didn't show itself in the test prior then you're an abort. Done. We cannot continue doing 40 minutes of restarts every time. As for pre-organisation of who's flying which position - this will help lessen the time taken to ready up but will always be subject to vagaries and interference of Real Life. Leaders will have to prepared to be flexible and adjust to on the spot deviations promptly and decisively. It would help if those partaking read and thoroughly understood the SoPs The point of me writing all that guff was not just to stroke my own ego or cos I had nothing better to do; it plays an important role in getting everyone in server and airbourne in the minimum of time. How? Well it means that the required information to be imparted at briefing is condensed down to just the following: 1. Formation assignments (or any deviations from prepared) - 1-2 minutes 2. Target - type and location - 10 seconds 3. Navigation - waypoints, points of note & egress headings - 1-2 minutes 4. Loadout - 10-20 seconds 5. Runway in use - 10-20 seconds 6. Any other matters lead wishes to bring up - 30 seconds Everything else is known and should not vary between missions. Thus a briefing could be over in as quick as 3 minutes. As for start time; next mission is scheduled for 23/06/20. This mission will have a participation cutoff of 2100 BST. If you are not in comms prior to this you will not be flying. If you have not entered server and selected you plane by 2110 you will not be flying.
    2 points
  3. Haven't updated yet. Thanks for the reminder.
    1 point
  4. L - to - R; Arthur, Fruitbat, FT.
    1 point
  5. I tried, but no action when I clicked the link in the thread. Is it this one in the BOX libary?
    1 point
×
×
  • Create New...