DarkFib3r

Thanks ssnake, I appreciate it! Yeah, pressing the Next button twice feels like a needless gesture. I modeled the quiz after Duolingo, which always provides feedback on whether you are wrong or right. But I can see the value of eliminating success feedback and simply moving on to the next question. Thanks again for the pin and the feedback!

Hey all, I created a little quiz application to help with vehicle identification that you might find useful: There are lots of armored vehicles, but there are also aircraft from different eras, too. I hope you find it fun and helpful!

I have CH Pro pedals and I have not experienced the same issue as you. Maybe the pedals are being considered a joystick? As a test, you could try disabling the joystick in Steel Beasts to see if that resolves that issue.

--fullscreenwindow=true worked perfectly and fixed my issue. Thanks, this saves me numerous reboots and time!

Thanks for the ideas. I am running full screen, but I will try windowed mode to see if that remedies things.

I have a pair of MIMO USB monitors (480x800px) that use DisplayLink Manager 8.0.644.0, but they stop displaying the moment I run Steel Beasts. The monitors still have power, but the displays stop showing the desktop. A reboot fixes this issue, at least until I run Steel Beasts again. The monitors work fine on all other games and the issue seems isolated to SB. Any thoughts on why this would be happening or suggestions on how to avoid this particular problem? I realize that it is probably a specialized problem given that many users likely do not use mini USB monitors. I use them for flight sims along with a pair of Cougar MFDs, if you were wondering. It would be nice to have them keep working after I play SB so I could avoid the reboots. Thanks!

Holding ALT and rolling the mouse wheel will focus the thermal imager on most, if not all, tanks.

Top notch answer, thanks Mirzayev. That's exactly what I was looking for!

I understand the difference between GLOS CITV and GLOS GPS, but what I am having trouble with is determining which one to use in which circumstance? It seems to me that you use GLOS CITV if you want to override and fire, as TC, through the CITV screen. And you use GLOS GPS if you plan on overriding and firing, as TC, through the GPSE. Are there any other situations that would dictate using one mode over the other? Thanks!

Hi 12Alfa, Given that there is lots of interest from a bunch of different time zones across the planet to attend your training sessions (which are great, by the way), to completely remove ambiguity of the start times for the 1CAD training events, you might want to also include GMT time (also known as ZULU time) whenever you promote a new session. In this case, your event start time is September 29, 00:00Z, which is equivalent to September 28, (2100AST, 2000EST, 1900CST, etc). Once DST hits, the local times will change by an hour but the ZULU time will stay constant. However, you may also bump up the ZULU time at DST so that you can start at the same local time for ADT? Also, to be completely clear to newcomers, you might want to specify on every event that you meet in the steelbeasts.com TeamSpeak server. Adding these components to every event posting may get your more attendees as there are less barriers to figuring out when and where your events are happening. It took me a bit of sleuthing to figure out when and where exactly you guys met, so I am speaking from experience that the above information would be helpful. FWIW.

12Alfa, can you please verify the time and TS location of the Wednesday training session for Sept. 21? I want to ensure I communicate it clearly to others who may attend. Thanks!

Hi 12Alfa, Gusy and I will attend with the potential for another person or two to tag along. The opportunity for some training is greatly welcomed! Where should we meet and what time? I am assuming the SteelBeasts TS at 9:00pm EST, but please let me know if that is wrong.

In a recent game, I reversed my MBT (an M1A1) to escape an HE barrage. Unfortunately, there was a tree approximately 25 meters directly behind my tank and I rammed into it at full reverse speed. This action killed both my loader and my driver, leaving the tank immobilized. I have never been in a tank before, but I would assume that the crew in a 60 ton tank would barely feel the impact of a tree, let alone get killed by the impact at less than 60kph. I always imagined tanks smashing through trees and buildings as if they were not there, primarily being concerned about getting stuck in a basement rather than the impact hurting the crew. But again, I have no real world experience in this arena :-) Is this a realistic concern for tankers? Thanks!

Nice, thanks! I must have looked at 20+ M1A1 pictures and not once did I see that hole under the coax.

The M1A1 has two sights, the primary GPS and the auxiliary GAS. The GPS is the "doghouse" sight on top of the turret, easily visible on most M1A1 pictures. But the GAS is a telescope sight situated along the barrel somewhere and I have not been able to see it in game or on M1A1 pictures on the interweb. Can someone point out where the GAS is physically located? Thanks!

Romeo 14's perspective running recon on the east side:

