Here we will maintain a list of bugs, reported by players, that we are working on correcting.

- Launcher crashes but running the game correctly works fine.- Memory leak. After several continuous hours of playing the campaign, the game may stutter and eventually crash.- DirectInput devices are not detected if they do not register as a simple Joystick (Microsoft GamePad works fine, as it is read through XInput).- Steam records achievements but does not display them on the community page.

I've noticed when renaming customized loadouts and such that the custom name freezes the client. Not really sure how to explain it but when you try to rename something after typing a few letters in the game won't let you click on anything or type anything. You have to press escape to go back to actually do anything. This is a multiplayer specific thing so far as I haven't checked this with saved games. I think your custom name is saved when you hit escape it just doesn't let you complete the name all the way.

That shotgun like weapon? You shoot at a specified area and then you scan where ever you shoot. The red shards you shot will turn into a red looking rift that pulls things towards it including yourself if you're close enough.

I'm suffering a pretty bad control glitch, where resetting to default controls doesn't actually set those controls, it only looks like it sets them. The old controls still apply, but I can't un-set them unless I reapply what the control was and take it off again...

I mentioned this in another post along with another user, but in the 2nd level where you encounter your first puzzle with the yellow door, scanning the door does not cause it to open. Loading the most recent autosave before that section seems to correct the issue, but I thought I would mention it here.

I changed graphical settings from windowed to fullscreen (thank you!). After quitting normally, the application refused to shot diwn - I had to go into the task manager to kill the process.

The game now crashes once launched from the launcher. Same effect when launching directly outside of the launcher.

-- EDIT: Problem is not solved by rebooting.-- EDIT: Tried verifying files from Steam. Verification concluded successfully. Restarting Retrovirus from Steam brought up a .NET repair and maintenance utility, which concluded successfully. Game still crashes after attempting to acquire fullscreen.

Could you post your hardware specs, especially video card and if you have multiple monitors? By the way, a good way to recover from settings that crash is to go to the save folder (button in launcher), and up one folder there is a Graphics.ini file. Either delete it or change the WindowMode line to "WindowMode = Borderless". In our testing, using your native resolution for full-screen was the most stable, and you can drop sampling if you need better performance.

Could you post your hardware specs, especially video card and if you have multiple monitors? By the way, a good way to recover from settings that crash is to go to the save folder (button in launcher), and up one folder there is a Graphics.ini file. Either delete it or change the WindowMode line to "WindowMode = Borderless". In our testing, using your native resolution for full-screen was the most stable, and you can drop sampling if you need better performance.

Will do so and let you know, thanks for the speedy reply! My system is:

Could you post your hardware specs, especially video card and if you have multiple monitors? By the way, a good way to recover from settings that crash is to go to the save folder (button in launcher), and up one folder there is a Graphics.ini file. Either delete it or change the WindowMode line to "WindowMode = Borderless". In our testing, using your native resolution for full-screen was the most stable, and you can drop sampling if you need better performance.

Changing mode back to Borderless Window lets the game proceed normally. It runs at 16fps, so not quite playable, but it works! I can go in and change the game to Borderless manually until a patch deals with this issue. Thanks you!

Fullscreen was just added, so we appreciate you offering information on any issues it introduced. The most helpful reports (if our own bug reporter didn't appear) are from the Windows Event Viewer. The stack from a .NET Runtime error points us right to the problematic code.