Jump to content

Volcano

Members
  • Content count

    7,187
  • Joined

  • Last visited

4 Followers

About Volcano

  • Rank
    Senior Member
  • Birthday 02/14/1977

Personal Information

  • Location
    Texas
  • Occupation
    Game Design
  1. 20 APR scenario: !OBJ PV - MP_4019b SPECIAL CONSIDERATIONS: Draft? Yes. Random CO selection? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules. !OBJ PV - MP_4019b.zip
  2. Yes, its been updated quite a bit since then - lot's of oldies still in circulation.
  3. 13 APR scenario: Where the Victoria Crosses Grow 2013-4023 SPECIAL CONSIDERATIONS: Draft? No. Random CO selection? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  4. Open play-test prior to TGIF

    Indeed, that is a good use of AT ditches and other obstacles; known distance to obstacle belt, enemy at the obstacle, engage with HESH at known range.
  5. Open play-test prior to TGIF

    Yes indeed, unless I am remembering incorrectly, the HESH was the IL's go-to round for long range killing, because the KE of the period had insufficient penetration at longer range. Of course the target had to be stationary though, little chance to hit a moving target with HESH at range...
  6. 30 MAR scenario: !Battle for Schwaben Creek Valley T72 v10-4010-OMU SPECIAL CONSIDERATIONS: Draft? No. Random CO selection? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  7. Glad you had fun. Come back every Friday.
  8. Hello all, Until further notice, we are going to adopt the randomized CO method (aka. 'the die roll') for TGIF, but excluding the newest members. This seems to be a good way to quickly determine a CO, and a lot of people seem to like the 'chance' element to it, and it spreads around the experience and responsibility, and it is a good way to "change up the experience" to keep TGIF fresh (which we try to do from time to time). So basically, there won't be any CO volunteers accepted for now, until we decide to change it up again, and this also avoids the issue that some have that the same handful of people CO all the time (myself included). EDIT: Those who CO'd the previous week are exempt from the CO draft roll.
  9. 23 MAR scenario: Border Dispute 2013-4010-MAD SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  10. 16 MAR scenario: !Zollerheim 2012-4010-OMU SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  11. 09 MAR scenario: Civil War Mykonos-4010a SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  12. SB 4.023 - Marder gun sound loop problem

    The sound file is fine, what is happening is that the number of samples is exceeding the limit (due to rate of fire), which causes previous sounds to be terminated, so you get the pop. This is something that a new audio engine would have to address (or maybe in the mean time the buffer can be increased on that one particular sound, we'll see).
  13. No Sound ( getting these errors) [solved]

    OK, glad you found the cause. BTW, in my previous post I meant to say to temporarily "disable it" (Nahmic), not "change it" (typo). Oh well, you figured it out.
×