Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Mirzayev

  1. When your hobby consists of posting stuff that no one will read.
  2. You know there are multiple drones already in Steel Beasts, right?
  3. You can take screenshots by holding Shift+F12.
  4. That's awful! He was a good man and I enjoyed the many hours I spent playing Steel Beasts with him. I'm glad I knew him.
  5. 1. Click "Offline Session." 2. Pick a scenario. 3. Play it. Yep.
  6. We're beyond license activation. He's asking how to play single player scenarios and the hotkey for third person.
  7. Or just keep going. There shall be no end to the shenanigans!
  8. I know this won't be read by the OP, but for others who may want to know about license activation: https://www.steelbeasts.com/topic/7797-license-activation-how-to/
  9. If only there were freely available release notes on the same download page as previously linked that told exactly what the latest version was, and how to install it...
  10. There was an M3A3. They have all been converted to the M2A3 layout.
  11. Wish: the ability to save IP addresses with a nickname for multiplayer sessions so you can select something like "Rev's Server" as opposed to ""
  12. @ben and I figured this out six months ago with one of my scenarios. I guess I shoulda reported it. 🤣
  13. @Thrown Tread33 Here is what is happening: If you have any off-map artillery the default is that they will fire first. Off-map artillery will execute fire missions until the number of committed batteries is maxed out. On-map artillery will then be called into fire. Included is a quick scenario to demonstrate this. Open it and call in 3x HE fire missions. All of these will be fired by your off-map artillery. If you call in a fourth artillery mission while the first 3x are processing, your on-map M109s will fire it. If you only want on-map artillery units to fire, remove all of the off-map artillery tubes and batteries under the support options. Artillery Test.sce
  14. I'd argue that if you are making a scenario where the enemy reacts in a manner that the player is totally unprepared for then you are making a bad scenario. A good scenario with replayability should have more than one enemy course of action that the player can determine from reading the briefing. Usually these courses of action are not completely new plans with zero similarities: most COAs will share many similar features. The challenge to give to the player is enough information to know where to look to try to determine which course of action the enemy is using so they can modify their plan appropriately during the execution phase. I'd also offer that all information that the player needs should be contained within the scenario. Having to look up threat task organizations in an external document is lazy scenario design, IMO, but one that is very common in many commercial "military realism" oriented games. There are multiple echelons above a Platoon, Company, Battalion, etc. that would realistically be feeding information to their subordinate unit (IE the player) to allow them to make an actionable plan with a reasonable chance of success. This information will never be 100% correct, but it certainly won't be 100% wrong. You can also add other variations to existing enemy COAs. Maybe there is a 10% chance that the enemy will commit their reserve to your AO, and so now you have to fight two tank companies as opposed to one? Maybe there is a 35% chance that the enemy will commit rotary wing aviation to disrupt your planned offense? Maybe there is a 75% chance that the enemy will conduct non-observed "terrain denial" fires on locations where the player is likely to put observation posts? You can definitely get creative with adding in additional "things" that can bleed over from the area of interest into the player's area of operations. They don't have to be game changers, but they should be something that forces the player to consider them in their plan or face the consequences.
  15. Start here and get the scenario you want: https://www.steelbeasts.com/files/category/140-41-single-player-scenarios/ Drop the scenario into your "My Scenarios" folder under documents. Default directory is: C:\Users\<YOUR USERNAME>\Documents\eSim Games\Steel Beasts\My Scenarios
  16. It is important to note that this was just for the server patch sent out by Nils, NOT the bundle installer. That worked fine.
  17. The server update for 4.379 is triggering a Trojan detection via Windows Defender. I was able to get it to work via exclusions, but it took some experimentation. Figured this might be worth testing prior to the next release. Results were the same regardless of browser (Opera, Chrome, and Edge) used.
  • Create New...