Holland 1st MRB

Ticket closed. You are welcome to post another ticket if the problem persists, however this ticket appears to be dead.

Do you have any mods enabled that edit fire, textures, landscape, etc? Make a clean save before the glitch happens (Escape, save, save game. NOT quick save), and disable the mods. Load up the game again from that save and see if there is any difference. If the problem is fixed, re-enable the mods one by one. If you do have such mods, have you installed them correctly? If you downloaded mods outside of the Steam Workshop, many mods require an external mod manager as opposed to the one found in Skyrim. Many others also require the SKSE (Skyrim Script Extender) to function properly. If one of your mods requires this, the problem should have disappeared upon disabling of the troublesome mod. This happens every single time? What if you restart the game? Do you use the HD texture pack? Have you attempted to lower your graphics settings? I will do my best to help you, though Skyrim is riddled with odd glitches that have little in the way of solutions, other than the hopes Bethesda patches them at some point.

Are there any error messages after the crash? Any strange behavior at all?

Generally, when Steam starts acting up, the first step is to restart the program (Steam). If you do not restart your computer often, restart it now. Check if anything works afterwards.

Happy to hear the problem was resolved.

http://dayzmod.com/

The disconnect issue is due to the recent update. We all have the problem. Try dropping your current primary weapon before picking up a new one. As for the mic, the first step is to make sure you have set it up properly. To do this, first go into the start menu, and click "Control panel". From there, click "speech recognition", and "set up microphone". Follow the steps provided. After that, recheck both your ventrilo and DOD:S mic settings. Make sure your microphone is set to a reasonable volume, if you have an adjustment on the device. Lastly, your transmit level may need to be altered both in ventrilo, and in DOD:S.

The last time I had heard of this problem coming up, it was a result of a source engine update. Surprise, surprise. When it happened before, you could avoid the crash if you switch teams without going to spectate first, though you will end up taking a death as a result.

Closed as requested. Please post another ticket with any further issues.

Closed as requested. Please post another ticket with any further issues.

Looks great guys! Keep up the amazing work!

Happy birthday Parker.

Happy birthday.

Do you still need assistance with this ticket? If so, please respond with any further information you may have, so as we might be able to resolve the issue for you.

Do you still need assistance with this ticket? If so, please respond with any further information you may have, so as we might be able to resolve the issue for you.

Happy Birthday!

Step one is to restart your computer. Too many people leave their computers on 24/7, for whatever reason. Re install DODS. Test it. If it does not work, close Day of Defeat Source via the task manager (hl2.exe, if I remember correctly). Update all drivers, including DirectX, Visual C++, etc. Test DODS. If it does not work, close Day of Defeat Source via the task manager. Close Steam if you haven't already. Navigate to your steam folder via My Computer, and rename the clientregistry.blob to something like "clientregistryOld.blob". Restart steam, and test DODS. Verify your game cache (right click the game in the library, click properties, then local files, then "verify game cache". Test DODS. Open the launch options (right click in library, click properties, then launch options) and type "-autoexec" (Without quotes). Test DODS. Note; this should reset all client-side settings to those found in the autoexec file in your DODS folder.

I had muted him twice a few days ago for repeatedly arguing with admins over any issue that came up in the server.

STEAM_0:0:5897221 For completion of the form.

Though the intention was good, the thought is rediculous. There is little to legally be done, unless you have a significant amount of free time and money to persue it. Unless personal information has been taken, considering it was an action against an individual and not a group, likely without bias, it is generally classified as vandalism. Furthermore, I highly doubt this community wants to get involved with the discussion of or distribution of milacious software. If that is the kind of topic that interests you, there are countless well-equiped communities elsewhere that can help you. Very sorry to hear what has happened, it is certainly a violation of your privacy. Perhaps a discussion of retaliation is better debated via vent or steam.

Happy Birthday!

Topic closed. Feel free to post another ticket if any further problems come up.

Topic closed. Feel free to post another ticket if any further problems come up.

Topic closed. Feel free to post another ticket if any further problems come up.

Happy birthday!