18 January 2016 - 00:35 CET
We now have new tools we can all use to objectively test hitreg. The game now has a console command called "hitreg" that outputs data about how and if you hit your target.
How to use the hitreg command:
The hitreg command can not be used on any server. It must first be enabled by a server admin. This means you will need to run your own server, or ask your favorite server admin to enable it for you.
The server admin can enable hitreg to be turned on with the following console command. "sv_tests 1"
Once a server admin has done that, a client can then type "hitreg" in console to begin recording data to the log.
"sv_tests 1" and "hitreg" will need to be re-enabled after each map change.
The client will see the following in his console confirming that hitreg has been turned on.
Server operators and admins, sv_tests should not be used for fun. It is similar to cheats, but instead of allowing anything it only allows a few debug tools to be turned on. Think before you turn on tests. The hitreg command does not give anyone an advantage, but it does dramatically increase the clients bandwidth usage. I would only allow a couple individual players to test hitreg at a time so that you do not stress the server.
So now you have used the hitreg enabled. Look for "srv.hit" and "cli.hit" in your console or log to see if you actually had a hitreg issue.
While viewing the log I typically press Control -> F and search for "srv.hit" to find the hitreg issues. Your log is found in your "C:\Users\YOURUSERNAME\AppData\Roaming\Natural Selection 2" folder. You may see a lot of "diffs found" but those are unimportant. There is not a hitreg issue unless there is a discrepancy between srv.hit" and "cli.hit" such that one is true and the other is false. I have two examples shown below.
This is a no reg on a fade. The server (srv.hit) says it was a miss, and my client (cli.hit) says it was a hit.
This is a false positive on a fade. The server (srv.hit) says it was a hit, and my client (cli.hit) says it was a miss.
How to provide data to the developers about hitreg:
The developers are looking for a video similar to this. (demonstrates one of the few remaining hitreg issues)(Video by Ironhorse)
Or similar to this video I made showing the fade hitreg issues I have used in my examples above.
As was done in the examples, you need to make a video with the following traits:
[list]
[*] The video shows you getting a no reg or false positive.
[*] Shortly after you get the no reg or false positive, the console in shown in the video. You can open up the console with the tilda "~" key which is right above the tab key.
[*] Video must be high quality. The developers need to be able to see what was going on.
[*] Video ideally would be 60 fps. This makes it easier for the developers to see what was happening.
[*] Uploaded to a place the developers can access the video. Youtube works great because it allows 60fps videos.
[/list]
If you wanted to above and beyond in gathering data for hitreg, it would be nice if you provided the log along with the video. The developers do not need the whole log, but just posting a portion of it like the example I gave at the beginning of this post would be nice. If you post it here, please put a spoiler around it. You could also upload your log to pastebin.com and link it here. If you do not want to post your log publicly I would private message @Ironhorse on the UWE forums.
It did not take me long at all to record and upload that video. Not counting time playing ns2, it probably takes me about 5 minutes to set up, edit, upload, and post a video like above.
If you do not know how to record your gameplay, don't worry it is easy. There is a lot of free software available to use. I would start by reading this reddit guide to pc gamplay recording.
When all of that is done, post your video in this thread at the UWE forums
How to use the hitreg command:
The hitreg command can not be used on any server. It must first be enabled by a server admin. This means you will need to run your own server, or ask your favorite server admin to enable it for you.
The server admin can enable hitreg to be turned on with the following console command. "sv_tests 1"
Once a server admin has done that, a client can then type "hitreg" in console to begin recording data to the log.
"sv_tests 1" and "hitreg" will need to be re-enabled after each map change.
The client will see the following in his console confirming that hitreg has been turned on.
Client : 412.793579 : hitreg checking on, prec 2
Server operators and admins, sv_tests should not be used for fun. It is similar to cheats, but instead of allowing anything it only allows a few debug tools to be turned on. Think before you turn on tests. The hitreg command does not give anyone an advantage, but it does dramatically increase the clients bandwidth usage. I would only allow a couple individual players to test hitreg at a time so that you do not stress the server.
So now you have used the hitreg enabled. Look for "srv.hit" and "cli.hit" in your console or log to see if you actually had a hitreg issue.
While viewing the log I typically press Control -> F and search for "srv.hit" to find the hitreg issues. Your log is found in your "C:\Users\YOURUSERNAME\AppData\Roaming\Natural Selection 2" folder. You may see a lot of "diffs found" but those are unimportant. There is not a hitreg issue unless there is a discrepancy between srv.hit" and "cli.hit" such that one is true and the other is false. I have two examples shown below.
This is a no reg on a fade. The server (srv.hit) says it was a miss, and my client (cli.hit) says it was a hit.
Client : 1068.375366 : 32092-1: Diff found for attack on Fade-1899 (physTime 1068.275):
srv.hit: false
cli.hit: true
This is a false positive on a fade. The server (srv.hit) says it was a hit, and my client (cli.hit) says it was a miss.
Client : 1068.482910 : 32095-1: Diff found for attack on Fade-1899 (physTime 1068.383):
srv.hit: true
cli.hit: false
How to provide data to the developers about hitreg:
The developers are looking for a video similar to this. (demonstrates one of the few remaining hitreg issues)(Video by Ironhorse)
Or similar to this video I made showing the fade hitreg issues I have used in my examples above.
As was done in the examples, you need to make a video with the following traits:
[list]
[*] The video shows you getting a no reg or false positive.
[*] Shortly after you get the no reg or false positive, the console in shown in the video. You can open up the console with the tilda "~" key which is right above the tab key.
[*] Video must be high quality. The developers need to be able to see what was going on.
[*] Video ideally would be 60 fps. This makes it easier for the developers to see what was happening.
[*] Uploaded to a place the developers can access the video. Youtube works great because it allows 60fps videos.
[/list]
If you wanted to above and beyond in gathering data for hitreg, it would be nice if you provided the log along with the video. The developers do not need the whole log, but just posting a portion of it like the example I gave at the beginning of this post would be nice. If you post it here, please put a spoiler around it. You could also upload your log to pastebin.com and link it here. If you do not want to post your log publicly I would private message @Ironhorse on the UWE forums.
It did not take me long at all to record and upload that video. Not counting time playing ns2, it probably takes me about 5 minutes to set up, edit, upload, and post a video like above.
If you do not know how to record your gameplay, don't worry it is easy. There is a lot of free software available to use. I would start by reading this reddit guide to pc gamplay recording.
When all of that is done, post your video in this thread at the UWE forums
