Repository navigation
Steelbound 0.2.0 (Beta)
Steelbound 0.2.0 (Beta)
This is the first beta. Thank you to everyone who tested the alphas – almost everything in this release comes from your reports, clips and diagnostic packages. Steelbound is still a work in progress, so please keep telling me what breaks.
Highlights
- AMD graphics cards: white flashes and white areas. This was the big one. Some graphics drivers (AMD among them) handle one Direct3D 11 feature differently, and on those drivers the extra in-between frames above 30 FPS could come out partly or completely white – when closing the hatch, at ignition, on monitor frames. At 120 FPS three out of four frames you see are in-between frames, so it could look like whole screens were white. I could finally reproduce this without an AMD card, and the game now detects it and draws those frames another way.
- White, grey or black textures and missing pictures (#7, #11–#15, #19, #23–#26, #30–#32 and more). The game keeps some of its pictures in a special memory area. On some PCs (very often with AMD cards) parts of that area end up at high memory addresses, and my texture loader wrongly rejected those addresses – so those textures were never loaded: white channel labels in briefings, white weapon pictures, grey letters, missing ground, building and tree textures, white instruments. Your diagnostic packages showed exactly this, and when I force the same memory layout on my PC, I get your pictures – and with the fix they're gone.
- Monitor view (experimental). A new view that shows the main monitor full screen, exactly as it looks inside the cockpit: same light, colour, grain, interference, night vision and HUD, just without the cockpit around it. If you like, the radar and FRONT VIEW appear as small panels. You'll find it in the launcher under Graphics › Cockpit & monitor (Cockpit: Monitor view) or in the Esc menu under Cockpit, and you can switch it while playing. It starts once your VT is online; the startup sequence and a damaged cockpit stay as in the original. Not available in VR.
- White lines while looking around. The long white streaks across the main monitor when you turn were gaps between ground and sea tiles. They are mostly gone (Mission 02: from 60 to 4 in my test run, the city mission from 7 to 2). What my tests still count is mostly real motion like surf, not errors.
- Fire and lights no longer shine through walls (#16). Fire, smoke, explosions, door lamps and VT lights are now hidden behind buildings again, like on the original console.
- Missing help texts and messages are back. After any mission you had played (and after the title demo), the game's own text lines were not shown: the help line under the menus ("Move Out", "Campaign"), the message after Mission 11, the hint before Mission 20 and the troop-choice question. All fixed.
Fixes
Campaign and story
- Ending of the first campaign (#8, #9): the ending text and the credits now play after the final boss, instead of a wireframe picture.
- Cutscene sound playing twice in Mission 10 (#10): I tracked this down to a short stall during the in-mission movie; more work on it is planned.
- Loading freeze (#27, and very likely the Test start crash in Mission 08): a rare hang while loading a mission is fixed. It was much more likely on some systems than on others.
Controls
- Joysticks and HOTAS – new live view and calibration: Controls › Joystick/HOTAS now shows every axis live, and you can calibrate each axis (range, centre, deadzone, invert, "no centre" for throttles). The game uses your calibration.
- "Copy device info" in the same dialog copies your device's name, IDs and the list of axes/buttons the driver reports – no input values. If a device does not work, please paste this into your report.
- Flight sticks that only reacted diagonally (e.g. Hori in Xbox mode): the assign dialog now learns axes from the rest position and refuses to put the same axis on both aim directions. If you assigned the aim axes in alpha.9, please assign them once more.
- Older joysticks with unusual axis IDs (e.g. Logitech Wingman): their stick axes are now read as well, not just the throttle. Tested with simulated devices – feedback from real hardware is very welcome.
- Original controller unplugged and plugged back in: it now works again right away instead of freezing its last state.
- Replays: a replay now ends only with its own key (Backspace by default, bindable). The mouse no longer ends a replay by accident, and the click that brings the window back to the front is ignored.
Display and sound
- Game slowing down in big fights (#29): on some systems (especially AMD cards at 120 FPS, or when another program uses the graphics card at the same time) the whole game could slow down after explosions and fires. The game now keeps its speed steady and skips in-between frames instead. The first appearance of an effect also stalls less, because its shader is now prepared faster.
- Frame rate list matches your monitor: the launcher and the Esc menu only offer frame rates up to your monitor's refresh rate. Rates that don't divide evenly into it are marked "(may judder)". If your saved value is higher than your monitor, it stays and is shown as "(above monitor)".
- One "Original" preset running at your monitor's refresh rate, plus Performance.
- Volume sliders for master, music, effects and voice – in the launcher and in the Esc menu.
Privacy
- Earlier versions wrote a line for every released key into the log file. That was a leftover from a developer tool. The game no longer logs key presses. If you shared logs or diagnostic packages from alpha.9 or earlier, they may contain these lines (key codes and timing only).
Line of Contact (work in progress)
Still locked in the launcher ("Coming soon"). Progress since alpha.9: two copies of the game now play the same mission together and stay in sync, the sound works, and the mission picture has come a long way – terrain up to the horizon, objects like power lines, the full 3D cockpit with its instruments, and the main monitor after the hatch closes. It still runs slowly in the mission, so there is more to do before I unlock it.
How to report problems
Press F11 (or Esc → Feedback), describe what happened and submit the pre-filled GitHub issue. After a crash, use Report on GitHub on the launcher's Play page. Please don't attach game files or saves.
Known issues
- White or missing textures: both causes I found are fixed, but I could not test on a real AMD card. If anything still looks white, grey or black, add the line
tex_missing_mark=1touser.cfgand press F11 on that spot: missing textures then show up in a signal colour, and every F11 report now includes a short texture health section that tells me why. - Thin white lines above 30 FPS: much rarer now, but a few may remain in fast turns. 30 (original) is always clean. If you still find a spot with clear white lines, an F9 clip helps me most.
- HD texture packs are experimental: if something looks wrong, press Shift+F8 to compare with the original look.
- USA version: experimental, so expect differences from the European version.
- Joysticks/HOTAS: the new axis handling was tested with simulated devices only.
- VR, replays from the launcher and video export are experimental.