Ssnake

...overwhelming chances are, it's not because we don't want to. 95% of all incoming emails are being answered within 24 hours, the majority within 6 hours. Most people contacting us - either directly by email, or by using our contact form sheet, supply only a single email address (more on that later). While the vast majority of email addresses supplied this way to us are correct, there's still a non-zero chance for a typo. We may be able to spot and correct such errors if they are in the second half of the address, e.g. @uotlook.com or @gnail.com - but whether you're tankmaster771 or tankmister717 we have little chance of guessing right. Then there's spam filters. Corporate email addresses like to filter our messages because there's "games" in our name, others find the license ticket codes highly suspicious (only cyber criminals encrypt, there are no legitimate cases!). Whatever the cause, sometimes our replies and license tickets will be found in there. If you don't check there and rather assume the worst, chances are that our subsequent apologies get swallowed by the very same filter. An all-time classic is the full mailbox. You don't receive your ticket - because the mailbox is full. You ask, where's my ticket, and never receive our reply - because the mailbox is full. You send us an angry letter demanding a refund and still don't get a reply? Maybe, just maybe, the mailbox is full. Who knows what other messages you missed, recently? You will never know. This is why we think that it's a good idea to send us one alternative email address. We're not collecting such data because we want to trade with them. There simply needs to be an alternative communications channel so that we can actually get in contact with each other. Yes, there are cases where we need a bit longer to reply. Someone might be sick, or traveling, or answering your question is unusually complex. Give us a day or two, then nudge us with a gentle reminder. Don't wait months. Try to supply us with additional info, like the date of a purchase or other relevant information.

All our emails to you are being bounced by your mail server with the rather unambiguous message: Mailbox full This probably explains everything. Remedy: delete emails that are no longer needed, or switch from IMAP to POP3, or kindly provide us with an alternate email address like we asked for in the order form sheet.

"not" in what way?

It is no accident to the extent that the complexity of such a step up in mission scope and responsibility naturally is a steep upward learning step - but we didn't make it "extra hard" with malicious deliberation. Keep in mind, tank commanders usually receive about two years of training (one for basic tank soldiering, one to make a tank driver's license and then the Commander's course), and then an additional year or two to progress to the platoon leader position (if you're on the fast track of an officer's career, otherwise it might take six years or eight; of course that's not just all learning but also the practice of the art at all levels). But if you find things progressing too fast: Hey, there's a Planning Phase, even when you run a tutorial mission. So, make a plan. Think of when you want which unit to move, and give their routes corresponding embark conditions. And of course you can always order units to move at slower speed (but then you'll be exposed longer to enemy fire). The M1s in the tutorial give you above average protection, and I think the enemy is somewhat undergunned, so the cards are still stacked in your favor. It may be better to stick in defilade for a minute longer to prepare for the next move, but then move quickly. And as always, practice makes perfect.

Case, hopefully, solved. Fellow software developers: Don't run Steel Beasts while your debugger is open. The CodeMeter runtime doesn't like that, and will lock the CodeMeter container in use. But if it has happened: Send me a CmDUST log file and a license request file, and I'll unlock your CM stick again (until you test my patience doing the same mistake over and over, at which point I'll assume malicious intent, or trolling).

The thought has crossed our minds, but we have more urgent tasks at hand for development, and ... there are other, non-intuitive factors to be considered that complicate the decision-making process.

Rotary encoders.

There is an API for that in SB Pro, just not in the Personal Edition.

that isn't the case anymore? We are using a new joystick library now, true; as far as I'm informed, the main advantage is that SB Pro no longer insists on input exclusively from the primary controller (ID 0). I'm not sure however whether our Controls dialog will actually register buttons #1...4 for reassignment. Maybe it does, but even then you probably will save yourself hassle if you connect these buttons on the grip with the controller button numbers that Steel Beasts expects.

What I can tell is that the resistance of handles (in real life) varies a lot. In the ASLAV-25, to name an example, they are a combination of hand hold and control handle, and therefore are very stiff. To operate them for an extended period you'll need to develop a lot of forearm strength. In the Leopard 2, while in stabilized mode there is very little resistance. However, while in Emergency mode, in the Leopard 2A4 you would operate the hydraulic valves directly, so the stiffness becomes much higher; we try to replicate that in SB Pro by increasing the deadzone. Some people think that you can still control the turret with adequate precision in this mode; personally, I always preferred to use the hand cranks after getting the turret in the general direction of the target. Specific advices: Make the palm switch an actual switch in your replica (button #3), and not a circuit breaker, so that Steel Beasts can handle the signals adequately. You'll notice that joystick buttons #1 (trigger), #2 (laser), #3 (see above), and #4 are hardcoded in SB Pro. Ideally your replica would conform to that wiring. Choose a somewhat universal grip design. Chances are, you won't be playing one specific tank in SB Pro, but a range of them, both as commander, gunner, and occasionally as a driver as well. For the more modern tank designs, a universal trend is to put moar buttons on the control handles. CV90s have a three-way switch that is permanently giving a signal in one position to let you select the fire mode for 3P/KETF ammo. It's a relatively unique feature, but if you have it on your stick, the CV90's fire control system will suddenly make so much more sense.

Yeah... no maintenance, no gun cleaning, ... "just the fun parts".

Plus, the gift that keeps giving. LARS has been retired in the late 90s, but someone thought, rather than paying for the disposal of these munitions we might just as well fire the old 110mm rockts from the 227mm MLRS and save money. So, they bought adapters for millions. Sounds not too bad yet? Except, they never fired those rockets. Not only is their shelf life expired. They can't be safely disposed of because the rocket bodies are seeping explosives, so you can't pull them out of the storage racks without everything blowing up in your face. 🙄

Man, that thing was loud.

This is now bug #12284.

Are you sure it's not set in the Mission Editor as an option for these units? (Options ... Ammunition ... "Unlimited")

Yeah, that would be the solution. Create a copy of the Transfer Manager shortcut, and edit its properties to add the command line option --ignorelock This would be similar to what'd escribed in this video, except that it's abbout the Transfer Manager, not SB Pro:

I would expect the Luchs driver (and reverse driver) to have an image intensifier vision block facing forward (reverse), each. Now bug #12278.

Now registered under no. 12277.

Thank you!

Like I wrote above, follow the link. That post contains details.

Neither patch nor reinstall will help. The mutex file needs to be deleted. Please follow the link below for instructions without command line use:

Hm. It's not supposed to do this anymore, but it's hard to argue against empirical evidence. As I'm on the phone right now: please search this forum for "mutex", and you should find advice.

I've never seen on an actual Abrams. The image shows a version with 105mm gun, so M1, or M1IP. At the time they had the MERDC-pattern, usually, which is quite different from this one. This here looks like a late Wehrmacht pattern where they lathered some green paint on the yellow factory primer and called it a day. Maybe someone thought it'd be fun to see how it might look like.