This is absolutely something we’ve been looking at, especially in the past year. I can not provide the exact timeline for the rework and/or any change, but it’s one of the work-in-progress projects. We do want to make it much more useful for you guys, and for Team Sec as well.
Hey guys! Quick heads up - on 19 July at 15:00 UTC, we‘ll be hosting a Q&A with members of Team Security on the discord server, where CCP Aisling and CCP Stinger will answer your questions about the fight against botting and RMT in EVE. Submit your questions in the #ask-ccp channel. Deadline for question submission is 18 July. Only questions relevant to the topic will be considered. We will also not be discussing individual tickets, if you have an outstanding one we encourage you to contact the Player Experience Team through our official support channels.
We have released an update from Team Security on everything that has been going on in 2021!
Please use this thread to discuss the development blog and ask questions to the team.
Greetings, Capsuleers!
It's been a while since our last update on the efforts of the Security team in their battle against Real Money Trading (RMT), botting, account hacking, and fraud – so without further ado, let's jump right into this comprehensive overview and update on EVE’s security!
First, we’d like to cover who exactly is on the team, and what each member does. In the past year there have been both leavers and joiners, with the current team comprising:
Hi
We have managed to somewhat replicate this now. It is caused by a combination of GPU, Monitor features (VRR / Freesync), and control panel settings in AMD Adrenaline.
We had some success in restoring it to the way it previously worked by changing Freesync / VRR-related settings in the AMD control panel. I’d recommend taking a look at the settings and try toggling them off and see if that helps.
We’ll be visiting this issue in the future, but there is something funky (technical term) going on here. It only impacts very specific setups, so we’ll be speaking with our partners to try and narrow down the exact reason.
Hi
Thank you for the excellent bug report. With your help, we were able to reproduce this in our testlab.
Unfortunately, this is a driver problem. We specifically tested for this issue on a GPU matching yours (as listed in DXDiag) and saw the issue. Then we tested on a 1060 and saw the same problem. Updating the driver solved the issue.
The problem is that the GPU you have is quite old (almost 12 years), so NVIDIA dropped support for it in their drivers around 4 years ago. I believe you have the latest driver installed for your GPU. We are extremely limited in what we can do here, as the problem is being caused at a very low level between the driver and hardware.
We have an internal defect on this to see if we can make some changes on our side to get around it, but I can’t promise this is even an option.
devtrackers.gg
