Eyetest plugin CSGO broken #18
Comments
|
Hi lunatixxx, Were you using the latest version of SMAC from this repository (which is 0.8.6.7) or were you using an older version of SMAC? Currently, I think this repository is the only one still active/free as others are either old repositories or a modded version that you have to pay for, so I believe this would be the best version to use at this time. The latest version is 0.8.6.7, so I would advising using that version of the plugin if you are not doing so. It was picked up where the official version left off some years ago and its been getting updates, albeit very slowly. Silence |
|
SourceMod 1.9 is the latest stable build. 1.10 is just an unstable developer version, not ready for public use. My guess is that SMAC is compiled with the latest 1.9, and probably will be edited to support 1.10 when it becomes stable. |
|
It was the last version of SMAC yes. |
|
If it was the last version of SMAC before original development team stopped working on it, then the eyetest module definitely had some issues with CS:GO and TF2, specifically due to alt-tabbing due to updates in client/server state when tabbing. In the latest version from this repository, that issue was fixed a few months ago, so the eyetest module should work, though you'll still need compatibility mode on. So if you haven't tried this version of SMAC already, give this version a try and see if it works better than the version you have. That being said, CS:GO has had a number of updates and, truth be told, I do not own servers or play CS:GO myself, so most of my testing is done on test server I set up with bots to test general functionality and gameplay to see if something breaks the plugins. It is entirely possible that an update between May 2019 and now could have broken the modules. If it is still broken, please let me know. |
|
Hello, I have the same problem with smac_eyetest on SM 1.10 & 128 tickrate. Here are some logs:
|
|
At a glance, it seems it might be related to tickrate, so I'll check it out. I would disable this plugin for now to keep it from banning users. |
|
any fix @Silenci0 ? |
|
Sorry I haven't responded back to this, but right now, I do not have a fix for it yet. I was testing this in a few other games to determine if this was a CS:GO only problem or if it might be something I can replicate in other games, but so far I was unable to replicate the issue, so it seems only related to CS:GO. I have yet to figure out if its an update or if perhaps having 128 tickrate is the issue that is causing problems in CS:GO (I bet it was an update, but I cannot be sure of that). I'll need to do more testing in CS:GO as I see, based on the logs you presented, that users were getting banned reusing and tampering with old movement commands, which are two separate checks, which might indicate other issues (or it could be the same issue, not sure yet). |
|
@xSL0W and @lunatixxx I have been testing with CS:GO on a test server I created using only the SMAC plugins and SM 1.10 and, so far, I have not ran into this issue with the eyetest module enabled and bans set to on. The server was setup for 128 tick and I attempted changing video/screen settings and using various weapons, particularly the awp since that seems to also be a common weapon that the plugin is banning for (at least according to xSL0W's logs). I have also attempted to use high mouse acceleration, alt-tabbing, changing the video from windowed, fullscreen, and fullscreen windowed with 4:3, 16:9, and 16:10 aspect ratios all while playing the game. So far, no logs or notices have come up and I have yet to be banned or notified of any violation of the eyetest plugin. Admittedly, I have never run a CS:GO server before and, because my server is a simple test server that I'm running locally with bare bones plugins, I'm not sure if my testing is sufficient enough to find this issue or if the problem is due to some other plugins or server settings that I might not have enabled. If it is possible, would either of you mind telling the following:
I realize I might be asking a lot, so if you do not wish to volunteer any of this information, I completely understand. But presently, I am uncertain as to what could be potentially causing this or if there are specific steps or plugins involved that might be triggering the eyetest module that is causing these bans, so if there is any further information you can provide, that would be great. Also, on the other side of things, the plugin has been updated to 0.8.7.1 and has been updated to use SM 1.10 and the new syntax, so perhaps that might be the issue? Versions prior to 0.8.7.0 were compiled on SM 1.9 and used old syntax, though I'm not sure if that makes a difference or not (both of you were using SM 1.10 with older versions, which is why I'm curious). If you choose to test this out, please set the ban cvar to 0 so that players do not get banned by the plugin. |
|
If anyone else is able to provide any further information about this issue (including steps on how to reproduce the problem), please list them here. I will keep this issue open for now. |
|
Hello, I own an AWP Only Server. SERVER.CFG rates
sm_cvar sv_parallel_packentities 0 Network / Throughputsm_cvar sv_parallel_sendsnapshot 1 CPU Tweakssm_cvar fps_max 0 Hit Registrationsm_cvar sv_client_predict 1 Ragdolls / Propssm_cvar g_ragdoll_important_maxcount 1 Experimental Async / MultiThreadingsm_cvar occlusion_test_async 1 My Plugins list:
|
|
@xSL0W thank you for posting that info, it is very appreciated! Also, I noticed from your plugin logs that both the eyetest and autotrigger modules are both reporting as version 0.8.6.0, which are much older versions of these modules. This might be part of the issue with eyetest banning people as version 0.8.6.4 and above actually fixed some issues with the eyetest module and any type of alt-tabbing or screen focus issues, so I think an update of the SMAC plugins might fix the problem for you. I'll double-check some of the plugins in your list (as well as the server settings) and see if they cause issues for the eyetest plugin, but please be sure to update the plugins to the latest version available and see if you still have issues afterwards. Also, be sure to disable the autoban feature for now while testing it as it will still log violations if it sees them. You can turn them back on once you are comfortable with the plugin not falsely banning people. |
|
I will check these days with the latest version |
|
Updated to latest version, same problem: L 12/03/2019 - 22:35:10: [smac_eyetest.smx | 0.8.7.1] Pancho Shansa (ID: STEAM_1:0:151809075 | IP: 188.254.205.89) was banned for tampering with an old movement command (tickcount). CmdNum: 2035 | [3180:3152:3181] |
|
I have been testing this with the server settings and some of the public plugins found in your previous posts and I am still unable to replicate the issue or cause myself to be banned by the plugin while using an awp. Retesting old issues (such as alt-tabbing from the game) also did not register any bans or error messages from the plugin. Unless there is something that is specifically causing the bans to be triggered, such as user settings or some set of commands/scripts that are being commonly used that can cause this problem, I'm not sure what else can be tested to verify that this is an illegitimate ban or not. If there is some info about how to reproduce this issue or if the issue commonly occurs during an event (such as a map change or respawning), please let me know. |
|
Hello, I dont know how to reproduce this bug, but I have an ideea. |
|
Please do not take this the wrong way, but I don't add people on Steam for things like this because it sets the precedent that people can simply add myself or other contributors to fix an issue instead of making creating an issue here and responding to that, thus losing valuable documentation/information that would otherwise be recorded for others to see. While some could argue that I could simply append steam conversations to issues, I'm not willing to do that personally and I doubt many others will be either. The only time there would be an exception is if an issue does have a cause, but we aren't willing to discuss it publicly, in which case, I'd make an exception, though I'd prefer DMs on Allied Modders (profile: https://forums.alliedmods.net/member.php?u=193590 ). Steam is simply not the place for this kind of thing, in my personal opinion. Putting the above aside, a debug version of the plugin doesn't sound like a bad idea, but I do not have one and making one that is meaningful would take some time, though it is a good idea and will most likely be implemented at some point in the future. However, the real issue here isn't that we don't know what is happening, as players are getting banned for using old commands based on tick count, the questions are "how are players triggering this detection?" and "is it a legitimate detection?" as it does not seem to be happening to every player, just a few of them based on the logs/responses already provided. If this were happening to every player on the server, yourself included, it would easily be a case of the plugin simply not working correctly, which would be far easier to test/debug as we could replicate the conditions and/or actions causing it. However, its only happening to some players and cannot be replicated as easily by either myself or you, so the problem is how are others triggering it when we are not? What are they doing differently than us? Are they running scripts or have settings from their game client (or even settings via server plugins) that are different from what we are using? I think the best way to figure that out is by asking the players who got banned what was happening at the time of the kick/ban and by working with them to figure out how to replicate the issue. If these players are people you (or your admins) have been playing with regularly on your server, and are on good terms with, it should be much easier to speak to them regarding this. |
|
@Silenci0 Given it's only a specific part of the module that's giving false positives, can you just disable the FYI: This bug only happens if the tickcount is >64. My 64-tick server is doing fine and has no false positives while my 128 tick server has false positives. The issue seems to be affecting those with lower-end computers, especially when they alt-tab. I suspect it's a continuation of this bug that hasn't been tested and fixed in CS:GO. |
Even with the compatibility mode activated it just detect everyone as a cheater on a 128 tick server. Don't know about other games, i knew there were some false positives in L4D2 but it was rare. Sourcemod 1.10 was used, what is the best version for SMAC by the way?
The text was updated successfully, but these errors were encountered: