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,878
  • Joined

  • Last visited

3 Followers

About Volcano

  • Rank
    Senior Member
  • Birthday 02/14/1977

Personal Information

  • Location
    Texas
  • Occupation
    Game Design
  1. Yep, I got that, but I dislike typos.
  2. Double negative, so yes, there will be a draft. Just kidding, I fixed it.
  3. 17 FEB scenario: Mech Company MTC (1978)-4010 SPECIAL CONSIDERATIONS: Due to an issue that has since been fixed for the next update, the REVIVE conditions had to be temporarily changed in this scenario to get it to work. It could turn out that units that are killed in the repair area turn out to be immortal, or zombie-like (they may get revived immediately when killed). If that is the case then it is recommended that neither side hangs around the enemy's repair area in overwatch. Move in and occupy and hold to prevent repairing and reviving. There will NOT 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. Mech Company MTC (1978)-4010.zip
  4. Ouch, we hope you recover OK.
  5. Yes, please, better to not create expectations which are possibly let down in the end (it frequently happens), nor place unnecessary pressure on those that are tediously working on the improvements. The final FPS situation should be better (this is a stated goal, and is not a secret), but exactly how much better is not reliably known at this time. This is why it is better for those that are privy to such information to not comment any further until we are closer to release. I understand the enthusiasm though, but let's please leave it at that for the moment.
  6. OK that post is better. The original post was too broad, so it it was removed because it is too early to know what the exact final results of the optimizations are. Also, these results have yet to be tested on a wide range of computer specifications. The point here for everyone is that these observations were made from an experimental test version on one specific PC, with some features disabled, and everyone should not get their hopes up as to the final performance until we get closer to release date. As long as everyone understands this then, yes, factual statement: FPS should improve, which is certainly a good thing, but by how much exactly we do not yet know.
  7. That FPS information is total speculation at this point and should not be repeated. It is not official, and some features were completely disabled in the tests. Better to wait for the final version...
  8. I just updated the scenario to "4010a" on the end of the name. I improved a few things on the UN side mainly, some bad logic was left over from when the side was AI only. Also, added a bit more information to the map so they know where their reinforcements will arrive (if they get them). Also, I went ahead and implemented some actual ROE behavior for the UN (see the map for notes on their behavior) where they cannot use their primary weapon systems until they become activated, and the notes on the UN side in the briefing for more information. Hopefully it all works. Two important things here: It is not in the spirit of the scenario for the CO to have a plan file here. That includes graphics, or unit placement. There is supposed to be no plan, just position your units very quickly and roughly and figure it out as you go. If this is a problem with anyone, then please do not CO the mission. DO NOT LOAD A SAVE PLAN FILE. The UN side should NOT shoot its own forces to cause it to become hostile, if they do, this is considered cheating and forfeit the scenario result on their side. I have set the logic so that the UN will eventually become hostile if both sides kill each other too much, so don't worry, it will happen. Also, the UN can use coaxial MG all they want if they deem it necessary to hinder hostilities between the two sides.
  9. UN can intervene immediately, but the AI will not engage them or vice versa until someone fires at them. Humans can do whatever they want of course. Also, the UN AI becomes hostile to everyone once that happens. I am sure the UN will become hostile within about 5 minutes of starting the mission.
  10. 10 FEB scenario: Brush Fire-Town Dispute-UN playable-4010a SPECIAL CONSIDERATIONS: Need three COs: UN side, Lubango side, Luena side. Basically all sides are against each other. There will be no actual time allowed to plan in the planning phase. Once everyone is in the planning phase, a timer will be started -- all sides have TWO MINUTES to move units in their deployment zones and then the mission will begin. Actual planning is expected to occur during the mission (or not at all). This can be a short scenario. If it is over within 40 to 60 minutes then we may consider playing it again (since there is no time spent in planning). There will not 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.
  11. It is something strange that the forum does. Basically when you post the picture, but you go back and edit the post, then it will add another thumbnail. If you edit it twice then you will have the thumbnails on there three times. What you do is - edit the post, and delete all the images within the post, then save it. At that point the forum will add in the thumbnails (again).
  12. Thanks. Yes, its a known issue when you paste, but not when you type; its been like this since SB1 AFAICR (not new).
  13. 3 FEB scenario: 6k Front 2013-4010-M1A2-OMU 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.
  14. Actually, ignore that, I might be confused as to what you are referring to.