Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Volcano

Members
  • Content count

    6,838
  • Joined

  • Last visited

3 Followers

About Volcano

  • Rank
    Senior Member
  • Birthday 02/14/1977

Personal Information

  • Location
    Texas
  • Occupation
    Game Design
  1. Thanks for the compliment. I do what I can. Yeah, Tank Duel looks interesting, at least for a quick tank vs. tank game. Will have to keep an eye on it...
  2. Question... For the crash reported in: Of the user/users who CTD'd, were they running Windows 10? Was someone trying to print something (like the map)? Or did they print something in the planning phase? If so, is the printer configured properly? If so, then this has been fixed, but that person should configure their printer. If this is not what happened then perhaps someone uploaded the wrong DMP file, from another incident perhaps. I guess these questions are for Zaphod, since it seemed like he is the only one that CTD(?).
  3. Yep that would be me.
  4. Diamonds aren't supposed to be easy to find...
  5. I have MBT, it's nice. I also have Panzer, and all of its expansions. Looking forward to FRG and BOAR expansions for MBT too. Some people just don't understand that PC sims and PC wargames are nice, but there is a certain amount of satisfaction gained from playing a boardgame. Pushing something physical around the map, and working through the to-hit and damage result is suspenseful. You like X-Wing? Try my "X-Wing Squadrons" at BGG, it gives purpose to something that otherwise has no purpose.
  6. Got them, thanks!
  7. In Windows 7 it will be in your... C:\Users\Administrator\AppData\Local\CrashDumps ...with a .dmp file extension.
  8. Strange, it was there - it just didn't add the link to it. Added the link now...
  9. 13 JAN scenario: REFORGER '85 v.09 (cap zones) This is a brand new scenario from the community. M1A1 vs. Leopard 2A4. SPECIAL CONSIDERATIONS: There will be a draft. 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. REFORGER '85 v.09 (cap zones).rar
  10. INTENT: We are trying something new this year and we put all the "battle tested" scenarios into a list, and then randomly shuffled that list to create a TGIF play list. We are going down that list in order, choosing the next scenario to play from it rather than picking on a whim. Rather than post the list here (because the list can/will change throughout the year), a post will be created here before each Friday mentioning the scenario that will be played. You can then download the scenario and decide if you want to CO (post here if you want to take it), otherwise whoever volunteers on Friday will be the CO. CO GUIDELINES: Basic guidelines as to who can volunteer as CO from week to week. The intent is solely to afford everyone the opportunity to CO: No one may volunteer to be a CO back-to-back TGIFs. That is, if Mr. X volunteers to CO this week, he cannot volunteer to CO next week, but he can volunteer the week after that (every other TGIF). EXCEPTION: if a scenario requires more than two COs (i.e. because it has more than two sides) then there is no restriction on volunteering back-to-back with the previous TGIF. If no one volunteers to be the CO, then anyone can CO at the time of the event. So, in the example above, Mr. X can CO again that next TGIF if no one volunteers during the week. TGIF HOUSE RULES: There will always be bugs in software and Steel Beasts is no exception. More-so, functionality that exists in the Pro version which has carried over into Pro PE often creates unforeseen situations which allow for abuse and unrealistic behavior. To counter this, there are "TGIF HOUSE RULES" which are basically a set of ethical rules to allow "fair and realistic play" to keep scenarios from bogging down into the morass of shame. The House Rules are as follows (and the list may grow over time): DO NOT adjust the number of rounds per tube when calling off-map artillery strikes, because they currently have unlimited ammunition so it creates ridiculous situations. (Using number of rounds per tube with on-map artillery is fine because they are delivered differently and have finite ammunition.) If you want a long off-map artillery strike, just keep repeating it. DO NOT adjust the duration when calling off-map artillery strikes -- for the same reason as rule #1. Also, like rule #1, setting the duration for on-map artillery strikes is OK. If you want a long off-map artillery strike, just keep repeating it. DO NOT use support vehicles (supply vehicles, bridge layers, maintenance vehicles) for reconnaissance. DO NOT intensely study the enemy's side in the scenario in the Mission Editor. You can open it and look at both sides, but do not touch anything or evaluate the reinforcement criteria, events, conditions, routes and waypoints. Looking at the enemy side to get an idea of what they have is acceptable, especially since you have to do this to figure out which side to CO anyway. DO NOT use helicopters with the intent of causing a distraction for the AI. Everyone knows when this is happening, like when empty transport helicopters repeatedly return to "buzz" (fly over) enemy units at top speed again and again. Flying in on troop insertions and back out again is acceptable, as is engaging targets from a battleposition. DO NOT hover helicopters at maximum ("Normal") height in battle positions, to use as an ATGM platform or to act as a recon satellite or an AI distraction. This is unrealistic at the moment since the Scenario Designer currently has no way to restrict/limit/cap flight height because he may want to represent certain types of conflicts where long range air defense and air superiority fighters exist. At such time, if ever, that the Scenario Designer can specify a maximum flight height, then we can remove this house rule. NOTE: Failure to abide by the house rules will result in drastic measures by the TGIF coordinators, such as not posting the scenarios in advance, removing features from scenarios (like artillery and aircraft), or in the case of repeated violations, barring certain users from CO'ing. Also, the CO should strive to have all users on his side play within the guidelines of the house rules. DISCUSSION: *AFTER* the scenario is played, feel free to post constructive criticism about the scenario here, so that it can be improved. All constructive criticism will be taken into account, but pissing and moaning will be ignored. Constructive criticism = complaints with specific suggestions Pissing and moaning = complaints with no suggestions DISCLAIMER: Keep in mind that: The scenario may change at the last minute depending on TGIF turnout. Any plan file that you may create may be rendered invalid by last minute adjustments to the scenario (if you are going to CO, it is better to save a plan AND take a screen shot of the plan as backup). Sometimes this list may not get updated due to real world situations. This list will continue until we point in time that it is deemed "too much trouble", which is the moment in which we determine that no one new is CO'ing, or the situation is no different than before, or that the matches are becoming unfair (due to both sides studying the enemy situation in advance). If this list turns into a mud flinging contest, because someone was sour about losing or in order to insult a scenario designer then posting the scenario early will end. The scenarios that appear in this list are either new, classics, or at least played frequently and deemed "balanced". If you have a scenario that you think should be added to the play list then PM or create a post here about it.
  11. 30 DEC scenario: 1973 Sinai Operation scn09-H2H Given the path the campaign played out, we are at this particular final scenario. If Blue wins then they win the mini-campaign, and if red wins (or if both sides lose) then the campaign result is a draw. This scenario is a typical TGIF length scenario, not a short 30-40 minute one like the past weeks. Depending on how the previous two missions went, there is also a similar Red "good path" scenario where the fine result is either a Red win or a draw. Next time we play this out the scenarios will be better tweaked and hopefully better balanced to create more a chance that Red can win the later stages. SPECIAL CONSIDERATIONS: There will NOT be a draft. Whatever side you chose last week then choose the same side this week, DO NOT SWITCH SIDES (no one likes a quitter). If you didn't play last week then pick any side you want. Planning Phase (for both missions) will be timed, 20 minutes maximum then we start. The CO does NOT have to be the same person in every scenario. Whoever wants to do it can do it, mission by mission. If someone wants to CO every mission then that is fine too. 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. Updated the scenarios to fix an issue with the artillery (I didn't want to hear Red whining about it).
  13. 30 DEC scenario: 1973 Sinai Operation scn06-H2H and... {1973 Sinai Operation scn05-H2H or 1973 Sinai Operation scn07-H2H} Scenario 6 is difficult for both sides to win, if I remember correctly. If Red wins it then they win the entire campaign. SPECIAL CONSIDERATIONS: There will NOT be a draft. Whatever side you chose last week then choose the same side this week, DO NOT SWITCH SIDES (no one likes a quitter). If you didn't play last week then pick any side you want. Planning Phase (for both missions) will be timed, 20 minutes maximum then we start. The CO does NOT have to be the same in every scenario. Whoever wants to do it can do it, mission by mission. If someone wants to CO every mission then that is fine too. 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.
  14. Good game Red. The result was... Mission 1, Red win. (Go to mission 3) Mission 3, Blue AND Red loss, neither side had the 600 points to win (which the briefing states is a draw and in the case of a draw, is counted as a Red win). (Go to mission 6) Next TGIF... Mission 6 (Mission 5 or Mission 7 possible). If Red wins Mission 6 then campaign is over as a Red Victory.