Ssnake

So, the Details sliders are all set to zero, and you still get very low frame rates? What about the window size/selected screen resolution. Have you tried changing any of it? What about driver settings. If you create an application-specific profile, be sure to disable all fancy stuff for the moment to see if the frame rate counter goes up. If it does, enable the different elements again like antialiasing, anisotropic filtering, etc., until you observe the frame rate dropping again. That would be your bottleneck. Re-reading your initial statement, since this seems to be exclusively about thermal views... What happens to your frame rate in the Leopard 2A5's or Leopardo 2E's rearward driving camera view (F9, then F2)? What happens if you open a mission in the editor, then test it from within the editor, and while the mission is running and you are in the observer's position of a vehicle, you activate the thermal view (Num+)? Will your frame rate NOT drop in any of these cases?

...or a StuG III, being one of the most popular armored vehicles of the Wehrmacht and oven overlooked despite being the "most successful" design when comparing kills to costs of procurement ... and similar in shape (though not size) to Jagdpanthers and Jagdtigers. All we can really say is that the pock marks around the impact suggest a HEAT warhead. With our tank platoon leader's course we once made a battlefield tour with a WW2 tank veteran (commander/platoon/company leader). One of his opening remarks were if we knew the most frequent illnesses/occupational hazards of tank commanders. After a few seconds, he just said "Lead poisoning of the brain" and more or less left it there.

I feel your pain. My T.16000 has a severe drift to the right on my main computer, but works perfectly fine with the notebook. I now face the joy of figuring out which of the gazillion USB devices is creating the trouble. Maybe I should use the stick exclusively with the notebook to begin with.

Different stick or not, as a game controller device it must be given an ID in Windows, or else SB Pro won't recognize it. If you use Foxy's Windows Joystick Analyser you can see a menu entry "Joystick ID" to select inputs from different sticks/game controllers. So, even my Thrustmaster T.16000 has an ID. So would the Cougar, or the Warthog, unless they register as some input device other than "game controller". Steel Beasts will accept joystick signals only from game controller devices that conform with the Windows regulations for joysticks, and which are registered as the preferred device, #1.

Underwater fording will require a 20 minute preparation. It is unlikely that this would be done under fire. Therefore we saw no need to implement such a feature. The air intake point of Leopards are set to the commander's hatch (ca. 2.20m), based on the rationale that the deep-fording capability can be accomplished with minimal preparation time. When dealing with water obstacles this will already give Leos a substantial advantage in SB Pro scenarios over, say, an M1 with only about 80cm fording depth. The steep river embankments were implemented due to Z buffer issues (shimmer effect of water surface and river bottom, if both are relatively close to each other). There is no real solution to get around this actually (except bigger Z buffers, which isn't configurable but a graphics card hardware imposed limit). Once that we add some transparency to water surfaces however, the shimmer effect might become visually acceptable. We will look again into this matter as soon as we have updated the visuals for water bodies.

The Palm switch may be hard coded to button #5; I may be wrong about it, but did you try to assign a different key/joystick button it in the Controls dialog box of Steel Beasts? WRT the rest, Alt+J and Ctrl+J (SHift+J?) will recenter the stick or invert the Y axis (you need to do it just once; SB will store the axis preference). Maybe that'll help? Or maybe there's some button constantly on that might cause the drift?

How could they, if there was nothing that they contributed to it? It's all wild speculation ... until they confirm our guesswork by telling us that we can't make it public, of course.

What can you do, when the Canadians don't even want to talk to us and rather plug their ears singing "Nananana...."?

The dinging seems to occur when a window loses keyboard focus, even if it is still in the foreground. I have no idea why this may happen, but so far my solution has been to Alt+Tab to some other application or the desktop, and then Alt+Tab (or Win+Tab) back to the offending window. Usually the ding is gone then, and I can type whatever I want. I don't know if that's going to solve all your problems, but it's worth a try.

Meh. If your training objective is that gunners habitually take their eyes off the sights to fiddle with buttons, touchscreens are a good choice. On the other hand, if you want to do it cheap, then do it really cheap with a desktop trainer. Otherwise use a container with full instrumentation. Anything in between is chickenshit.

Hedge, don't get defencive about that!

More to demonstrate the CNR Sim/CNR Log integration. It was surprisingly quiet this year, actually. We feared the worst with Raydon setting up a cal .50 gunnery simulator right next to us, but either they didn't make a live demonstration or they had the common sense to switch off the sound. Or maybe our feedback to the organizers actually made a difference, who knows. :cul:

