Ssnake

Well, the pillars wil auto-adjust.

These are all pretty strong HE explosions that, while failing to penetrate the armor, still generate shock (gyros > stabilization) and fragments with a high likelihood of ripping off the radio antennas. The die roll differentiation will occur at lower explosion thresholds, e.g. RPGs, medium caliber HE rounds, ...

Okayyyyy... Cage fight! Two go in, one comes out? Maybe you can find an arrangement to split the workload.

You should NEVER try to fix an error message about a missing DLL by simply copying it into the program folder. Just consider all file operations in the program folder as TABOO. Sure, it might work but it's bad practice for a number of reasons. The proper way to handle such cases is to check if the icon you just clicked points to the right executable in the right location, and if it does, to take the error message as a hint that the installation is corrupt. Solution: Uninstall, reinstall. Why is it bad practice? Typically, after putting the first DLL into place, another error message pops up about another missing file Corollary: If you "reinstall" your installation file by file until there are no more error messages, that doesn't necessarily mean that you fixed the installations. Maybe we just ran out of error messages. You could still get funky application behavior, and thus trigger a nightmarish support case. DLLs are about as powerful as program files. Would you accept "TotallyInnocent.exe" from an unknown source on your computer? (Hint: The correct answer is: No!) Not saying that Mark isn't to be trusted or had malicious intentions, but you could also ask Google for the file and find it "somewhere on the internet" and you just don't know who made it and for what purpose - both as far as declared intent goes, and undeclared. Don't invite vampires into your home! Like program files, DLLs have versions. Just because two DLLs have the same name does not guarantee that they are of the same version. Different versions mean different functionality mean, possibly, funky application behavior with the resulting Support Case From Hell. (That's not just an unpleasant experience for me, but for you too) Files that you drop manually into the program folder do not get uninstalled. Which may cause further trouble down the road, months later.

This is now bug #8601.

...at least on that fateful evening when CompuServe offered alphanumeric email identifiers rather than strictly numerical codes, and I had to come up with something, quickly. Digital land rush and all. These days, it's more difficult. Hail.Hypnotoad was already taken with gmail, I found out.

Just to clarify the wording - 4.161 was an upgrade to previous versions, we charged classic license owners money for it. All the versions since last August were patches - free bugfixes, no new features. Updates are in between. Mostly bugfixes, free of charge, and with some new features.

Thanks for the kind words. There may be a misunderstanding, though. I wrote of a "significant update" (not upgrade) (and this year, not 2022), so it's not going to revolutionize everything. Still, more than a patch, and more than just a patch with a token feature addition. 😎

Ideally, make a screenshot when it happens. I have switched the default hotkey (Shift+F12) against time acceleration (F12), so it's less awkward to use.

Note that primary licenses need to be activated first before you attempt to activate secondary licenses. This may be relevant if you order everything on a single ticket.

We're aware of the bumpy roads issue, and working on it. Not sure what the latest status is.

Actually, since a good while ago there's now also a general Search field in the upper right hand corner above each thread/page

...or a special form of hubris...

I don't code. The programmers might object to that statement, and rightfully so. I just happen to be the public face.

magNify. so easy... 😜