Five minutes on Donner...

[Rufio]

[ame]https://youtu.be/rgwIVWvno8o[/ame]

Red wire-frame = client side hit (ideally these would register on the server)

Demo commands:
sv_showhitlocation 1
showimpacts 1

Running a standard config:
cl_interp_ratio 1
cl_interp .033
cl_cmdrate 67
cl_updaterate 67
rate 100000
etc...

 

[crom]

Although theoretically cl_interp 0 will set the lowest possible interpolation automatically given the server settings.

try typing in game (not in the cfg file ):

cl_interp 0.021

see if it improves your reg. Sometimes this works better for me.

 

[Rufio]

Although theoretically cl_interp 0 will set the lowest possible interpolation automatically given the server settings.

try typing in game (not in the cfg file ):

cl_interp 0.021

see if it improves your reg. Sometimes this works better for me.

Dude...i'm telling you...i've been around a long time...this isn't a client-side problem. Especially when I'm getting hits on guys that are static, the interpolation wouldn't matter. A 12 millisecond difference in interpolation would not have prevented 3-5 shots from registering at the end of the video.

 

[crom]

Also in your config file the following lines are not controlled client side anymore and can safely be removed:

cl_cmdrate 67
cl_updaterate 67
rate 100000

I'd try running a clean autoexec with simply:

cl_interp_ratio 1
cl_interp .033
etc...

and see if it improves.

Also can you post a video with net_graph enabled? It would be very helpful to see the network data while video is playing to help troubleshoot.

To be honest if you just type in console; cl_interp 0 everything will be at the best possible settings including lerp which will be 20 ms. The server defaults just about every setting once you log in. Once logged in you can adjust settings though.

 

[MoistTowelette]

Maybe you're just bad Rufio. <3

 

[Rufio]

Also in your config file the following lines are not controlled client side anymore and can safely be removed:

cl_cmdrate 67
cl_updaterate 67
rate 100000

Please try to avoid spreading information that isn't true. Rate can be set as high as 1,048,576. The cl_cmdrate and cl_updaterates can be adjusted to values lower than 66.
[ame]https://www.youtube.com/watch?v=IY4htxq9NB8[/ame]

Try using the garand and I think you will notice what I'm talking about compared to using the heavy.

Use whatever settings you want, pick the garand, record a demo, and send it to me and i'll make a video demonstrating the same issues.

 

[crom]

This is not true at all. I can get my rate to almost 2,000,000 on servers if i set it high enough. Also, most servers will allow you to change your cmd and update rate to lower than 66. Where are you getting this crom! Your info is wack!

Also, try using the garand and you will notice what I'm talking about. You won't notice anything crouched with your BAR.

Use whatever settings you want, pick the garand, record a demo, and send it to me and i'll a video demonstrating the same issues.

Post a video with actual network setting with a netgraph 4 and someone may be able to help. If you do not have network info included debating if it is client or server issue is as good as guessing and no one will be able to respond to your post in a meaningful way.

Also, pointing out what I have tried to tell you; looking at the above screenshot your lerp is 100 which it will always be no matter what you have in your autoexec. The server overwrites all the netcode when you log in and in order to change it you will have to manually input cl_interp 0 (or anything above 0.021 if you prefer) in order to lower your interpolation. This is true with rifles, bars, sniper, mg... The class you play has no effect on these settings.

That I would say is the issue. Hope it helps.

 

[Rufio]

Maybe you're just bad Rufio. <3

duh

 

[Predator Lark]

Please try to avoid spreading information that isn't true. Rate can be set higher than 1,000,000. The cl_cmdrate and cl_updaterates can be adjusted to values lower than 66.
https://www.youtube.com/watch?v=IY4htxq9NB8

Try using the garand and I think you will notice what I'm talking about compared to using the heavy.

Use whatever settings you want, pick the garand, record a demo, and send it to me and i'll a video demonstrating the same issues.

Rufio is Correct in his statement, all of these rates can be changed client side. Yes the server can have limitations on the range for these rates, but to remove them from your config I would not recommend. Also the Update Rate and Command Rate you would want to match the server. Our servers are 67 tick servers, hence why you would want them set to 67 so that you are pushing the most data along with setting the rate as high as you can.(At least in my experience). Example CSGO servers are 64 tick servers for regular matchmaking therefor Update and Command rates are locked in at 64 by the game as lower rates can cause stuttering.

