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.

Rotareneg

Members
  • Content count

    1,634
  • Joined

  • Last visited

Everything posted by Rotareneg

  1. Since there wasn't a SB specific video thread like the SB screenshots one, I figured I'd start one. Here's an uncut run of Zipuli's Tank Platoon in Attack using the M60A3 (TTS):
  2. Yep, I found and reported it about 5 minutes after 4.019 came out as one of the first things I looked at was the new BRDM model.
  3. Another issue that's probably making it easier than intended is that BRDM-2 AT's are currently broken and cannot guide their missiles. Just played it through and won on single player, I liked the atypical objective of just finding where they are defending instead of the more common "KILL EVERYTHING!" Also, I forgot how different SB plays when the observer position is disabled, maybe some day they'll get that working for multiplayer sessions too. Oh, and one last thing: issues like the map updates changing are why I don't like password protected scenarios, it just means when they inevitably break due to some future update, they can't be fixed by anyone but the original creator who might not be around any more.
  4. That scenario was from 2.6, there wasn't an option back then to disable enemy map updates, it was all-or-none.
  5. Troops on the back of a technical are transparent to a LRF and are amazingly tolerant of 120mm HE rounds, some times even surviving a direct hit to the head. I'm not sure how much of that latter issue is the troops themselves, or the HE ammo acting up. I tested with DM11, Slsgr 95, M908, and OF-26 ammo, the worst they could do was just kill the one guy who got directly hit, there was no splash or frag damage to anyone else. I know the HE effects need an overhaul, I just figured I'd mention it in case there's something else going on here (frag rounds DO send out fragments if they hit trees, for example.) HE vs truck.7z
  6. I'm not quite sure where he was going with that either, as it's kinda obvious that you use music with emotional content similar to the media you're working with. You probably wouldn't use a lighthearted comedy soundtrack to sell a dark and gritty horror film (unless it involves clowns and you're trying to be ironic I suppose.) It does get annoying when, as in the movie trailer spoof I posted above, everyone uses the same cliched style defined by the current standard "recipe for success," but that doesn't really apply to someone picking some music they like for the end credits of a game they play.
  7. The manual azimuth function, triggered by the "K" key when in the commanders position of any unit, is always available. The manual azimuth setting in the mission editor only controls whether the tank clock automatically rotates or if it stays fixed pointing "up." You can activate the compass when looking through binos, but it won't actually show the compass tape on screen until you zoom out. It would be nice if the map had some basic "ruler and protractor" functions. You can work around that by printing a map and using real-life tools, but that seems a bit sub-optimal when SB is being used as a "game" as opposed to a real-life training tool.
  8. As demonstrated in this trailer for TITLE:
  9. If I load a scenario in the editor and use the Mission text -> Copy... function to copy the briefing from another scenario and then save the scenario, the resulting scenario file is much smaller than the original. Attached is an example, test1.sce is "normal" and test2.sce is after using the Mission text -> Copy... function. File_size_change.7z
  10. Yes, it just plays the credits.wav file in the "eSim Games\SB Pro PE\music" folder. Rename or delete it, or replace with a different one (renamed credits.wav of course.)
  11. New item for the Content Wish List: Bayonets!
  12. And be sure to go through the tutorials to gain proficiency with the basic functions of the sim and particular tank you're using.
  13. Version 1.0.0

    62 downloads

    Yet another variant of the old "Tanks!" scenario. Randomized starting location for your vehicle and enemies, enemy riflemen in woods, FASCAM artillery, and ATGM teams. Includes separate scenarios for: BMP-2 Centauro CV90/30-FI CV90/35-NL CV90/40-C Leopard 2A4 Leopardo 2E Leopard AS1 M1A1(HA) M1A2(SEP) M3A2(ODS) M60A3(TTS) Marder 1A3 T-72B1 (m.1985) Too hard, too easy, or want different tank or different enemies? Load it up in the mission editor and change 'em, it's easy!
  14. I figured out what it's doing: the "Mission text -> Copy..." function clears the navmesh for some reason.
  15. I'm not sure if this is working as intended or not: Selecting manual fire control disables smoke grenades. Tested on M1's, Leo 2's, and Bradleys.
  16. Firing an AT-5 from a BMP-2:
  17. Towed AT guns would be cool, the T-12 AT gun for example matches up chronologically with existing SB equipment.
  18. I stand to be corrected, but as far as I understand it the primary changes are aimed primarily towards elevation data, not terrain data (which in SB means trees, water, roads, buildings, etc.) Currently the SB mission editor defaults to embedding elevation data in the scenario file. When you run a scenario SB automatically performs elevation adjustments, leveling the ground next to roads for example, which isn't a big deal as the current elevation data is pretty coarse, 12.5 meters per sample. The new engine will support much higher resolution meaning potentially much larger scenario files and longer loading times if high res elevation data was embedded in the scenarios and automatically adjusted for road leveling, etc. when loading. It would seem the main change is that that scenarios will no longer contain the base elevation data, but instead can contain pre-generated elevation adjustment data (that is presumably created when saving the scenario in the mission editor and which compresses down to a relatively small size as it only contains the difference between the base data and the new elevations.) Thus, when players download the scenario via a browser or else get it from a multiplayer host, they'll need to have the base elevation data already on their system. This is how it used to work with the original Steel Beasts, and even with the current version of SB you can optionally save scenarios without embedding the elevation, requiring the player to have the data already on their system.
  19. Completing 99 missions would be mind numbing IMO...
  20. This tank:
  21. Options->Display-> Z-Buffer Size: 24 Bit