Ssnake

Ownership should be completely independent from waypoints (unless referenced in the ownership condition). I agree, this sounds fishy.

SHP data can't be imported into a terrain profile; the data would have to come in ASCIGrid or DTED (as described in the User's Manual, in the Map Editor chapter).

...and the next update, coming February, will bring a revision.

It may be "technically possible" (e.g. by creating spiralling roads and turning them into ramps), but I would still agree with the intent of the statement that it's simply not practical. As far as the addition of new tanks is concerned - I'm all for it. It needs to be understood however that much of our development - not all of it - is driven, and enabled, by the demands of our military customers. They decide if they need a simulation for their training, they decide if they disclose a tank to eSim Games, and which parts of it. The more access we're granted, the easier it is to create a faithful simulation. Conversely, without access we have to cobble together what we can find in open sources which is often not enough, or at least doesn't allow for a very detailed simulation. I'd love to have a playable Merkava, but will we ever see one? Unlikely. The other aspect is available time. Creating a playable tank for which there is no demand outside the Personal Edition invokes not only the costs of researching the vehicle, creating the 3D model, the programming, the testing. It also creates opportunity costs - that we could have worked on something for which we would have been paid, but didn't. That's not to say that we'd never do such a thing - we have a playable BMP-2, T-72M1, Challenger 2, Scimitar, T-55, T-62, BTR-60/70/80/82, BRDM, M1, M1IP, M1A2SEP, the Technical with the recoilless rifle, and more - and for none of these we had a military contract. Still, we need both - a pause in contractual work and the opportunity to investigate a vehicle in order to create a suitable model for you. Should the Polish or the Korean army decide that they need the help of eSim Games to create a K2 MBT crew simulator, we would of course render assistance. I suspect however that this is something for which an American-German company like eSim Games is only third tier, with preference for a Polish or Korean domestic solution.

Yeah, but the .mil customer tasked us with allowing for a human loader, so we couldn't keep the old automated loading. Also, keep in mind that if you're having a protracted firefight, you're doing it wrong. The Centauro, after all, is a reconnaissance vehicle.

It's now registered as #11445.

Please isolate the incident, we'll investigate the scenario.

You can always save the Theme of a map under a new name, edit its colors while remains otherwise unchanged, then apply the THM file to the scenario. The THM data will then be stored in the scenario file, no extra delta map.

You can select the option in the Mission Editor to adopt the color scheme of the chosen map's Terrain Theme. And there, you could set the color of bog to anything within the RGM spectrum that looks appropriately alarming to you. Note that any terrain under, I believe, 25% traction will receive the hardcoded teal color (unless the "use Terrain Theme colors" option overrides), not just terrain labeled as "bog".

It is possible to link scenarios into a "small operation". We do not yet have a video tutorial for that, just what's in the user's manual.

Nomad, you have new mail. Since we can't identify the problem, we decided that we need better reconnaissance.

Okay, I guess we can rule out the conflict of having multiple audio devices as the source of trouble. The debug log file has these four conspicuous lines: [18:56:11,437] CSound ERROR: Incompatible WAVE file format [18:56:11,437] CSound ERROR: Could not read wave header [18:56:11,437] CSound ERROR: File could not be opened [18:56:11,437] CGame ERROR: Could not initialize sound card! My next best guess is a sound driver issue. This seems absurd since Steel Beasts uses an about-as-generic-as-it-gets sound file format. Then again, there are these lines, and they're here for a reason.

Also, be on the lookout for "network overload" messages at runtime, and in the debugLog.txt file after the session.

Is now #11442.

I can only see a hole that I would attribute to "a" subcaliber kinetic energy round. I wouldn't dare to call caliber and sub type. It does, however, not look like a 100mm full caliber hole to me. I've heard that steel sabots create wider holes than late tungsten or dU designs, so maybe that's what we're looking at.