Unfortunately there is only so much you can do client side to improve registration. There is a reason why DODS servers were 100 tick for a long time. Once the game stopped bringing in as much money and less servers were being rented the provider companies went a cheaper route. You could request a 100 tick server but they would charge more and possibly add a fee if they feel the server can not handle the increased information being sent through it and need to upgrade the resources of the server.

The game is old the engine is old the structure of the game is old. The lack of knowledge by most pubs into rates and lerp is growing. We all complain about reg...its not a client side issue. Dods servers aren't what they used to be which were quality...doesn't matter who you rent through they aren't going to put all their resources into a dods server when they have growing games that they can put their high end servers toward.

Personally as much as I complain, I am glad to say that I have 4 home servers to play on...Any eGO server is better than no server...

- Lark

 

[Dr.Compton]

The MG has the worst reg idk why you guys complain, I fire 30 bullets and only two hit you guys! Ridiculous,

 

[crom]

Yes but the way in which you change the settings is what I am trying to explain .

If you set the netcode once logged onto the server you can change the values.

The point I am making is that if you make the changes in your autoexec config file the changes will not go into effect. The server now overwrites all netcode in the autoexec.cfg.

So you have to log on and then, before you select a team, make the changes each time.

The changes will remain in effect even if you switch server maps ie. Donner then Kalt as long as you do not close the client.

But if you try and put your "favorite" netcode settings in your autoexec and think they are executing each time you log on the only thing that will execute are cosmetic client side changes all netcode commands have to be changed everytime you log on unfortunately.

Sorry if that wasn't clear in my posts Lark.

How's it going BTW. Strange winter up here this year!

 

[He@d$hoT]

I thought that was the purpose of making your autoexec read only?

 

[crom]

I thought that was the purpose of making your autoexec read only?

It writes to your config.cfg file and executes the netcode from there.

But once logged in you can make changes in console.

 

[crom]

OK OK many apologies for the misinformation.

I starting thinking about it and remembered I updated many things around the time of the new server including a new autoexec.cfg. I check it and it was not a true cfg file anymore but a txt.

So yes I misspoke several times thinking the new server was not reading the netcode.

All is the same and autoexec.cfg changes still are read.

Sorry guys

But I am glad to not have to input my netcode changes each time manually as I have been!

 

[He@d$hoT]

edit: never mind you just made another post before I submitted this one

Autoexec is loaded after config.cfg
you can also simply bind a key to exec it
you do not need to enter anything in the console each game
I have never heard of anyone having to do that
If config.cfg is being overwritten and executing after autoexec, you can also make config.cfg read only.
Although, don't go changing game settings because they will change right back next time.

 

[crom]

edit: never mind you just made another post before I submitted this one

Autoexec is loaded after config.cfg
you can also simply bind a key to exec it
you do not need to enter anything in the console each game
I have never heard of anyone having to do that
If config.cfg is being overwritten and executing after autoexec, you can also make config.cfg read only.
Although, don't go changing game settings because they will change right back next time.

Your previous post is what got me thinking actually so thanks for the light bulb. No more cursing each time I log in

 

[He@d$hoT]

Now for a good question, is the lerp reading in netgraph accurate? No matter what I do, my lerp is always reading as 100ms in net_graph3. I am convinced the servers automatically adjust it, regardless of our config files. I have no real issues with the hitreg though.

 

[crom]

Now for a good question, is the lerp reading in netgraph accurate? No matter what I do, my lerp is always reading as 100ms in net_graph3. I am convinced the servers automatically adjust it, regardless of our config files. I have no real issues with the hitreg though.

If you set cl_interp 0 it will go to 20. Typically when as I was telling Ruffio I set it to 0.021 as it just seems to work for me whatever the reason.

log in to an empty server and before you join a side type in console:

cl_interp 0

Your lerp should read 20

As long as all other netcode is not changed.

 

[He@d$hoT]

Mine is set to 0.033

However, no setting changes it.... it always reads 100ms in-game using net_graph 3 for me. setting it to 0 does not change it either. I tried on multiple servers, 100ms is all I can get it to read.

 

[SS-Shifty]

I actually do change it every time I start playing because I'm afraid of messing with the original config file.
I don't trust my coding skills here -___-