Ah, so you want fording sites?

Guys... stop poking fun at him. It's clearly a photoshopped image, and slightly blasphemic I might add. Tanks can't drive over water. They would sink.

Looking at your screenshots, it seems as if your CM stick is being recognized by Windows. That's good. It may also be that you are trying to start the latest Steel Beasts Pro PE version but you haven't transferred the license to your stick yet. This could be because you haven't given permission to the Java or ActiveX applet on the License Central web page, or because of something else. If you cannot or do not want to run the Java/ActiveX applet on this web page, you can still create a remote update file. For that, right-click the desktop and select "New... Wibu Control File". In the new window, click "Create". In the next dialog box, make sure to have the entry "100146: eSim Games" highlighted (with blue background color); by default all entries are selected. Click OK. This generates the remote programming file. Now visit the License Central web page again, switch from "Direct" ro "Remote" and locate the ...RaC file on your desktop. After you uploaded this file, you'll be prompted to save a new file (ending with ...RaU). Once that you saved it to your desktop, double-click it. This will transfer the license to your CodeMeter stick. If we're lucky, your troubles will end right there. General advice, if the aforementioned recommendations do not work: Please run the CmDUST program of the CodeMeter program group ("Tools" subdirectory). After it is finished, a Windows Explorer window will pop up containing a new file, "CmDustResults.log". Please send that to Support@CodeMeter.com and add me to the CC list, so I can also have a look at it.

Yeah, we all can dream... Getting access to one, and the associated user manuals, is the obstacle.

Your interpretation is correct. This is supposed to reflect the quality of the training of your own troops. You could create several profiles and then play with the good or the bad one to see how it affects the balance of a scenario. Just a few basic statistics, nothing else.

Have you tried it in Windowed mode? (Alt+W) Might be interesting to see if there is an error message lurking in the background. What are your details settings? You may want to cut back on the ground clutter slider settings (Alt+D while you play). Another useful thing would be to open the task manager and see if there is some other process that consumes all the CPU time (remember, if you right-click in the process window in the category bar, you can select additional metrics to be shown). In the Performance view, go to "Show" and set a checkmark to show the kernel time. This can be helpful to identify whether it's the operating system or an application that uses the CPU time. Or start the performance monitor to see if there are other background activities that aren't shown in detail by the task manager. None of this will immediately solve the problem, but it may reveal some details that will give us a clue.

Unfortunately the video title is misleading. It was a Bill 1 demonstration with a remotely controlled Centurion tank (may it Rest In Pieces).

The Javelin video was staged; however, while it represented a (misleading) best case event - plus, they loaded the tank with C4 and not normal, slower burning propellant - it wasn't outright a lie. Just a ... selective presentation ... of elements which, individually, are quite possible.

The big flames certainly came from the propellant. Immediately after the RPG stuck, there's a "venting" first followed by the massive fire of the cnflagrating propellant. Still, the final explosion is so violent that I wouldn't be surprised if a few HEAT or HE shells went off as well. But with enough propellant on board, it wouldn't be necessary either.

Very likely so.

...but that was a problem with which every army had to deal, just think of the many Sherman variants, or the evolution of the T-34. Sure, nothing as excessive as, say, the Panzer IV, but still.

If I wanted to blow a serious four-digit dollar figure on a joystick, I'd pick the one for the CV90/35 or the Lemur or CV90/30. They may not be perfect for a Leo 2 or M1, but they have so many buttons that you can easily operate an M1 or Leo with them, and still use the full capacity in the CV90. Some things like fuze modes for the 35mm KETF rounds are only conveniently selected with these specialized controllers. What appears clunky and complicated in SB Pro when using keyboard and mouse all of a sudden becomes convenient and well thought out, if only you have enough buttons and multi-position flip switches. Yes Hedge, since about two years the export regulations have become a lot less complicated for many countries (not all of them, though).

Well, the remaining Wehrmacht generals had all the incentive in their memoirs to lay blame for everything that went wrong on the one guy who a) was clearly out of his mind at the time b) had conveniently committed suicide c) was burnt to ashes d) didn't leave a diary or other contradicting point of view At the same time the public was all too willing to ignore that it was the same great generals who were a) appointed by said corporal b) were all falling over themselves to carry out his lunacy Hopefully no longer.