GrenadeBoy wrote:cant post a thread in bug reports because i just joined, but whenever i save my game it has an MAV. Saving and Quitting doesnt work either. please help, I dont want to play in keter all the time :(. Also the test.exe thing works without an MAV so its not that.
EDIT: Woah what the fuck how come playing in a resolution less than my native one worked. Thats odd
EDIT2: it also works without fullscreen but seriously, this should be fixed.
EDIT3: Nevermind fullscreen thing doesnt work :(
EDIT4: Sorry for so many edits but WHAT THE FUCK now it crashes whenever i save no matter what resolution
EDIT5: okay sorry again, but I figured out the problem. It is so motherfucking dumb i cant even... When your save file name is too long and you save it kicks you out with an MAV so yeah. Think you should put that in the thread. I dont know what produces an error and what doesnt because for some reason the name "lol test" didnt kick me out but "oh no" did. So Ill try finding out more later
Make sure you do all your testing first before you post a bug. It helps make your report a lot clearer.
Also, what version of SCP are you playing? 1.0.4? Is it a patch, or a full download (downloading the entire new version)? These are a few things to keep in mind when writing reports.
If everything is starting to go wrong, I suggest that you download another copy (not a patch) of the version you are playing, and see if your MAV goes away. I know from experience that changing settings like running as administrator, enabling/disabling bumpmapping, and resolutions can potentially corrupt a save file which may explain your string of edits (1-4). I don't know why, but it happens to me a lot. I once changed settings so much in a single save file that it wouldn't even open (MAV at loading screen) unless I have the settings set exactly to the previous save. I recommend having separate save files for each test that you want to conduct. Ex. one for running as admin, one for running as admin and bumpmapping off, one for a resolution change, etc.
Let me know if your problem persists after you download a new copy of your current version (also let me know what the version is, I'm assuming it's 1.0.4).