I do not have a lot of experience with Russian equipment and I am wondering which Russian tanks/IFVs - in Steel Beasts - have thermal sights? For the Russian vehicles which do not have thermals but which have infrared sights, does regular smoke (i.e. not multi-spectral) effectively block these sights from working in the game? Thanks!

I recently experienced the same issues with Windows Updates on a fresh Windows 7 install. Windows Update was not seeming to download or install updates, at least not in a timely fashion. N.B. I turn automatic Windows Updates off after a past experience where it tried to rape my computer with a guerilla Windows 10 upgrade that I did NOT want. I solved my issue by following this post: http://www.infoworld.com/article/3058260/microsoft-windows/heres-how-to-significantly-speed-up-windows-7-scans-for-updates.html; after that, SB and the 4.004 update worked fine. In a nutshell: "Install a COMBINATION of the following updates on Win7 SP1 -- KB3138612 AND KB3145739. I found out that patching KB3145739 alone without patching the WU Client for Win7 SP1 is not enough." Manually downloading and installing KB3138612 and KB3145739 unclogged Windows 7 Updates and allowed my system to receive all of its patches. It wasn't lightning fast after the update (there are over 1GB of patches), but at least I now receive the updates from MS. I hope this helps!

I agree. Once I get a thermal contact, I normally switch to daylight scope immediately as more often then not I can make out the vehicle better that way. It also lets me know if the vehicle is behind a smokescreen. I also heavily rely on the daysight to verify when enemy vehicles are down; that's harder to do through thermals as the smoke does not show up as clearly.

In the M1A1, this does not appear to be the case. I'll verify tonight, but I recall trying this from the gunner's position and Backspace not switching to battlesight range.

How do you clear a joystick button assignment from the Controls page? I am using a Warthog Thrustmaster and my preference is to use a TARGET script that emulates key presses rather than assign the DirectX button inputs through the Controls page. I would prefer that the DirectX button assignments are removed from my controls profile to keep it clean, but I can't seem to get rid of the joystick button assignments. I ended up assigning legacy joystick buttons to an unused button on my stick but would prefer something cleaner. Thanks!

Based on your explanation, when you use the LRF and get the flashing zeros, the ballistic computer may NOT have a reasonable value entered into the ballistic computer? So in the M1, flashing zeros may NOT represent 1200 meters (default battlesight range) and it is up to you, as commander or gunner, to get a reasonable number into the ballistic computer in this instance. For a single crewed vehicle, if I am the gunner and I get flashing zeros and I notice it, I would quickly jump to the commander with F7, hit Backspace for battlesight, hit F6 to go back to the gunner, and F2 to resume firing. The flashing zeros will now be replaced with 1200 and I can rely on that number instead of the variable number that might be in the ballistic computer from the bad return on the last LRF. Have I interpreted this correctly? Thanks!

I actually reported two issues: the map freezing up in multiplay; and a CTD when trying to rejoin multiplay. A) the map freezing up in multiplay This issue occurred in-game when running a scenario. I clicked on an infantry unit waypoint and right clicked to change it. The mouse pointer turned into a crosshair and I could not complete my action. While the mouse still moved, the map would not scroll and the interface was unresponsive for 15 minutes. The DMP files shared were not generated by this issue. B) CTD when trying to rejoin multiplay This crash occurred at the end of the countdown when rejoining multiplay. The scenario loaded and the map loaded. But when the countdown reached zero to resume multiplay, my system CTD'd while the other players resumed without issue. The DMP files are for two of these attempts to rejoin, each which resulted in a CTD. To replicate, run a network session game, add some warfighting graphics, play for a bit, and then pause and allow a join-in-progress. They will be able to join but their game will CTD when the countdown reaches zero; the original players will be able to continue without issue. In the future, if my friends or I experience this again, we will run the debugging version of SB so that you have more information to work from.

As an update, a friend experienced the same issue as I had in multiplayer this evening. We were halfway through an online mission and a fourth player showed up. We paused, allowed the player to connect, and resumed. He was able to load in and received the final countdown to unpause and resume the game. When the countdown finished, he CTD'd while the other players resumed. This happened twice. The mission was small, but the map had a number of warfighting graphics on it from the initial planning session. We ended up quitting our in-progress game and restarted with the fourth player joining at the beginning and everything was fine. So it seems like there might be some problems with the join-in-progress function in 4.0.0.4 under certain circumstances. Perhaps it's related to synching the custom map graphics? Or maybe it is something else? I hope this extra information helps!

Hi Ssnake, the crash dumps have been sent to you. Thanks for the speedy reply!