Holland 1st MRB

Please refer to this post. The problems may be related. If there are any further questions, feel free to post them here or in the other topic.

Did Magoo's solution help?

I've spoken to Arsenault this morning. His crashing problem has been resolved by removing his custom folder. Completely. This tells me what I had been suspecting earlier in this post, that it is in-fact, a result of an incompatibility in custom content. I would suspect it is from using modifications that are at least partially incompatible with the infamous Steampipe update. To those of you still having this annoying issue, go into your DOD:S folder, and delete your custom folder (backing up anything you want to save to a different location). From there, you can recreate an empty custom folder and add in content that is known to be working on the current game build. Please post back if this has worked, or if not, any information that can be given would help us further.

Despite mountains of suggestions, no resolution has worked for the original poster as of yet. If you have recently started encountering this issue, you may start from the top of the list if you wish, though I cannot guarantee it won't be a complete waste of your time. The following suggestions have been attempted, and may be re-attempted at your own will. -Restart your computer --Ensure all drivers are up to date on your computer, and that you have the latest version of DirectX installed. (Drivers can be updated from the device manager, or manually if you know what the internal components of your computer are.) ---Completely remove any and all custom content from DOD:S, including HUDS, configs, skins, etc. These may be backed up outside of Steam's file system if you do not want to re-download them later. ----Verify game cache (Right click on the game in your Steam library -> Properties -> Local Files -> Verify integrity of game cache) -----Deleting all files inside the main steam folder, except for the Steamapps folder, Steam.exe, and the UserData folder. Run Steam.exe after deleting all other files to re-download a (relatively) clean copy of Steam. ------Open up the command line of DOD:S (Right click on DOD:S in the Steam library -> Properties - > Launch Options) and type "-autoconfig" without quotes into the box that comes up. Click OK and run DOD:S. Should this not work for you, you should remove the -autoconfig command from the launch options. -------Uninstall any and all Source Engine games from your computer, including DOD:S, then re-download DOD:S only. --------Nuke the lot. See two posts above.

Happy to hear it has been resolved. If you have any further problems, feel free to post them here, and we will do our best to assist you further.

Hello Lead Farmer, To start off, it is a good idea to restart Steam when this problem comes up. Close Steam down completely, and make sure it is not running in the background by checking the system tray (Bottom left of the screen by default) to make sure there is no Steam icon present. Once you have restarted Steam, try to play again. If the issue comes back up, please post back here and I will continue to assist you.

Happy to hear your issue was resolved. If anything further comes up, feel free to post back here and we will do our best to assist you further.

At this point, I am inclined to believe (by elimination of all other ideas) that this issue is related to shared files between source engine games on your local machine. The unfortunate part is, I have no idea, and no way to find out exactly which file that is. And so to pull the advice of Cutts from another topic;

What is the current situation with this ticket? Is your spray still failing to load properly?

Any updates on this ticket? Is it still an issue? Please post back, informing us of the current situation, and we will do our best to assist you further.

Is there any news about this ticket? Is it still an issue? Keep in mind, there are two different keys for taking screenshots. One is set via Steam options, and the other is in-game. The default for a screenshot via Steam is F12.

Is this still an issue? If so, are there any updates, or changes in the symptoms since this was posted?

Is any further assistance required with this ticket? Was your build successful?

Small and I have gone through the following; Verified game cache Steam refresh (Deleting all files other than steamapps, steam.exe) (Includes clientregistry.blob) Changed download regions Ensured steam settings related to downloads were correctly configured. Small even went as far as to completely reinstall the game between yesterday and today. None of the above resolved the issue.

Only the pistol mod seems to be out. Admin and medic are working fine. The CStaff is already aware of the problem, and are sorting it out. Just be patient.

Well, happy to hear it has been resolved. If any further problems come up, feel free to post again. We would be happy to assist you further.

The config_default.cfg stores default bind settings for the game. These are not loaded unless the config.cfg file is missing. If you feel it necessary to change your binds via the .cfg file directly, you should only be making changes to the config.cfg, not the config_default.cfg file. Should the config.cfg file be missing, it will automatically be recreated using information contained within the config_default.cfg. Or at least, that is the way it is supposed to work. I am assuming this was just a typo, though your config.cfg and config_default.cfg files should be located in the \steam\steamapps\common\Day of Defeat Source\dod\cfg folder. The first thing I would suggest to you, is to delete both your config.cfg and config_default.cfg files, then start DOD:S. If you have any custom binds that you do not want deleted, back up both files to another location (desktop for example) before you delete them. After the game is loaded, close it, or minimize it, and go back to your dod\cfg folder. Open up the config.cfg file and check the default bindings. As for the screenshots, the bind is set within Steam itself, and is not associated with the game. F5 is the steam default for a screenshot. This key can be changed by clicking on the "Steam" drop-down at the top left of the main Steam window and selecting "Settings". From there, select the "In-Game" tab. From there you can set your screenshot shortcut key.

Didn't even blink. *Pats self on back*

Happy Birthday!

Ticket closed. If you have any further problems or questions, do not hesitate to post them. We would be happy to assist you to the best of our ability.

Ticket closed. If you have any further problems or questions, do not hesitate to post them. We would be happy to assist you to the best of our ability.

Happy to hear it! What this tells us is that there is a problem with your settings somewhere down the line. From here, you can decide whether or not you want to stick with the current settings, or move your settings to wherever you would like them to be. It would be a good idea to change the settings individually, so that if one setting is causing a problem, we will know what specifically is causing the problem. Note, that while you have that command in the launch options, the game ignores all autoconfig files you have (like dillons configuration). In order to use these files again, you will have to remove the command from your launch options.

Okay not sure if things were moved around on the last update, but I'm not finding anything for launch options? *edit* - nvm found it was looking in the DoD:s folder on my computer and not in the Steam Library, added the autoconfig, will see if it helps and advise. My apologies, I should have been clearer as to where I meant. Please let me know if it makes any difference.

Since an update that occurred months ago, the Source SDK tool had ceased working properly. This prevented anybody from working on maps, and some other custom content related to Source Engine games (like DOD:S or CS:S). Valve has acknowledged the problem, and put forward information that may interest you, if you are an active Source SDK user. Look here; http://forums.steampowered.com/forums/show...d.php?t=3119389 https://developer.valvesoftware.com/wiki/SDK_Installation

We are still working on this issue, though have yet to come up with some probably causes. Since Mottola claims to have completely reinstalled DOD:S, I'm not sure the problem is part of DOD:S itself. I would suggest the following; Close steam if you currently have it running. Go to your main steam folder (For example, Program files\Steam\), and delete all the files within the main steam folder with the exception for Steam.exe, the SteamApps folder, and the userdata folder. Run Steam.exe, allowing it to update fully.