So, I decided to come back to BEAT after a bit of a break, but something was wrong. While the game background was properly filling the screen, the other assets (everything from the main menu options down to the "loading..." animation) were completely off-center. While I could interact with menu options, gameplay was completely off-center and unplayable, and the options menu was jumbled and unresponsive. I couldn't change resolution and changing fullscreen wouldn't stick. But thanks to a thread here, I found how to access the .cfg for the game and manually change options and thought I'd open a thread with a general guide for the .cfg file.

Before I start, if anyone has any relevant insight (other OS .cfg locations, hidden variables, etc.) please post them here and I will edit accordingly.

Locating the .cfg File
Windows Vista/7: C:\Users\<username>\AppData\local\BIT.TRIP BEAT\beat.cfg

The .cfg is a plain text file that can be edited with any word processor, though Notepad or equivalent works just fine; each line corresponds with an option or function in-game. Inside will be a block as follows:

Fullscreen = yes
Resolution = 1920x1080x32 @ 30Hz
WindowSize = 1600x900
VSync = yes
MouseSpeed = 1.000
MouseSensitivity = 10
EnableKeyboard = no
KeyboardSensitivity = 5
EnableGamepad = yes
GamepadSensitivity = 5
EnableVibration = yes

Fullscreen: Accepted variables = yes, no
This line tells the game whether or not to run in fullscreen mode. If changing fullscreen mode in-game either does not toggle fullscreen, or the change does not save to your next session, you can change it here to ensure the change sticks.

Resolution: Accepted variables = vert.xhor.xdepth @ refresh (example: 1920x1080x32 @ 30Hz)
This line tells the game what resolution, depth and refresh rate to use in fullscreen mode. If your screen seeems misaligned or jumbled, or if changing resolution in game won't work, you can adjust it here. Unless you want to mess around with a custom resolution, set the value to your native resolution, depth and refresh rate, If you do not know your depth and refresh rate, you are likely running default values of x32 and @60Hz respectively.

WindowSize: Accepted variables = vert.xhor. (example: 1600x900)
This line tells the game what resolution to use in windowed mode. If your window is larger than your screen, causing play field or window controls to be off-screen, and changes made in-game will not stick or cannot be changed, set this line to a resolution smaller than your native resolution.

VSync: Accepted variables = yes, no
This line tells the game whether or not to wait for vertical sync while in fullscreen mode. If changing VSync in game will not stick, you can change it here.
NOTE: This game seems to run its best with VSync off. If you notice a lot of stuttering in-game, try turning VSync off to see if it improves.

MouseSpeed: Accepted variables = x.xxx (example: 1.000)
This value seems to multiply the movement speed of your mouse, allowing fine tuning of the mouse to give speeds over or under the set sensitivity level. As opposed to MouseSensitivity, this option changes cursor speed in menus as well. There is no in-game option for this, so it can only be adjusted here. If game control response does not feel right to you, yet changes to mouse sensitivity do not quite get you where you need to go, set your mouse sensitivity to the closest comfortable value you can find, then make adjustments here.

MouseSensitivity, KeyboardSensitivity and GamepadSensitivity: Accepted variables = 1 - 10 (example: 5)
These lines control the game sensitivity of the corresponding device (if active). The higher the value, the faster the paddle will move in-game when receiving commands from that device.

EnableKeyboard and EnableGamepad: Accepted variables = yes, no
These lines enable keyboard and gamepad control in-game. Having one active will not disable mouse control, nor will having both active cause control conflicts with each other.

EnableVibration: Accepted variables = yes, no
This line controls gamepad vibration. It should be noted that, while this option can be freely changed, it will only function if EnableGamepad is set to yes (whether or not the gamepad is actually used).

To help me keep track of feedback, rather than using the horriblly unsorted comment system, consider dropping by my group for my guides: Azure Fang's Guides and Workshop! Permissions are set so that you DO NOT need to join the group to post to the forums.

Comments here will still be read when possible, but may be missed. Threads in the forums in the group will never be missed.