Resolved - Something wrong in DoDs

[C. Wilson 1st MRB]

Name: Casper Wilson

Rank: Corporal

Type of issue: Not sure

Brief Description of Issue: On picture 1 you can't see the door. Then on picture 2 you can see the door if you move a little closer. On picture 3 you can't see the tree but then on picture 4 you can if you move a little closer. I have tried all the different settings/verify integrity of game cache files and I even checked out my girlfriends DoDs game/steam account and it's the same error.

I hope there is someone out there that maybe know this kind of problem.

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

Current Status:Resolved

Main Technician: Holland

Supporting Technician: Heresy

Edited March 5, 2014 by Heresy 1st MRB

[Holland 1st MRB]

This is a result of the r_propsmaxdist variable in DOD:S. It sets the maximum distance for props to be drawn on the screen. This is likely modified if you use any configurations (it is not changed in Dillon's config).

However, you can change it manually by typing the following into your console;

r_propsmaxdist value

Where value = the maximum distance you want objects to be drawn. Default value in most source engine games is 1200.

*Warning* setting this value too high may have negative impacts on the performance of your game. Play around with it to find a setting you like, and if there are any issues, revert to the default setting.

[C. Wilson 1st MRB]

Thanks Holland!

But when I type this in my console nothing happens?

[Holland 1st MRB]

Thanks Holland!

But when I type this in my console nothing happens?

There isn't any feedback from inputting the command in the console. I'd suggest typing it in, and then start a map where you notice the issue. (You may have to restart the map whenever you change the value for it to take effect)

[C. Wilson 1st MRB]

I have tried:

r_propsmaxdist value1200

r_propsmaxdist value 1200

r_propsmaxdist 1200

r_propsmaxdist1200

r_propsmaxdist value

And nothing works at all.

Edited February 20, 2014 by C. Wilson 1st MRB

[Holland 1st MRB]

As stated in my earlier post, you were to replace "value" with the number you wanted. 1200 is the default, so setting it to that value will be changing nothing.

A simpler example;

r_propsmaxdist 1500

[C. Wilson 1st MRB]

I typed r_propsmaxdist 1500 and nothing happened and with even r_propsmaxdist 5000 nothing is changed.

[Holland 1st MRB]

I typed r_propsmaxdist 1500 and nothing happened and with even r_propsmaxdist 5000 nothing is changed.

Some maps set their own values to this and similar variables. The next best suggestion I can give you is to adjust the Direct X level your game is running. This can also have an effect on the distance props fade out from.

To change the dx level the game runs in, right click Day of Defeat: Source in your steam library, and click Properties from the drop down box. From there, click "launch options" and input the following;

-dxlevel 9.5

Accept the changes and relaunch the game. This may or may not have any effect, depending on the dx level you already had your game set to (default is 9.0+). Again, having the dx level set at higher levels may have adverse effects on performance for older computers. Setting it to a lower value may introduce graphical errors, and increase the issue you are having.

In the end, the problem you are experiencing is part of the source engine only drawing objects to a certain distance, in order to optimize performance. It's not a bug or glitch with the game or with your computer. That being said, I will continue to look into something to minimize the effects of it.

[C. Wilson 1st MRB]

It did not solve the problem.

How do I change back to the option I used before I typed -dxlevel 9.5? - cuz now the graphic/water details is looking like shit,

By setting it to the default 9.0 you said did not change anything.

Edited February 20, 2014 by C. Wilson 1st MRB

[C. Wilson 1st MRB]

And my laptop uses directX 10 and DODS was set to directX v9.0 in options before I typed in -dxlevel 9.5.

Edited February 20, 2014 by C. Wilson 1st MRB

[Holland 1st MRB]

And my laptop uses directX 10 and I think DODS was set to directX 9.0+ before I typed in -dxlevel 9.5.

I've made a typo on the command. There should not be a "." in the version number. That is likely what is causing the decrease in graphical output.

Should be;

-dxlevel 95

Could even set it higher by using -dxlevel 98

Try that, and see if it is improved.

[C. Wilson 1st MRB]

It works fine/like normal on -dxlevel 98 thanks - But I still have the same problem with things is gone at long distance like in the beginning of this post.

[Holland 1st MRB]

I'm afraid there isn't much more we can do for you. The fade is a variable set into the maps themselves (everyone has it), and it seems the usual workarounds have not provided the desired effect.

I will keep the topic open if anybody else has further suggestions.

[Heresy 1st MRB]

Was it working before and then it stopped working? A last resort you could try if it was working before would be to reinstall the game, that or make sure your configs are all cleared.

[C. Wilson 1st MRB]

Heresy - it suddenly stopped working and I did a full uninstallment of the game last night and deleted everything that has to do with DODS. The weird thing is that all my binds, medic, salute and stuff like that was the same like before. It did not get deleted or changed. How is that possible when I have deleted every DODS folders/game on my laptop?

[Heresy 1st MRB]

It is Valve's cloud sync called SteamPipe, it pulled your configurations back in. You may see if you can clear any configs that you don't know of from your config.cfg file and then mark it as read only to see if there is any affect in game. Make a copy of the file first

[C. Wilson 1st MRB]

Pvt. S. Jones joined the server while I was there and I explained what issues I was having. We then did an experiment and he has the same graphical problem with the things dissapering at distance (trees, flowerpots, windows, doors and so on). It seems like it's some sort of general problem out there that effect some people

[Gearhart 1st MRB]

im not sure if this is an actual command but what is ur cl_detaildist set to if there is one?

researched it and it is default is 1200 not sure what it effects but worth a shot

Edited February 25, 2014 by Gearhart 1st MRB

[C. Wilson 1st MRB]

Gearhart - how do I check that? - because to be honest I have not heard about it before and I don't know how to check things in the console

[Heresy 1st MRB]

You would enter this command via the developer console. If you enter cl_detaildist it should show the current value.

Example from the console:

] cl_detaildist

