CCP_Caffeine

Thanks for the reports everyone. We’re going to try getting an internal reproduction on this with the latest Windows updates.
There is something unusual happening here, as we’ve not changed the code behind the mouse cursor tracking for a long time.

If you are experiencing the problem, can you file a bug report when it happens from within the client by pressing F12. It would be very useful if you would paste this thread URL in and mention me.

Thank you

Hey Multimorti Oramara

We don’t have an exact release date, but the work has been going really well internally. We’re in the final development stages, which is mostly lots of tweaking and defect fixes.

Keep an eye on the news items for a release date.

The fix is taking a bit longer than we would like. We’re aiming for a deployment early next week to resolve this.

Thanks. We’ve just got a repo on this and are working on a fix.

Hi

If all goes to plan, we’ll be deploying a change which should fix this problem tomorrow. It will alter the way the window for the client interfaces with the OS.

To explain how the window rendering works:

In full screen mode, there will be a black bar at the top of the screen in line with the notch. As a result, the notch is “ignored”, at the cost of losing a few pixels at the top of the screen. You can still move the mouse cursor into the black bar area.

In August there was a change to allow all of the pixels to be used when ‘fixed window’ was selected. This means that if you have a notch, the client will render around it giving you the most screen estate possible.
The downside of this is that the client still considers this a ‘real’ area, meaning you can move things into the area where the notch exists and you won’t be able to see it. We believe the impact of this is low though, as there are almost no such windows in EVE that could be accidentall...

Hi both
If you’ve not filed an EVE Bug report from the client, please do. This will help us in trying to find the root cause.
Many thanks

Hi
Do you filed a EBR (EVE Bug Report)? We are not aware of any issues with FSR currently.
If you could file a report for us and include screenshots and a loglite, we can see if anything is reported by your system.

There were some further changes made to AA today, which means many of the ‘overlays’ like the tactical overlay are now not part of the AA pass. It should be significantly sharper and have no blur after the patch released today.

Could you let me know if this improves things for you?

Hi
I asked the GMs to reply to you and look into it further. We’re not aware of any startup crashing issues on macOS. We’ve tested on both Intel and Apple Silicon based systems and not been able to find any problems.

Hi
We’re not aware of crashing issues with the Mac client since the fix we deployed yesterday.

If you are experiencing crashing, please file a bug report so we can investigate. Feel free to tag me and @CCP_Habakuk in the ticket.

It is worth making sure you have “download everything” turned on in the launcher, as this has sometimes caused problems when the connection has been unstable and the client is fetching assets.

Hi there

I’ve heard from AVG today, and they have confirmed they have whitelisted the file. They say it make take up to 24h to take full effect. Please keep your product up to date, and hopefully it should just start working when you get the updates from AVG, if it is not already.

Many thanks!

Thank you for the reply.

I’ve checked the file on Virus Total, which tests the file against many different AV vendors. It is showing as clean: VirusTotal

I am reaching out to AVG about this issue to see if they can help on their side. This is part of their “Behavior Shield” defense, which tries to figure out what things a virus may do, and preemptively stop them. A good indication is that it is a “Generic” and not a specific match to a known virus.

Unfortunately it is more common than we would like that some anti-virus packages get tripped up by our frequent patching, along with capturing input (so we know what keys you have pressed to play the game ...

Hi Demortis

If you can provide a screenshot / file information of the quarantine, we will look into this. However in past cases, it has been the anti-virus vendor detecting a false positive, via a heuristic scanning approach.

We of course take these cases extremely seriously and we’ll look into it as soon as we have further information on the specific file causing an issue.

Best regards

Hi there

We are aware of the Vsync / sync issues in general. I made a post about it here: Version 20.06 - Known Issues - #134 by CCP_Caffeine
This is something we’ll be taking a closer look at with our partners, as it’s a combination of software and hardware causing this problem. You may have some success restoring it to how it previously worked by toggling vsync / VRR / Freesync settings until we can get to the bottom of the problem.

Issue 2: However dx12 causes a hard cra...

Hi all

In the last release we moved to DX12. We are aware that a small number of people had some stability problems within the first few days. We’ve since patched all known crashing issues and our metrics for this are looking good (Check out the devblog on how we know: Upgrading Crash Reporting Systems | EVE Online)

I’m keen to hear from anyone that is still experiencing client stability problems that are resolved by moving to DX11, as we’re unlikely to be aware of them at this point. As DX12 will be important to future updates, we want to ensure any outstanding issues are resolved.

We’re aware of a small number of (non crashing) DX12 is...

Hi
Could you file a bug report from within the client, so we can get more information (like what OS version you’re running etc.). Also let us know what headphones you’re using.

Many of us at CCP play on a Mac with Bluetooth headphones, so we’re not aware of any specific Bluetooth issues right now.

Many thanks!

Thanks for letting me know!
It’s so strange. We’ve been testing for this across multiple machines, with no luck of replicating it so far. Yet we see it in player videos.
If this is causing you any gameplay issues, you can revert to DX11 in the launcher by unticking the DX12 box.

Regarding the bug report: Could you double check that number? I’ve checked the system, but nothing is showing for that ticket. It would typically be 6 numbers and not 7 in length.

Unfortunately we are not able to reply to every bug report, but if you see ‘attached’ it means...

edit - found your bug report. Thanks!

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.