Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Ssnake

  1. Interesting. I didn't even know that the old method worked, let alone that it was a conscious design decision. To that extent I don't feel us to be obliged to preserve it. But of course I can see the utility value of this or "something like this", so I'll see what we can do to make your life a bit easier here, maybe by dropping the annoying habit to replace the file name with the first file it finds in the target folder rather than preserving the original name until the user actually clicks of a different file.
  2. Ssnake

    Text Flickering

    Even better, there's the "--fullscreenwindow" command line parameter to create a borderless window that fills the whole desktop. Of course that only works with the same resolution as chosen for the desktop, and if you have a desktop spanning two or more monitors funny stuff may happen.
  3. It can happen that if a theme contains a texture that is no longer there, it gets replaced with black; prior to 4.159 the texture atlas might actually shift all texture positions by "one" (so that all subsequent textures would be off); I recommend to check the THM file for that scenario first and to fix possible missing textures. But if this isn't really the problem, maybe you have discovered something else. Difficult to say from a single screenshot.
  4. I don't think we could ever identify why the mouse pointer disappeared for some, mostly because it doesn't happen on any of our machines (beta testers, programmers).
  5. Not sure what to say. You may have discovered an edge case. The results may be adequate, but I can't really say much from a handful of screenshots that don't show the angles that would allow a complete assessment. There may be a discrepancy between the in-game impact location and the recorded location in the AAR ("shouldn't happen", but can I rule it out with absolute certainty? No.)
  6. Quite possible. We won't know until after a programmer commented.
  7. Steel Beasts 4.1 no longer uses these old file formats. They need to be converted into the new file format, called "map packages". This is in principle a very easy process. Unfortunately it's made complicated because there are a lot of special cases. Try to open one of your old scenarios in the mission editor. If you get an error message, read it carefully. It will list the name of the map files that were used to create it. Now try and find those map files; there are two: HGT and TER files. If you have them both, open the Map Editor with the "Default Map". Then go to the File menu (top left) and select "Convert map from TER..." This will start a map conversion wizard that will guide you theough the the map package conversion process. You will have to enter a map name. Maybe add something to the name to make sure that you will recognize it as one of yours. Add a short description to make it easier to recognize the map in a few years. You may also need to enter the approximate south-west map coordinate if the map that you want to convert is very old. If you don't do that, the day and night time and the star and sun position will be wrong (but nothing worse will happen). After the map conversion is complete (this will take a few minutes), go to the file menu again and "publish" the map, then save it. Now go back to the mission editor and open your scenario file again. When the error message comes up, select the button to "replace the map", and pick the map that you just converted by the name that you gave it. Save the scenario file. You're done!
  8. There's but one cocktail containing gin that I find acceptable, and that's because it's the whole bar drowning out the taste of it - Long Island Ice Tea.
  9. The problem was solved in under an hour. What more do you expect?
  10. Secondary licenses are available again in our web shop.
  11. He who made this doesn't like beer... I'll try to find a substitute, though.
  12. We should have the 4.169 full installer ready later today. There was a hesitation to supplant the 4.156 full installer with it because of the palm switch inversion issue, so we'll have both up there until there's a solution that makes both obsolete.
  13. I thought that if you set the first AA slider in SB to 0 you would then use AA modes straight from the graphics card driver, but apparently this is not the case. I'll pass this on to one of the programmers for comment.
  14. I have only heard of them ... in frightful whispers of huddled betatesters, and the mad screams and hollering of programmers during their fever dreams, locked up in their lightless cells.
  15. Another stunning success for eSim Games Tech Support.
  16. Having to press a palm switch button when "joystick" and not "control handle" is selected in the Controls dialog is definitely a bug/not intended; we inverted the handling of palm switched since SB 1.0 for good reason. This will be addressed.
  17. No, it's a bug.
  18. The --fullscreenwindow command line option may be an alternative for you. For that you'd need to create a duplicate link of the Steel Beasts incon on your desktop, and then add the command line parameter in the icon's properties' "Target" line, similar to the Steel Beasts "debug mode" icon in the Troubleshooting folder.
  19. That's why we split it from the Steel Beasts installer, so that you wouldn't have to download the same 13 GByte with every update.
  20. There's always the option to press that button to restore default assignments. But typically this creates more work than fixing this one or two buttons, which is why I'm not recommending it. But the option is there. Very simple, very reliable - but potentially with a lot of side effects.
  21. We converted everything for the official eSim Games supplied scenarios (in the "Scenarios" folder). Everything in "My Scenarios" requires your action. Typically it is as easy as to open the mission in the mission editor, and then to save it again. If it can't be opened directly in the Mission Editor, the error message will at least describe what needs to be done. These two general help threads should arm you with the necessary background knowledge: About updating your scenarios About updating your maps As to "why" this needs to be so hard, well, we couldn't really make this any easier. The old way of working with the data allowed for an anormous degree of flexibility (resulting in an equally enormous number of special cases), and it played very loose with data integrity (because they could be embedded in the scenarios). Once that you stop embedding map data in a scenario file and still want things to work in network sessions you can no longer rely on file names as the first, last, and only line of defense.
  22. Yes, it should really be called "SB Map Tools". With so many new things, at least we should be consistent in the naming.
  • Create New...