Holland 1st MRB

Done.

Happy Birthday!

Check the launch options in Steam (Right click DOD:S, click properties, then Launch Options). Make sure it is empty (with the exception for the -novid command that stops the Valve intro, if you want it). Specifically, the -autoconfig command would override any settings in the config.cfg file.

Done.

This is... Amazing. Forget being a kid, I want one right now.

SSgt. J. Candy: "You should get a laser sight for that knife." GySgt L. Barry: "They don't have those yet, but you can get a bipod." A bipod knife?

Ticket set to closed. Feel free to post a new ticket if any further problems come up.

Ticket set to closed. Feel free to post a new ticket if any further problems come up.

Happy Birthday!

Firstly, thank you for taking the time to post a lengthy demo on the individual. It is always appreciated. I apologize for the time it has taken to respond to your request. I personally found the demo to be inconclusive as to wall hacking. I noticed many points in the demo where he should have seen an enemy/was surprised/went out from around a corner at an inopportune time. Tick 1600: Sees an enemy run into a room, chases after the enemy unaware that a team mate has already killed the enemy. Tick 2200: Primes a rifle grenade to throw it onto the bridge, rounds the corner to end up face-to-face with an enemy that was waiting for someone to do just that. Tick 5000: Primes another rifle grenade and throws it onto allied street. Nobody is there to kill. Tick 6000: He picks up a sniper and starts peeking allied street. You see him peek out, not seeing the enemy crouched behind the sandbag, but does a double-take as he notices some movement from that location. Tick 9000: Peeks the corner again with the sniper, still not seeing the individuals at the end of the street. The enemy sniper shoots but only wounds him, bringing dirtybirds attention to where the enemy is positioned. Tick 11000: Axis side of wheel-house. There is an allied player on the stairs, whom dirtybirds is distracted with, while another allied player runs up to him from the ground floor. Doesn't seem to notice him until he is fully in his view. Unfortunately, the demo crashes at approx. the 5:30 minute mark. His reaction time was fairly average when an enemy rounded a corner in front of him. He didn't seem to be tracing people through walls. He was surprised, or seemingly unaware of enemy positions on almost every case. He repeatedly took actions that someone aware of the enemy in terms of wall-hacking would (logically) never take. My conclusion is that dirtybirds is not wall-hacking in this demo. That being said, again I do thank you for taking the time to take a lengthy (20 mins) demo of him, and posting it with the proper format on our forums. It is really good to see regular public players taking it upon themselves to try and improve our server, and police it from potential trouble-makers. Keep it up! CWO. N. Holland

This request seems to have been lost in the listing. It's been taken care of.

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.

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.

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.

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

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)

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.

Done.

In the 1st MRB, we pride ourselves with providing a neutral and mature server for people to play on Day of Defeat: Source. We do not appreciate immaturity, and do not tolerate disrespect to our members or offensive comments to other players in our server. We allow swearing in our servers, however remarks as to an individuals race, religion, or sexuality are not tolerated. That is disrespect. You have been banned as per request for three days. I suggest you take that time to make an attitude adjustment, and come back with a more mature frame of mind. In the future (and I expect we won't be having any further issues), the appropriate unban request form can be found here. It is a pinned topic under the "Military Police" section of the forums. See you in three days. CWO. N. Holland

Problem fixed, topic resolved.

Right click his link and press "save link as". Then place it in your cfg folder.

Ping masking is not normally a ban offence in our public server. The individual may be kicked for ping masking (or banned if it is causing a repeated issue).

Banned for 1 month.

Banned for 1 week.

Perhaps I am missing some important information, but America the Beautiful is not the national anthem. A patriotic song, sure. But not the anthem. It's somewhat concerning that some people have referred to it as such.