Resolved - Weird Lag/black screen/predator style game play

[Gardner2]

Name: K.Gardner

Rank: TSgt.

Type of issue: (Software, Hardware, Steam, Not sure) Steam?

Brief Description of Issue:

I am getting some really weird lag since Panda accidently banned me yesterday. I\'ll lag and one of 5 things happen:

1) screen gitters for a brief moment, then I see dead bodies fall from where ever players were and game continues no problems.

2) everything goes black but I can still see health bar, minimap, chat and the flag captures but the rest of the screen is black lasts for about 3 seconds then starts playing again.

3) it does the black out screen briefly like in #2 but then everybody appears to have become predators and are completely invisible to me till it does a black screen thing again........

4) same as #1 but then the flags at the actual capture points will show the oposite teams colours (example I\'m on axis, axis has control of the flag (capture icons show this), but the flag is allied?). http://cloud-2.steampowered.com/ugc/846952...4FE9A6C6CA338D/

5) same as #1 but the other players are about 10\' from where I see them (tested this one out with Erikson in the pub when it was empty)

I tried taking a demo but can not seem to find the file as the folders have all changed since that last steam update so no clue where it is....

***Medical Supply Staff ONLY Below this line***

Current Status: Resolved

Main Technician:

Supporting Technician: Johnson

[M. Johnson 1st MRB]

Is there any errors in your console whilst playing?

[Gardner2]

just joined and wow there is a wall of errors so yes I am getting errors in cosole, I am not running any scripts/skins/mods or anything I have run a verify game files today as well from Steam, I've copied my console wall of red below:

The server is using sv_pure 0. (Enforcing consistency for select files only)

SOLID_VPHYSICS static prop with no vphysics model! (models/props_crates/tnt_bunch2.mdl)

SOLID_VPHYSICS static prop with no vphysics model! (models/props_crates/tnt_bunch2.mdl)

SOLID_VPHYSICS static prop with no vphysics model! (models/props_crates/tnt_bunch1.mdl)

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : maps/dod_jagd/stone/blendcobbledirt002a_1280_-2032_-368

- Surface center : 2570 1093 -368

Warning: WorldTwoTextureBlend found on a non-displacement surface (material: maps/dod_jagd/stone/blendcobbledirt002a_1280_-2032_-368). This wastes perf for no benefit.

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : maps/dod_jagd/stone/blendcobbledirt002a_2064_64_-288

- Surface center : 2344 -64 -312

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : maps/dod_jagd/stone/blendstonedirt001a_376_-1376_-288

- Surface center : 426 -1290 -352

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : ground/flash_ground_blend

- Surface center : -71 -1234 -296

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : rubble/blend_donner_rubble1_dirtfloor013a

- Surface center : 2312 -328 -272

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : rubble/blend_muddyrubble001

- Surface center : 67 -617 -280

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : stone/blendcobbledirt001a_argentan

- Surface center : 1285 245 -336

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : stone/blendcobbledirt001a_avalanche

- Surface center : 212 -1655 -352

Warning: using WorldTwoTextureBlend on a non-displacement surface.

Support for this will go away soon.

- Material : stone/blendcobbledirt001a_nodetail

- Surface center : -104 -2218 -392

#Game_connected

Error reading weapon data file for: weapon_ifm_steadycam

The "Error reading weapon data file for: weapon_ifm_steadycam" one seems to keep popping up several more times while playing.

[Gardner2]

okay this issue appears to only happen on our pub server, just played several rouns on the private in 2 realisms with zero issues.

[Gardner2]

So far every map on the pub with the exception of Donner.

Still shows: Error reading weapon data file for: weapon_imf_steadycam

when it does it

[Holland 1st MRB]

Try adding -autoconfig into the launch options for the game. (I know, seems to be a bit of a trend lately.)

Right click on DOD:S in your steam library, and press properties. From there, click "Launch options" and input the following into the dialogue box that comes up.

-autoconfig

When you load the game, you will notice that everything has been set to the default settings which DOD:S detects automatically. If your screen resolution has changed to something other than what you normally play with, you can change the setting, however leave all other settings alone.

Play through a few maps on the pub, and see if any problems arise.

[Gardner2]

Try adding -autoconfig into the launch options for the game. (I know, seems to be a bit of a trend lately.)

Right click on DOD:S in your steam library, and press properties. From there, click "Launch options" and input the following into the dialogue box that comes up.

-autoconfig

When you load the game, you will notice that everything has been set to the default settings which DOD:S detects automatically. If your screen resolution has changed to something other than what you normally play with, you can change the setting, however leave all other settings alone.

Play through a few maps on the pub, and see if any problems arise.

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.

[Holland 1st MRB]

Try adding -autoconfig into the launch options for the game. (I know, seems to be a bit of a trend lately.)

Right click on DOD:S in your steam library, and press properties. From there, click "Launch options" and input the following into the dialogue box that comes up.

-autoconfig

When you load the game, you will notice that everything has been set to the default settings which DOD:S detects automatically. If your screen resolution has changed to something other than what you normally play with, you can change the setting, however leave all other settings alone.

Play through a few maps on the pub, and see if any problems arise.

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.

[Gardner2]

So far so good, been online most of the morning alt tab playing while at work, while I've been playing no issues. Looks like that fixed it!

Thanks

[Holland 1st MRB]

So far so good, been online most of the morning alt tab playing while at work, while I've been playing no issues. Looks like that fixed it!

Thanks

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.

[Gardner2]

So far so good, been online most of the morning alt tab playing while at work, while I've been playing no issues. Looks like that fixed it!

Thanks

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.

I have everything at default settings, no other configs/skins running. It was fresh install of DoD:s from my last issue months ago and have not changed anything since, so no clue which settings to change.