Shadowgrounds by Frozenbyte - English retail v1.04 patch
The patch features some minor fixes within the game and some additional features. The patch also prepares the game to support the upcoming downloadable Level Editor, which will be available next week. Below is a list of some of the fixes and added features.
Changelog:
Version 1.04:
FIXES:
* Major crash bug related to fonts fixed (this affected PDAs, weapon upgrade menu and some others)
* Minor text fixes throughout the English version
* One Mission 12 conversation bug fixed
FEATURES:
* Keyboard-only aiming possibility added (no mouse required)
* Windowed mode now with titlebar (movable window)
* Unofficial support for more keyboard buttons
* Error reporting (see below!)
Version 1.02 UK:
FIXES:
* Many collisions fixed in the missions, the player should no longer be able to get to the "edge of the world" in any mission
* New sound drivers might help with some sound issues
* Creating a new player profile name now caps at 19 characters so the text string no longer goes out of screen
* Bugs related to Profiles fixed
Version 1.01:
FIXES:
* Mission 4: ISERCom; Some people have experienced problems like getting stuck in the corridor fight in the middle of Mission 4. After this patch this should be fixed (the doors should open automatically after x minutes).
* Mission 7: Provectus; in co-op, after this patch the players should be able to continue the game if they die during the Provectus reactor fixing.
* GeForce 6600GT; some graphics bugs fixed (new NVIDIA drivers fix a lot of bugs too)
* Minor text fixes throughout the game
* Slightly modified font (better comma etc)
FEATURES:
* After completing the game on "Hard" difficulty, a new difficulty setting "Very Hard" becomes available.
* After completing the game on "Very Hard" difficulty, the ultimate difficulty setting becomes available: "Impossible".
* "Reset After Load" added to Shadowgrounds Launcher; if the game crashes when you press "START" in the Loading Menu, disabling this feature may help on some graphics cards.
EXPLANATIONS
More up-to-date information can be found at the official website, at
http://www.shadowgroundsgame.com/new/index.php?page=troubleshooting
PATCH 1.04:
* Error reporting
This version includes error reporting. What this means is that the computer creates a "dump" file of the errors, and you can send this to Frozenbyte, the developers. The dump is located at:
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson
Check the user.dmp file and make sure it was created around the time of the crash.
Take the user.dmp and send it to
[email protected] with a subject line "Shadowgrounds user dump" or something like that. Also please describe what happened in as much detail as you can. Thanks.
If the user.dmp isn't found in that directory, you can search for *.dmp on your Windows partition.
* Keyboard-only aiming possibility added (no mouse required)
the following enables the keyboard only mode for player 1
(first, deactives mouse cursor, then sets the control aiming scheme to keyboard, and finally unbind any previous
controls bound to alt, then rebinding it to a special keyboard aim scheme strafe)
/1st_player_has_cursor 0
/1st_player_control_scheme 12
unbind alt
bind camera_unit_align_lock_toggle,alt
* Windowed mode now with titlebar (movable window)
(has some known bugs)
/windowed 1
/maximize_window 0
/window_titlebar 1
* Unofficial support for more keyboard buttons
Shadowgrounds allows only certain keyboard buttons to be mapped as controls.
However, some people might want to use buttons that are not supported initially. Such could be the left and right brackets on the US keyboard (located next to the P letter).
This is possible but it requires that you manually edit the keybinds.txt which is located in Profiles\yourprofile\Config\ directory. Please take a backup copy of this file before you edit it.
Now, you should see lines of text with a keyboard button next to it, such as:
attack = button-1
Before you can map your desired button to the file, you need to know the correct number for it. This might be hard to obtain, because it's only included in the DirectX Input key codes names, and doesn't seem to be readily available on the Internet. The best way is to experiment or get in touch via the Feedback Form. The key codes are related to their position on the keyboard.
In the case of the left and right brackets, their numbers are #26 and #27, respectively. So if you want the left bracket to shoot the primary fire, you would write:
attack = #26
That should work.
