Ssnake

I don't think anything changed there recently. But it's probably a feature that rarely gets attention. Closing #12086, then.

Note that the ballistic shield doors on the Leopard 2 open separately for each channel. Could it be that you just opened the daysight, but left the door of the thermal sight closed? This would be relevant if you used the interior 3D controls rather than the hotkey (Alt+B, I seem to remember).

There may be a misconception at work. On receiving artillery fire, (AI) Leopard crews will - close the ballistic shield doors - put the thermal imager in standby If you as the human gunner open those doors and stay in the TIS view, everything remains black until you activate the thermal imager again (Num+). Otherwise, if you leave the gunner's position, the AI gunner will close those doors again. Could it be that this is what happened to you?

Thanks a lot for these kind words; note that in the AAR, if the damage in the event is displayed in black color, you've hit a target to no (new) effect. If something changed, the damage description will be in red color.

Sydney Opera House - +50% culture production, must be erected in a coastal city. Best wishes to everybody for the coming orbital period!

Which scenarios are out there where the player would take control of the T-72B3? It's consistently one of our videos with the highest viewing range, and occasionally people ask me about this, so... Maybe we can collect links to such scenarios in this thread.

Hm. I have not much of another idea. There's always the possibility that a bit gets flipped by cosmic radiation. The chances for that are low, but non-zero, and usually inconsequential (like, a color change for one pixel in a JPG image). But once in a while it can have notable consequences: Far more likely, however, is a bug. But as long as it cannot be reproduced, that's hard to fix. Let me know if it happens again.

Please check the scenario for duplicate IDs, while running it in Test Mode (Mission Debugger).

Well, well, well...

The mutex file, unfortunately, is the attempt to make the tool more robust, and according to theory, these leftover files "should" no longer occur. Evidently they do; unfortunately it seems to happen rarely, or under hard-to-replicate conditions, which makes this a bit harder to fix. You could push this as a priority item in your organization's bug list, maybe.

...and to you all too, from the eSim Games team!

....and here we go again, thread locked. I share the sentiment about media pundits in general that are never held accountable for their false predictions; Nassim Nicholas Taleb has something to say about them as well. But you bloody well know the forum rules, and went ahead and violated them anyway.

One of the many bugs that you will never get to see because it's been discovered in an experimental branch by our own quality assurance team. The kind of bug that I'm listing in an often overlooked big block of just bug numbers at the end of release notes, with a big Thank You to the beta testers.

That is now bug #12088.

Thanks for the find! This is now bug #12086.

The manual installation procedure doesn't change between these versions, other than file names.

Did you previously uninstall, or simply delete the Steel Beasts program folder? My assumption for the moment is the latter; in that case, there will be leftover entries in the Windows Registry, letting Windows (and the installer) think that there's still something to uninstall, while at the same time there is no uninstall option left because all the executable files have been removed. Remedy: You could try and mess with the Windows registry. Usually I don't recommend this because, frankly, the people who simply delete program folders tend to be of the more impulsive kind, the registry is the central database of the operating system, and that's a potentially volatile mixture. Alternatively, I recommend the manual installation procedure as described in the (full) 4.379 release notes (note that the eSim Games Downloads page only has the "austere version" because some people think that less information is better; I disagree for right now rather obvious reasons). But I think there is a complete version somewhere here on SteelBeasts.com in the Download area. I tried the "Resources/Documentation" and "Resources/General" section, but it's not there. Maybe someone can help this man? Generally, install the map packages first. Then the Steel Beasts program files. Afterwards you could add the Transfer Manager (recommended, but optional).

Now bug #12083.

Well the accepted max range for coax is 1600m.

On one hand I'd say that we're making progress about as quick as I expected and we're not lagging much behind the optimistic projections. On the other, for PE users it will still take at least three more years before there's a realistic chance for a release, and there's a non-zero chance that it'll take longer. There will be at least one more major V4 release, possibly two, before we can offer a version 5 to the general public.

Please just contact us rather than trying to fix it yourself.

That's a version 5 thing.

We made no changes. It seems justified. Maybe it wouldn't need to be 180° and just 45 or 60, if that's at the core of your objection. But I think it's undisputable that it has to be moved out of the way.

Well, please contact me (you can use the email given in that error message). Please plug in your CM stick (if you have one) and then open the Windows Start Menu. Type "cmdu" to find the diagnostic app "CmDUST", and run it. When the data collection is complete, it'll open a new window of the Windows File Explorer. In it, find a file names "CmDust-Result.log"; please attach that file to your email. Also, if you used a different mail address than your regular one for your purchases in our web store, telling me may help to speed up things a little bit.

What issue?