"cl_detaildist" = "1200"

You can access the console using the tilde key which is the key with the "~". To enable developer console go to Options, Keyboard, Advanced

[C. Wilson 1st MRB]

I typed in "cl_detaildist" and it showed:

"cl_detaildist" = "1200"

- Distance at which detail props are no longer visible

Should I set it higher to solve my problem?

Edited February 25, 2014 by C. Wilson 1st MRB

[Heresy 1st MRB]

No harm in trying to increase it. The worst case is you set it back to the default value.

[C. Wilson 1st MRB]

Me and Gearhart tried it and it did not work at all.

Edited February 25, 2014 by C. Wilson 1st MRB

[Heresy 1st MRB]

This thread is interesting and the post from BullDoser has some good information.

http://forums.steampowered.com/forums/show...d.php?t=1614805

The values that I would try setting to see if it helps. I know you set r_propsmaxdist before but did you try 5000?:

r_propsmaxdist 5000 //Maximum visible distance for props.

cl_detailfade 4000 //Distance across which detail props fade in

cl_detaildist 12000 //Distance at which detail props are no longer visible

cl_phys_props_max 3000 //Count of physical Props

[Heresy 1st MRB]

This thread is interesting and the post from BullDoser has some good information.

http://forums.steampowered.com/forums/show...d.php?t=1614805

The values that I would try setting to see if it helps. I know you set r_propsmaxdist before but did you try 5000?:

r_propsmaxdist 5000 //Maximum visible distance for props.

cl_detailfade 4000 //Distance across which detail props fade in

cl_detaildist 12000 //Distance at which detail props are no longer visible

cl_phys_props_max 3000 //Count of physical Props

I tried these on my system and I still see the effect that was described originally with the tree and the door. I was reading some posts that attribute this to the map itself rather than the configuration of the game or the system running it.

[Heresy 1st MRB]

Still had the same issue after downloading the map again.