Leaderboard

I always wanted to have a more gunner controller like input device. Having spend some time on the "real" simulator again over the past 2 years, I now decided it's time to something done. For the moment I have finished my POC phase and am on the way of building the first prototype. So from the Hardware side im using: torsion spring loaded mechanism that I ripped out of a sim racing steering wheel for X rotation (left right) torsion or dual spring mechanim on a shaft for Y rotation (up down) for a maybe future V2 version already sourcing parts to replace the spring mechanism DC motors, basically a constant force feedback version Android 10" tablet gyrosensor for the positioning, and touchscreen for button and keyboard inputs Not decided yet might add some real physical buttons to the handles, but would require the device to be wired On the software side: Freepie apk for Android to send gyro sensor data to the PC (the way any racing game on a mobile works, rotate device for steering, tilt for acceleration) Opentrack with freepie input and vjoy output to receive the sensor data and translate to axis movement of the vJoy virtual device SpaceDesk Server Client to convert the Android device into a secondary PC monitor Helios (mainly used in flight sim to build virtual cockpits on touch devices) to be run on the tablet and providing virtual buttons and switches. Physical buttons might be added during prototyping Joystick Gremlin to map everything together onto a single virtual HID device that is then used in SB as controller The POC testing with my phone as gyro sensor went better as expected. It feels just more natural and even without dialing in response curves fits my liking more than the joystick and/or gamepads that I have tested/used so far. Will post more progress once mor of the 3D printing is done

I'm noticing either a problem or misunderstanding with the 'Enter Battlesight Range' TC function. The same thing happens on all the MBTs I've tried. I hit the key and the battlesight range 1200m is entered into the FCS, but the gunner always lases and generates a new range before firing. My understanding is that battlesight is a quick engagement with the gunner firing without lazing. I'm using the 'battlesight' key only and not issuing a separate 'fire' command. Something seems odd. What is the correct sequence? Anyone else? :c:

Prototype works, but resolution with the way to map gyro data to vjoy axis is nah ... at best 6 bit is usable with some curve fine tunings but not to my liking. Back to drawing board now I think I go the full way with DC motors and constant force feedback and use the wireless screen only for Helios and create input profiles https://youtu.be/apYyVN_W9Ro?si=wMGdNNaS5EDkKVtB

I build everything, here is an image of my latest build plus some of my stash. Tanks Andy "Tankleader" Elesky

Another great session. Well worth getting up at 0430 for here. Next week it gets even better with a 0330 kick off.

Fixed.

I wish.

The balance of scenarios is constantly shifting. With every new version, AI routines get modified, armor and ammo parameters get reassessed - and things might no longer work as intended. The Mission Editor is part of the Steel Beasts Experience. We want people to use it, and modifying an existing scenario is a very good way to learn how to use the editor. Scenarios aren't monolithic miracles dropped from the heavens that must not be touched by mere mortals. They are more like play-doh sculptures that you can transmogrify into something new, possibly for the enjoyment of others. Preserve the credits, though.

The Skif kit of the T64 isnt bad for its age. I have a couple somewhere, including one with the accurate armour turret to get rid of some of the imperfections. But it really didnt need it. If you are building the tracks, and are frustrated they dont have holes in all the tracks, i found a hole punch, followed with slowly drilling them out with a hand drill worked very well. T72M1 from tamiya is still very good. As is the Chally 1. Anyone got any recommendations on a decent T62? The only one ive ever built was the Tamiya one, which had massive issues.. Understandable perhaps, in that it dated from the early 70's. Get the skills together and when you can afford it, invest in an RC tank, of which there are a lot on the market. If you figure out the airbrushing, it pays dividends later.

Battle sight for M68 was given as 1600 for sabo, 1100 for HEAT. Was not told there was a change when starting to work with APFSDS rounds so I always assumed it was the same.

The thing with battle sight is you have somehow found yourself at a range where an exact measurement of the range is unnecessary as the round you fire will hit the target anyway. At least in the estimation of your TC. And firing those few tenths, or hundredths, of a second faster because you don't lase may mean the difference between your vehicle surviving or your mission succeeding.

That is correct. Only the TC can enter battlesight range into the FCS in the M1. In the Leo2s, the gunner can do it. (Well, the M1 gunner can enter battlesight range using the manual range function in the FCS, but that kinda defeats the point with battlesight engagements.)

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.

Yeah, that confirms what I was saying. Which is unfortunate. Too much to ask for in an update?